Thanks for the proposal. Before implementation, a maintainer should confirm the contract:

- User problem and expected behavior.
- Public CLI/API/docs surface affected.
- Compatibility impact and migration path.
- Validation plan.
- Whether this should be solved in repo docs/code or by external orchestration glue.

Until this gate is approved, do not create a mutating worktree. Discussion can continue here, but the accepted contract must be captured in the issue or PR artifacts.
