Altium - the Altium Bridge

@@ -36,7 +36,7 @@ Altium is a licensed host app. The bridge never installs it silently; it detects 3. **`ok:true` is not enough — verify.** `show_*` and `state` return frames; look at them. `run_outjob` returns `files[]` actually written. 4. **One script at a time.** While the agent is resident, never run `altium_run_script`; it raises Altium's "Another script executing now" modal. Send work through `altium_eval` / `altium_run_command`. 5. **Never leave a modal.** Prefer commands that carry their parameters (`altium_run_command` with `params`) so no picker opens. After any mutating step, `altium_check_dialogs`.-6. **Reuse the running Altium.** Altium is single-instance; the agent survives across your calls (auto-stops after 30 min idle, auto-restarts on the next verb).+6. **Reuse the running Altium.** Altium is single-instance; the agent survives across your calls (auto-stops after 5 min idle from 0.2.9, auto-restarts on the next verb). 7. **Absolute Windows paths.** `C:/…` or `C:\\…`; no `%VAR%` expansion. Files from the container must be sent first (`send_files`). 8. **Surface `_hint` verbatim + branch on `errorCode`.** @@ -64,17 +64,32 @@ Altium is a licensed host app. The bridge never installs it silently; it detects | `altium_install_library` / `altium_compile_intlib` / `altium_extract_intlib` | Installed Libraries, .LibPkg → .IntLib, .IntLib → sources | `libraryPath` / `libpkgPath` / `intlibPath` | | `altium_build_footprint` / `altium_build_symbol_modes` | author a footprint from a `tools/kicad2altium.py` spec (via pads, roundrect, mech layers) / ONE symbol with N display modes | `libraryPath`, `spec` | | `altium_add_models` / `altium_symbol_mode` | N footprint models + params on a symbol / switch display mode + frame | `symbolName`, `models[]`, `params` / `mode` |-| `altium_test_board` / `altium_board_shape` / `altium_swap_footprint` | wired test board, rectangular board shape, footprint swap keeping nets | `footprintName`, `wMm`,`hMm`, `assigns` |+| `altium_add_symbol_art` / `altium_symbol_prims` (from 0.2.15) | draw the chip outline adom-symbol baked into the KiCad symbol onto a SchLib component (replaces earlier art unless `clear:false`) / read-only primitive counts, body rectangle, polyline bbox, models | `libraryPath`, `symbolName`, `kicadSym`, `clear`, `mode:"lines"\|"polyline"` / `models:true` |+| `altium_set_models` (from 0.2.15) | replace every footprint model on a symbol with ONE PCBLIB model (`set_params` footprint and `add_models` append) | `libraryPath`, `symbolName`, `footprint` |+| `altium_plate_vias` (from 0.2.20) | every drilled pad in a PcbLib that loaded on the Top Layer becomes a plated Multi-Layer pad (heatsink vias); `altium_save` afterwards | `libraryPath`, `footprintName` (optional filter) |+| `altium_place_on_sch` | one symbol or a `;` list on ONE new sheet as U1..Un; the sheet is sized from the measured parts (500 mil gaps, 600 mil margins, A4 minimum), designator above and part number below each body, title block filled | `libraryPath`, `symbolName`, `schPath`, `title`, `number`, `revision`, `drawnBy`, `description` |+| `altium_test_board` / `altium_board_shape` / `altium_swap_footprint` | wired test board (one footprint or a `;` list, parts U1..Un with each part's name on the Top Overlay under its footprint), rectangular board shape, footprint swap keeping nets | `footprintName`, `wMm`,`hMm`, `pcbPath`, `assigns`, `stubs` | | `altium_clone_symbol` / `altium_rename_symbol` / `altium_remove_symbol` / `altium_read_symbol` | library manipulation on a SchLib (clone carries every display mode) | `from`,`to` / `symbolName` | | `altium_copy_footprint` / `altium_rename_footprint` / `altium_remove_footprint` | the same for a PcbLib (copy carries pads, bodies, drawing) | `from`,`to` / `footprintName` | | `altium_pcb_report` / `altium_normalize_bodies` | ground truth (pads/bodies/nets/tracks with bboxes) / centre bodies on pads | `want:"board"`, `footprintName` | | `altium_save` | save the focused document (pre-clears a dangling transaction) | `filePath` |+| `altium_close_document` | close one open document through its handle; never saves | `path` |+| `altium_read_board` / `altium_board_summary` / `altium_rules_by_kind` / `altium_layers_in_use` | ONE agent round trip for the whole board (components, nets, layers, copper, rules, occupancy, outline) and three views shaped from it | `sections`, `limit`, `raw:true` for the unshaped payload |+| `altium_read_schematic` | components on the CURRENT sheet with their parameters | `sections`, `params:false`, `limit` |+| `altium_cross_check` | designators on the sheet but not the board and the reverse (`matched`, `onSheetNotOnBoard`, `onBoardNotOnSheet`, `sameProject`) | `board`, `sheet` (paths, optional; opened in turn) |+| `altium_review_board` | 14 design-review checks over one board read, schematic-side checks with `includeSchematic`; partial by design (`skipped`, `notImplemented`) | `board`, `sheet`, `includeSchematic`, `checks[]` |+| `altium_license_status` / `altium_ensure_licensed` / `altium_setup_trial` | licence state in words + page frame / launch, claim a seat or name the human step / the one next onboarding action (see `altium-licensing`) | — / `launchWaitSec`, `allowSignInReset`, `allowTrial` / — | | `altium_signin_status` / `altium_license` / `altium_connect_workspace` | account + licence + workspace state; drive the License Management page (`action: show\|refresh\|use_license\|start_trial`) | — |-| `altium_a365_configure` / `_status` / `_query` | Altium 365 GraphQL (needs a token from a workspace that has Admin → Developer; the Develop trial does not) | `workspace`, `token`, `query` |+| `altium_a365_configure` / `_status` / `_query` | Altium 365 GraphQL (needs a token from a workspace that has Admin → Developer; the Develop trial does not) | `workspace`, `token`, `query`, `variables` |+| `altium_a365_oauth_begin` / `_oauth_status` / `_oauth_cancel` / `_refresh` / `_logout` | OAuth (PKCE) sign-in with an Altium-issued public client ID; tokens stay in the bridge cache and never appear in a reply | `clientId`, `workspace`, `selectWorkspace`, `timeout` |+| `altium_a365_library_overview` / `_library_schema` / `_files_upload` | workspace library summary / library-related GraphQL queries and mutations / upload a file to the Files Service and get a temporary `fileId` (see `altium-a365`) | — / `timeout` / `filePath`, `maxBytes` |+| `altium_animate_view` / `altium_foreground` | camera and zoom choreography run in-bridge / raise Altium for a user who asked to watch (replies `visiblyOnTop`) | `preset`, `steps[]`, `lane`, `pauseMs` / `reason` (10+ chars, required) |+| `altium_dialog_log` | what the standing dialog reaper dismissed | `limit` (default 25) |+| `altium_install_receipt` | the last `install_library_bundle` receipt (proof frame included) after a call outlived ab's budget | — | | `altium_demo` | six-beat tour: symbol → footprint → 3D part → schematic → 2D → 3D board | `stage` | | `altium_describe` | the full machine-readable catalog | — | -Lifecycle: `altium_launch`, `altium_close`, `altium_agent_start` / `_stop` / `_status` / `_recover`, `altium_diagnostics`, `altium_progress`, `altium_uninstall`.+Lifecycle: `altium_launch`, `altium_close`, `altium_agent_start` / `_stop` / `_status` / `_recover`, `altium_diagnostics`, `altium_progress`, `altium_uninstall`. `altium_agent_status` is read-only: `alive`, `responsive`, `residentAnywhere`, `liveWorkspaces[]` (a loop resident in another workspace is a freeze-on-close hazard; `altium_close` stops every workspace's loop).  ## Quick examples 

