test: stabilize v0.8.0 release gate

[flyingrobots]

Summary

Stabilizes the v0.8.0 release gate by bounding Docker-isolated Vitest worker concurrency by default while preserving explicit --maxWorkers overrides.

Verification

• pnpm test:local --run test/unit/scripts/isolated-test-args.test.ts test/unit/release/docker-test-isolation.test.ts tests/playback/CORE_test-runner-docker-daemon-hard-failure.test.ts
• git diff --check
• pnpm release:check

Release Context

RED: merged main release validation failed in Docker-isolated pnpm test with timeout-shaped failures under unbounded worker concurrency.

GREEN: release runner now defaults isolated Vitest execution to --maxWorkers 2; final pnpm release:check passed with Docker-isolated tests, security gate, and package dry run.

[coderabbitai]

Warning

Rate limit exceeded

@flyingrobots has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 52 minutes and 9 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: be349e84-64c0-4a8d-9ab8-fc805979c7fd

📥 Commits

Reviewing files that changed from the base of the PR and between 3394d6e and 6413d55.

⛔ Files ignored due to path filters (4)

• CHANGELOG.md is excluded by !**/*.md
• docs/design/BADCODE_full-suite-timeout-nondeterminism.md is excluded by !**/*.md
• docs/method/releases/v0.8.0/release.md is excluded by !**/*.md
• docs/method/releases/v0.8.0/verification.md is excluded by !**/*.md

📒 Files selected for processing (5)

• scripts/isolated-test-args.ts
• scripts/isolated-test-runner.ts
• test/unit/release/docker-test-isolation.test.ts
• test/unit/release/v080-witness.test.ts
• test/unit/scripts/isolated-test-args.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.8.0-blockers

---

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 and usage tips.}

[flyingrobots]

@codex second opinion requested. Self-audit found one issue before merge.

Issue	Severity	Source	File	Lines	Recommended mitigation
Release witness says the release/v0.8.0-blockers branch sync is still pending even though the branch has already been pushed to origin. This makes the release witness stale immediately after this PR was opened.	P3 Docs	Self	docs/method/releases/v0.8.0/verification.md	discovery section	Add a deterministic docs regression for the branch sync line, update the witness to say the branch is synced to origin/release/v0.8.0-blockers at commit 62aecf5, then commit the fix.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 62aecf57d3

ℹ️ 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".

[flyingrobots]

Activity Summary

Issue	Severity	Source	File	Commit SHA	Outcome
Release witness still said the release/v0.8.0-blockers origin sync was pending after the branch had already been pushed.	P3 Docs	Self	docs/method/releases/v0.8.0/verification.md; test/unit/release/v080-witness.test.ts	6413d55	Added a deterministic witness regression, updated the witness to record the pushed origin branch, verified targeted release-doc tests, lint, and full pnpm release:check.

Thread status: GraphQL review thread query returned zero review threads, so no PR threads required resolution.

Verification:

• RED: pnpm test:local --run test/unit/release/v080-witness.test.ts failed before the witness update.
• GREEN: pnpm test:local --run test/unit/release/v080-witness.test.ts passed after the witness update.
• Relevant suite: pnpm test:local --run test/unit/release/v080-witness.test.ts test/unit/release/package-docs.test.ts test/unit/release/docker-test-isolation.test.ts passed, 3 files / 8 tests.
• Lint: pnpm lint passed.
• Full gate: pnpm release:check passed, including Docker-isolated tests at 217 files / 1595 tests, security gate, and pack dry run.

[flyingrobots]

Activity Summary Addendum

A Codex review thread arrived after the first activity summary with the same witness-sync finding. It was already fixed by 6413d55 and is now manually resolved.

Issue	Severity	Source	File	Commit SHA	Outcome
Release witness recorded the blocker branch origin sync as pending after the branch had been pushed.	P3	PR / Codex + Self	docs/method/releases/v0.8.0/verification.md; test/unit/release/v080-witness.test.ts	6413d55	Added a deterministic witness regression, updated the witness to record origin/release/v0.8.0-blockers, pushed the branch, and resolved the Codex review thread via GraphQL.

Final local verification after the fix: pnpm release:check passed with Docker-isolated tests at 217 files / 1595 tests, security gate, and pack dry run.