Skip to content

Repository navigation

🐛🧑‍💻 - SDD draft generation repeatedly disagrees with its own case budget and traceability #695

New issue
New issue
Closed
Bug
#696
Closed
🐛🧑‍💻 - SDD draft generation repeatedly disagrees with its own case budget and traceability#695
Bug
#696
Assignees
efraespada
Labels
100%Progress: 100%branchedIndicates that a branch has been created for this issue.bugSomething isn't workingbugfixSomething isn't workingpriority: highCritical issue, needs immediate attention.size: LIndicates a large-sized task or issue that requires significant effort and time.

Description

@efraespada
efraespada
opened on Oct 25, 2026

Is there an existing issue for this?

  • I have searched the existing issues.

Which actions are affected?

Issue

Which platforms are affected?

Linux

Description

Issue #694 cannot reach its Action-owned branch because successive pre-branch SDD generations fail case identity, requirement mapping and, most recently, per-area case-budget consistency after the one bounded regeneration.

The strict publication checks added in #653 correctly reject contradictions. The drafting workflow still asks the provider to independently generate the case inventory, budget arithmetic and reciprocal requirement links, with a 10,000-character soft target even for a resolved 96-case specification. Repair receives only a closed category and starts another complete generation. The rejected candidate is not published for a maintainer to edit.

Expected: generate one authoritative, explicit observable case inventory and deterministically render its derived budget and reciprocal requirement tables before the unchanged publication validator runs. Preserve all requirement/case definitions, owner collision checks, immutable path checks, limits, one shared repair and fail-closed publication. Preserve explicit resolved scope and test requirements; do not fix this by relaxing validation or lowering the requested acceptance budget.

Actual: https://github.com/vypdev/copilot/actions/runs/40168044978 fails with case-budget after bounded repair, before publishing any SDD or managed branch.

Reproducing the issue

  1. Start admitted feature ✨🧑‍💻 - Specify a cross browser GitHub extension usability features MVP and Action integration #694 with in-progress and provide its resolved browser-extension decisions and 96-case acceptance inventory.
  2. Let the Action analyze/draft against the selected immutable base.
  3. Observe the bounded draft workflow independently produce the inventory, per-area allocations and reverse mappings.
  4. The strict consistency validator rejects a mismatch; the fresh regeneration can repeat it. No branch or editable first SDD commit is published.
  5. Reproduce deterministically with a drafting fixture supplying a valid explicit inventory and derived-table placeholders, multiple requirement edges and offsetting allocations. Require exact compiled counts and reverse links; malformed, colliding or path-invalid candidates must remain blocked.

copilot Version

3.10.4; repository issue workflow uses ./; failing run 40168044978

Relevant Log Output

Pre-branch SDD gate failed: The SDD draft still violates its case-budget format contract after one bounded repair.
Error code: validation.invalid-input
Reference: 6b3237d6-cdbd-4ea5-852d-5336fee268ae

Additional context and comments

Maintainer explicitly requests correcting this blocker, then uploading the complete extension specifications on the branch the Action creates for #694 and preparing its PR. This bugfix is scoped to deterministic draft assembly and regression tests; preserve the existing product contract and security/publication checks. Update the owning SDD/catalog evidence/docs proportionally. Prepare a reviewable PR; do not merge, deploy, release or create a replacement managed branch without the required authorization.

