epic: MVP readiness hardening before broader rollout #16

Parent epic: #1

Summary

Track the remaining work needed to claim an internal MVP floor for the guardrails distribution without overstating readiness.

Philosophy

This epic follows the guardrail canon already fixed in the repo:

• mechanism-first quality and safety
• fastest reliable feedback layer first
• pointer-based instructions and progressive disclosure
• implementation is not enough; runtime proof is required
• preserve upstream compatibility unless an extension point is missing

Now required before MVP claim

• guardrails: safe agents and workflow commands #5 safe agents and workflow commands
• guardrails: provider admission policy #6 provider admission policy
• guardrails: scenario and replay harness #7 scenario and replay harness
• guardrails: plugin hardening wave 2 for MVP floor #13 plugin hardening wave 2 for MVP floor

Later, after MVP floor

• guardrails: authoritative CI and release gates after MVP #14 authoritative CI and release gates
• guardrails: broader Claude asset migration beyond MVP floor #12 broader Claude asset migration beyond MVP floor

Success

The internal distribution can be described as an MVP only after the now required issues are merged and verified. The later issues improve operational maturity, but they do not block the first MVP floor.