1 files changed, 2 insertions, 2 deletions
diff --git a/.ai/workflows/no-approvals.org b/.ai/workflows/no-approvals.org
index 5f54b96..b4c7fcf 100644
--- a/.ai/workflows/no-approvals.org
+++ b/.ai/workflows/no-approvals.org
@@ -35,7 +35,7 @@ Mode resets when:
 
 The interaction gates that step the workflow back to Craig for an "OK to proceed?" check:
 
-- The commit-message gate in =commits.md= Step 2. Print the final commit message inline, then commit immediately. No "approve / request changes / open in editor" prompt.
+- The commit-message gate in the =publish= skill, Step 2. Print the final commit message inline, then commit immediately. No "approve / request changes / open in editor" prompt.
 - The PR-description gate. Print the final body, then create the PR.
 - The PR-review-reply gate. Print the final reply, then post.
 - "Ready to start?" / "Plan looks like X, proceed?" gates before implementation work begins.
@@ -49,7 +49,7 @@ The engineering-discipline gates protect quality, not Craig's interaction time.
 - =/review-code= against the staged diff before every commit. Critical and Important findings still block. Minor findings still surface. No "proceed anyway" override unless Craig has given it explicitly for this batch.
 - =/voice personal= on every publish artifact (commit messages, PR titles + bodies, PR review comments). The full pattern walk happens. The printed result just doesn't wait for approval.
 - The full test suite + lint + compile before commit (per =verification.md=).
-- Fetch-and-reconcile in =commits.md= Step 0.
+- Fetch-and-reconcile in the =publish= skill, Step 0.
 - Session Log updates per =protocols.org=. Every state-mutating turn writes to =.ai/session-context.org= before the closing message. The log is the crash-recovery anchor while Craig is away. Missing entries lose work.
 - Subagent review-gate cadence (=subagents.md=). Review each subagent's output before the next dispatch.
 - Destructive or irreversible operations per =CLAUDE.md='s "Executing actions with care": force-push, =rm -rf=, dropping a column, dropping a branch, package removal. These need explicit consent regardless of mode. No-approvals is for *interaction* gates, not destructive-action consent.