doc-sync — Keep .docs/ + README.md in sync with landed work

This skill brings a repo's documentation up to date with the work that has
landed in git but not yet been written up. It is the doc equivalent of a
cargo doc rebuild: the code shipped, now make the narrative match.

When to use

• After a plan closes with a GOAT/gain verdict (promote, keep-opt-in, or honest fail).
• After a batch of issues resolves (especially negative-result issues that move a
  primitive's status line).
• After a feature is promoted to default-on OR demoted to opt-in.
• Quarterly as a doc-hygiene gate.
• NOT for speculative work — only landed, committed work counts.

BOUNDARY.md — the 4th doc surface (added 2026-08-21)

Every repo ships a root BOUNDARY.md: Owns / Does not own / May depend on
(crate-granular allowlist) / Inherited (links) / Drift ledger. It is a
doc-sync surface because its drift ledger is a claim about issue state, and
claims rot:

• Row ⟺ open issue. A fixable / owner-call row REQUIRES an existing
  issue file; a by-design row cites a decision record instead. When an issue
  closes, its row must be removed in the same commit — the noise-reduction
  rule extended to BOUNDARY.md. A row whose issue is gone is the boundary
  equivalent of a stale README claim.
• Flag row-without-issue and issue-without-row (a boundary issue that
  landed with no ledger row is invisible to the guard).
• Don't hand-verify the dep tables — run
  riir-ai/scripts/ci_boundary_contract.sh. It fails on an undeclared
  cross-repo dep, a stale allowlist row, an unparseable ledger, and on the 4
  split-prep invariants. --list-deps prints the measured graph.
• Numbers in a contract are measurements, so they carry a date. If a row
  cites "N symbols" or "N packages", re-measure before trusting it in a new
  decision (riir-ai/BOUNDARY.md D2/D3 are the pattern).
• The contract is per-repo; cross-repo rules live in ONE canonical home
  (chain admission → riir-chain, dep matrix + split-prep → riir-ai) and
  every other repo LINKS. Never copy a cross-repo rule into a second file —
  that is the duplication doc-sync exists to catch.

The workspace repos and their doc shapes (derived, never counted — de-counted 2026-09-04)

The header carried a hand-typed count (18, measured 2026-09-01) while the
workspace moved to 16 live repos on 2026-09-04 (three to git/obsolete/) — the
same rot class the boundary-guard skill de-counted in its 21st run. It is 18
again since 2026-09-10 (riir-esp32 moved out of riir-chain 2026-09-06;
riir-kat spun out of riir-clippy 2026-09-10) — same count, different
membership, which is exactly why the count is derived and the census below is
a snapshot; the one-liner derives the membership.

The header said "14 as of 2026-08-28" over a table of 12 rows until
2026-09-01 — wrong twice, and six repos had no row at all, so a sync run that
walked this table skipped them silently. Don't re-type the count; derive the set
the same way the boundary gate does:

cd /Users/katopz/git && for d in */; do
  [ -f "$d/BOUNDARY.md" ] && [ -d "$d/.git" ] && echo "${d%/}"
done

Canonical count + product-vs-workspace split: katgpt-rs/AGENTS.md §"Repo count".

Each repo has a different doc layout. Read the repo's AGENTS.md first —
it documents the canonical layout and the numbering discipline.

Repo	.docs/ shape	README.md	Numbering highwater	Working branch
katgpt-rs	10 numbered folders (01_orientation/ … 10_audits/), unnumbered files inside. The public selling-point book.	Large showcase + feature tables + getting-started.	.plans/.highwater, .issues/.highwater, .benchmarks/.highwater, .research/.highwater	develop
riir-ai	12 numbered folders (01_orientation/ … 12_inference/; 02_inference/ was renumbered to 12_inference/ on 2026-08-08 to resolve a 02_ prefix collision with 02_crates/). The private consolidated selling-point book.	Large showcase + crate table.	same .highwater files	develop
riir-chain	7 numbered folders (01_orientation/ … 07_formal_verification/, reindexed from flat on 2026-08-08), unnumbered files inside. Canonical self-description — the chain owns the truth about the chain; riir-ai/.docs/07_neuro_symbolic_chain/ is the consumer/fusion view and links here. Two workspace members (riir-chain lib + riir-chaind daemon). Build surface still lives in README.md; FV invariants in AGENTS.md + .proofs/README.md.	Build commands + feature flags + the wallet/RPC trust surface + the merkle_root lesson.	same	develop
riir-neuron-db	11 numbered folders (01_orientation/ … 11_cli/; the 11th added 2026-09-09 for the ndb CLI — Plan 327, Warm-tier CRUD + identity login + multi-node sync), unnumbered files inside. Covers all src/ modules + examples/. Matches the riir-ai/.docs/ format.	What the crate owns + feature gates (default-on / opt-in) + feature→chain mapping + merkle_root/can_freeze lessons.	same	develop
riir-train	6 numbered folders (01_orientation/ … 06_cross_cutting/, reindexed from flat on 2026-07-15), unnumbered files inside. Training-method research vault.	Role + sibling layout.	same	develop (flipped from main 2026-09-04 — develop created from the main tip and made the default branch, the Issue 704 convention; main frozen)
riir-game-sdk	10 numbered folders (01_orientation/ … 10_multiplayer_topology/; the 10th was added for the two-binary production topology + avatar/game sync facade), unnumbered files inside. Covers all src/ modules + examples/. Matches the riir-ai/.docs/ / riir-neuron-db/.docs/ format.	Boundary rule + leaf constraint + spatial canonical + Phase 2/3 status + feature gates.	same	develop
riir-mmorpg-examples	No .docs/ folder — docs live in AGENTS.md (extensive: role, topology, plans/issues/benchmarks index, canonical-failure lessons) + README.md (status + build commands + env vars) + .plans/ / .issues/ / .benchmarks/ files. POC consumer of riir-game-sdk.	Status + build commands + Plan/Issue index.	same	develop
riir-refine	12 numbered folders (01_orientation/ … 11_domains/ + 12_ane/; the 12th added for the Apple Neural Engine substrate knowledge — private runtime API, MIL/blob formats, M3 Max findings, the Rust-bridge negative result + working ObjC substrate — riir-ai Issue 726 T0 distillation), unnumbered files inside. The code-healer vault — corpus/drafter/pruner/verify/self-evolve/domains narrative. AGENTS.md carries the batch-mining progress notes (the sweep record home for cross-repo clippy heals).	Status + Quick Start + Usage + feature gates.	same	develop
riir-unity	RETIRED 2026-09-04 → git/obsolete/ (owner act). Lineage only; do not route work here. No .docs/ folder — AGENTS.md-centric (domain boundary, Unity MCP rules, issue log) + .benchmarks/. The Unity host; Rust work belongs in riir-viewbridge, so doc-sync here = AGENTS.md issue-log sections + module-map freshness.	Role + boundary + sibling layout.	same	develop
riir-viewbridge	1 numbered folder (.docs/01_orientation/ — README.md + crate_role.md) + a .docs/README.md index; AGENTS.md still carries the workspace layout, boundary rules (latent/raw wall, generated-bindings, catch_unwind) + issue log, and .benchmarks/ the node GOAT. The Rust FFI side of the Unity bridge. This row said "No .docs/ folder" until 2026-09-04 — the folder arrived in the workspace scaffold 2f0257c (Plan 532 P0 part 2), i.e. a shape change that never came back to this contract, which is the failure the Shape-change contract below exists to prevent.	Role + boundary + build commands.	same	develop
mmorpg-remake	1 numbered folder (.docs/01_orientation/ — README.md + unity_host.md, from Plan 031 Phase 5) + AGENTS.md/README.md/BOUNDARY.md. The Bevy/wasm viewer half after the Unity host split out. Row ADDED 2026-09-04 — the repo was enrolled 2026-09-03 and this table never got a row for it, while carrying three retired ones: 18 rows over a 16-repo workspace, wrong in BOTH directions.	Role + boundary + build/run commands + the vessel-texture + present-mode records.	same	develop (highwater: .issues 005, .benchmarks 002)
riir-dapps	1 numbered folder (.docs/11_kat_service/, numbered to MIRROR the kat-service group elsewhere — there is no 01–10 here, so don't read the prefix as a tenth sibling) holding dated evidence bundles (2026-09-10_domain_swap/: a README narrative + 5 manifest/health JSONs), plus the AGENTS.md-centric remainder (the one-way game → dapps → chain invariant, the three-test rule, tiered-durability record) + .plans/ / .issues/ / .benchmarks/. The settlement-composition layer. This row said "No .docs/ folder" until 2026-09-11 — the folder landed tracked in eb85243 (2026-09-10, Plans 023+024, cited from AGENTS.md §Status) and never came back to this contract: the Shape-change contract's exact failure, caught by a doc-sync run deriving the census instead of reading it.	Boundary + build + the direction_gate + kat rail status.	same	develop
riir-dao	No .docs/ folder — AGENTS.md-centric (the KAT tokenomics agent: signals → strategy → guard → advisory → commit; the G5 advisory-only verdict) + .plans/ / .benchmarks/.	Boundary + build + the direction gate.	same	develop
riir-armageddon	RETIRED 2026-09-02 → git/obsolete/ (owner act). Lineage only; do not route work here. .docs/ exists but is EMPTY — AGENTS.md-centric in practice (arena/game-product domain types). Added 2026-09-01	yes	.issues 005, .plans 008	main — not develop; check before branching
riir-auth	.docs/ exists but holds only .highwater — i.e. no docs at all, AGENTS.md-centric in practice (the numbering file was created ahead of the folder's first document). Added 2026-09-01	yes	.issues 002, .benchmarks 4, .plans/.docs/.research at 0	develop
riir-burner	RETIRED 2026-09-04 → git/obsolete/ (owner act). Lineage only; do not route work here. Flat numbered FILES, no folders — .docs/001_model_verdict.md … 016_*.md (7 files; two share 016 — the numbering discipline is not enforced here). Added 2026-09-01	yes	.issues 015, .plans 019	develop
riir-deployer	2 numbered folders (01_orientation/, 02_runbooks/) + a .docs/README.md index — the smallest numbered shape in the workspace. No CLAUDE.md. Added 2026-09-01	yes	.issues 003, .plans 002, .benchmarks 001	develop
katgpt-web	No .docs/ folder — AGENTS.md-centric. Added 2026-09-01	yes	none	main — the feat/percepta-arch-diagrams checkout note is history: Issue 002 (2026-09-09, 01a9c51) merged + ff'd main to the working branch and the local feat branch is deleted; the repo sits on its trunk
mmorpg-editor	NAMED (not numbered) .docs/ subfolders — new-game-schema/, registry/, plus loose GAME_ASSETS.md. Carries ARCHITECTURE.md + DESIGN.md alongside AGENTS/README, and ARCHITECTURE.md is where the internal layering lives (BOUNDARY.md covers only the outer edge). Added 2026-09-01	yes	.issues 141, .plans 140	develop
riir-esp32	No .docs/ folder — AGENTS.md/BOUNDARY.md-centric (the ESP32 Satellite device-tier POC: crates/riir-satellite-probe, emulator recipes; explicitly not prod). Row ADDED 2026-09-11 — the repo moved out of riir-chain 2026-09-06 and this census never gained a row (the same silent-skip class the de-counted header warns about).	Role + boundary + domain test.	.issues 110, .proposals 006	develop
riir-kat	No .docs/ folder, no README — AGENTS.md/BOUNDARY.md/HISTORY.md-centric (the KAT network CLIENT + wire-protocol plane, spun out of riir-clippy issue 088 on 2026-09-10; single crate). Row ADDED 2026-09-11 — born 2026-09-10, censused a day late.	none — AGENTS.md §Status is the surface	.issues 1	develop
riir-shader	4 numbered folders (01_orientation/, 02_substrate/, 03_porting_method/, 04_size_budget/), unnumbered files inside — the WebGPU visual-effect substrate as Bevy plugins (ports every vgpu.sh example to wasm32+native as composable plugins; leaf, zero riir-* deps; upstream vercel-labs/vgpu @ 42bc4bc, MIT, attribution header per shader) + the crates/riir-shader-graph serde-only graph medium (Proposal 001 Phase 1, 3aa01ce). Row ADDED 2026-09-12; CORRECTED 2026-09-14 — the 09-12 row said "No .docs/ folder" and the book landed 7h later (2b78bb5, 09-12 07:48, "Phase 2 doc-sync — 4 folders, 10 docs") with the Shape-change contract never run by the producer; the 09-14 run re-derived the census and caught it.	yes (README)	.issues 16 · .plans 002 · .benchmarks 3 · .proposals 001	develop
mmorpg-remaster	Flat numbered FILES (.docs/00_principal.md … 10_quest_system.md + lessons_code_smell_audit_023.md + task_index.md; design docs from the remaster gap analysis, c0954dc). READ-ONLY to agents (main + develop, owner rule). Row ADDED 2026-09-14 — the repo joined the contract set at katgpt-rs Issue 760 making the workspace 20, but this census table never gained a row (the 09-12 anti-pattern census counted 19), and the flat-numbered-FILES shape it carries was wrongly believed to have left the workspace with riir-burner.	yes (README)	.issues 30 · .plans 045 · .benchmarks 042	develop (read-only)
seal-remake	6 numbered folders (01_orientation/ … 06_tooling/; 01_orientation carried the whole book — 2 docs, one for a host retired a month prior — until 2026-10-24, when the code-surface enumeration step below grew the other five from the crates' own lib docs: 02_viewer, 03_game_core, 04_edge, 05_multiplayer_topology, 06_tooling) + a top-level .docs/README.md entry point. AGENTS.md remains the LANE-level narrative (feature umbrellas, boot postures, env vars) — the book never restates it. Row ADDED 2026-10-24 — the repo was missing from this census entirely, which is how a 1-folder book over an 8-crate / ~550-file workspace passed every run green.	yes (README)	.issues 119 · .plans 052 · .benchmarks 026 · .proposals 007	develop
riir-reflex	5 numbered folders (01_orientation … 05_resources) + top README.md — the fleet-format book its AGENTS.md documents; 03_decision_flow mirrors to reflex-site (the mirror law). Public decision-engine serving repo (katgpt-rs Plan 603 deliverable). Row ADDED 2026-10-24 — born post-09-14, never gained a row (the seal-remake class).	yes (README)	same .highwater files	develop
riir-reflexer	6 numbered folders (01_orientation, 02_wire_protocol, 03_decision_flow, 04_vessel_format, 05_measurement_lane, 06_resources) + top README.md — the vessel FORMAT repo. Row ADDED 2026-10-24 (post-09-14, no row).	yes (README)	same .highwater files	develop
riir-instinct	3 numbered folders (01_serving, 03_decision_flow, 05_resources) + top README.md — the open decision lane (the moat half is riir-rethink); the number gaps are the seed's own, not a shape to fix. Row ADDED 2026-10-24 (post-09-14, no row).	yes (README)	same .highwater files	develop
riir-rethink	Numbered folders with gaps (03_decision_flow, 05_resources, 06_trust_flow, 07_moat_licensing_key_root, 08_architecture_primer — no 01/02/04; the seed's own numbering) — the PRIVATE moat repo, born 2026-10-03 from riir-instinct/moat/. Row ADDED 2026-10-24.	yes (README)	same .highwater files	develop
riir-refab	1 numbered folder (001_orientation) + README — the pure-Rust rigged-GLB refab lane, born 2026-10-11, zero workspace deps by contract. Row ADDED 2026-10-24.	yes (README)	same .highwater files	develop
riir-infer	Flat numbered FILES (001_exl3_trellis_format_support.md … 004_silero_vad_audio_lane_poc.md + unnumbered p4_opening_checklist.md) + README — the LLM-inference substrate carved from riir-ai 2026-09-22 (public). Row ADDED 2026-10-24 (post-09-14, no row).	yes (README)	same .highwater files	develop
seal-game-editor	4 numbered folders (01_assets, 02_schema, 03_registry, 04_signoffs) + top README.md — the desktop content editor; AGENTS.md is the routing table, ARCHITECTURE.md/DESIGN.md carry the layering. Row ADDED 2026-10-24 — predates the 09-14 census but the seal family was never in the contract set that census counted.	yes (README)	same .highwater files	develop (tickets per the git-workflow skill)
seal-online-remaster	Flat numbered FILES (00_principal.md … 10_quest_system.md + task_index.md; the mmorpg-remaster shape class) — the game runtime + legacy data source. DEPRECATED 2026-09-16: migration source only, read-only upstream, its remaining crates path-dep INTO seal-remake; do not route new work here. Row ADDED 2026-10-24.	yes (README)	same .highwater files	develop
sealm-toolkit	.docs/ exists but is EMPTY (the riir-auth class) — the Seal M asset toolkit (Python tools beside seal-game-editor). Row ADDED 2026-10-24.	yes (README)	same .highwater files	develop
mirror-twin-lint	4 numbered folders (01_assets, 02_schema, 03_registry, 04_signoffs) + top README.md — the seal-game-editor shape. Row ADDED 2026-10-24 — BOUNDARY carrier with no row.	yes (README)	same .highwater files	develop
jup-tool	No .docs/ folder — born 2026-10-14 (the JUP rescue tooling: Rust binary + CF Worker, hand-rolled Solana wire primitives). Row ADDED 2026-10-24.	yes (README)	same .highwater files	develop
reflex-site	No .docs/ folder — the public arena site front (gist-rs/reflex-site). Row ADDED 2026-10-24.	yes (README)	same .highwater files	develop
riir-llm	No .docs/ folder — the shared LLM-transport leaf (riir-refine Issue 124). Row ADDED 2026-10-24.	yes (README)	same .highwater files	develop
seal-std	No .docs/ folder — born 2026-10-07; the shared standard crates (leaf-per-crate, wire-is-contract law in AGENTS.md). Row ADDED 2026-10-24.	yes (README)	same .highwater files	develop
seal-render	No .docs/ folder — born 2026-10-21 (the canvas core carved from seal-game-editor, plan 412 step 1c); AGENTS/README/BOUNDARY only. Row ADDED 2026-10-24.	yes (README)	same .highwater files	develop

The sync workflow (per repo)

Step 0 — Enumerate the code surface (owner mandate, 2026-10-24 — do this FIRST, every run)

Baseline-diffing (Step 1) covers TEXT, never SURFACE: a book that never grew passes every
baseline range green while the code underneath tripled. seal-remake held a 2-doc book over an
8-crate / ~550-file workspace for weeks — every run green, nothing doc-shaped ever committed.
Before diffing anything:

1. Derive the surface — workspace members + [[bin]] rows from the root manifests, and
   the crate file counts (find crates/*/src -name '*.rs' | wc -l). Never trust a count typed
   in any doc (including this one).
2. Ask what no doc row covers. A crate/bin with zero book coverage is a GAP even when every
   existing doc is accurate — the book UNDER the code is the same rot as a stale claim, just quieter.
3. Fill gaps from code facts: workspace members → a crates map (role from each crate's own
   lib doc); a big uncovered crate → its own numbered folder (family format: bare slugs, a README
   index per folder, a top-level .docs/README.md entry point). Structural maps only — module
   roles from //! headers, features from Cargo.toml, bins from [[bin]] + bin headers. Anything
   not derivable this session is "—" or deleted, never guessed. NEVER restate the repo's
   AGENTS.md lane prose — that duplication is the drift this skill exists to catch; link it.
4. Then run the Shape-change contract below if the fill added top-level folders — the census
   row update is part of the fill, not an afterthought.

Step 1 — Find the last documented commit

git --no-pager log --oneline <branch> -- ".docs/**" "README.md" | head -20

The most recent docs: commit is your baseline. Everything after it is undocumented work.

Step 2 — List landed-but-undocumented work

git --no-pager log --oneline <baseline>..<branch>

Filter for:

• feat: / fix: commits that close a plan or issue (grep the message for Plan NNN / Issue NNN).
• docs: commits that close research notes or benchmarks (these may already be half-documented).
• Promotions / demotions (search for promote, demote, default-on, opt-in).

Cross-reference against the repo's .plans/, .issues/, .benchmarks/,
.research/ folders — read the highwater files to know the current max number.

Step 3 — Classify each landed item

For each undocumented plan/issue, classify it:

Verdict	What to write
GOAT PASS + promoted to default-on	Add to the default-features list in README. Add/update the feature table row in .docs/01_orientation/overview.md (or equivalent). Mark the plan's TL;DR with the promotion date.
GOAT PASS + stays opt-in	Add to the opt-in features table in README. Update the .docs/ feature catalog. Honest about why it stays opt-in (heavy, fusion-pending, diagnostic-only).
GOAT FAIL / negative result	Add to the negative-results section (09_feature_catalog/negative_results.md for katgpt-rs, equivalent elsewhere). Mark the plan with the failure mode. Keep the entry — negative results are load-bearing.
Issue closed (investigation)	If it changes a primitive's status (e.g. "map-fidelity hypothesis exhausted"), update that primitive's README/docs entry. If it's pure investigation with no status change, it may not need a doc writeup — judge case by case.
Research note (PASS/Gain/GOAT)	If it led to a plan, the plan entry is the writeup. If it's a standalone PASS verdict with no plan (e.g. "already shipped"), add a one-liner to the relevant .docs/ group README.

Step 4 — Write the updates

Apply the repo-specific rules:

katgpt-rs (the public engine)

• README.md: feature showcase entries (one ### section per primitive with a GOAT gate table), the opt-in features table, the default-features list, the Documentation Index.
• .docs/01_orientation/overview.md: the full feature-flag table (one row per flag).
• .docs/09_feature_catalog/: opt-in features + negative results.
• .docs/<group>/README.md: the group's fusion map + file list.
• Numbering: never reuse a plan/issue/benchmark/research number. Read the .highwater file, use value + 1, write it back.

riir-ai (the private runtime)

• README.md: crate table + feature showcase.
• .docs/: 12 numbered folders — drop new docs in the right group, add one line to the group README.
• Cross-repo: if a katgpt-rs primitive was consumed, note the fusion in the riir-ai doc AND the katgpt-rs doc (bidirectional cross-refs).

riir-chain (7-folder .docs/ book, reindexed 2026-08-08)

• README.md: build surface, feature flags, consumers, drift notes.
• .docs/: 7 numbered folders mirroring the riir-ai/.docs/ format — 01_orientation (what it is + feature surface + module map + how the ledger works), 02_consensus, 03_economics, 04_daemon (incl. the operator runbook), 05_wallet (trust boundaries, SIWR, node certificates), 06_operations (rolling upgrade across protocol versions, e2e coverage, failure scenarios), 07_formal_verification (pointer — the invariant table stays in AGENTS.md). Drop new docs in the right group folder and add one line to that folder's README.md index table. The top-level .docs/README.md is the entry point.
• Division of labour with riir-ai (set 2026-08-08): riir-chain holds the canonical chain docs; riir-ai/.docs/07_neuro_symbolic_chain/ is a fusion map + feature highlights that links here and keeps only what is riir-ai's own (the Egg/Shell raw-vs-latent boundary, latent precision realms, game-layer sync strategy, CF Workers edge topology). Do not re-centralize chain internals in riir-ai — that duplication is what drifted before. Cross-link bidirectionally.
• Module map discipline: 01_orientation/overview.md claims to list every src/ and crates/riir-chaind/src/ subtree. If a plan adds a module, add the row — a map that silently omits modules reads as "these do not exist".
• AGENTS.md: the FV (Lean 4) invariant table lives here (mirrored in .proofs/README.md), NOT in .docs/. Plan 016 spec self-tests live next to each spec module under .proofs/RiirChainProof/.

riir-neuron-db (11-folder .docs/ book; 10th added 2026-07-30, 11th 11_cli/ added 2026-09-09)

• README.md: build surface — feature gates (default-on / transitive / opt-in / per-feature prose sections for promoted primitives) + Formal Verification summary + License. Prose sections are reserved for promoted default-on features; opt-in features get table rows only.
• .docs/: 11 numbered folders mirroring the riir-ai/.docs/ format. Drop new docs in the right group folder (by capability: shard substrate / freeze-thaw / consolidation / vessel / specialized / zone / examples / FV / local-kv Warm tier / CLI), add one line to that folder's README.md index table. The top-level .docs/README.md is the entry point. The 05_secure_vessel/vessel_primitive.md doc is the restored home of the old 15_vessel.md (corrected: riir-neuron-db is "this crate", NOT katgpt-rs per Plan 006). The 10_local_kv/ folder covers the LocalKvStore + CommitLevel/CommitBatch + WAL compaction + BM25 (the Warm tier substrate backing per-player state recovery in riir-mmorpg-examples Plan 013, added Issue 043). The 11_cli/ folder covers the ndb binary (Plan 327: Warm-tier CRUD, identity login via riir-auth account_key, multi-node WAL-mirror sync).
• AGENTS.md: the FV (Lean 4) invariant table lives here (mirrored in .proofs/README.md), NOT in .docs/. The .docs/09_formal_verification/ folder is the narrative overview; AGENTS.md is the authoritative invariant table.
• Cross-repo: if a primitive was consumed by riir-ai or riir-chain, the fusion is documented bidirectionally.

riir-train (6-folder .docs/ book, reindexed 2026-07-15)

• 6 numbered folders (01_orientation/ … 06_cross_cutting/), unnumbered .md files inside — mirrors the riir-ai/.docs/ format.
• Training-method research vault: adapter training, distillation/RL, data filtering, cross-cutting audits.
• README.md is minimal — role + sibling layout.
• main branch (no develop).

riir-game-sdk (10-folder .docs/ book; 10th added for multiplayer topology)

• README.md: build surface — boundary rule, leaf constraint, spatial canonical, feature gates, Phase 2/3 status table.
• .docs/: 10 numbered folders mirroring the riir-ai/.docs/ / riir-neuron-db/.docs/ format. Drop new docs in the right group folder (by capability: spatial-entity / tick-world / rules-ai / game-builder / zone-living-world / gm-dashboard / examples / lessons / multiplayer-topology), add one line to that folder's README.md index table. The top-level .docs/README.md is the entry point. The 10_multiplayer_topology/ folder covers the two-binary authority/player production model + avatar/game sync facade (the consumer pattern for the documented C1/C2/C4 chain topologies).
• AGENTS.md: authoritative repo-local context (phase status, boundary rule rationale, leaf-constraint argument, the canonical-failure lessons). The 09_lessons/ folder is the narrative mirror of those lessons.
• examples/: showcase examples are part of the doc surface (Issue 517 rule) AND documented in .docs/08_examples/.
• Leaf constraint reminder: this crate has zero sibling path deps. Docs that reference sibling repos use relative links only — never imply a code dependency.

riir-mmorpg-examples (no .docs/ folder — AGENTS.md-centric)

• POC consumer of riir-game-sdk (orchard multiplayer: 1000-NPC swarm + cross-target Bevy binary).
• No .docs/ folder — documentation lives in:
  • AGENTS.md — the authoritative narrative (role, topology, plans/issues/benchmarks index, canonical-failure lessons, honest POC-grade caveats).
  • README.md — build surface (status, build commands, env vars, Plan/Issue index).
  • .plans/ / .issues/ / .benchmarks/ — individual plan/issue/benchmark files.
• The AGENTS.md is large (~1000+ lines) and IS the doc surface — doc-sync for this repo means keeping AGENTS.md sections current with landed plans.

riir-refine (12-folder .docs/ book)

• .docs/: 12 numbered folders mirroring the riir-ai/.docs/ format — corpus / drafter / pruner / verify / ruliology / examples / benchmarks / lessons / self-evolve / domains / ANE substrate knowledge (12_ane/, riir-ai Issue 726 T0 distillation). Drop new docs in the right group folder, add one line to that folder's README.md index table.
• AGENTS.md: the batch-mining progress notes + sweep records live here (the cross-repo clippy-heal record home). A landed heal slice in a sibling repo (katgpt-rs, riir-train, riir-ai) gets its progress note in the SAME commit as the heal — a later doc-sync run defers to the healing session (never write progress notes for someone else's in-flight sweep).
• README.md: Status + Quick Start + Usage + feature gates.

riir-unity — RETIRED 2026-09-04 (git/obsolete/), lineage only

• AGENTS.md: domain boundary (no Rust crates here; UPM package is build output; no engine substrate in C#) + the Unity MCP rules + the issue log. Doc-sync = issue-log sections for resolved issues + module-map freshness (the Packages/com.riir.viewbridge/ population + scene wiring notes).
• The Rust side of any feature lives in riir-viewbridge — cross-repo arcs (e.g. Issue 004) document on BOTH sides at arc close.

riir-viewbridge (.docs/01_orientation/ + an AGENTS.md-centric remainder)

• AGENTS.md: workspace layout (core/derive/abi/xtask) + boundary rules (latent/raw wall, generated-bindings rule, catch_unwind) + the issue log.
• .benchmarks/: GOAT records (e.g. Bench 002 node GOAT). Doc-sync = issue-log resolution entries + benchmark cross-refs.

Every repo not subsectioned above (riir-dapps, riir-dao, riir-auth, riir-deployer, riir-esp32, riir-kat, katgpt-web, mmorpg-remake, mmorpg-editor)

• Follow the census-table row — these are AGENTS.md/BOUNDARY.md-centric: doc-sync = AGENTS.md/BOUNDARY.md status sections + numbering highwater + README freshness (riir-kat has no README; its AGENTS.md is the surface). The repo's own AGENTS.md supersedes this skill. The no-docs rows added 2026-10-24 (jup-tool, reflex-site, riir-llm, seal-std, seal-render) and the empty-book sealm-toolkit ride the same treatment.
• katgpt-web checkout may sit on a feature branch (see census row) — sync the branch you find, and say which one in the run log.

Step 5 — Verify

• No broken links: every [...](.plans/NNN_*.md) must point to a file that exists.
• No stale numbers: if a README entry says "ratio 0.01" but the benchmark says "0.27", the README is wrong — update it.
• Numbering discipline: .highwater files must be bumped when new plans/issues land.
• Honesty: a GOAT FAIL stays a GOAT FAIL in the docs. A "stays opt-in" primitive is documented as opt-in with the reason. Never upgrade a verdict in the docs without the benchmark to back it.

Step 6 — Commit (ONLY through the gate — never bare git add + git commit)

Per the global AGENTS.md rule: always commit at task completion. Use docs:
prefix. Stay on the repo's working branch (develop for most, main for
riir-train). Do not push.

Commit through tools/sync_commit.sh — the mechanical form of the
staged-index standing lesson below (the #42 incident swept a stale sibling
index through a bare git add + git commit; prose did not stop it, this
does). The gate refuses a non-empty index up front (stale sibling state —
adjudicate it first, never auto-clear), stages only the named paths, refuses
anything staged beyond them, and commits via the partial form
(git commit -- <paths> — a temporary index from HEAD + the named paths), so
content staged concurrently never enters the commit and the real index is
never disturbed:

sh <workspace>/katgpt-rs/.agents/skills/doc-sync/tools/sync_commit.sh <repo> \
  "docs: sync .docs + README with recent plans (NNN, NNN, NNN)" \
  .docs README.md

Name exactly the paths THIS run edited — the file when the edit is one file,
the smallest containing dir otherwise; never a directory you did not touch.
.plans/ .issues/ .benchmarks/ .research/ join the list only when the run
actually wrote there.

Cross-repo coordination

The 5-repo (now 10-repo) family shares numbering namespaces for
plans/issues/benchmarks/research within each repo but NOT across repos.
When a katgpt-rs primitive is consumed by riir-ai, the fusion is documented
bidirectionally: the katgpt-rs doc notes "consumed by riir-ai/NNN", and the
riir-ai doc notes "consumes katgpt-rs/NNN".

Formal verification (Lean 4) has its own cross-repo pattern (Research 351):
each repo's .proofs/ instance is self-documenting via its invariant table in
AGENTS.md. The doc-sync skill does NOT cross-port Lean files between repos
(coordinator rule C4: private proofs stay private).

Shape-change contract (when .docs/ grows a new top-level NNN_* folder)

This is the root-cause guard for skill drift. The recurring failure mode: a
plan adds a top-level .docs/NNN_*/ folder to a repo, lands the commit, and
nobody updates this skill file — so the next doc-sync run operates on a
stale folder-count assumption (canonical drifts: riir-neuron-db 9→10 via
Issue 043, riir-game-sdk 9→10 via the multiplayer-topology docs, riir-chain
flat→7 via the 2026-08-08 reindex, riir-ai 11→12 via Plan 455's orphaned
02_inference/ folder discovered 2026-08-08). This contract makes the update a
grep-able checklist instead of an implicit expectation.

Trigger: any plan/issue/commit that adds a new top-level .docs/NNN_*/
folder to any repo that already has numbered folders — or a doc-sync run's
Step 0 surface fill doing the same (seal-remake 2026-10-24: 1 → 6 folders +
the top-level entry point, from one run's enumeration) — measured 2026-09-14 as
12 of the 20: katgpt-rs, riir-ai, riir-chain, riir-clippy,
riir-dapps, riir-deployer, riir-game-sdk, riir-neuron-db, riir-shader,
riir-train, riir-viewbridge, mmorpg-remake. Or that gives a .docs/ to
one of the five with none (katgpt-web, riir-dao, riir-esp32,
riir-kat, riir-mmorpg-examples) or the one whose .docs/ holds no document
(riir-auth) — creating the folder is itself a shape change and requires this
contract. Derive the split rather than reading it here (ls */.docs); the
previous version of this trigger named riir-viewbridge as having none while
its .docs/01_orientation/ had shipped in the repo's own scaffold commit —
and the version before that kept riir-shader in the "none" list for two
days after its 4-folder book landed (2b78bb5), because a census row nobody
re-derived beats no row at all for hiding a shape change.

Checklist (run in the SAME pass as the folder-adding commit):

• Verify ground truth. ls <repo>/.docs/ and count the NNN_*
  folders. Do not trust the skill's current number — it may already be stale.
• Update the table row in ## The workspace repos and their doc shapes above: bump the folder count, extend the range
  (…NN_<new-folder>/), and add a short provenance note
  (plan/issue number + one-phrase capability description).
• Update the Step 4 section for that repo: change the header
  count, add the new folder's name to the capability list, and add a
  one-sentence description of what the folder covers.
• Grep-verify zero stale counts. After the edit, run
  grep -nE "<old_count> (numbered|folder)" ~/.agents/skills/doc-sync/SKILL.md
  for the repo you touched — it MUST return zero hits. (Example: after
  bumping riir-neuron-db from 9 to 10, grep -nE "9 (numbered|folder)"
  filtered to the neuron-db rows must be empty.)
• Commit. This file is NOT in a git repo (~/.agents/ is on-disk
  only), so the update lands by saving — but the repo-side commit that adds
  the folder should reference this contract in its message (e.g.
  docs: add .docs/10_local_kv/ (shape-change contract: doc-sync SKILL.md updated)).

Who runs this: the agent executing the plan that adds the folder — NOT a
later doc-sync run. doc-sync is the consumer of the skill; the contract is
the producer-side obligation. A doc-sync run that discovers a stale count
(row says 9, disk says 10) is a SIGNAL that the producer skipped this
contract — fix the skill then, but also note the gap.

Anti-patterns

• Do not write a doc entry for a plan that hasn't landed yet. Speculative docs go in .proposals/.
• Do not remove a negative-result entry when closing its issue — the negative result is load-bearing documentation.
• Do not upgrade a GOAT FAIL to a PASS in the docs without the benchmark file to back it.
• Do not impose a .docs/ shape that differs from the repo's existing convention — respect the FORMAT you find. Numbered vs flat vs named folders, slugs vs prefixes: follow what's there. FORMAT is not COVERAGE (owner correction, 2026-10-24, twice-paid): the same line was read as "the book is 1 folder, keep it 1 folder" while the code grew to 8 crates — respect-for-shape became the excuse for a book that covered 2 topics over ~550 source files. The convention decides HOW docs are shaped, never WHETHER the code is covered; Step 0's surface gap overrides it, and the fill lands in the family format. Re-measured 2026-09-14 over the live 20 (the 09-12 measurement read 19 — it had no row for mmorpg-remaster, which joined at Issue 760): 12 numbered folders (katgpt-rs 10, riir-ai 12, riir-chain 7, riir-clippy 12, riir-dapps 1, riir-deployer 2, riir-game-sdk 10, riir-neuron-db 11, riir-shader 4, riir-train 6, riir-viewbridge 1, mmorpg-remake 1), 5 with no .docs/ at all (katgpt-web, riir-dao, riir-esp32, riir-kat, riir-mmorpg-examples), 1 whose .docs/ holds no document (riir-auth — only .highwater, which reads as a shape and is not one), 1 NAMED subfolders (mmorpg-editor), 1 flat numbered FILES (mmorpg-remaster — the shape did NOT leave the workspace with riir-burner; the 09-12 version of this sentence was wrong because that repo had no census row to be counted through). Don't re-type this census: the one-liner in the trigger above derives it, and every hand-written version of it in this file's history has been wrong within days — the previous one said "8 numbered / 8 AGENTS.md-centric" over a table whose membership differed from the workspace in BOTH directions. A shape change is a deliberate, committed decision governed by the Shape-change contract above.
• Do not renumber existing docs — the numbering discipline is monotonic and never reused.
• Do not document trivial mechanical commits (lockfile bumps, clippy fixes) unless they close a tracked issue.

Standing lessons (distilled from the run log — the load-bearing process rules)

• Per-file logs + pickaxe are the reliable baseline tools. git log -- .docs README.md AGENTS.md once reported 5a1330b as game-sdk's newest doc-touching commit while git log -- AGENTS.md + git log -S '<landed-string>' -- <file> proved 1977d83 (two days newer) had touched AGENTS.md. Always re-verify a suspicious baseline per-file before declaring a range clean.
• Narrow producer-side syncs leave holes the baseline heuristic can't see. A narrow sync fixes its own feature and skips everything else, so the strict baseline..HEAD range can be empty while the book still misses older landings. Gate runs GREP the book for recently-landed headline features; don't just trust the range. The inverse gap exists too: code landing to MATCH an already-documented row (mmorpg ?transport=local) is invisible to any baseline heuristic — nothing to fix, but don't declare a gap either.
• Grep extraction regex must include digits. ^[a-z_]+ = over [features] silently dropped avatar_sync_ed25519 and game_sync_p2p — nearly filed phantom "documented-but-dead feature" findings. Use ^[a-z0-9_]+ =.
• The staged-index check must GATE the commit, not precede it. One run saw two sibling-staged files in git diff --cached --name-only output and then sailed past them because the check was ;-chained ahead of git add + git commit — the sibling's WIP landed inside the run-log commit (benign outcome, luck not process). The correct form: run the check as its OWN command and read it, or use git commit -- <paths> (a partial commit builds a temporary index from HEAD + the named paths, leaving anyone else's staged hunks intact — the safe form on shared checkouts). scripts/staged_set_audit.py (katgpt-rs) reports the same signal class pre-commit. Mechanical since the 10-26 gate unit: every doc-sync commit goes through tools/sync_commit.sh (refuse-nonempty-index → add named → verify staged ⊆ named → partial commit); the bare form is retired for this lane — the #42 incident proved the prose alone doesn't hold.
• A doc claim of determinism is a claim about a proof. When a fix refutes the proof (the ndb Bm25 tie-truncation class), grep the book for the CLAIM, not just for coverage of the fix — the fix landed with in-source comments only and the book kept asserting the falsified invariant.
• False positives: grep the repo's OWN .benchmarks/ before declaring coverage. Different repos (and even different series in one repo) reuse bench numbers — the overview's only "Bench 025" hit was a different numbering series.
• Broken links: prose citations survive file removal, markdown links do not. The noise-reduction rule removes record files but no link-fix pass followed, so every closed issue left ](.issues/NNN…) links dangling. Standing tools (committed in katgpt-rs .agents/skills/doc-sync/tools/ — moved out of a repo-root tools/ that no longer exists; the 2026-09-04 landing row below still says tools/ and is history, not a path): python3 .agents/skills/doc-sync/tools/linkcheck_sweep.py (census) + python3 .agents/skills/doc-sync/tools/link_fix.py <repo> (auto R1-repoint / R3-delink), re-sweep to verify, commit pathspec'd .md only. Guards baked into the tools: absent-repo (a link into a workspace repo not checked out on the running box is UNVERIFIABLE, not broken — exists() is box-relative), backtick (link text already code-marked is emitted unwrapped), EOL (the fixer reads/writes with newline="" since 2026-09-22 — CRLF/mixed files round-trip byte-exact; before that the read_text/write_text pair LF-normalized whole files, measured on a CRLF .research/200, and the old 'restore EOL to HEAD convention manually' workaround is retired), and a markdown link split across lines is invisible to one-line fix regexes (NOMATCH → manual two-line edit).
• Never cite "Plan/Research NNN" without naming the repo when the number exists in more than one namespace — and never link a path you haven't verified (ls it first; per-repo numbering namespaces collide constantly).
• Classification against dirty trees uses git show <rev>: content, never the working tree. Sync remotes first; git show -1 <sha> mis-parses (the -1 overrides the sha — pass the sha alone). The reliable per-file baseline is the 4-surface set (AGENTS.md / README.md / .docs/ / the feature file) + a since-count.
• "0 passed" in a baseline run is the reliable gate detector — grep on attribute FORMS lies (whole-file #![cfg] gates sit below doc-comment headers, mod-level cfg(any(feature…)) compiles empty under default).
• Baseline-diff is coverage of TEXT, never of SURFACE (owner correction, 2026-10-24). A clean baseline..HEAD -- .docs README.md range says nothing about landings the book NEVER covered: seal-remake's book held 2 orientation docs (one retired) over an 8-crate workspace, and every run passed it green because nothing doc-shaped was committed. Each run ENUMERATES the code surface once (workspace members + bins from the root manifests; derive, never trust a stale count) and asks what no doc row covers; the crates map it writes is role-from-lib-doc only (facts read that session), never a restatement of AGENTS.md lanes — that duplication is the drift this gate exists to catch.

Run log (compact — full narratives live in git history)

Each row's durable record is the named docs:/fix commit(s) in the repo it
touched, plus this file's own history
(git log -p -- .agents/skills/doc-sync/SKILL.md — rows carried full
narratives until the 2026-09-05 compaction; git log -S '<date>' -- <this file> recovers any of them). Re-compacted 2026-09-11 — the rows appended
after 09-05 had regressed to full narratives again; same recovery applies.
New rows append ONE compact line each (hashes + one phrase — never narratives; the 09-05 and 09-11 compactions both followed regressions to full narratives). Maintenance rule: whenever this file exceeds 60KB, prune the run log to the newest 15 rows (checked at any full-gate run); every removed row is recoverable via git log -S '<date>' -- <this file>. Prune events: 09-21 (119→15, 104→51KB — the one-line convention HELD, the ~8-rows/day cadence didn't: 67 file-touching commits in 10 days) · 09-23 (25→15, trip-preempt at 59.1KB) · 09-28 (25→15, 56.9→50.4KB, same trip-preempt) · 10-12 (17→14+new=15, 60,152→56,506 — trip at the 60KB line) · 10-26 (two lanes pruned in parallel — #31/#32/#33/#34 out across the gate unit + the ai-1127 unit; 15→13 rows, 60,851→<60KB).

Date	Scope	Verdict	Record (primary fix commits)
2026-10-26	commit-gate tool unit (M3, riir-refine idle-loop — the #42 incident's own remediation; Protocol-H light: HEAD==origin ed5e4fd58, disk 867G/613G, 0 zombies, kv960 ×3 WIP untouched)	tools/sync_commit.sh LANDED — the staged-index standing lesson made MECHANICAL: refuse non-empty index (stale sibling state, adjudicate-first) → add named-only → verify staged ⊆ named pathspecs → PARTIAL commit git commit -- <paths> (real index never disturbed); 5-arm throwaway-repo test PASS (named-only / stale-index REFUSED / gate-2 fires on extras / sibling staged content PRESERVED through a partial commit — the #42 shape, now impossible / dir pathspec); Step 6 rewritten (bare add+commit retired for this lane) + the standing lesson gains the mechanical-since pointer; landed THROUGH the gate itself (kv960 WIP untouched)	katgpt-rs (this commit)
2026-10-25	delta unit (M5 Ultra amo, post–ai-1127-lever-2 doc pass; lever 2 was built + RED-refuted + reverted by the same session — nothing landed, so the doc unit is AGENTS.md/book hygiene only; sibling lora WIP + the ARTB lane untouched as-found)	riir-ai: AGENTS.md mmorpg feature list was missing THREE landed primitives (1126 corridor / 1127 town_bias+lever-2-declined / 1128 anchored_spawns) — rows landed be8a6eb07; Step-0 surface check found riir-games-mmorpg at ZERO 02_crates coverage (285 files / ~200 features, invisible to the book while every delta run passed green — the TEXT-vs-SURFACE class) → 4-slug sub-book filled from module docs, index row added 77a7b7dae; issue 1129 filed+done same session, file removed per the noise rule 7ed4b6c2c	riir-ai 77a7b7dae · katgpt-rs (this commit)
2026-10-26	delta unit #42 (M3, riir-refine idle-loop item-13; Protocol-H: 36-repo sweep — llama.cpp + riir-ai ff-pulled clean-behind, ndb DIRTY ×21 = the glm ARTB-632 WIP as-found, disk 867G/613G, 0 zombies/worktrees; the #41 linkcheck tool ⚠ already discharged upstream 1c0813b3b — workspace now self-derived; ⚠ INCIDENT: the run-log commit swept a STALE sibling index (pre-f8b7a70c2/e7523c5ec snapshot — reverted landed work in 17 files incl. the .py gate feature); fully repaired same hour 08effb073+14a0c3040 (net unit diff vs ebb4ceb11 = SKILL.md only, gate PASS re-verified, sibling's unstaged kv960 WIP untouched); run table pruned 16→14 (the #22 stub row + the 10-19/#30 pair caught by over-matched old_text — collateral, recoverable via git log))	linkcheck 7514 files / 30 repos: TOTAL 11 → 2 — the post-#41 issue-removal wave (chain 166, refine 171, rethink 038): 9 FIXED across 5 repos — chain bench-347→HISTORY c3c36ea6, refine bench-121→HISTORY 19fd693c, reflex bench-163→rethink HISTORY 29b22b4, rethink ×3 (HISTORY's bench-163 path one .. too deep — the #40 depth class; 013+034 repointed) b0721c8, seal-remake ×3 (126+009's 171 fusion links→refine HISTORY) 17e6d2e7 · the 2 standing kv960 DEFERs ride (6th pass) · delta book gaps 1 FIXED: riir-kat AGENTS feature table gains kat_protocol_migrate (T2-landed 7e3711f, no lane commit ever banked the row) 31dba40; ai 1125 / sdk 051 / infer 1115+1118+1119 / sr 121 verified self-doc'd	riir-chain c3c36ea6 · riir-refine 19fd693c · riir-reflex 29b22b4 · riir-rethink b0721c8 · seal-remake 17e6d2e7 · riir-kat 31dba40 · katgpt-rs (this commit)
2026-10-26	delta unit #43 (M3, riir-refine idle-loop item-13; Protocol-H light: katgpt-rs == origin 4a70279ed, disk 867G; ndb ff'd behind-19→0 onto the amo 633 wave; boundary-guard 245th scoped row + the ndb 632 claim-lease unblind landed same session earlier units)	linkcheck 7523 files / 30 repos: TOTAL 2 → 3 → 2 — the NEW ndb bench-506 dangling issue-635 link (635 closed+removed 203dce3) repointed to its Bench 507 record; landed mid-air against the amo lane's T3 633-closeout editing the SAME line — union resolution kept (their 633-CLOSED/Bench-510 prose + my 635 fix), ndb 34e79a6 after one conflict round-trip · the 2 standing kv960 DEFERs ride (6th pass) · book gaps 0 — ndb 633 wave / seal-remake 121 / ai 1126-1129 all self-doc'd per convention	riir-neuron-db 34e79a6 · katgpt-rs (this commit)
2026-10-25	delta unit #41 (M3, riir-refine idle-loop unit 6 post-boundary-242; Protocol-H: 30-repo sweep all behind=0, sibling dirty as-found ×8 repos; ⚠ tool fix needed upstream: linkcheck_sweep v2 has a hardcoded /Users/katopz/git default — worked via LINKCHECK_WORKSPACE env, the skill's tool block should note it)	linkcheck 7513 files / 30 repos: TOTAL 5 → 2 — riir-ai plan-633 ×2 dead issue-1068 links delinked (issue CLOSED+REMOVED 25810b231, resolution recorded in the plan itself) ed661f66a + katgpt-rs issue-963 consumer link followed the seal-remake blaze-pilot renumber 122→126 012d03d95 (pushed after the ai sibling lane's 9e343e845 landed mid-unit — rebase clean) · the 2 standing kv960 DEFERs ride (954/955 → .issues/960, that lane, 5th pass carrying) · delta CLEAN 0 book gaps — every post-#40 landing is a live lane's self-doc'd arc (ai 1022/1056/i971 benches, infer plan-622/1117/bench-891, train 628/649 QRR lane, seal-remake+sge plan-412 slices + the 124/122 fixes, dapps T3a–c, ndb artb-632)	riir-ai ed661f66a · katgpt-rs 012d03d95 (this commit)
2026-10-25	delta unit #40 (4090 box shikuwa, riir-refine idle-loop overflow-continuation item-13 unit; GPU = sibling QRR cell 99%/24 GiB the whole unit, zero-cargo; Protocol-H: 31-repo fetch sweep — riir-ai +2 / rethink +1 / seal-* 2–29 ff-pulled clean, riir-train dirty+behind 17 = sibling WIP as-found, C: 28 GiB reported for owner disk-clean, 14 ELEVATED git/ssh zombies 10-22/23 confirmed owner-act (taskkill access-denied); 971 watch FIFTH PASS ran inside this unit — prism-b10822 escalation tag, riir-ai 9cf087a6d)	linkcheck 7505 files / 31 repos: TOTAL 3 → 2 — the NEW riir-infer 893→train-671 cross-repo link repointed ../../../ → ../../ (three ups from a .benchmarks file exits the workspace to E:/riir-train; two is the correct escape — verified exists on disk AND at origin before the edit; riir-infer 5fcafd4) + the 2 standing kv960 DEFERs ride (954/955 → .issues/960, the kv960 lane, 4th pass carrying) · delta CLEAN 0 book gaps — every post-#38 landing self-doc'd by construction (refine bbtree 322/289 + issue-171 verdict ARE docs commits; ai 1125/tripwire + rethink 032 + seal-* lanes carry their own docs commits) · run log pruned 15→14 + this row (60KB trip-preempt)	riir-infer 5fcafd4 · katgpt-rs (this commit)
2026-10-25	delta unit #39 (M5 Ultra amo, i1122 campaign wait window — zero-cargo unit; Protocol-H: 12-repo fetch 4 moved — riir-ai +1 docs / katgpt-rs +1 docs / riir-refine +6 docs+B281 ff-pulled clean, seal-remake +27 pull DEFERRED (the sibling ARTB lane actively editing that tree — dirty files overlap the incoming commits) · ai i1122 issue: v2 adjudication OUTCOME row landed (06:13 ctx512 re-cell stays OWED, prior restored+verified, force-flagged to v3; v3+v4 chained))	linkcheck 6776 files / 18 repos: TOTAL 31 → 29 — the 2 ai-051 fixes from #38 (4090-side) account exactly for the delta, NO new breaks from the pulled docs commits · all 29 = absent-repo UNVERIFIABLE (seal-game-editor/riir-dao/riir-esp32/riir-deployer/riir-shader absent from this subset box) + the 2 standing kv960 DEFERs · delta CLEAN; run log pruned 14→13 rows (60KB trip-preempt: my row would have crossed it)	riir-ai b553d444b · katgpt-rs (this commit)
2026-10-25	delta unit #38 (4090 box shikuwa, riir-refine idle-loop item-13 unit; Protocol-H: 9-root fetch all in-sync except rethink behind-1 ff-pulled (M5's own docs commit 3f5ef3d); riir-train dirty ×2 + untracked startlux models = the sibling training lane's live WIP, as-found; zombies = the documented owner-gated census unchanged; E: 359G)	linkcheck 7450 files / 31 repos: TOTAL 4 → 2 — ai Proposal 051 ×2 cross-repo citations of REMOVED rethink Issue 016 repointed to rethink HISTORY §"issue-file hygiene" + the Phase-2 status line updated to the closed verdict (T5–T6 taken up at Bench 071, D1 trigger FIRES, remainders owner-gated) — the inbound-ai half of a hygiene pass whose rethink-side half landed on M5 (#37) but whose cross-repo citations were only visible from a box running the full sweep · katgpt-rs 954/955 → .issues/960 standing DEFER rides (kv960 lane) · delta CLEAN 0 book gaps — all post-#37 landings self-doc'd docs commits (refine 5bbc2ba6d, ai fde28e06c, rethink 3f5ef3d)	riir-ai 75877cdcb · katgpt-rs (this commit)
2026-10-25	delta unit #37 (M5 Ultra amo, i1122 campaign wait window — zero-cargo unit; Protocol-H: 18-repo fetch 6 moved, ff-pulled katgpt-rs −2 / riir-refine −28 / riir-rethink −2 / riir-infer −10 (.DS_Store-only dirt) / riir-reflex −2 (incoming commits disjoint from the sibling's dirty file); THIS BOX IS A SUBSET — seal-game-editor/riir-deployer/riir-shader/riir-dao/riir-esp32/mirror-twin-lint ABSENT)	linkcheck 6774 files: TOTAL 38 → 7 FIXED (riir-train 4: README bench links followed the issue-556 renumbers 264→665/241→663 + plan 248/437 followers + removed-issue-621 → HISTORY; rethink 2: removed 016/031 → HISTORY; ai 1: league-doc Issue 919 → HISTORY) + 29 UNVERIFIABLE (absent-repo targets — not broken, box-relative) + 2 standing DEFER (katgpt-rs 954/955 → .issues/960, the kv960 lane) · all landed items in the 5 pulled repos verified self-doc'd in-commit (1117, 622-T4.1, 1108-T3, 962, refine B278)	riir-train 265b6b6b · riir-rethink 3f5ef3d · riir-ai fde28e06c
2026-10-24	delta unit #36 (M3, riir-refine idle-loop continuation post defer-marking unit; Protocol-H light: disk 281Gi/606Gi, 0 zombies, 4 clean-behind roots ff-pulled — riir-infer ×2, riir-refine ×1, sge ×3, seal-render ×3; dirty roots left as-found ×7; 4090 still down re-verified)	delta CLEAN 0 book gaps across 12 active repos — every post-baseline landing is a claim row (refine batch 274), mechanical rustfmt (infer), or a live claimed lane's in-flight arc (ndb 632, sdk 049, sge plan 412/428 trio, seal-std steps) self-doc'ing at closeout · linkcheck 7427 files: TOTAL 4 → 2 FIXED (ai issues 1113/1122 Bench-998 refs lacked the ../ prefix — target exists tracked; c0d22c23a) + 2 DEFERRED (katgpt-rs 954/955 → .issues/960, the kv960 lane's never-landed issue file, the #33 precedent)	riir-ai c0d22c23a · katgpt-rs (this commit)
2026-10-24	delta unit #35 (4090 box shikuwa, idle-loop housekeeping post-#34; Protocol-H: 4 behind roots ff-pulled — riir-ai −1, riir-train −1, reflex −1, rethink −3; untracked sibling data left as-found; disk-clean owner-approved same cycle: 18 repo target/debug + prismml build + C:/tmp scratch, E: 14.4→411 GiB free)	delta CLEAN 0 book gaps — all 4 landed items self-doc’d in-commit: riir-train bench-422 P2 NO-GO re-run + 423-F1 + issue-644 ticks ride their own docs commit, rethink 032 T10.2 doc cross-references the reflex fix, riir-ai bench_1113 provenance fix is test-only mechanical (anti-pattern rule) · no feature/flag/README changes anywhere	katgpt-rs (this commit)
2026-10-24	census repair (M3; derived-set diff vs this table — the seal-remake class swept workspace-wide; RECOVERED via git log -S 'census repair' 2026-10-26: 15 rows added, every BOUNDARY carrier on disk)	pruned 2026-10-26 (#43 trip-preempt: 12 rows at the 60,000-byte line; the 10-26 parallel-prune precedent)	katgpt-rs (git log -S 'census repair' -- .agents/skills/doc-sync/SKILL.md)
2026-10-26

TL;DR

Diff git history against the last docs: commit. For each landed plan/issue,
write the matching README/docs entry using the repo's existing shape and the
verdict from its benchmark file. Commit with docs: prefix on the working
branch. Never upgrade a verdict without proof; never delete a negative result.