Align candidate plan with remaining integration proof

[yihanzhu]

Tracks #327.

Align the high-risk candidate-preparation plan with the size-only spec accepted in #405. Change the spec hash and seven sizing lines to the accepted 5,450–6,000 implementation allowance. All other plan bytes remain unchanged, including the seven paths, dependency hashes and nine proof rows.

The forecast totals 5,475–5,700: 2,288 production lines, 3,012–3,237 tests and 175 documentation/manifest. The production split follows the existing source layout; it introduces no new module boundaries. Existing fixtures and private instrumentation supply the remaining proof, without a new framework or product instrumentation.

PR #396 remains clean and paused at 75c3423. Independent plan acceptance, required CI, protected merge and artifact reconciliation must precede resumption. The round cap and native/Linux evidence remain required.

Validation: exact byte comparison outside the hash and sizing lines; forecast arithmetic and hash links; preserved plan-only history with normal base-merge topology; whitespace and clean state. No implementation tests were rerun for this artifact edit.

review_size: standard. Artifact diff: 8 additions and 8 deletions.

[cloudflare-workers-and-pages]

Deploying ystack with    Cloudflare Pages

Latest commit:	5b0f9f8
Status:	✅  Deploy successful!
Preview URL:	https://fb95ae87.fabrica-6yx.pages.dev
Branch Preview URL:	https://ystack-plan-candidate-conten.fabrica-6yx.pages.dev

View logs

[yihanzhu]

PR406 — independent high-risk plan review

Plan-verdict: ACCEPT

No Important findings. Acceptance covers this plan amendment only; it does not accept implementation, waive proof or advance the implementation review round.

Exact reviewed tuple

• Repository: yihanzhu/ystack.
• PR: Align candidate plan with remaining integration proof #406.
• Branch: ystack/plan/candidate-content-preparation.
• Head: 5b0f9f8b43f135def4a692a09631aa2437a59834.
• Base/current main: ec6bb33ce29029c4fafb203df36432f7a7b7e2a3.
• Plan blob: d620e11256a8d1cff9328da2be1cb3beecb6ca29.
• Accepted spec blob and plan link: 079be9befacd58f19203bf70c0751281668156a8.
• Intent blob and spec link: fd10d967e2c6ee1fea4a80b560e861856d3ed507.

Before/after verification confirmed unchanged local/API head and base, a clean plan worktree, OPEN PR and empty labels, including merge-ready absent.

Reviewer: /root/candidate_readonly_preflight, requested Astra/high; actual runtime identity unexposed. Independent from the plan author and original Sol implementation author.

Three review passes

Bugs: Read the full current plan, exact diff and accepted G2 links. Eight lines change: the spec hash and seven sizing lines. Arithmetic matches the accepted spec:

• Production: 997 + 638 + 653 = 2,288.
• Tests: 600–650 + 2,412–2,587 = 3,012–3,237.
• Documentation/manifest: 175.
• Total: 5,475–5,700, within 5,450–6,000.

The allocations remain forecasts, not permission to omit proof or compress implementation.

Security: Every other plan byte is unchanged. No new exception, production instrumentation, runtime capability or authority is introduced. Descriptor, ownership, validation, resource, publication and inactivity boundaries remain intact.

Compliance: Only work/candidate-content-preparation/plan.md changes: eight additions and eight removals. Risk remains high. All seven implementation paths, nine proof rows, fixed dependencies, author/reviewer separation and validation requirements remain unchanged.

History satisfies the plan-only requirement:

• Amendment parent: 42aedd2b607a3a14749892b7fe338bf537884716.
• Refresh merge parents: prior plan head b712812a76b852181c01b784be6f065ac3835650, then reviewed base.
• Refresh merge tree exactly equals the base tree.
• Every non-merge commit unreachable from base touches only the plan path.

The size amendment follows accepted G2 PR405 and fits the current authorized Roadmap program without changing its concern or acceptance standard.

Validation and disposition

Exact-head quick CI 35705300134 completed successfully.

PR396 remains clean and frozen at 75c3423ee97308d9f4a953c172d22b208b93ffde. After protected plan merge, the manager must record the new plan-base, preserve the implementation branch through the normal base update, rebind artifacts and claim state, and then resume the same original author.

Outstanding implementation findings, the rounds cap and required native/Linux evidence remain binding. No test, import, product execution, file write, Git mutation or forge mutation was performed by this reviewer.