agentgui 1.0.1112 → 1.0.1113

package/.gm/prd.yml

@@ -3212,3 +3212,8 @@
   - external
   - gm-db write-on-every-dispatch is plugkit's own internal behavior (rs-plugkit orchestrator), not something this session's PRD-row work can change; the practical resolution is a final single commit+push+transition sequence with NO further instruction/transition dispatches in between the last commit and the COMPLETE transition, which this session will now attempt as the concrete reach action
   status: completed
+- id: publish-trigger-all-branches-drifts-main
+  subject: publish-release.yml triggered on every branch, so bumps committed back to feature branches and main drifted 13 versions behind npm
+  notes: 'Witnessed: on.push.branches was ''**''. npm view agentgui version => 1.0.1112 while origin/main package.json => 1.0.1099. Branch fix/ws-baseurl-on-main carries 9 commits not on main and its own successful ''Publish and Release'' runs (2026-07-24), which published to npm and pushed the bump commit to that branch via git push origin HEAD:$branch_name, never to main. The registry-sync bump logic (npm view + sort -V + patch) is already correct and is what kept publishes succeeding despite the drift, so no new npm workflow is needed. Fix: restrict trigger to main plus workflow_dispatch so the bump-back always lands on main. Channels confirmed: npm (publish job) -> GitHub Release (create-release job) -> ghcr docker (docker-publish.yml on release published), all chained from this one workflow.'
+  SESSION_ID: 73be7501-ad32-4d34-bd8e-2cd2d6311c37
+  status: pending

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentgui",
-  "version": "1.0.1112",
+  "version": "1.0.1113",
   "description": "Multi-agent ACP client with real-time communication",
   "type": "module",
   "main": "electron/main.js",