Node-based terminal manager for AI coding agents — tmux-backed terminals and parallel agent sessions as draggable nodes on an infinite pan/zoom canvas. macOS, Linux, and a browser Server Edition.
TypeScript adhdagent-orchestrationai-agentscanvasclaude-codecodexcoding-agentsdeveloper-toolselectrongeminilinuxmacosmultiplexeropencodeparallel-agentsterminalterminal-emulatorterminal-multiplexertmuxworkspace-manager
docs(canvas-sync): residual (2) is almost any visit, and the seen-drop is not protection (D13, D10)
review44627344307c
diff --git a/docs/team-presence.md b/docs/team-presence.mdindex 2078e44b3..331e668c0 100644--- a/docs/team-presence.md+++ b/docs/team-presence.md@@ -499,8 +499,10 @@ They are in the vocabulary now, and everything around them is the node machinerywaits. What it does not cover: (1) a baseline taken while the solo gate is closed (`shouldPublish`false) is not rebased, so an owed item swallowed there syncs only when it next changes — the gatecloses on an open publisher only when a hosted role drops to read-only; (2) a round trip to- another project with any emit there (A → B → A): the emit in B forgets the owed node (it is not on- B's canvas), and the load that returns to A adopts A's whole scene, so a held edge is not cast+ another project (A → B → A), which in practice is almost ANY visit to B: an emit keeps owed only+ the nodes of the scene it diffs, and the publisher emits on every change to B's `nodes` state+ (React Flow's own measure and selection updates included, not only an edit), so the owed A node is+ forgotten there; the load that returns to A adopts A's whole scene, so a held edge is not castafter the node is trimmed until the edge itself changes; (3) a `remove` that was itself refused (noactive project) and then adopted over is not retried. None of the three is a regression — thepublisher behaved the same way before holds existed.diff --git a/src/core/canvas-sync.test.ts b/src/core/canvas-sync.test.tsindex 450aaec2e..5b3f7ce41 100644--- a/src/core/canvas-sync.test.ts+++ b/src/core/canvas-sync.test.ts@@ -121,7 +121,8 @@ describe('stampMutation', () => {})// Unstamped is judged exactly as before rule 4: never stale, so an unstamped upsert ordered after a- // remove IS applied over it (canvas-order `supersededByRemove`). Hygiene, like the clamp above.+ // remove IS applied over it (canvas-order `supersededByRemove`). Not protection either: omitting+ // `seen` gets the same verdict.it('drops a non-integer / negative `seen`, degrading to unstamped (judged as before rule 4)', () => {for (const bad of [-1, 1.5, NaN, Infinity, '5', null]) {expect(