@@ -273,7 +273,7 @@ def say_send(phrase):     d = res.get("data") if isinstance(res.get("data"), dict) else res     # VERIFY BY DELIVERY, never by the thread's name (issue #59: a correctly     # named tab that delivered nothing, and an unnamed tab that delivered --    # measured live on AdomLapper 2026-08-25, where a successful send came back+    # measured live 2026-08-25, where a successful send came back     # with "title": null).     #     # BUT delivered_to ALONE PRODUCES FALSE FAILURES. The API's own hint calls

@@ -15,6 +15,11 @@ for HOME_DIR in "$HOME/.claude/skills" "$HOME/.codex/skills"; do   install_skill "$HOME_DIR/altium-libraries"     "$HERE/skills/altium-libraries/SKILL.md"   install_skill "$HOME_DIR/altium-boards"        "$HERE/skills/altium-boards/SKILL.md"   install_skill "$HOME_DIR/altium-outputs"       "$HERE/skills/altium-outputs/SKILL.md"+  install_skill "$HOME_DIR/altium-instances"      "$HERE/skills/altium-instances/SKILL.md"+  install_skill "$HOME_DIR/altium-licensing"      "$HERE/skills/altium-licensing/SKILL.md"+  install_skill "$HOME_DIR/altium-uia"            "$HERE/skills/altium-uia/SKILL.md"+  install_skill "$HOME_DIR/altium-wiki-import"    "$HERE/skills/altium-wiki-import/SKILL.md"+  install_skill "$HOME_DIR/altium-a365"           "$HERE/skills/altium-a365/SKILL.md" done  # Dashboard: the pkg ships it, the dock runs `altium-dashboard serve --print-url`.

