Propose composition and observation comparison contract (0219)

[SoundBlaster]

Summary

• Add SG-RFC-0219: Composition and Observation Comparison Contract.
• Link related issue/task (if any): Hypercode documentation PR #35; Hypercode source snapshot is pinned to commit 0661903e94c8e3d0ea47cf9971fe4911cebace9c.

Motivation

• Desired/Observed integration needs a consumer boundary that preserves Hypercode's minimal composition model and exposes incomplete evidence instead of silently flattening code relations.

Goals

• Define a bounded comparison contract and fixture acceptance plan.
• Runtime comparison, scanners, generation, metric gates, viewer integration, and a future Clojure application are out of scope.

Changes

• Add the proposal and archived discussion source.
• Register source/promotion tracking and an explicit deferred_until_canonicalized posture; marker checks establish document tracking only.
• Add a DocC mirror and synchronization group.

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.

Proposal-ID: 0219
Spec-Impact: docs-only
Spec-Rationale: Define and track a deferred consumer contract without changing canonical specifications, runtime comparison behavior, or authority.

Validation

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

Commands run:

make proposal-tracking-gate
make docc-sync
.venv/bin/python -m pytest -q tests/test_supervisor.py -k "proposal_tracking or proposal_promotion or proposal_runtime"
make spec-evidence-gate
.venv/bin/python tools/spec_evidence_gate.py --pr-body-file /tmp/specgraph-composition-pr.md
git diff --check

Results:

• Tracking, DocC, and spec-evidence gates passed; 67 focused tests passed.
• Markdown fences and local link targets checked. No runtime behavior changed, so no new runtime tests were added.

Risks / Notes

• Backward compatibility impact: none; no grammar, public runtime schema, or CLI changes.
• Migration/config changes required: none.
• Known limitations: proposed result semantics and fixture criteria are not an implemented comparator; no Clojure repository or UML Viewer compatibility claim.

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]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-20T06:15:02.779111Z	61447cf	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.