Attach SG-SPEC-0063 trace baseline

[SoundBlaster]

Summary

• What changed?
• Added SG-SPEC-0063 to the live registry-backed trace regression anchors.
• Link related issue/task (if any): implementation_work::SG-SPEC-0063::changed_acceptance / attach_trace_baseline.

Motivation

• Why is this change needed?
• The graph next move selected SG-SPEC-0063 because its implementation work item was blocked by a missing matched trace baseline.
• What problem, gap, or user need does it address?
• The spec already had registry entries, but the declared test surface did not contain a live SG-SPEC-0063 anchor, so the trace projection kept the node in planned.

Goals

• What should this PR achieve?
• Make SG-SPEC-0063 match its declared tests/test_supervisor.py trace surface.
• Move the current implementation-work item off attach_trace_baseline.
• What is intentionally out of scope?
• No changes to canonical specs, runtime code, evidence registry content, or SG-SPEC-0064.

Changes

• Added SG-SPEC-0063 to test_live_spec_trace_contract_is_registry_backed.
• Verified that rebuilt trace/implementation surfaces classify SG-SPEC-0063 as implemented and remove its implementation work item.

Validation

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

Commands run:

python3 -m pytest -q tests/test_supervisor.py -k 'live_spec_trace_contract_is_registry_backed or implementation_work_index'
python3 tools/supervisor.py --build-spec-trace-index
python3 tools/supervisor.py --build-spec-trace-projection
make implementation-delta
make implementation-work
make next-move

Results:

• Focused pytest: 12 passed, 603 deselected.
• Rebuilt trace projection: SG-SPEC-0063 state: implemented.
• Rebuilt implementation work index: SG-SPEC-0063 work item present: False, entry_count: 2.
• make next-move advanced to implementation_work::SG-SPEC-0064::changed_acceptance.

Risks / Notes

• Backward compatibility impact: none; this only adds a live test anchor for an existing registry-backed trace contract.
• Migration/config changes required: none.
• Known limitations: SG-SPEC-0063 is implemented via a semantic/test trace anchor, not a runtime code surface; runtime realization remains intentionally out of scope for this semantic cluster.

Checklist

• PR title clearly describes the change
• Scope is focused and minimal
• Documentation updated (or N/A)
• No secrets or sensitive data added