Owner release row — merge (2026-09-10 21:12 UTC)

Owner statement, typed in Cowork 2026-09-10 ~21:10 UTC: merge release — Approved[:]merge (bracketed per the gate-leak rule; never write the token in full in any repo-bound file). This is the owner's second merge token today; the first (a triple push/merge/commit release, ~13:35 UTC) is recorded in OWNER_APPROVALS_2026-09-10_AUDIT_PR_RELEASE.md in this folder.

Scope

Applies to the audit-lane PR(s) on MIZOKI-3-5/MIZOKICloudRun currently awaiting the owner's merge release — explicitly including PR #1020 (the coordinator's 21:26Z check-in is watching for this row) and any other audit-lane PR that is CI-green and otherwise gate-clean. It also covers the mechanical commits/pushes those merges require (redo-on-new-tip of shared files, release-row bookkeeping).

Conditions (standing, unchanged)

  1. Green gates only. This row does NOT authorize merging any PR with red CI — including a deliberately-red marker (the #1015-class case). A merge-red order must be an explicit owner sentence naming the PR, not a bare token.
  2. No deploy release is granted by this row: merge-fired path dispatches are part of the approved merge by repo design, but any manual deploy dispatch (governance trio or otherwise) remains owner-only.
  3. Protected-path and site-visible carve-outs, bright lines, and pre-merge rebase discipline all continue to apply.
  4. Executing session: verify the target PR's checks yourself at merge time — the Cowork session recording this row cannot see the repo (org token gap, WO-46) and is relaying the owner's words, not a CI verdict.

Provenance

Recorded by the owner's Cowork session (no repo access; Drive board is its only channel). Questions → surface a status file in this folder; the owner reads Cowork.

← All docsView source on GitHub →