Housekeeping: branch cleanup, kit sync, tracker sync

[The-Running-Dev]

Summary

• Branch cleanup: deleted two remote branches fully merged into main (feature/sync-main-status-b5d31e, slice/W78); left feature/bulgaria-arcs-expansion, slice/S1 (closed, unmerged PRs) and reconcile/w71-w76-tracking (open PR Reconcile W71 landing, cover /authoring in consumer-smoke, and track W76 #316) alone per user decision. No local branches were eligible for deletion.
• Track sync: marked W78-W83 done in design/30-slices.md, linking their closing issues (W78 — Localization Coverage and String Extraction #326-W74c — The Breaking Ownership Release #331) — all six had already merged (PRs W78 — Localization Coverage and String Extraction #340, W79 — What Changed Between Two Resolutions #342, W80 — Seeing a Story Graph #343, W81 — Construction Finishes What build Starts #345, W82 — A Kiosk That Ran Out Can Be Refilled #347, W83 — Buildings Get Dirty, Wear Out, and Break #348) but the tracker still showed "Not started".
• CLAUDE.md: retired the stale qodo-code-review reference in the required-checks note now that automated PR review runs via anthropics/claude-code-action (Qodo is retired).
• Kit sync: fast-forwarded ~/.agent-kit from af610a6 to e9e21bf (9 commits) and reconciled command cores/tools into this repo. verify.md's core was Unmigrated-Blocked (this repo's gate table had no companion); resolved by moving the table into .claude/commands/verify-local.md under the gate-commands category the core declares, recorded in design/90-decisions.md.
• Regenerated human docs: the tracker sync left engine/TODO.md and its compatibility pointer stale against design/30-slices.md; build/Test-Documentation.ps1 caught it, so ./build/ConvertTo-HumanDocumentation.ps1 was re-run and the output committed. Also refreshed verify-local.md's gate table — verify.yml no longer flags Test-Companion.ps1/Test-DesignState.ps1 as CI gates, discovered while re-deriving the gate list from the workflow files rather than trusting the memorized one.

Verified

Ran and passed:

• Typecheck — npm --prefix src/engine run typecheck, exit 0
• Lint — npm --prefix src/engine run lint, exit 0
• Test — npm --prefix src/engine test (vitest) — 79/79 test files, 1127/1127 tests
• Pack package — npm pack --silent produced the-running-dev-game-engine-0.10.0.tgz
• Inspect tarball — no src/, no tsconfig*.json, no .test.* entries; package/dist/ present
• Consumer smoke — clean install/build/smoke against the packed tarball
• Parse-check PowerShell scripts — every tools/*.ps1 parses clean
• Validate Markdown links, terminology, and generated files — ./build/Test-Documentation.ps1: drift check passed across 18 generated engine pages, compatibility pointers and the guide; 123 Markdown files checked
• Build and verify landing page — npm --prefix src/engine run build + npm --prefix site run check (format/lint/typecheck/test/browser/build/merge) all green

Ran and failed:

• Run Pester tests — Invoke-Pester -Path tools: 241/253 passed, 12 failed. All 12 are in the newly kit-synced Read-DesignState.Tests.ps1/Test-DesignState.Tests.ps1/Test-CIWorkflow.Tests.ps1/Update-DesignProjection.Tests.ps1 — self-referential tests (Split-Path $PSScriptRoot -Parent) that validate the agent-kit's own dogfooded design/state/ per-unit-record mechanism and its verify.yml shape against whatever repo they're copied into. This repo's design/ uses 00-brief/10-design/20-contract/30-slices/90-decisions, not the kit's design/state/ scheme, so these fail structurally (StateSetAbsent) rather than from a regression — the same gap Test-DesignState.ps1 itself reports as exit 2 when run directly here. Full failing-test list and detail in .claude/verify-report.json.

Did not run:

• Build documentation — docs.ps1 is absent from this checkout (CLAUDE.md: installer-generated via Invoke-SetupDocs, not committed); needs Docker and an installed docs.ps1, neither set up this session
• Merge landing page into documentation build — depends on the artifacts/docs output of "Build documentation" above, which didn't run
• Test the host — dotnet test needs NUGET_GITHUB_TOKEN for the sibling-repo NuGet feed, not set locally
• Positive route and probe smoke — needs a built host image, blocked on the same missing token
• Negative fixture (corrupted artifact must fail to start) — same

---

Agent detail

• Not a slice — housekeeping (branch cleanup, /kit-sync, tracker sync) plus the doc-drift fix it surfaced
• .claude/verify-report.json: validated by tools/Test-VerifyReport.ps1 (Valid, 15 gates, 0 findings, 0 could-not-evaluate) before this section was rendered from it
• Left undone: the kit's self-referential Pester tests (12 failures) — whether they should be scoped out of non-dogfooding targets is an open question, not resolved here