🐛🧑‍💻 - Expose blocked pre branch SDD outcomes and safe recoverable draft diagnostics #714

Is there an existing issue for this?

• I have searched the existing issues.

What actions are affected?

Issue

What platforms are affected?

Linux, macOS, Windows

Description

A pre-branch SDD consistency failure can leave an issue with state:blocked, state:awaiting-maintainer, in-progress and SDD, but no actionable failure card in the conversation and no reviewable candidate/diagnostic artifact. In #702 the only visible bot comment is the welcome message. The workflow log correctly contains a closed reason and tells the maintainer to review draft tables, but that draft was never published and no artifact exists to inspect. This makes recovery speculative and repeated normal issue events regenerate a candidate without exposing which mappings failed.

Keep strict consistency checks, one bounded automatic repair, original owner/baseline case preservation and Action-owned branch lifecycle. This issue is about useful failure publication and safe, bounded recovery evidence, not suppressing validation or treating a malformed draft as implementation acceptance. A generated invalid candidate is not by itself evidence that the validator is wrong.

Expected issue UI: “Specification preparation is blocked. No specification or branch was published. Requirement/case mappings need correction. Review the safe diagnostic [link], update the issue's decisions/input if needed, then retry this same issue. Existing answers and published specifications are retained.” Show the current reason, run link and correlation; update one durable card idempotently, with technical detail below the recovery action. A welcome/recommendation intent must not suppress a blocking SDD outcome.

Provide a reviewed privacy-safe way to inspect the relevant candidate/table diagnostics (e.g. bounded authenticated artifact or sanitized structured diagnostics). Do not blindly publish raw agent output, secrets, untrusted HTML/commands or private source in public comments; define retention, truncation/redaction, permissions and expiry/retry recovery. Distinguish specific validation evidence from generic error categories. No infinite regeneration or elevated privileges.

Reproducing the issue

1. Inspect ✨🧑‍💻 - Browser extension H1 portable workspace target builds and architecture gates #702 and its labels/comments after these failed runs:
   • https://github.com/vypdev/copilot/actions/runs/40220870653 — requirement-mapping failure, reference 433d012f-510e-487a-9c2a-766c7d8af9fd.
   • https://github.com/vypdev/copilot/actions/runs/40220870768 — case-identity failure, reference d8c11b59-4a99-44b0-ae45-af32642a64d2.
   • https://github.com/vypdev/copilot/actions/runs/40220870888 — case-identity failure, reference 2b65ddc8-f566-4906-b436-1a6052b764a1.
2. Logs report Conversation publication omitted: no explicit semantic publication intent. on repeated failures. The first run publishes only a welcome message: ✨🧑‍💻 - Browser extension H1 portable workspace target builds and architecture gates #702 (comment).
3. The run artifact list is empty; the maintainer cannot review the rejected draft tables requested by the recovery instructions.
4. Reproduce deterministically with a malformed candidate after its single repair and compare issue UI, retained state and retry behavior. Do not rely on live model nondeterminism as the only test.

copilot Version

3.10.5, trusted master runtime 39679e2, observed 2026-10-25.

Relevant log output

The SDD draft still violates its case-identity format contract after one bounded repair.
Conversation publication omitted: no explicit semantic publication intent.
Action: Review the draft tables; use distinct fully qualified case IDs and preserve the baseline inventory. Retry the same issue workflow.
Retained state: Existing answers and published SDDs were preserved; no draft was published.

Additional context or comments

Deferred follow-up; do not start a branch/hotfix/deployment now. Distinct from #701 (comment-command operand validation) and #700 (reopened dismissed finding reconciliation). #702 is the first extension engineering milestone; malformed candidates were rejected before any implementation branch was published.

Owning contract: specs/pre-branch-sdd-gate.md; inspect src/application/usecases/sdd/pre_branch_sdd_draft_workflow.ts, the gate/result publication integration and semantic issue presentation. Update owning SDD/catalog evidence/tests/docs together. Minimum 14 distinct regression cases: 5 closed failure-category/recovery presentations; 3 semantic-intent/idempotent publication cases; 3 bounded/redacted/access-controlled diagnostic evidence cases; 3 retry/retained-answer/no-premature-branch cases. Supported-locale matrix is additional, not extra distinct cases. Existing root gates and pure-policy branch budgets remain in force.