Close Relay runtime slimming epic

[sungjunlee]

Summary

• record the final merged runtime, test, recovery, and accounting baselines
• document the evidence-backed acceptance of 6,226 runtime LOC, 226 above the aspirational target
• close the sprint checklist after Retire vNext transition vocabulary and dead compatibility selectors #1193, TOCTOU: relay worktree base creation precedes containment validation (from #1185 review) #1191, Measure and retire unused legacy rubric, ownership, and lineage compatibility #1194, Shrink or remove special pre-run stranded-worktree recovery #1195, and Simplify Relay test accounting and narrow internal testing seams #1196

Final baseline

• runtime: 6,906 -> 6,226 LOC (-680)
• Relay tests: 14,848 -> 13,985 LOC (-863)
• recover.js: 2,187 -> 1,476 LOC (-711)
• Simplify Relay test accounting and narrow internal testing seams #1196 accounting: 4,345 -> 498 LOC (-3,847)
• unjustified current vNext terminology: 0

Verification

• full serialized gate from Simplify Relay test accounting #1202: 583 pass, 0 fail, 2 expected skips
• GitHub matrix for Simplify Relay test accounting #1202: 9/9 green
• closure docs and skills-lint: 46/46 green

Closes #1197

[coderabbitai]

Warning

Review limit reached

@sungjunlee, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: CHILL

Plan: Pro Plus

Run ID: 77e2a01f-a604-48d5-99f5-9f522ce84ee0

📥 Commits

Reviewing files that changed from the base of the PR and between abee561 and 3987f6a.

📒 Files selected for processing (2)

• backlog/sprints/2026-08-relay-runtime-slimming.md
• docs/relay-runtime-slimming-1197.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3987f6a4b7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Reconcile the still-live 6,000-line completion gate

This declares the 6,000 LOC target merely aspirational and accepts 6,226 LOC, but docs/plans/2026-07-31-relay-runtime-core-reset-vnext.md:722-727 still defines 4,000–6,000 LOC as a Definition-of-Done requirement, explicitly marks it NOT MET, and says it remains unsatisfied until the runtime drops below 6,000 or the band is explicitly raised. The resulting repository marks the sprint complete while its completion contract says the opposite; update or supersede that contract, or record the newly approved band, as part of this closure.

Useful? React with 👍 / 👎.