Register proposal 0013 runtime realization

[SoundBlaster]

Summary

• What changed? Registered Proposal 0013 as runtime-realized by the existing default-deny allowed-path handling.
• Link related issue/task (if any): make next-move selected Proposal 0013 / runtime_realization after Register proposal 0012 runtime realization #392.

Motivation

• Why is this change needed? Default-deny write authority behavior already exists in supervisor runtime, but Proposal 0013 was still reported as lacking runtime realization.
• What problem, gap, or user need does it address? Removes stale proposal runtime pressure and lets the graph advance to Proposal 0014.

Goals

• What should this PR achieve? Mark Proposal 0013 runtime, validation, and observation coverage as complete.
• What is intentionally out of scope? No behavior change to allowed path enforcement and no canonical spec mutation.

Changes

• Added Proposal 0013 to tools/proposal_runtime_registry.json with default-deny allowed-path runtime, validation, and observation markers.
• Added a focused regression asserting Proposal 0013 has no remaining runtime next gap.

Validation

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

Commands run:

python3 -m pytest -q tests/test_supervisor.py -k 'proposal_0013 or proposal_0012 or proposal_runtime_index or allowed_paths_empty or outside_allowed_paths'
git diff --check
python3 -m json.tool tools/proposal_runtime_registry.json >/dev/null
make backlog
make next-move

Results:

• Focused tests: 8 passed, 606 deselected.
• Backlog after this slice: entry_count = 26, runtime_realization = 17.
• Next move advances from Proposal 0013 to Proposal 0014 / runtime_realization.
• Pre-commit hooks passed during commit.

Risks / Notes

• Backward compatibility impact: none; registry metadata and regression only.
• Migration/config changes required: none.
• Known limitations: the next proposal runtime backlog item is Proposal 0014.

Checklist

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

[SoundBlaster]

Independent stack review from #390: no blocking findings. I checked the PR-local diff against its stacked base, verified the Proposal 0013 registry entry points at existing default-deny write-authority runtime/validation/observation markers, and confirmed the focused proposal runtime tests/checks are green in the stack context. On the stack tip, {
"output_mode": "summary",
"artifact_kind": "graph_next_moves",
"schema_version": 1,
"generated_at": "2026-05-16T21:30:51.216678+00:00",
"current_scene": "high_priority_backlog",
"scene_confidence": "medium",
"recommended_next_move_kind": "review_backlog_item",
"canonical_mutations_allowed": false,
"tracked_artifacts_written": false,
"policy_artifact_path": "tools/graph_next_moves_policy.json",
"recommended_next_move": {
"move_id": "next_move::backlog::implementation_work_index::implementation::implementation_work::SG-SPEC-0063::changed_acceptance::attach_trace_baseline",
"kind": "review_backlog_item",
"title": "Review backlog item: implementation_work::SG-SPEC-0063::changed_acceptance",
"reason": "The graph backlog projection has an actionable item with the highest current priority ordering.",
"next_gap": "attach_trace_baseline",
"command_hint": "Open the backlog projection entry and take one bounded follow-up action.",
"success_condition": "The selected backlog entry is resolved, reclassified, or promoted.",
"review_required": true,
"bounded_scope": [
"implementation_work::SG-SPEC-0063::changed_acceptance"
],
"source_artifacts": [
"runs/implementation_work_index.json"
],
"subject": {
"subject_id": "implementation_work::SG-SPEC-0063::changed_acceptance",
"subject_kind": "implementation_work_item",
"title": "",
"domain": "implementation",
"source_artifact": "implementation_work_index",
"status": "blocked_by_trace_gap",
"review_state": "",
"next_gap": "attach_trace_baseline"
}
}
} now advances the proposal runtime backlog to Proposal 0014.

[SoundBlaster]

Independent stack review from #390: no blocking findings. I checked the PR-local diff against its stacked base, verified the Proposal 0013 registry entry points at existing default-deny write-authority runtime/validation/observation markers, and confirmed the focused proposal runtime tests/checks are green in the stack context. On the stack tip, make next-move now advances the proposal runtime backlog to Proposal 0014.