[efraespada]

When specs/catalog.json is absent from the trusted base, pre-branch SDD preparation used to report generic workflow.failed and retry guidance. Confirm absence with a bounded immutable Git tree lookup, then publish a typed configuration.unsupported prerequisite diagnostic with the trusted revision and reviewed merge/synchronization recovery.

Use the existing source-freshness fence and owned status upsert before publishing the EN/ES card. A candidate copy cannot replace the pinned source. Genuine Git read/object failures, malformed existing catalogs and missing support files retain their separate failure paths. Missing-catalog preparation performs no model analysis or branch/specification publication and retains issue/branch state.

Validation:

• 35 reserved regression cases; seven focused suites pass 395 tests with one pre-existing platform-only skip. The new pure fact, message catalogs and status renderer have 100% coverage. Every added runtime statement and branch is hit.
• An independent owned Git probe now returns the missing-catalog type with its actual commit; an unknown object remains Error 128. Actual EN/ES renderer previews include the trusted SHA without raw Git commands. These probes do not execute consumer code or publish live issue comments.
• Types, lint, docs, workflow/agent-doc contracts, specification/catalog generation, Graphify and build pass. npm-package validation and isolated CLI/API/web smoke pass. Full normal commit hooks pass build, all 816 suites / 15,512 tests (35 pre-existing skips), and lint. Committed bundles validate and match the verified source/build identity.

Update the owning SDD, catalog and prerequisite/error-recovery documentation together. The new recovery carries no untrusted operands, and the renderer withholds forged recovery data while validating its closed source fact.

Closes #808

[docs-page]

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/copilot~821

Documentation is deployed and generated using docs.page

[vypbot]

Bugbot: review complete

Current status: No active findings on 7ae2878.

Pull request · Verified commit · Workflow run

[vypbot]

Copilot approval · Human review needed

Status: A protected workflow, policy, or trust-boundary file changed.
Completed: 1/1 observed checks succeeded; Bugbot complete.
Action required: Ask a human reviewer to decide.
Impact: No new approval is confirmed for this revision.
See checks

Technical evidence

Revision: 7ae2878bae22; base: 65f10a28f7a1; reason: protected-path.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.17%. Comparing base (5b3664f) to head (7ae2878).
⚠️ Report is 113 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #821      +/-   ##
===========================================
+ Coverage    94.50%   95.17%   +0.67%     
===========================================
  Files         1035     1105      +70     
  Lines        33299    36365    +3066     
  Branches      9824    10858    +1034     
===========================================
+ Hits         31468    34611    +3143     
+ Misses         699      673      -26     
+ Partials      1132     1081      -51     

Files with missing lines	Coverage Δ
...tion/policies/application_error_message_catalog.ts	100.00% <ø> (ø)
...cation/policies/sdd_preparation_message_catalog.ts	100.00% <ø> (ø)
...lication/policies/sdd_preparation_status_policy.ts	100.00% <100.00%> (ø)
...ation/usecases/sdd/pre_branch_sdd_gate_use_case.ts	93.77% <100.00%> (+0.07%)	⬆️
src/data/model/application_error.ts	100.00% <ø> (ø)
src/domain/sdd_trusted_catalog_failure.ts	100.00% <100.00%> (ø)
...infrastructure/pre_branch_sdd_workspace_adapter.ts	77.87% <100.00%> (+0.29%)	⬆️

... and 159 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.