Front-gate evolution: manager-debate consensus as the gate for proactive issues (needs explicit sign-off)

[yihanzhu]

Status: APPROVED by the user (2026-06-26) — front-gate rail change authorized

The user explicitly signed off: "approve #49, that's what I want." Implement the consensus-as-gate model.

Goal

Move the front gate up an altitude: the user approves the north star / direction; within an approved north star, Faber⇄Codex manager-debate consensus gates proactive issues (no per-issue user approval). This implements the user's "pursue the north star non-stop; only involve me at milestones/drift" vision, replacing the per-issue front gate for proactive issues.

Acceptance criteria

1. Reconcile the front-gate wording across manager/CLAUDE.md, templates/faber-command.md, README.md, and reviewer/manager-review.md to the consensus-as-gate model for proactive issues:
   • Faber drafts a proactive issue (debating, not ready) → runs scripts/manager-review.sh → on consensus (Faber agrees + Codex PROCEED), Faber removes debating and applies ready and runs the loop — without per-issue user approval.
   • REFINE → another round (cap ~2); DROP / no consensus → close with rationale; default-drop, but LOG vetoed-but-north-star-relevant items.
2. Clarify "never self-approve": Faber alone still cannot approve — but Faber + cross-vendor Codex consensus can, for proactive north-star work. Update the "Never" / front-gate sections accordingly (remove the absolute "never apply ready without the user's per-issue approval" for the proactive path).
3. The user's gate is now at the north-star level: the user approves the north star / direction; Faber pursues it autonomously; the user is involved at north-star achieved, goal drift/transition, and needs-human. State this in manager/CLAUDE.md + README (loop/design).
4. User-directed issues keep the direct path (the user's explicit approval gates them).
5. Preserve every other rail: reviewer read-only/comments-only, CI hard gate, rounds cap, needs-human, the manager-reviewer being veto-only, auto-merge safety (in-session, high-risk→human), the north-star log.

Likely files

• manager/CLAUDE.md, templates/faber-command.md, README.md, reviewer/manager-review.md

Test expectations

• CI green (structure check; docs/prompt-only).

Self-modification note

This deliberately relaxes the front-gate rail (now user-authorized). /faber needs scripts/install.sh re-run; manager/CLAUDE.md takes effect on Faber's next read. Sequenced AFTER #48 and coordinated with #50 (shared files). Call out in the PR.