Add durable product workspace binding evidence

[SoundBlaster]

Summary

• Add proposal 0211 and producer-owned durable product workspace binding evidence to initialization receipts.
• Link related issue/task (if any): cross-repo durable product workspace binding rollout.

Motivation

• Downstream managed operations need stable workspace identity and layout evidence without re-deriving paths from route slugs.
• The receipt must remain public-safe and must not give SpecGraph ownership of Platform routing, SpecSpace state, or Git execution.

Goals

• Emit digest-bound workspace-relative initialization evidence with strict privacy and authority boundaries.
• Intentionally out of scope: Platform artifact routing, managed execution, Git worktrees/commits/PRs, canonical spec mutation, and Ontology writes.

Changes

• Add workspace_binding_evidence to ready and blocked product workspace initialization reports, including project config digest and repository identity hints.
• Add proposal/docs/registries and regression coverage for digest stability, idempotent initialization, blocked evidence, and raw/local path privacy.

Spec Evidence

For SpecGraph logic/tooling changes, cite at least one existing SG-SPEC-####
or proposal ####. PR body is preferred; commit trailers with the same fields
are accepted. For a true no-impact change, use Spec-ID: NO-SPEC-IMPACT and
provide a rationale.

Spec-ID: SG-SPEC-0001
Proposal-ID: 0211
Spec-Impact: schema, lifecycle, tooling
Spec-Rationale: Product workspace initialization now emits producer-owned evidence consumed by the Platform binding contract.

Validation

• Tests added/updated for changed behavior
• Local checks passed

Commands run:

make test
.venv/bin/python tools/python_quality.py
make proposal-tracking-gate
make docc-sync
make publish-bundle

Results:

• 1839 passed; Python/spec YAML quality passed; proposal and DocC gates passed; public bundle safety gate passed.

Risks / Notes

• Backward compatibility impact: additive report field; existing initialization fields remain unchanged.
• Migration/config changes required: Platform must require proposal 0211 evidence only when adopting the v1 durable binding.
• Known limitations: evidence is report-only and workspace-relative; it is not a repository allocation or execution authority.

Checklist

• PR title clearly describes the change
• Scope is focused and minimal
• Documentation updated (or N/A)
• Workflow/artifact changes distinguish presence from readiness/status
• Consumers prefer authoritative repaired/promoted/latest artifacts where relevant
• Temporary or intermediate paths are scoped to the current run/task where relevant
• No secrets or sensitive data added

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.