Adom Gantt

@@ -167,6 +167,65 @@ Carbon. - **`mssel` + `msphase`**, the two fixture-coupled legacy suites, against 0.50.0 and   0.51.0 on separate fixtures and ports (`g51/abms51.sh`): **BYTE IDENTICAL**, same md5. +### The live operation the token was built for++Drew approved this explicitly. It is recorded here because it is the first time anything+in this project has touched `/home/adom/project/dc-demo-gantt/`, and because it is the+proof that the token does what the round claims.++This section was written AFTER 0.51.0 was published, so it is in the page repo and not+in the immutable tarball.++**The restart.** The live server had been up since 17 August carrying pre-0.42.0 code in+memory. The process was found from the LISTENING SOCKET on 8901 by inode through+`/proc/net/tcp`, never by name, and its own `/proc/<pid>/cmdline` was read back and+matched against this exact data file and this exact port before anything was sent to it.+There is no pattern kill anywhere in `g51/live-restart.sh`: a `pkill node` in this+container kills VS Code Server, which is the container.++```+backup      /tmp/gantt-live-backup-20260821-173859  (data, sidecar, changelog, sessions + md5.txt)+old pid     54446   node ~/.local/bin/adom-gantt --data .../dc-demo.json --port 8901+new pid     997999  same command line, ppid 1, own session and process group+health      before {"rev":2405,"integrity":{"ok":true,"chained":true}}+            after  {"rev":2405,"integrity":{"ok":true,"chained":true}}+```++The restart also finally activated 0.42.0's auto-schedule `describeEvent` branch, which+had been on disk and not in memory since 19 August.++**The five edits.** Applied through the token, over HTTP, by `g51/live-edit.mjs`. It was+rehearsed first against a COPY of the three live files served on port 9051, which is how+every value below was checked before the real server saw any of them.++Each edit names the uid it is for and the name that uid is expected to still carry. Drew+edits this plan live, so a uid whose name has moved is a decision the operation has not+read: it is skipped and reported rather than written over. All five matched. The plan+moved twice while the operation was being prepared (rev 2397 at first read, 2413 at the+capture the write was based on), which is exactly the case the check exists for.++| uid | Item | Changed |+|---|---|---|+| 00177 | Get carrier quotes | name to "... OSDC + Hart", "Fort Worth to Rayburn" to "Fort Worth to Hart Senate Office Building" in the description, note appended |+| 00071 | Find where to deliver crates in DC | note replaced, "Rayburn dock" to "Hart/Senate dock" in the description |+| 00120 | Ship the workcells to DC | note appended |+| 00129 | Load in and set up both cells | note appended |+| 00070 | Find LTL company or logistics handler | note appended |++Eight events, revs 2414 to 2421, every one of them `adom-gantt agent`, every one chained.+`integrity.ok:true, chained:true` before and after. `stateRev` 1042 to 1043, so any tab+holding the older revision gets a 409 and a reload rather than clobbering this.++**Nothing lost.** The 228 items the operation did not name were compared field for field+against the capture taken immediately before the write: 0 differ, and the item count is+233 both sides. Drew's own next edit landed at rev 2422 seconds later and the five edits+were still there on a re-read, which is the last-write-wins guard doing its job in the+direction that matters.++**One thing deliberately left alone.** 00177's description still says "Rayburn freight+elevator is 8x8ft w/ 5ft door". The approved edit named one phrase to replace and that+was not it, so it stands. It is worth a follow-up now that the venue is Hart.+ ### The stale SKILL.md description, cleared  0.50.0 shipped a tarball whose SKILL.md frontmatter still carried 0.49.0's sentence about