@@ -4,7 +4,7 @@   "type": "app",   "title": "Altium - the Altium Bridge",   "brief": "Adom Bridge for Altium Designer: a resident DelphiScript agent gives the AI eval, the 1,100-command process launcher, all 8 EDA surfaces with screenshots, compile/ERC, DRC, OutJob outputs, native SchLib/PcbLib authoring with STEP 3D bodies, and dialog handling by PID.",-  "version": "0.2.20",+  "version": "0.2.21",   "hero": {     "type": "image",     "path": "screenshots/hero.png"@@ -126,6 +126,7 @@     "dockbar.json",     "install.sh",     "package.json",+    "skills/altium-a365/SKILL.md",     "skills/altium-boards/SKILL.md",     "skills/altium-bridge-plan/SKILL.md",     "skills/altium-install/SKILL.md",

@@ -21,6 +21,35 @@ at the centre (per-primitive copy), nets created and assigned by pad designator named "49" joins the EP net), one stub track per assign. Size the FR4 to enclose silk + courtyard + 3 mm margin so the pin-1 dot is visible on the 3D board. +`footprintName` takes a `;` list (from 0.2.13): the parts are spread evenly along X inside+the wMm x hMm outline on one new board, and `assigns` / `stubs` apply to the LAST part+placed. From 0.2.18 / 0.2.19 the parts are designated U1..Un (the designator text stays+hidden) with the footprint name as Comment, and each part's name is written on the Top+Overlay under its footprint: 35 mil stroke text, centred on the part using the text's+measured bounding rectangle, its top 2.5 mm below the part centre, clear of a 3 mm part's+courtyard. Size `hMm` so that label fits on the board. Every call creates a NEW PcbDoc;+without `pcbPath` it stays unsaved.++## Schematic sheets: `altium_place_on_sch`++`altium_place_on_sch {libraryPath, symbolName, schPath, title, number, revision, drawnBy,+description}` places one symbol, or a `;` list, on ONE new sheet as U1..Un with the part+number as Comment. From 0.2.16 / 0.2.17 the sheet is sized FROM the parts:+- pass 1 measures every symbol's bounding box, pins included, plus 250 mil a side for the+  pin-number text;+- the sheet is a custom size: the row of parts with 500 mil between them and 600 mil+  margins, never smaller than A4 landscape (11500 x 7600 mil); slack is spread evenly over+  the gaps and margins;+- the designator sits centred above each body and the Comment centred below it, whatever+  the library part did with them;+- `title` / `number` / `revision` / `drawnBy` fill the title block, `description` becomes a+  text frame inside the drawing frame along the top, and `_hints` names any of them left+  empty.+The sheet size is not read back from `SheetSizeX/Y`: on ADDevelop those report the 9500 x+7500 default after a custom size is set. Every call creates a NEW SchDoc (no append yet);+after a re-run `altium_close_document {path}` the stale sheet before capturing with+`altium_show_schematic {filePath}`.+ ## Board shape: only the editor process works  `IPCB_BoardOutline.PointCount/Segments/Rebuild` is a silent no-op and `.Clear` HALTS the@@ -60,6 +89,36 @@ their nets. Trust the report, not a return code. - **Frames under a locked Windows session are BLACK** (DirectX): check   `desktop_get_foreground` ≠ 0 before trusting a board frame; GDI editors still capture. +## Whole-board read, cross-check and review++- `altium_read_board {sections?, limit?, raw?}`: ONE agent round trip for components, nets,+  layers, copper, rules, occupancy and outline (`sections` is a csv of those, default all;+  `limit` default 2000). Returns `summary`, `designators`, `nets`, `layers`, `copperLayers`,+  `rules`. `raw:true` returns the unshaped agent payload (what the test fixtures record).+- `altium_board_summary`, `altium_rules_by_kind`, `altium_layers_in_use` are views shaped in+  the bridge from the same read. `layers_in_use` gives `copperLayersInUse` (copper layers+  carrying copper, densest first; a floor, not the stack, since an empty plane is invisible)+  and `layersWithPrimitives` (silkscreen and mechanical counted too).+- `altium_read_schematic {sections?, params?, limit?}`: components of the CURRENT sheet+  (`designators`, `components`, `count`); `params:false` skips parameters; `limit` default+  500. A hierarchical parent holds sheet symbols, not parts.+- `altium_cross_check {board?, sheet?}`: opens each path in turn (Altium holds one current+  document), then reports `matched`, `onSheetNotOnBoard`, `onBoardNotOnSheet`,+  `schematicComponents`, `boardComponents`, `sameProject`. The schematic side is ONE sheet;+  on a hierarchical design run it per leaf sheet. A `_warning` appears when sheet and board+  sit in different folders.+- `altium_review_board {board?, sheet?, includeSchematic?, checks?}`: 14 checks over one+  board read: `placeholder_values`, `single_pin_nets`, `unused_mechanical_layers`,+  `off_grid_components`, `duplicate_designators`, `components_outside_board_outline`,+  `components_near_board_edge`, `disabled_design_rules`, `missing_critical_rules`,+  `duplicate_rule_priority`, `components_without_footprint`, and the schematic-side+  `vendor_part_numbers`, `missing_datasheets`, `schematic_placeholder_values` (these need+  `includeSchematic:true` or `sheet`). `checks` filters by name. Reply: `findings[]`+  (`check`, `severity`, `message`), `counts`, `checksRun`, `availableChecks`, `skipped`,+  `notImplemented`, `unknownChecks`. A clean result means the checks that RAN found nothing.++All of these need a licensed Altium and read the current document unless a path is given.+ ## Reading the board as data (0.1.11)  `list_designators`, `component_data {designator?}`, `component_pins {designator}`, `list_nets`,

@@ -16,8 +16,8 @@ description: >- ---  Parent skill: **adom-bridge-sdk-new-app** (the method) and **adom-bridge-sdk** (the contract).-Written 2026-08-29 from live probes of Altium Designer 26.9.1 on John's box (`galliaApril`-container → `AdomLapper` desktop) plus the vendor docs and the community MCP bridges.+Written 2026-08-29 from live probes of Altium Designer 26.9.1 on a Windows test machine+(driven from an Adom container) plus the vendor docs and the community MCP bridges.  # altium-bridge — plan of record @@ -32,7 +32,7 @@ container → `AdomLapper` desktop) plus the vendor docs and the community MCP b | Listening ports | **none** while idle. No application COM automation server registered — only document ProgIDs (`AltiumLibrary`, `AltiumDraftsmanDocument`, …). | | UIA | The VCL/DevExpress shell **IS exposed**: 45 nodes on the licence screen — `MainMenu` MenuItems (File/View/Project/Window/Help/Preferences…), `TGUIDocBarButton`s, `TdxTabSheet` panes, all with `automationId`s and `invokable:true`. The **Home / License Management page content is a WebView2** (`ProgramData\...\WebView2Cache` exists) — its *Start Free Trial / Get License / Sign Out* buttons are **not** in the UIA tree. | | State dirs | `%APPDATA%\Altium\Altium Designer {ED62C102-…}\` (prefs), `%APPDATA%\Altium\AD26\`, `C:\ProgramData\Altium\Altium Designer {ED62C102-…}\Extensions\` (Altimade, Draftsman, IPC Footprint Generator, EXPORT3D, IPC2581, SchLibGenerationTool, …), `HKCU\Software\Altium\Altium Designer {ED62C102-…}`. |-| Auth state | Signed in as *John John* (Altium account), **no license**; a free *Altium Designer Viewer* seat is offered and a **15-day trial** button exists. Vendor docs: **Viewer mode prohibits scripting** → licence is a hard prerequisite for every in-app lane. |+| Auth state | Signed in to an Altium account, **no license**; a free *Altium Designer Viewer* seat is offered and a **15-day trial** button exists. Vendor docs: **Viewer mode prohibits scripting** → licence is a hard prerequisite for every in-app lane. |  ## 1. The surfaces, ranked into lanes @@ -138,7 +138,7 @@ Costs a licensed AD + a build toolchain; do it only after L2 proves insufficient ## 2. Authentication & licensing — the gates, in order  1. **Altium account sign-in** — system browser OAuth (email / Google / SSO). Drive with-   `nbrowser`/pup from the bridge; the user's Google session on this box is warm. Human step: password/2FA only.+   `nbrowser`/pup from the bridge; the user's browser is usually already signed in to their identity provider. Human step: password/2FA only. 2. **Licence** — On-Demand / Standalone / **Trial (15 days)** / **Viewer (no scripting)**. The    trial button lives in the WebView2 licence page → CDP or image click, one toast to the user    because it is a contractual click. `altium_readiness` must report `licensed:false` with the@@ -214,11 +214,11 @@ heartbeat and recover. Keep `handlers/dialog_classify.py` with title → categor    `altium-libraries`, `altium-a365`, `altium-signin` sub-skills), 30–40 discovery triggers, hero,    `make release`, audit checklist. Then (optional) Phase 5: C# SDK extension. -## 6b. Phase 0 RESULTS (measured 2026-08-29, AD 26.9.1 Trial, AdomLapper) — the facts the code is built on+## 6b. Phase 0 RESULTS (measured 2026-08-29, AD 26.9.1 Trial) — the facts the code is built on  | Experiment | Result | |---|---|-| Trial licence | `Start Free Trial` (WebView2, image click) → Edge opens `altium.com/365-intro/activate-add-eval` → workspace form (name, region, terms, **Activate**) → workspace `Adom` provisioned at `john-john-3.365.altium.com` in ~60 s → back in AD: **Refresh**, then **Use License** on "Altium Designer Develop · On-Demand · Trial · 30 days". Title flips to `… - Trial`. |+| Trial licence | `Start Free Trial` (WebView2, image click) → Edge opens `altium.com/365-intro/activate-add-eval` → workspace form (name, region, terms, **Activate**) → a workspace is provisioned at `<name>.365.altium.com` in ~60 s → back in AD: **Refresh**, then **Use License** on "Altium Designer Develop · On-Demand · Trial · 30 days". Title flips to `… - Trial`. | | `-R` forwarding | A second `X2.EXE -R<Server>:<Cmd>(…)` forwards to the running instance and exits in ~2–8 s. **If the instance is busy (any modal, or a script running) the helper hangs and shows its own "There is another instance … busy" Information dialog** — kill it. | | `RunScriptText` | Works from the shell: `-RScriptingSystem:RunScriptText(Text="Begin RunApplication('…'); End;")`. **Statements only** — a `Var` block is "Unknown identifier: Var". | | `RunScript` | `-RScriptingSystem:RunScript(ProjectName="…\X.PrjScr"\|ProcName="Main")` works with a plain `\|` when the arg is passed VERBATIM (PowerShell `Start-Process`, or Python `Popen("<one string>")`). `Popen([exe, arg])` re-quotes (the path has a space) and the helper never forwards. `^\|` is only for cmd.exe. |

@@ -47,6 +47,14 @@ If you upgrade a bridge while a loop is resident, the OLD loop keeps heartbeatin path. A script lane refuses when ANY workspace has a live heartbeat — that is deliberate; stop the old loop (its workspace path is named in the refusal) rather than forcing past it. +`altium_agent_status` shows this from the outside: `alive` and `responsive` for the selected+instance's loop, plus `residentAnywhere` and `liveWorkspaces[]` (`workspace`,+`heartbeatAgeSec`) across every workspace. `alive:false` with `residentAnywhere:true` means a+loop is resident in a workspace the selection does not point at, which is a freeze-on-close+hazard until it is torn down; `altium_close` stops every workspace's loop. `alive:true` with+`responsive:false` means the loop is inside a long Altium process: wait, do not start a+second agent.+ ## Where single-instance assumptions hid  All three were live bugs, all found within an hour of running two Altiums:

@@ -31,6 +31,38 @@ data only — switch views with the process `Sch:ToggleComponentDisplayMode` **Ralph rule: frame-check EVERY mode, not a sample.** The first LAN7800 shipped with three defect classes visible only in the modes nobody looked at. +## Chip outline on the symbol (from 0.2.15)++adom-symbol bakes the chip-thumbnailer outline into every KiCad IC symbol as polylines.+`altium_add_symbol_art {libraryPath, symbolName, kicadSym}` carries that artwork onto the+SchLib component: the bridge reads `kicadSym` (a Windows path on the Altium box, stage it with+`send_files`), takes the symbol's body rectangle and every polyline, and the agent maps the+KiCad body rectangle onto the component's own rectangle, so the outline lands between the+pin-name columns as it does in KiCad and Fusion. Drawn thin (`eSmall`) in grey.+- `clear` (default true) removes the component's existing lines and polylines first, so a+  re-run replaces the art instead of stacking it. Only the pins and the body rectangle+  survive, hand-drawn lines included. `clear:false` stacks.+- `mode`: `lines` (default) draws each polyline as eLine segments, the primitive+  `build_symbol_modes` draws with. `polyline` draws ISch_Polyline objects; measured+  2026-09-19, those rendered on VL53L5CX and stayed invisible on VL53L8CX with identical+  geometry, which is why `lines` is the default.+- Fails with a clear error when the symbol has no body rectangle or no polylines (bake the+  outline with adom-symbol first). Reply: `polylines`, `points`, `cleared`, `mode`,+  `bodyRectMil`. `altium_save` the SchLib afterwards, then `altium_show_symbol` to look.+- It draws the outline only. Group captions are written by adom-lbr into the SchLib it+  generates, not by this verb.++`altium_symbol_prims {libraryPath, symbolName, models?}` is the read-only check: `pins`,+`rectangles`, `lines`, `polylines`, `bodyRectMil`, `polyBboxMil` and, with `models:true`,+the footprint models. The model walk is off by default because it halted the engine on+ADDevelop. After `add_symbol_art` in `lines` mode, expect `lines` to have grown and the art+to sit inside `bodyRectMil`.++`altium_set_models {libraryPath, symbolName, footprint}` (from 0.2.15) replaces every model+on the component with ONE PCBLIB model. `set_params` footprint and `add_models` both append,+which is how a symbol ends up with two; this removes all existing models, 3D-only ones+included. Save afterwards.+ ## Footprints: the spec lane  `altium_build_footprint {libraryPath, spec}` consumes a `tools/kicad2altium.py` spec:@@ -43,6 +75,19 @@ defect classes visible only in the modes nobody looked at. - Pads must carry a Layer or they are SILENTLY DROPPED (measured); `Bottom*/Mid*` pad size   properties do not exist in this engine (halt). +## Heatsink vias from an imported library: `altium_plate_vias` (from 0.2.20)++adom-lbr writes heatsink vias as pads with a hole inside the thermal pad. Altium loaded those+pads on the Top Layer: the holes came, the layer did not, so they were not through-holes.+`altium_plate_vias {libraryPath, footprintName?}` walks every footprint in the PcbLib (or+only `footprintName`) and sets each drilled pad that is not already on Multi-Layer to+`eMultiLayer` with `Plated := True`. Reply: `holes` (drilled pads seen), `plated` (pads+changed), `fixed` (`Footprint:Pad;...`). It edits the open library in place, so+`altium_save` the PcbLib afterwards; `altium_footprint_primitives` on a placed part should+then report layerId 74 for the vias. Pads already on Multi-Layer are skipped, so running it+twice is harmless. adom-lbr 2.46.1 and later write the pads as plated Multi-Layer in the+file itself; the verb is for libraries generated before that.+ ## 3D bodies: the canvas rule  The stored lib component is NOT the editing surface. A body added straight to the component

@@ -19,7 +19,7 @@ Parent skill: [altium-bridge](../altium-bridge/SKILL.md). ## The rule that explains almost everything  **One On-Demand seat serves EVERY Altium app on the machine.** Altium Designer and Altium Designer-Develop draw from the *same* seat — on John's box the trial licence is literally named+Develop draw from the *same* seat — on the test machine the trial licence is literally named `Altium Designer Develop` (On-Demand, Single Site, 1 seat) and both apps use it. So:  * Two Altiums can RUN at once. Only ONE can be LICENSED at once.@@ -47,6 +47,22 @@ whole fix, and nothing else worked. `altium_close {force:true}` now refuses unless you also pass `acceptSeatLoss:true`, precisely so this cannot be reached for casually. +## The three status and recovery verbs++- `altium_license_status`: read-only. `running`, `licensed`, `licenceState` (from the window+  title), `seatStuck`, a plain-words `summary`, and `shot` of the License Management page.+  Trial details (days left, seat n/n, licence code) exist only on the page, so read the frame.+- `altium_ensure_licensed {launchWaitSec?, allowSignInReset?, allowTrial?}`: one call to get+  the user usable. Launches Altium if it is not running (waits up to `launchWaitSec`, default+  240), returns at once when already licensed, otherwise tries `use_license`. With no seat+  free it returns `no_seat_available`; with `allowSignInReset:true` it signs out instead and+  returns `signed_out_for_reset` (`needsHuman: "browser sign-in"`); with `allowTrial:true` it+  opens the trial flow and returns `trial_needs_browser`. Every reply carries `steps[]`.+- `altium_setup_trial`: onboarding from nothing to a working trial. Returns ONE next action+  per call with a `stage` (`install`, `launch`, `signin`, `done`) and names human steps in+  `needsHuman` (the installer's EULA click, the browser sign-in) rather than faking them.+  Signed in but unlicensed, it hands over to `ensure_licensed` with `allowTrial`.+ ## Swapping the seat between Designer and Develop  ```bash

