🐛 - Verified SDD progress fails before assessment when original citations exceed the field budget #957

Is there an existing issue for this?

• I have searched the existing issues.

Which actions are affected?

Commits

Which platforms are affected?

Linux

Description

Copilot 3.10.13 successfully recognizes the selected, unchanged maintainer SDD on Domus PR 61. It classifies all three source batches, then rejects the original citation framing before collecting any implementation evidence. The mandatory citations plus a nonempty fact per obligation exceed the unchanged 8,000-code-point assessment field. No assessment is published and exact-head Copilot Verification fails.

This is a source-capacity admission failure. The seed publication reconciliation succeeds, unlike #910. It occurs before evidence and assessment queries, unlike the completed-output length failure in #932 or the final aggregate rejection in #925. #829 concerned generated requirements and did not expose a source identity. This case reports a verified original requirement and line.

Reproducing the issue

1. Use Domus issue 57, its officially selected published owner appendix at 5fac9bf02a473fb10ee77dd3bdfac30d6e55af56, and the exact linked PR head 7045b30e0b1a8d1fa0e03441effcba5cf5a00925 over develop 9b2495922c57a7fddef7c75885fd22acd6a7bd9a.
2. Inspect Commit attempt 2. Commit confirms the verified SDD publication, accounts for six seed source lines outside the classifier and classifies batches 1, 2 and 3. It then logs that original citations cannot fit and makes no evidence or assessment query.
3. Inspect the Verification check. The safe facts are validation.evidence-too-large, phase assessment, reason assessment-text-limit, field $.requirements[21].summary, requirement R156, original issue line L156, retryable false. That line is the published draft's definition of done.
4. The exact-head Bugbot review completed with the one prior finding fixed. The independent product checks do not satisfy Copilot Verification.

copilot Version

v3.10.13 via vypdev/copilot@v3, resolved commit ace49e4a7ce0f6a007fef5d11479eb9b7a5846e3.

Additional context and comments

The reconciled, complete requirement set and exact original sources should remain in the frozen manifest. Use a supported assessment and rendering representation that can preserve them within the declared field limits, such as the existing canonical source anchors where appropriate. An identical retry cannot increase capacity. The consumer keeps the original issue and SDD, managed branch and required verification gates intact.