Repository navigation
Description
Is there an existing issue for this?
- I have searched the existing issues for missing catalog/pre-branch preparation failures. ππ§βπ» - Pre branch SDD crashes on a valid repository native capability catalogΒ #716 concerns an incompatible existing native catalog, ππ§βπ» - SDK proposed capability catalogs have no truthful greenfield SDD bootstrap route without implementation evidenceΒ #777 concerns proposed-capability bootstrap, and ππ§βπ» - Expose blocked pre branch SDD outcomes and safe recoverable draft diagnosticsΒ #714 concerns consistency rejection diagnostics. This occurrence is a missing configured catalog in the trusted base before those validations can run.
Which actions are affected?
Issue
Which platforms are affected?
Linux
Description
The pre-branch SDD gate correctly withholds a branch when its configured catalog is absent from the trusted base, but the user-facing card loses the actionable missing-catalog cause and reports only workflow.failed with generic retry guidance. Retrying the same base cannot create the missing catalog.
Please preserve fail-closed behavior and retained state while surfacing a bounded typed missing-catalog diagnostic, the immutable trusted revision, and appropriate prerequisite/recovery guidance. This report does not ask Copilot to bypass SDD preparation, create an unmanaged branch, silently initialize a replacement catalog, or accept unreviewed drafts.
In this consumer the complete catalog is being reviewed in a separate documentation PR; it has not been merged into develop. Its absence in the trusted base is real. The diagnostic should explain that prerequisite rather than imply a transient agent/provider failure or an interoperability error in a catalog that was never loaded.
Reproducing the issue
- Consumer: https://github.com/vypdev/geckocv/issues/49 . The issue was admitted using the installed bug form, then marked contract-change and in-progress. Pre-branch SDD is enabled.
- Trusted develop: f6c43676e05a694b627571172356f8e26f8d7efc. It does not contain specs/catalog.json. The proposed catalog remains under review in https://github.com/vypdev/geckocv/pull/32 .
- Run: https://github.com/vypdev/geckocv/actions/runs/41070204902 .
- The log shows the exact git show failure for that missing trusted file, before specification preparation/publication. No new branch or specification is published.
- The resulting card https://github.com/vypdev/geckocv/issues/49#issuecomment-6525007413 exposes workflow.failed, reference d1437310-6854-4c07-bfc7-0dd2a022b233 and generic retry instructions. It says specific table facts are unavailable, but does not identify the absent trusted-catalog prerequisite.
- The issue remains in-progress/SDD/contract-change/state:blocked/state:awaiting-maintainer. No unmanaged branch or same-state retry was attempted.
copilot Version
The actual setup log resolves vypdev/copilot@v3 to f5e5a4c, 3.10.6. This is an observation of that published runtime, not a regression claim against unexecuted develop fixes or a newer release.
Relevant Log Output
Pre-branch SDD gate failed: Command failed: git show f6c43676e05a694b627571172356f8e26f8d7efc:specs/catalog.json
fatal: path 'specs/catalog.json' does not exist in 'f6c43676e05a694b627571172356f8e26f8d7efc'
Publishing result: 6 result(s), 4 step(s), 1 error(s).
Error code: workflow.failed
Reference: d1437310-6854-4c07-bfc7-0dd2a022b233
Additional context and comments
Suggested controls: missing catalog versus missing Git object/provider failure; configured existing regular catalog; partial/malformed pair; a missing file in a pinned trusted base despite candidate copies; typed actionable card before model calls; zero branch/spec publication; retry guidance that distinguishes missing prerequisites from transient failures. Preserve safe handling of path/command/credential data and all specification/branch gates.
Please handle the diagnostic fix through the Copilot team's normal workflow. This reporter has not started upstream implementation, reduced product/SDD scope, disabled pre-branch SDD, created a replacement branch, changed runtime selection or deployed/released anything. The consumer's catalog review remains a separate required prerequisite.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
[-]Pre-branch SDD missing trusted catalog is hidden behind generic workflow.failed and retry guidance[/-][+]π - Pre branch SDD missing trusted catalog is hidden behind generic workflow.failed and retry guidance[/+]vypbot commentedon Oct 30, 2026
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 helpto see the available commands, or mention @vypbot with your question.[-]π - Pre branch SDD missing trusted catalog is hidden behind generic workflow.failed and retry guidance[/-][+]ππ§βπ» - Pre branch SDD missing trusted catalog is hidden behind generic workflow.failed and retry guidance[/+]1 remaining item
vypbot commentedon Oct 30, 2026
Implementation plan
Acceptance: With specs/catalog.json absent from the pinned trusted base, the gate publishes a bounded typed missing-catalog diagnostic that identifies the base revision and instructs the user to merge the prerequisite before retrying; it retains blocked state and publishes no branch or specification, while unrelated Git read failures keep their existing failure classification.
Need something else? Mention the bot with a question or use
/copilot help.vypbot commentedon Oct 30, 2026
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)
Merge pull request #821 from vypdev/bugfix/808-pre-branch-sdd-missingβ¦
vypbot commentedon Oct 30, 2026
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.