From 6fa73729b60d410be38fe0829aa1bf31ca9308b1 Mon Sep 17 00:00:00 2001 From: Ben Westgate Date: Tue, 20 Oct 2026 03:46:59 -0500 Subject: [PATCH] docs: Read policy from the current PR target Old topic branches can retain superseded contribution rules, as happened while addressing PR #144 after #152 merged. Require agents to consult the current target-branch contributor guide and AI policy before acting on a PR. State that the tool-neutral policy permits AI-written descriptions and review replies while keeping publication within the user-authorized scope. The maintainer explicitly approved this AGENTS.md patch. Validation: reviewed the exact approved patch, checked referenced local paths, and ran git diff --check. Documentation only; application tests are not applicable. Refs #144 and #152. --- AGENTS.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index fd47d954..d6b72f90 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -86,11 +86,16 @@ Resolve scope questions from the changed code and the invariants first. Ask only if a material security decision remains unclear; identify the decision rather than stopping on general uncertainty. Ask before running a recommended security review. -Follow `docs/developer/AI_POLICY.md` for contributions and `SECURITY.md` for -private vulnerability reporting. Local edits, checks, and atomic commits are -allowed; do not automatically push, open pull requests, write replies, contact -maintainers, or claim authorship. A human publishes contributions. Never commit -to master or push to an open pull request branch without explicit user direction. +Before acting on a pull request, read `CONTRIBUTING.md` and +`docs/developer/AI_POLICY.md` from its current target branch. Follow that merged +contribution policy when the topic branch contains an older version. AI may +write PR descriptions and review replies under the tool-neutral policy. + +Follow `SECURITY.md` for private vulnerability reporting. Local edits, checks, +and atomic commits are allowed. Publish only within the user's authorized scope; +permission to use AI does not itself authorize contacting others. Never claim +independent human authorship, commit to master, or push to an open pull request +branch without explicit user direction. When asked to commit, keep commits focused and independently passing unless the user explicitly requests a combined commit. Use an imperative subject of at