spec: size complete candidate preparation repairs and proof

[yihanzhu]

Tracks #327.

Complete candidate-preparation repairs and the accepted proof are forecast to exceed the current implementation allowance. Raise that allowance to 4,400–5,200 added plus removed lines, changing only numeric sizing fields in the spec. All other bytes remain identical, including risk, intent link, seven allowed implementation paths, limits, safety requirements and all nine proof rows.

The preserved #396 head is 59e3a31 against base 519982c. Its 3,711-line diff comprises 2,026 component lines, 1,531 test lines and 154 documentation/manifest lines. The same implementation author estimated 405–625 additional component lines and 365–575 additional shared proof lines. That produces a 4,481–4,911 forecast, leaving 289 lines below the proposed ceiling. These are forecasts for completing the existing acceptance criteria, not evidence that the remaining repairs or proof have passed.

The complete round-0 independent review identified descriptor and content remeasurement, streaming/accounting, publication/reply and selector repairs, plus gaps in the already accepted nine proof rows. Reuse existing fixture setup, independent oracles and synchronized fault controls. No new test framework, added acceptance matrix, reduced proof or scope expansion is proposed. Implementation paused before round-1 edits under claim codex-candidate-fix-r1-c3ebb603-996f-40c0-8581-cf0307aa8ca9.

This size-only G2 amendment is within the named manager's continuing Roadmap authorization. It still requires separate independent review and required CI. The existing plan is deliberately unchanged and still links the preceding spec blob. After G2 merge, a separately authored, independently reviewed plan amendment must land before the preserved implementation can resume. No installation, activation, real-target execution or authority expansion is included.

Validation: exact byte comparison permits only eight numeric sizing-line changes; all other spec bytes and the intent/plan blobs are unchanged. Forecast arithmetic, single-parent spec-only amendment commit with normal base merges preserved, clean worktree, structure manifest, rename gate and git diff --check pass. No implementation tests or CI pass are claimed for this artifact-only edit.

review_size: standard. The artifact diff is 8 additions and 8 deletions in work/candidate-content-preparation/spec.md.

[cloudflare-workers-and-pages]

Deploying ystack with    Cloudflare Pages

Latest commit:	c0527a5
Status:	✅  Deploy successful!
Preview URL:	https://7dedab85.fabrica-6yx.pages.dev
Branch Preview URL:	https://ystack-spec-candidate-conten.fabrica-6yx.pages.dev

View logs

[yihanzhu]

Current manager read this complete independent G2 review. Requested reviewer gpt-6-astra/high, actual serving identity unexposed. The optional topology wording nit has been clarified in the PR body. Implementation remains paused until the separate plan amendment is accepted.

Independent G2 review — PR 399, round 0

VERDICT: PASS

This verdict accepts only the numeric size amendment to the candidate-content-preparation spec. It does not accept implementation PR 396, resolve its Important findings, establish complete implementation proof, or authorize implementation to resume before its separate high-risk plan amendment is accepted.

Identity and exact reviewed tuple

• Repository: yihanzhu/ystack.
• PR: spec: size complete candidate preparation repairs and proof #399; OPEN, no labels, no merge-ready label.
• Branch: ystack/spec/candidate-content-preparation.
• Head: c0527a5.
• Current base/main: 88d1280.
• Worktree: /private/tmp/claude-501/-Users-yihanzhu-git/dd83267a-8ae2-4699-9afa-a8ca0bf3421c/scratchpad/wt-pr346; clean before and after the refreshed review.
• Spec author: /root/candidate_size_spec_author, requested Astra/high.
• Independent reviewer: /root/candidate_readonly_preflight, requested gpt-6-astra/high; actual runtime model identity is not exposed.
• Spec blob: e5530e70a4d1247c54255b8426bd86bdf3f88d0d.
• Unchanged intent blob: fd10d967e2c6ee1fea4a80b560e861856d3ed507.
• Unchanged plan blob: a2ace8b26464bec5bef636b9aa03b5403e2250dd.

The prior 86f836d / 519982c inspection was preflight only after main advanced. This verdict binds the refreshed tuple above. Independent remote reads before and after the refreshed review returned that same head, base, branch, OPEN state and empty label list. The final local read returned the same head and an empty porcelain status.

Evidence and scope

