Add executor analysis report review outcome

[SoundBlaster]

Summary

• Add proposal 0112 for build_executor_analysis_report_review_outcome.
• Build a local-only runs/local_operator_executor_analysis_report_review_outcome.json from valid analysis_report review packets.
• Link the new outcome contract into supervisor policy, CLI/Make, docs, registries, tests, and static bundle exclusions.

Motivation

• 0107 added policy validation for analysis report review packets, but stopped before producing an operator-facing outcome artifact.
• This closes that runtime gap without granting proposal-draft, patch, canonical mutation, gap-closure, or static-publish authority.

Goals

• Produce ready_for_operator_review only from a valid analysis_report review packet accepted by executor_analysis_report_consumption_policy.
• Block missing/invalid packets, proposal_draft packets, authority expansion, privacy leakage, and contract drift.
• Keep the new artifact local-only and excluded from public static bundles.

Changes

• Added docs/proposals/0112_build_executor_analysis_report_review_outcome.md and source draft tracking.
• Added executor_analysis_report_review_outcome_contract and supervisor builder/validator/write path.
• Added make executor-analysis-report-review-outcome and CLI flag.
• Added focused supervisor/API tests and static bundle exclusion regression.

Validation

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

Commands run:

/opt/homebrew/bin/python3.10 -m py_compile tools/supervisor.py tests/test_supervisor.py tests/test_static_artifact_bundle.py
/opt/homebrew/bin/python3.10 -m json.tool tools/supervisor_executor_adapter_policy.json >/dev/null
/opt/homebrew/bin/python3.10 -m json.tool tools/proposal_runtime_registry.json >/dev/null
/opt/homebrew/bin/python3.10 -m json.tool tools/proposal_promotion_registry.json >/dev/null
/opt/homebrew/bin/python3.10 -m pytest tests/test_supervisor.py -q -k "analysis_report_review_outcome or executor_analysis_report_consumption or supervisor_executor_adapter_policy_declares_request_report_contract or main_builds_local_operator_executor_analysis_report_review_outcome"
/opt/homebrew/bin/python3.10 -m pytest tests/test_static_artifact_bundle.py -q
make PYTHON=/opt/homebrew/bin/python3.10 proposal-id proposal-tracking-gate proposal-work-claims-gate
make PYTHON=/opt/homebrew/bin/python3.10 executor-readiness executor-smoke executor-task-smoke executor-report-contract executor-report-smoke executor-report-review-packet executor-analysis-report-review-outcome
make PYTHON=/opt/homebrew/bin/python3.10 publish-bundle docc-sync
make PYTHON=/opt/homebrew/bin/python3.10 test

Results:

• Focused supervisor tests: 13 passed
• Static bundle tests: 14 passed
• Proposal gates: passed, next proposal ID 0113
• Local executor chain: outcome ready_for_operator_review, next gap define_executor_analysis_report_followup_policy
• Publish bundle: safety gate passed
• DocC sync: passed
• Full suite: 1187 passed in 101.93s

Risks / Notes

• Backward compatibility impact: additive local-only artifact and CLI/Make target.
• Migration/config changes required: none.
• Known limitations: this does not define or execute follow-up policy for analysis findings; it only produces the review outcome.

Checklist

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

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d2230bea66

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".