Parent and approved subset
Follow-up to #163 and PR #164.
The operator-approved scope says:
Reviewers block unexplained exceptions.
A target may opt into a stricter zero-comments policy, but ystack core must not impose it on every project.
Assess the smallest synchronized changes needed in AGENTS.md, REVIEW.md, coder routines, and target templates.
This issue carries only the unresolved subset: make the accepted exceptional-implementation and comment floor reliably visible to an independent reviewer running inside a target repository.
Problem
PR #164 places the rule in ystack AGENTS.md/REVIEW.md, both coder routines, and templates/target-CLAUDE.md. That covers ystack itself and the Claude coder. An independent Codex reviewer in another target normally reads that target's AGENTS.md; it is not guaranteed to read optional CLAUDE.md and cannot see control-plane REVIEW.md. The target reviewer may therefore miss the blocking rule.
Outcome
Choose and prove one portable delivery path for target reviewers, such as a target AGENTS.md template/generated section or an explicit reviewer-adapter instruction input. Keep one source of truth and prevent drift between author and reviewer rules.
The delivered target rule must preserve:
- root-cause first and accepted-before-code exceptions;
- isolation, regression test, durable provenance, lifecycle, no-copy/no-public-API;
- non-blanket comment rules and target zero-optional-comments support;
- CI/review/human-merge safety floors;
- candidate changes cannot weaken the review rules used to judge themselves.
Constraints
Parent and approved subset
Follow-up to #163 and PR #164.
The operator-approved scope says:
This issue carries only the unresolved subset: make the accepted exceptional-implementation and comment floor reliably visible to an independent reviewer running inside a target repository.
Problem
PR #164 places the rule in ystack
AGENTS.md/REVIEW.md, both coder routines, andtemplates/target-CLAUDE.md. That covers ystack itself and the Claude coder. An independent Codex reviewer in another target normally reads that target'sAGENTS.md; it is not guaranteed to read optionalCLAUDE.mdand cannot see control-planeREVIEW.md. The target reviewer may therefore miss the blocking rule.Outcome
Choose and prove one portable delivery path for target reviewers, such as a target
AGENTS.mdtemplate/generated section or an explicit reviewer-adapter instruction input. Keep one source of truth and prevent drift between author and reviewer rules.The delivered target rule must preserve:
Constraints