Skip to content

🐛 - Identify missing canonical SDD obligations after bounded repair #952

Open

Description

@efraespada

Is there an existing issue for this?

  • I have searched the existing issues.

Which actions are affected?

Issue

Which platforms are affected?

Linux

Description

The pre-branch SDD workflow for Domus #38 repeatedly rejects a small companion after its automatic repair. Ownership subsequently validated, and the issue retains the maintainer's answers for the existing capability, companion path, prospective paths, and observable scenarios. Neither failed attempt published an SDD or branch.

Expected: the workflow should produce a complete canonical companion against the immutable base, or expose actionable safe diagnostics when deterministic validation rejects it. Keep the publication and branch readiness gates intact.

Actual: one attempt ended in case-identity, and the next reported that required headings or a numeric test budget were still missing. The latter diagnostic does not distinguish which obligation was missing, so a maintainer cannot correct the corresponding input without guessing. The exact rejected text is not needed.

Reproducing the issue

  1. Start a companion SDD on a feature issue with an existing capability owner and answer the blocking questions, as in Domus Develop branch aligned with master #38.
  2. Observe the first failed run, then the second failed run.
  3. Verify no SDD or managed branch is published after the bounded repair in either run.
  4. Use drafting fixtures for an omitted canonical heading, an absent numeric budget, and a case-identity error after repair; verify the workflow reports the precise safe reason and that invalid candidates still cannot publish.

copilot Version

vypdev/copilot@v3 at ace49e4a7ce0f6a007fef5d11479eb9b7a5846e3 (from the first workflow's action resolution).

Relevant Log Output

  • validation.invalid-input, case-identity, reference 3e7f1941-f9a2-453b-9abd-c22cfbf2c9e8.
  • validation.invalid-input: draft still lacked required headings or a numeric test budget after one automatic repair.

Additional context and comments

Related to the earlier, closed #695 and #714; this report concerns a new companion with seven explicitly named scenarios and the currently published safe diagnostics. This report does not request an implementation bypass or changes in the consumer repository.

Activity

  1. added
    bugSomething isn't working
    bugfixSomething isn't working
    priority: highCritical issue, needs immediate attention.
    on Nov 9, 2026
  2. added theissue type on Nov 9, 2026
  3. moved this to Todo in vypdevon Nov 9, 2026
  4. changed the title [-]Identify missing canonical SDD obligations after bounded repair[/-] [+]🐛 - Identify missing canonical SDD obligations after bounded repair[/+] on Nov 9, 2026
  5. vypbot commented on Nov 9, 2026

    @vypbot
    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.

  6. efraespada commented on Nov 9, 2026

    @efraespada
    MemberAuthor

    A third bounded attempt reproduced the publication block with a different precise reason: Domus workflow 42565052291 rejected the first visible relative Markdown destination outside the path table (repository-path, validation phase, reference 50544163-6ab7-4e95-9491-26fb77149b27). No candidate or branch was published.

    The consumer issue now includes a complete maintainer-prepared candidate with the standard projection slots. The same validators from the reported Action revision accepted its 20 canonical headings, seven derived cases, reciprocal links and repository path inventory against immutable Domus develop bcb731b4ae0557f15767fc218875ff4d596fe340. This checks candidate structure locally; the Action must still validate and publish its own candidate. Normal retry.

  7. efraespada commented on Nov 9, 2026

    @efraespada
    MemberAuthor

    The fourth attempt published the companion and admitted the managed branch: successful Action run, published SDD commit. Recovery used the complete validated candidate as issue input and the ordinary Action workflow. No branch or publication checks were bypassed. The earlier required-heading/budget message still does not distinguish the rejected obligation.

  8. efraespada commented on Nov 18, 2026

    @efraespada
    MemberAuthor

    Related reproduction on Domus #118. The Issue job reached validation and stopped after one automatic repair. No SDD or managed branch was published.

    The safe diagnostic now identifies requirement-mapping, section 4 and an observed count of zero data rows. The failure reference was 312bcfe1-b490-440f-b76f-5affeed40e31. The issue describes an update to an existing owner with populated requirement and case tables.

    I’ve supplied the new requirement rows and reciprocal case mappings in the consuming issue for the next preparation attempt. The published validation and managed-branch gates still apply.

  9. efraespada commented on Nov 18, 2026

    @efraespada
    MemberAuthor

    Another reproduction of both failures occurred on Domus #122, an update to the existing owning SDD for manual automation history on immutable base 1af12f3f2ecb1c6848f843808569e5ea3ba8da5a.

    • The Issue job stopped at validation.invalid-input, reason case-identity, section 14, with six proposed case identities reserved by an immutable owner. Failure reference 4592895f-3d4a-4a39-b46f-132963bbaff6.
    • After the maintainer answered the remaining qualification question, the Issue Comment job reached validation and stopped at validation.invalid-input, reason required-heading, reference bed4af7f-96fe-4333-b55d-140c1472171f. The status card still summarizes two possible obligations and gives no heading or budget location.

    Neither failed attempt published an SDD or branch. The consuming issue now includes a canonical draft seed with eight explicitly distinct case IDs and reciprocal mappings for the next native publication attempt. The SDD validation and managed branch gates still apply.

  10. efraespada commented on Nov 19, 2026

    @efraespada
    MemberAuthor

    Domus #143 companion publication recurrence

    The native companion attempt for Domus #143 failed after its bounded repair. The selected parent is 50ddb2d60de4b4a53970ecdde70eb746ade38d30, with CI and Branch Sync successful. The issue contains a twenty-section seed with six distinct task-progress-interface-R01 through task-progress-interface-R06 requirements and nine explicitly defined cases, plus answers to all eight requested clarification questions.

    The failed attempt reports validation.invalid-input, reason requirement-mapping, reference dbed0028-70b4-4463-b86d-49456c5ac892. Its safe diagnostic identifies section 4, data row 1, expected 0 and observed 1, with guidance to keep the existing definition or assign a new hyphenated identity. The published SDK maps that outcome to a conflicting retained requirement definition. The rejected generated candidate is unavailable, so its actual requirement identity and wording remain unknown.

    The six supplied seed identities independently pass the published SDK's validateSddRequirementIds and validateSddRequirementReservations against the four immutable task owners at the exact parent. Its derived budget and reciprocal requirement/case tables assemble, and all nine supplied case definitions are retained. This checks the input graph and reservation boundary. Full SDD format, consistency and catalog validation follow native publication.

    Recovery supplies the six exact new identities and reciprocal links explicitly, retaining the nine seed case IDs and existing owner definitions, then retries the same native issue flow. The consumer remains on the Action-owned publication path. Copilot source is owned by the other agent.

    The installed action release is vypdev/copilot@v3.10.13, with locally inspected published validation SDK revision ace49e4a7ce0f6a007fef5d11479eb9b7a5846e3.

  11. efraespada commented on Nov 19, 2026

    @efraespada
    MemberAuthor

    Successful publication replaced the supplied case inventory

    The retry for Domus #143 succeeded and published 0b1e65d877f5312e3499a20e5bccde01559237ac on the Action-owned branch. The issue became branched and state:working. The issue seed explicitly defines nine task-progress-interface-C01 through task-progress-interface-C09 cases. The clarification also supplies their exact identities and reciprocal links.

    The published companion instead defines ten cases using inventory4-C01, inventory6-C01 through inventory6-C04, inventory7-C01, and inventory8-C01 through inventory8-C04. All nine supplied identities are absent. The public source SHA-256 is 284aecddf33c133ab3e314dc84ed0c0993b21f7a085187d8265ef2cc1b2eba6d.

    Running the published SDK's validateSuppliedSddCaseIds(publishedMarkdown, expectedCaseIds) independently rejects this successful publication with case-identity, section 14, expected 9 and observed 0. The seed's requirement identities also pass their reservation check against the four exact parent task owners, and its nine-case derived graph assembles. This gives a reproducible public published candidate for the input-preservation failure.

    The consumer corrected the new companion through an ordinary fast-forward contribution on that existing Action-owned ref. Correction 09401f49be3ad10e52c63f935b9355b960ea5c52 restores the supplied six requirements and nine case definitions, budget, scenarios and reciprocal links. Format, cross-document consistency, supplied identity preservation and the eleven-capability catalog validate. All four earlier task owner documents retain their exact parent bytes. Product implementation follows this validated correction.

    The producer should preserve and validate supplied inventory definitions through the final companion publication path, including after clarification and bounded repair. Copilot source remains owned by the other agent.

    An independent continuation of Domus #91 also stopped at run 44491983136, case-identity, reference aa5c966f-524c-479e-9965-a887ebd2ee50, section 14 with three reserved case identities. Its rejected candidate is unavailable. The existing issue supplies eight new stock-local-barcode-C01 through stock-local-barcode-C08 definitions and retains earlier Inventory cases as references.

  12. efraespada commented on Nov 19, 2026

    @efraespada
    MemberAuthor

    Commit evidence selection after the consumer correction

    Commit run 44494026339 fails on correction head 09401f49be3ad10e52c63f935b9355b960ea5c52 with validation.evidence-unavailable, reference a2af2d1a-42ef-48f7-a707-35d2a834bbfe. The failure occurs before progress assessment because Commit cannot verify its selected SDD draft. The canonical comparison uses develop 50ddb2d60de4b4a53970ecdde70eb746ade38d30 and the correct contributor head.

    The original Action publication 0b1e65d877f5312e3499a20e5bccde01559237ac remains an ancestor. The contributor correction restores the nine supplied case definitions that the successful native publication replaced, as documented in the producer report. Its current source digest is 2d7365bc4516776a08ada49acda5a4a18e61d038846779fbdfddca614ec8c0e3. Published SDK format, cross-document consistency, supplied identity preservation and reciprocal catalog checks pass independently. Four retained task owners preserve their exact parent bytes.

    The native publication marker still records its original commit. The contributor correction and independent checks have their own explicit provenance. The issue's existing publication marker has been preserved.

    The consumer continues implementation under the maintainer's standing Copilot-defect exception, using the corrected nine-case source and all product validation gates. Final native checks can run again on the completed feature head. This records an automation evidence-selection failure alongside the public supplied-identity reproduction.

  13. efraespada commented on Nov 19, 2026

    @efraespada
    MemberAuthor

    Domus #143 / PR #144 retains the selection failure on the implementation head

    Copilot - Commit run 44507910892 fails on 6b666055c94d5288988fc88d9a665c6674996160 before progress assessment. The pinned comparison correctly selects develop 50ddb2d60de4b4a53970ecdde70eb746ade38d30 and the current managed feature head. The final diagnostic is validation.evidence-unavailable, reference 561620bc-725e-4715-8a39-d67eed664c1f, with the action stating that the selected SDD draft could not be verified. The same run publishes the failed Copilot / Verification check. Push Bugbot correctly delegates to PR #144. Exact failed job

    The preceding native publication replaced all nine supplied identities. Contributor correction 09401f49be3ad10e52c63f935b9355b960ea5c52 restored the six requirements and nine supplied cases in the new companion. Its content remains byte-identical on the current head, SHA-256 2d7365bc4516776a08ada49acda5a4a18e61d038846779fbdfddca614ec8c0e3. Independent checks with the published 3.10.13 SDK continue to accept format, reciprocal requirement/case mapping, exact supplied identities, repository references and all four retained task owners. The original native publication remains an ancestor and its bot-owned receipt remains present. Earlier producer/consumer reconciliation

    The consumer continues under the maintainer-authorized Copilot defect exception while following all exact-head product CI and valid review findings. A separate real packaging failure on the preceding package head was reproduced and corrected by updating the stale current-navigation evidence. The normal wheel acceptance passes, and its checksum exactly equals the independently qualified Linux wheel. Edge.50 retains its exact runtime/archive/wheel/image bytes. Installed-owner acceptance, final product CI and final review are still being followed. Consumer PR

  14. efraespada commented on Nov 19, 2026

    @efraespada
    MemberAuthor

    Domus #143 retains selected-SDD evidence failure on Edge.51 package head

    Native Commit run 44518577062 fails on bf819d718f4986ba2e9ab11eb9afbdaf0b815eb3 before assessment with validation.evidence-unavailable, reference c68fcb84-14bd-4117-b7e5-ac4d88182c4b. Job 135540955757 states that the selected SDD draft cannot be verified and publishes the failed Copilot Verification check from the same attempt. Exact job

    The corrected companion remains byte-identical at SHA-256 2d7365bc4516776a08ada49acda5a4a18e61d038846779fbdfddca614ec8c0e3. Independent published SDK 3.10.13 checks pass format, exact nine supplied identities, reciprocal requirements, repository references and retained-owner consistency. The initial Action publication and bot receipt remain in branch history. The consumer follows the authorized Copilot-only exception while all product CI and valid review findings remain required. An actual owner-observed stale-list defect in Edge.50 was reproduced and corrected in immutable Edge.51. Consumer PR, preceding occurrence

  15. efraespada commented on Nov 19, 2026

    @efraespada
    MemberAuthor

    Domus #91 repeats reserved case generation against a valid supplied seed

    Native issue-comment run 44517392368 rejects SDD publication with validation.invalid-input, reference 6e7a7672-3cb3-4dbc-8d42-89f61baaff9e. Its bounded diagnostics report four reserved case identities in section 14 after one draft attempt. The generated candidate is withheld, so the offending identities remain unknown. The two product decisions were already supplied and have been answered in the current clarification round. Consumer diagnostic, attempt

    The supplied five stock-local-barcode requirements and eight stock-local-barcode cases independently pass published SDK 3.10.13 identity and reference validation. The consumer now requests a bounded companion specs/stock-local-barcode.md, keeping the immutable Inventory baseline byte-identical. The fully derived companion seed additionally passes validateSddMarkdown, validateSddDraftConsistency against the exact develop source inventory, and validateSuppliedSddCaseIds. Product decisions, all five requirement definitions and all eight case assertions are preserved. The Action retains ownership of publication and branch lifecycle. Consumer issue

  16. efraespada commented on Nov 19, 2026

    @efraespada
    MemberAuthor

    Domus #91 publishes its validated seed through the native selection protocol

    The companion's generative attempt 44522900506 failed with validation.invalid-input, reference 7f8438a6-19eb-4536-a671-4f0ed929a7de. Its bounded diagnostics report a changed reserved requirement at section 4, row 1, across two draft attempts. The generated candidate remains withheld. Consumer failure, failed attempt

    The consumer subsequently uses the published native protocol to request review of the exact seed and select the Action-issued receipt. The Action publishes 5728f074bb4f0f8e1906cac96ff1c97e77570746 from verified merge source f2514e76c3b3e57d167392b873c5260e88bb27a6, with companion specs/stock-local-barcode.md owned by household-inventory. The first commit contains only the new companion and its two catalog projections. Published SDK 3.10.13 independently accepts all eight supplied cases, all five requirements, consistency and exact file navigation. The resulting file is byte-identical to the supplied seed after both official trusted projections, SHA-256 9f30bb5b6b4ec3401b78b5f05943279870ce21bd0adb29e165d546a5090603a1. The retained Inventory owner is byte-identical. Native publication and receipt, independent consumer proof

    The consumer proceeds through that Action-owned publication after following the merged parent's exact CI and Branch Sync. The ordinary generative failures remain recorded for producer investigation.

  17. efraespada commented on Nov 19, 2026

    @efraespada
    MemberAuthor

    The final producer workflow completed successfully at exact head daba2fbbdb80da47e939d3e3d76fc76b7f195c97.

    • Product CI 44540262462 and Branch Sync 44540262471 succeed.
    • Commit 44540262543 and Copilot / Verification succeed.
    • PR review 44540274743 and Copilot / Review succeed. The complete exact-head aggregate reports zero open, reopened, dismissed, verification-required and unknown findings.
    • The separate approval observer reports unsafe-rules for the existing unprotected develop configuration. That prerequisite and the maintainer's ordinary-merge exception are recorded in upstream 🆘 - Record unsafe rules approval block on an unprotected consumer develop branch #968.

    The earlier pending-status text was stale. The producer had completed successfully before the cancellation request, which returned “Cannot cancel a workflow run that is completed.” This update records its successful result.

    The original seed publication is 8962f141, with unchanged companion hash 42a798a2790cfc4e576ea302153f87285f1e531011f5242033969c7059c39fe2 and all five qualified numeric-field cases.

    Consumer vypdev/ha-ui#37

    Producer https://github.com/vypdev/ha-ui/actions/runs/44540262543

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingbugfixSomething isn't workingpriority: highCritical issue, needs immediate attention.

Type

Projects

  • Status
    Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions