Director Review and Publication
Director review applies only to a new document after its Content PR has merged to main and deployed as a draft. An administrator starts the session:
/review start-director <doc_location> <version|unversioned> <login>
The controller creates a clearly labeled Director Review PR. Its base is a synthetic main snapshot with only the selected document removed, while its head is the original full snapshot. This makes the complete document reviewable in GitHub without merging the synthetic baseline. The preview stays tied to that snapshot, so unrelated changes on main do not move the review target.
The named Director reviews the full rendered document and source, leaves comments or suggestions, and submits an approval when it is ready. Corrections remain in the Director Review PR. Discussion threads are useful records but are not workflow gates.
Approval automatically prepares a separate Publication PR. An administrator may instead waive Director review:
/review waive director [reason]
The reason is optional. A waiver is recorded and displayed as waived, never as an approval, and still prepares the Publication PR.
The Publication PR applies only the selected document, source, and related assets to current main, removes draft status, and links to the Director outcome. It is an administrator delivery step, not another Director round. Conflicting intervening changes stop publication for administrator reconciliation without resetting completed review:
/review retarget <doc_location> <version|unversioned>
After successful publication deployment, the controller retires the stable Director preview and closes the review lifecycle. An administrator can cancel an unfinished session with /review cancel; cancellation preserves its history and leaves the live document unchanged.