@@ -80,6 +80,18 @@ python3 tools/kicad2altium.py part.kicad_mod fp.spec "<Footprint>" "<desc>"   # altium_import_part '{"schLib":"...","pcbLib":"...","footprintSpec":"C:/.../fp.spec","step":"C:/.../part.step","params":{...},"description":"..."}' ``` +After the library exists (from 0.2.15 / 0.2.20), two finishing steps for parts that came+through adom-symbol / adom-lbr:+```bash+# chip outline from the KiCad symbol onto the SchLib component, then check it+altium_add_symbol_art '{"libraryPath":"<lib>.SchLib","symbolName":"VL53L5CX","kicadSym":"C:/lib/VL53L5CX.kicad_sym"}'+altium_symbol_prims   '{"libraryPath":"<lib>.SchLib","symbolName":"VL53L5CX"}'+# heatsink vias that loaded on the Top Layer -> plated Multi-Layer pads (libraries from adom-lbr before 2.46.1)+altium_plate_vias     '{"libraryPath":"<lib>.PcbLib"}'+altium_save           '{"filePath":"<lib>.PcbLib"}'+```+`add_symbol_art` replaces earlier art by default (`clear:true`); details in `altium-libraries`.+ ## Path C — APPEND into an existing library  ```bash

@@ -35,6 +35,13 @@ do those clicks"*. He was right — the licence lane had been clicking hardcoded | **Panels button** (bottom-right) | `GUIDocForm.TPanelsHolderXPButton`, name `Panels` | Invokable. | | Canvas / PCB + schematic editing area | NOT exposed | Custom-drawn. Geometry work goes through the resident agent's scripting API, never through input. | +## What the reaper did: `altium_dialog_log`++`altium_dialog_log {limit?}` (default 25) returns `reaped[]`, the dialogs the standing reaper+dismissed, including close-watchdog firings. Anything that reached the user and is NOT in+the list is either a save prompt (never auto-answered, by design) or a dialog missing from+the catalog: report it so it can be added with a safe action.+ ## Two costs, both paid for in this session  1. **UIA against Altium's MAIN window is slow enough to be unusable.** A `desktop_find_control` took

