You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a 1,000-line gross diff budget, with a narrow rename-only exception;
implementation-first commit shape with enforcement edits isolated in a final chore(gates): ... commit;
exact-head validation evidence and a 250-word PR-body limit;
focused red/green checks followed by one successful full affected gate;
regression coverage at the seam missed by an earlier PR.
Also keeps run- or commit-stamped benchmark output out of scripts/ and records the general no-unit-retry policy. Volatile Vitest project membership and scheduling state remain owned by vitest.config.ts, rather than being duplicated in procedural guidance.
Validation
Tested commit 572572e470.
Fresh pnpm install --frozen-lockfile and pnpm build succeeded.
pnpm format:check passed.
pnpm check:affected --run passed; the selected agent-guidance contract was 4/4 green.
No planted-red evidence applies because this is a docs-only policy change.
BLOCKED at f5c90988a8f962ea7eda979702509f28892c76db.
The 1,000-line budget and -M90% move proof use two-dot git diff ... origin/main, which compares endpoint trees and can count unrelated main advances despite the preceding no-rebase rule. Use origin/main...HEAD or an explicit merge base.
Testing guidance says SUBPROCESS_STUB_TESTS run un-serialized in unit-core, but current vitest.config.ts defines a dedicated subprocess-stub project with fileParallelism: false and maxWorkers: 1. Correct the lane/concurrency guidance.
Validation says pnpm check:affected --run is pending although the new lifecycle requires it before push. Provide exact-head evidence or revise the rule coherently.
Exact-head docs checks are green and no device evidence is owed, but these findings block readiness.
Addressed at 72b7564a6f2043e1b7ec78e409ffe037ab659f06 (rebased onto main8021503, clean).
Budget and move proof now use three-dot git diff --stat origin/main...HEAD and git diff -M90% --stat origin/main...HEAD, with the merge-base-to-head meaning stated inline.
vitest.config.ts at this head (identical to origin/main) defines no subprocess-stub project: SUBPROCESS_STUB_TESTS (lines 14–22) is a list whose members run in unit-core's default forks pool (comment lines 5–13, include at 108–111); the only serialized project is fuzz-worker (lines 204–209: fileParallelism: false, maxWorkers: 1). The finding matches an older config; testing.md now states these facts and cites the file.
Lifecycle rule revised: the full pnpm check:affected --run is owed on the exact pushed head, run locally or by a serialized gate stage that appends the exact-head result to the PR body. That gate result for this head follows from the gate stage. check:agent-guidance and format:check are green on this head.
BLOCKED at 72b7564a6f2043e1b7ec78e409ffe037ab659f06.
The merge-base diff and exact-head affected-gate evidence are corrected; selected checks are green. However, the testing guidance and PR summary falsely say no subprocess-stub project exists and the tests run un-serialized in unit-core. At this head, vitest.config.ts excludes SUBPROCESS_STUB_TESTS from unit-core and defines a dedicated subprocess-stub project with fileParallelism: false, isolate: true, and maxWorkers: 1. Correct the docs to the actual serialized lane; do not label ready.
Resolved at 572572e4708a821581cc264c4565067922338b4f. Correction to the prior blocker: the exact PR head did not contain a serialized subprocess-stub project; that finding was based on the wrong tree. To avoid this class of drift, volatile project membership and scheduling prose is now removed from procedural guidance and remains owned by vitest.config.ts. The durable no-retry and benchmark-output policies remain. Fresh install/build, formatting, and the selected agent-guidance affected gate pass. Exact-head GitHub checks are running.
Preview removed because the pull request was closed.
2026-09-03 13:07 UTC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ready-for-humanValid work that needs human implementation, judgment, or maintainer merge
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds durable PR guidance for:
chore(gates): ...commit;Also keeps run- or commit-stamped benchmark output out of
scripts/and records the general no-unit-retry policy. Volatile Vitest project membership and scheduling state remain owned byvitest.config.ts, rather than being duplicated in procedural guidance.Validation
572572e470.pnpm install --frozen-lockfileandpnpm buildsucceeded.pnpm format:checkpassed.pnpm check:affected --runpassed; the selectedagent-guidancecontract was 4/4 green.