chore(m17): seal Phase 2 acceptance

[Endofthestars]

Stack

M17 7/7 and Phase 2 acceptance umbrella. Base: m17/19-release-0.3.0rc1.

What changed

• record the M17 seal verdict as PASS_WITH_ACCEPTED_EXCEPTIONS
• add M17 Registry and golden acceptance to CI
• add packaged 38-tool smoke verification
• close the Roadmap milestone and open the Phase 3 RFC gate
• remove the deprecated package-license metadata form

Acceptance

• Kernel: PASS
• MCP: PASS
• Codex Plugin: PASS
• Codex CLI: PASS
• IDE: HOST-IDE-001 / BLOCKED_BY_ENVIRONMENT
• External Review: WAITING_FOR_DISCLOSURE_AUTHORIZATION
• Claude Code CLI: PENDING_HOST_VALIDATION

Validation

• 144 unittest cases
• 144 pytest cases and 174 subtests
• 81% branch-aware coverage
• Ruff and mypy passed
• SciPy oracle passed
• 89 schemas, documentation, and release policy passed
• all seven Skills and the plugin passed official validators
• sdist/wheel and Twine passed
• fresh rc1 Codex CLI explicit and implicit Skill trials passed without shell, edits, or canonical mutation

[Endofthestars]

M17 — The Instrumentarium Seal acceptance summary:

PASS:

• Phase 2 contract freeze
• MCP Tool Registry
• Codex plugin release hardening
• Review disclosure policy
• Golden REPAIR acceptance scenario
• 0.3.0rc1 package and release checks

Host acceptance:

• Tier 0 / Kernel — PASS
• Tier 1 / CLI Host — PASS
• Tier 2 / IDE Host — BLOCKED_BY_ENVIRONMENT (HOST-IDE-001, accepted exception)

External review:

• WAITING_FOR_DISCLOSURE_AUTHORIZATION
• This is an enforced permission boundary, not a failed acceptance item.

On merge:

• Phase 2 contracts are frozen at 0.3.0rc1.
• Phase 3 RFC work becomes eligible to begin.