Read the applicable AGENTS.md and REVIEW.md rules, current Roadmap program authorization and minimum-CI decision, the author's full final handoff and recovery handoff, the complete 610-line proposed spec, the full numeric diff, and the complete prior G3 raw review at review-396-r0.md. That prior review's SHA-256 is 9e8ed90ea70d7d48f301b2eb793eebf61f386cd551707149e77b13485c7e345a.

The amendment changes one allowed artifact path, work/candidate-content-preparation/spec.md, by 8 additions and 8 deletions. Changed lines are 559, 565, 569–572, 579 and 580. Direct byte comparison confirms equal 610-line lengths, identical text outside those eight lines, and identical nonnumeric text within them. Numeric-expression comparison accounts for replacement of the previous documentation range by its measured single value. Risk, intent link, accepted behavior, limits, seven implementation paths and all nine proof rows remain byte-for-byte unchanged. Intent and plan blobs are unchanged.

The implementation remains paused at 59e3a31 in the preserved clean implementation worktree. Its same-author round-1 attempt remains the preserved attempt. This review performed no implementation repair or execution.

Pass 1 — Bugs and correctness

No Important finding.

The proposed implementation allowance is 4,400–5,200 added plus removed lines. The forecast is supported by the preserved 3,711-line implementation: 2,026 component lines, 1,531 test lines and 154 documentation/manifest lines. The original implementation author's additional estimates are 405–625 component lines and 365–575 test lines. These produce component 2,431–2,651, tests 1,896–2,106, and total 4,481–4,911. The stated headroom is correct: 5,200 minus 4,911 equals 289.

The revised allowance is a reasonable forecast for completing existing repairs and proof. It does not guarantee that the eventual implementation will fit, nor excuse unexplained overrun. The prior G3 findings remain unresolved by this artifact. No new concern, acceptance matrix or test framework is introduced, and no accepted proof is reduced to meet the allowance.

Pass 2 — Security

No Important finding.

This numeric-only artifact amendment changes no executable code, authority, credential or network scope, installation or activation behavior, real-target permission, security limit, safety boundary or proof requirement. The complete accepted requirements remain binding. In particular, the prior implementation descriptor, content-integrity, accounting, publication and proof findings are not waived by the size amendment.

Pass 3 — Compliance

No Important finding.

The named manager's continuing Roadmap authorization permits reasonable in-scope size revisions while preserving independent review and the artifact sequence. This is a separate spec amendment by a separate author while implementation is paused. The unchanged high-risk plan intentionally still links the previous spec blob 3c464a2114e951fe01b86bb941d533a2264a3568. That intermediate mismatch is not permission to resume: after G2 merge a separately authored, independently reviewed high-risk plan amendment must land, and the preserved implementation must adopt the accepted artifact tuple through the required normal-history sequence before further code changes.

History is preserved. The earlier normal merge c29c6f1 has parents the original PR 346 head 4f26544 and then old main 519982c; its tree equals that old main. The single-parent amendment 86f836d follows that merge and changes only the spec. Its tree equals the preserved author alias head f9e7ab1. The refreshed head c0527a5 has exactly two parents: 86f836d followed by current main 88d1280. Relative to parent 1, it adds only work/materializer-package-rebinding/intent.md from main; relative to current base it retains only the eight numeric spec-line changes. No semantic candidate change accompanies the refresh.

One optional wording nit remains in the PR body's validation paragraph: “one-parent spec-only history” would be more precise as “single-parent spec-only amendment commit, with normal base merges preserved.” The actual topology is correct and fully disclosed here; this does not block acceptance.

Validation and limits

Final remote check: quick CI run 35684365101 reports checks SUCCESS and required aggregate ci SUCCESS at this exact head; the automatic test job is SKIPPED as expected under the accepted minimum-CI policy. Cloudflare Pages is also successful. This is quick CI, not a full-matrix or candidate integration proof claim. Numeric artifact-only review did not execute tests, import product code, generate fixtures, change caches, mutate the repository or write to the forge. Only this requested raw review file was written.

The manager must preserve the exact reviewed head/base and verify current required checks before protected merge. Any semantic change or further base movement invalidates this exact-tuple verdict. All implementation acceptance and proof obligations remain outstanding for the resumed G3 round after the separate plan gate.