@@ -1,7 +1,7 @@ #!/usr/bin/env bash set -euo pipefail for HOME_DIR in "$HOME/.claude/skills" "$HOME/.codex/skills"; do-  rm -rf "$HOME_DIR/altium-bridge" "$HOME_DIR/altium-bridge-plan" "$HOME_DIR/altium-part-import" "$HOME_DIR/altium-kicad-import" "$HOME_DIR/altium-install" "$HOME_DIR/altium-libraries" "$HOME_DIR/altium-boards" "$HOME_DIR/altium-outputs" "$HOME_DIR/altium-bridge-dev" "$HOME_DIR/altium-bridge-publish"+  rm -rf "$HOME_DIR/altium-bridge" "$HOME_DIR/altium-bridge-plan" "$HOME_DIR/altium-part-import" "$HOME_DIR/altium-kicad-import" "$HOME_DIR/altium-install" "$HOME_DIR/altium-libraries" "$HOME_DIR/altium-boards" "$HOME_DIR/altium-outputs" "$HOME_DIR/altium-instances" "$HOME_DIR/altium-licensing" "$HOME_DIR/altium-uia" "$HOME_DIR/altium-wiki-import" "$HOME_DIR/altium-a365" "$HOME_DIR/altium-bridge-dev" "$HOME_DIR/altium-bridge-publish" done rm -rf "$HOME/.local/share/adom/altium-bridge" rm -f "$HOME/.local/bin/altium-dashboard"