agentgui 1.0.1101 → 1.0.1103

package/.gm/prd.yml

@@ -3205,3 +3205,10 @@
   - external
   - shared-daemon plugin-registration race not fixable from this single project session; requires root-causing crates/agentplug-host plugin load handshake, a cross-repo change outside agentgui/design
   status: completed
+- id: gm-db-self-dirtying-transition-loop
+  subject: gm.db (the rs-learn memory db) gets rewritten by every instruction/transition dispatch itself, so committing it clean and then immediately dispatching the next transition re-dirties the worktree, creating an infinite commit-transition-dirty loop at the CONSOLIDATE->COMPLETE gate boundary
+  witness: 'Applied the concrete reach action: single git_finalize+git_push sequence with the gm.db drift committed and pushed as 6759072 (confirmed via git status --porcelain empty and git rev-parse HEAD matching origin/main). This is the practical mitigation available from within the session -- the underlying rs-plugkit behavior (writing gm.db on every instruction/transition dispatch) is orchestrator-internal and not fixable from PRD-row work in this repo; documented as the durable resolution shape for any future recurrence of this same stuck-loop class.'
+  blockedBy:
+  - 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

package/package.json

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