docs: NOW.md refresh + RUNBOOK-INDEX walk/generate_town rows + KIMI-ONBOARDING (#1623)

[100yenadmin]

Summary

Closes #1623. One doc-hygiene batch fixing the three staleness classes found in the 2026-07-20 takeover recon — no code changes:

1. docs/roadmap/NOW.md refreshed to the 2026-07-20 truth (was Jul 9, predating the entire generator chain). Keeps its under-one-screen contract and _Last updated: header pattern: ACTIVE charter [SPRINT-CHARTER] Act II close-out — the Rendered Felt sprint (#1284 grounding → rendered rest-scene demo → W5a player build) #1386 (Act II close-out); Jul-16 generator chain merged at tip fd23e972 (feat(world): THE 5-ROOM SPINE — shop + tavern_snug join the registered walkable world (#1581) #1604–engine/qa: rest-walk lastWalkPath surface — walk gate path-audits rest mode (#1582) #1609 spine, generate_town: perimeter-snap doors, clear landings, tall-anchor dressing + generator self-gate #1610/generate_town: narrative FOCAL dressing (beauty-floor lever from the dwing panel negatives) #1611/generator: non-collinear fire-beacon fields (dress_focal v2 + beacon-geometry bar, #1618) #1621 generator, qa: walk gate tri-state verdicts (GREEN/RED/ERROR), provenance stamps, door-cross camera re-assert #1613–client: runtime-spawned actors bind the animated roster setup (T-pose fix, #1601) #1616 instruments); Task [strategy][viewer] Project strategic map and board in dashboard #76 next-cycle packet PENDING (regen → box render ×3 → paint under err_cells ≤ 0.35 gate → hot-load walk gates → blind-adjudicated panels; ~140 Scenario CU, budget refilled 2026-07-20, box claim via [SPRINT-CHARTER] Act II close-out — the Rendered Felt sprint (#1284 grounding → rendered rest-scene demo → W5a player build) #1386 comments); companions render_recipe(geometry): generate paint-recipe clauses FROM the geometry JSON (kill hand-authored structure prose) #1619 render_recipe (in flight, zero-CU) + Experience gates: idle-motion stage in walk_test + owner-proxy playtest stage + /debug build identity #1620 experience gates; walk-GREEN rooms (crypt/tavern/throne_hall live + shop/tavern_snug certified in qa/certifications/); dwing wing closed 0-adopted/3 honest negatives; qa/RRI.json 2.7 partial/harness-contaminated — no valid release verdict exists; open PR ops: Unity project persistence + save cadence (LFS + autosave cron + on-boundary save) #1617; dist/ empty. Depth pointers to PROCEDURAL-SCORECARD + ROOM-PIPELINE-RUNBOOK + KIMI-ONBOARDING.
2. docs/RUNBOOK-INDEX.md +2 rows in Generation / assets, matching the existing 6-column format: qa/walk_test.py --room <room> (room walkability gate — binding Tier-0 ship gate; live player sandbox, $0; qa/evidence/walk-*/ reports; walk_gate in scores_db; owner ROOM-PIPELINE-RUNBOOK §11) and the town chain tools/generate_town.py → qa/seed_gfx_town.py (zero-CU local; fail-loud static gates incl. the beacon-geometry bar; owner PROCEDURAL-SCORECARD §THE TOWN COMMAND CHAIN). Both stamped last-verified 2026-07-20.
3. Lands docs/KIMI-ONBOARDING.md (previously local/untracked, written 2026-07-20) — the Kimi-side routing doc: reading order, live state snapshot, Task [strategy][viewer] Project strategic map and board in dashboard #76 packet, GEX44 access recipe, skills/agent-profile routing, Kimi↔Claude interop contract. Only its Status line was edited on landing (local/untracked → tracked (landed via the #1623 PR)); the body is the verified 2026-07-20 recon snapshot as written.

Why

Issue #1623: the Jul-16 generator-chain close-out (#1604–#1621) never propagated into the standing docs. NOW.md's own contract says it is rewritten at every session close; the Universal Run Contract requires every run type to have a RUNBOOK-INDEX row; and both agent sides need one committed routing doc to co-drive off the same surfaces.

Evidence

bash qa/fast_gate.sh from the lane worktree — PASS:

✓ deterministic engine tier: 257 passed
✅ FAST-GATE T0 PASS — core engine loops + seat path intact ($0, deterministic).

• Diff scope: 3 markdown files only (NOW.md rewritten, RUNBOOK-INDEX.md +2 rows, KIMI-ONBOARDING.md new). Zero code touched; wire contracts and registries untouched.
• GitNexus note: the repo's impact/detect_changes policy targets symbol edits; this diff contains no code symbols (docs-only). The MCP index is not bound to this lane and .gitnexus is untracked in worktrees — the documented Kimi-lane gap (KIMI-ONBOARDING §6) applies; fast_gate is the check per docs: refresh NOW.md to generator-chain truth + RUNBOOK-INDEX rows (walk_test/generate_town) + land KIMI-ONBOARDING routing doc #1623.
• Facts re-verified at PR time: qa/certifications/{shop,tavern_snug}.json present; dist/ empty; PR ops: Unity project persistence + save cadence (LFS + autosave cron + on-boundary save) #1617 open; [SPRINT-CHARTER] Act II close-out — the Rendered Felt sprint (#1284 grounding → rendered rest-scene demo → W5a player build) #1386 open with active-sprint label; ROOM-PIPELINE-RUNBOOK §11 = the walk ship gate; PROCEDURAL-SCORECARD §THE TOWN COMMAND CHAIN documents both town tools.

Test plan

• qa/fast_gate.sh green (257 passed)
• Docs-only diff — no runtime behavior change; empty/unused-path invariant holds by construction
• Owner review of the NOW.md truth claims against the live board before merge (DRAFT until owner confirmation per docs: refresh NOW.md to generator-chain truth + RUNBOOK-INDEX rows (walk_test/generate_town) + land KIMI-ONBOARDING routing doc #1623)

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0b2e9c18-8ca3-47e9-ae84-6077a098c318

📥 Commits

Reviewing files that changed from the base of the PR and between fd23e97 and 30b193a.

📒 Files selected for processing (3)

• docs/KIMI-ONBOARDING.md
• docs/RUNBOOK-INDEX.md
• docs/roadmap/NOW.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/docs-now-runbook-kimi

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.