Activity

  1. efraespada
    added
    bugSomething isn't working
    bugfixSomething isn't working
    priority: highCritical issue, needs immediate attention.
    on Oct 25, 2026
  2. vypbot
    added
    state:ai-processing
    on Oct 25, 2026
  3. vypbot
    assigned
    efraespada
    on Oct 25, 2026
  4. vypbot
    added the
    Bug
    issue type on Oct 25, 2026
  5. vypbot
    added this to vypdevon Oct 25, 2026
  6. vypbot
    moved this to Todo in vypdevon Oct 25, 2026
  7. vypbot
    changed the title [-]SDD draft generation repeatedly disagrees with its own case budget and traceability[/-] [+]🐛 - SDD draft generation repeatedly disagrees with its own case budget and traceability[/+] on Oct 25, 2026
  8. vypbot
    removed
    state:ai-processing
    on Oct 25, 2026

  9. vypbot commented on Oct 25, 2026

    @vypbot
    vypbot
    on Oct 25, 2026
    Contributor

    Hi! I’m @vypbot, the Copilot assistant for this repository.

    I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.

    Try /copilot help to see the available commands, or mention @vypbot with your question.

  10. efraespada
    added
    in-progressStart work on an admitted issue.
    on Oct 25, 2026
  11. vypbot
    moved this from Todo to In Progress in vypdevon Oct 25, 2026
  12. vypbot
    added
    branchedIndicates that a branch has been created for this issue.
    on Oct 25, 2026
  13. vypbot
    changed the title [-]🐛 - SDD draft generation repeatedly disagrees with its own case budget and traceability[/-] [+]🐛🧑‍💻 - SDD draft generation repeatedly disagrees with its own case budget and traceability[/+] on Oct 25, 2026
  14. vypbot
    added
    state:workingWork can proceed on the verified branch or without a branch.
    on Oct 25, 2026

  15. vypbot commented on Oct 25, 2026

    @vypbot
    vypbot
    on Oct 25, 2026
    Contributor

    Implementation plan

    Current status: Ready to start. No action is required from maintainers before implementation.

    1. Review drafting and publication contracts
      • Read the repository documentation and conventions, then trace SDD drafting, repair, validation, and publication paths.
      • Preserve the existing requirement definitions, owner and immutable path checks, limits, one shared repair, and fail-closed publication.
    2. Define authoritative case inventory
      • Specify a draft input shape for explicit observable cases, including their requirement links and area assignments.
      • Keep resolved scope and test requirements intact; do not reduce the requested case budget or relax validation.
    3. Compile derived tables deterministically
      • Build budget totals, per-area allocations, and reciprocal requirement mappings from the authoritative inventory.
      • Run the unchanged publication validator on the assembled SDD.
    4. Add regression coverage
      • Cover multiple requirement edges, offsetting area allocations, and exact compiled counts and reverse links.
      • Verify malformed, colliding, or path-invalid candidates remain blocked after the single bounded repair.
    5. Update owning evidence and documentation
      • Update the relevant SDD, catalog evidence, and drafting documentation to describe deterministic assembly and its contract.
    6. Prepare a reviewable PR
      • Implement the fix and tests on the issue workflow's authorized branch, then prepare a PR without merging or deploying.

    Acceptance: A drafting fixture with a valid explicit inventory and derived-table placeholders produces exact budget totals, per-area counts, and reciprocal requirement links that pass the unchanged publication validator; malformed, colliding, or path-invalid candidates remain blocked.

    Need something else? Mention the bot with a question or use /copilot help.

  16. vypbot
    added
    state:ai-processing
    size: LIndicates a large-sized task or issue that requires significant effort and time.
    85%Progress: 85%
    on Oct 25, 2026
  17. efraespada
    linked a pull request that will close this issuefix: derive SDD budgets and traceability from the case inventory #696on Oct 25, 2026
  18. vypbot
    removed
    state:ai-processing
    on Oct 25, 2026

  19. vypbot commented on Oct 25, 2026

    @vypbot
    vypbot
    on Oct 25, 2026
    Contributor

    Issue closed — historical progress

    Current status: closed as completed.

    The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.

    Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.

    Last assessment before closure (historical)

    Progress: 85% — in progress

    > Current status: The comparison shows deterministic assembly of case budgets and reciprocal requirement links before existing validation, plus regression coverage for the 96-case distribution, malformed slots, repair limits, size checks, and rejection boundaries. Specification and documentation evidence were updated. The supplied comparison does not establish that tests, builds, or package checks passed, and it does not show completion of the separate live #694 workflow acceptance check or preparation of a reviewable PR.

    Next: Confirm required test, build, architecture, documentation, and package checks; verify the live #694 workflow after promotion; prepare the reviewable PR.

  20. vypbot commented on Oct 25, 2026

    @vypbot
    vypbot
    on Oct 25, 2026
    Contributor

    Issue closed: synchronization recommendation retired

    No branch synchronization is required for this closed issue.

    The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.

  21. vypbot
    closed this as completedon Oct 25, 2026
  22. vypbot
    removed
    85%Progress: 85%
    on Oct 25, 2026
  23. github-project-automation
    moved this from In Progress to Done in vypdevon Oct 25, 2026
  24. vypbot
    added
    100%Progress: 100%
    and removed
    in-progressStart work on an admitted issue.
    state:workingWork can proceed on the verified branch or without a branch.
    on Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

100%Progress: 100%branchedIndicates that a branch has been created for this issue.bugSomething isn't workingbugfixSomething isn't workingpriority: highCritical issue, needs immediate attention.size: LIndicates a large-sized task or issue that requires significant effort and time.

Type

Bug

Projects

  • vypdev
    Status
    Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions