v1.36.291

Staged reviewers: review-feedback start accepts a v2 contract (leerness.review-feedback-contract/v2) with 1 to 5 ordered stages, for example a first and a final reviewer, each with its reviewer and maxRounds. The stages review the shared frozen scope and criteria in order, and each applies the single-reviewer rules to its own rounds and budget. A NO GO is re-reviewed by the stage that gave it; the next stage starts once it passes, and the review is GO when the last stage passes. The same model may serve several stages, but a v2 round names its reviewerSession, which cannot be a session another stage used (feedback_session_reused) or the session that recorded the reviewed implementation attempt (feedback_session_not_independent). Sessions are declared strings, not authenticated. agents record reviewed --feedback-round binds the latest round of that round's stage. Single-reviewer contracts and their history are unchanged; the 46 existing review-feedback probe cases pass unmodified.

Route to GO: human output of review-feedback start|submit|show is written in the project language (--language ko|en, then LEERNESS_LANG, the project manifest, Korean); it was English only. Section markers, status values and JSON text are the same in every language, and the English report outside the new block is byte-identical to 1.36.290 for six single-reviewer states. The report begins with a [GO_ROUTE] checklist. It lists the stage and reviewer, the rounds used and reviews left, each open blocker's required outcome with every acceptance check marked passed or open with its latest status and evidence, the fixed criteria and the regression check, the owner decisions when the review stopped, and otherwise numbered next steps with the agents record commands. JSON adds goRoute and nextRoundTemplate, a skeleton of the next round. Its placeholders and empty evidence lists are invalid on purpose: each of its 12 placeholders (13 in a staged review) is rejected on its own, and the checks of already resolved issues come prefilled as passed.

Reviewer guidance (AGENTS.md, the review checklist, reviewer role and dispatch prompts) asks for TO_GO as a numbered checklist in fix order: location, evidence and how to reproduce, the required behaviour, each check with how it will be verified and the evidence needed, then the pending criteria and regression check, the reviews left and the next steps. It describes staged reviewers and their session rule. A fresh English project's context budget grows by 219 tokens in standard mode (10,849 of 12,000) and by 218 in minimal mode (1,825 of 2,200). Both totals include the Korean-Windows code-page notice that handoff prints on this machine, about 70 tokens that the 1.36.290 figures did not include.