From d99dc11e4de3d86f8a8ece89c0d059175c0d57e6 Mon Sep 17 00:00:00 2001
From: "omegent-app[bot]" <306514130+omegent-app[bot]@users.noreply.github.com>
Date: Sat, 15 Aug 2026 14:00:11 +0000
Subject: [PATCH] docs(agents): stop treating every edit as a PR handoff

The old "required handoff" trigger fired on intermediate, uncommitted work.
Publication (commit/rebase/push/PR) now requires an explicit user request,
a specific VCS action, or another workflow in this file such as Discord-originated work.

Co-authored-by: Enrico Polanski <16064771+enricopolanski@users.noreply.github.com>
---
 AGENTS.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index 8d5bc1b6849e..c036dc0eb2b2 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -167,9 +167,11 @@ whole branching model. See
   work dir (`~/.t3/compose-work`, not tmpfs `/tmp`) before install. See
   [docs/fork-stack.md](./docs/fork-stack.md) ("Integration overlay compose and lockfiles").
 
-## Pull requests (required handoff)
+## Pull requests (when publishing)
 
-When implementation work for a user request is done (code, docs, config — not pure Q&A):
+Do not commit, rebase, push, or open/update a PR merely because an edit is complete. Do those things only when the user explicitly requests publication or the specific version-control action, or when another workflow in this file explicitly requires it (for example, Discord-originated work). A request to change code, docs, or config does not by itself authorize publication.
+
+When publication or a PR handoff is in scope:
 
 1. **Commit** the changes on a feature branch cut from `fork/dev`.
 2. **Open or update a PR against `fork/dev`** before handing off — for every kind of work, including