Altium - the Altium Bridge

@@ -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.24",+  "version": "0.2.25",   "hero": {     "type": "image",     "path": "screenshots/hero.png"@@ -140,4 +140,4 @@     "skills/altium-wiki-import/SKILL.md",     "uninstall.sh"   ]-}+}\ No newline at end of file

@@ -108,3 +108,16 @@ not burn time hunting for one: free the seat elsewhere and let Develop take it a | `License maximum usage reached` | seat stranded by a killed instance | close other Altiums politely, then claim | | `License Renewal Failed` | same cause; **re-fires on a timer** | clearing it is not the fix | | `You are not currently using an Altium Designer license` | seat free, nobody claimed it | `Choose a license` → `Use License` |++## View-only mode: "There are no Author seats available" (from 0.2.25)++An Altium 365 workspace has a fixed number of AUTHOR seats, separate from the Altium licence. When+another running Altium signed in to the same workspace holds the last one (another machine, or Altium+Designer next to Altium Develop), this instance raises **Workspace Unavailable** at launch and drops to+**view-only mode**. The trap: documents that were already open keep working, and every NEW document is+silently refused. From 0.2.25 the bridge says so: `errorCode: view_only_no_author_seat` on+`altium_open_document` and on every verb that opens a library or board first.++Fix, no sign-in needed: `altium_close` the OTHER Altium (cleanly; a killed Altium strands the seat until+its lease expires), then `altium_close` + `altium_launch` this one so it asks for the seat again. If you+launched an Altium on a second machine for a test, close it when you are done: it is holding the seat.