Add issue ownership guidance to AGENTS.md (#754)

7990021bd3d9821a6c3695f7a5e2d3c013f6444e · 2026-05-08 16:05:15 -0700 · Trevin Chow

Files touched

M AGENTS.md

Diff

commit 7990021bd3d9821a6c3695f7a5e2d3c013f6444e
Author: Trevin Chow <trevin@trevinchow.com>
Date:   Fri May 8 16:05:15 2026 -0700

    Add issue ownership guidance to AGENTS.md (#754)
---
 AGENTS.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index fddd527b..002cf7d3 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -96,6 +96,9 @@ See [`docs/GLOSSARY.md`](docs/GLOSSARY.md) for the full term table and disambigu
 
 **`Printer` (slug @handle) vs `PrinterName` (display) — parallel pair, distinct from Owner/OwnerName.** `APISpec` and `CLIManifest` carry a second slug-vs-display pair for printer attribution. `Printer` is the GitHub @handle of the human who originally ran the press (e.g. `mvanhorn`), drives the per-CLI README byline link and the library-side registry attribution, and reads `git config github.user`. `PrinterName` is the prose-shaped display name (e.g. `Matt Van Horn`), rendered as the README byline parenthetical, and reads raw `git config user.name`. Resolution is tiered for both: the existing manifest wins over git config, so regens by other contributors do not overwrite the original printer (mirrors `resolveOwnerForExisting`'s preserve-on-regen guarantee). When `Printer` is unset at `Generate()` time, the generator emits a stderr warning and leaves it empty; the publish skill (Step 6) refuses to publish empty or literal `"USER"`/`"user"` sentinel values. Distinct from `Owner`/`OwnerName` (which carry the API-spec / wrapper-author identity); the printer is the human, the owner is the API vendor or wrapper author.
 
+## Issue Work Ownership
+When starting work from a GitHub issue, claim the issue before implementation: assign it to yourself, or to the GitHub user you are explicitly working on behalf of. If the issue already has an assignee, treat that as active ownership until you can determine otherwise from recent activity or direct confirmation. For a plausibly stale assignment, ask the current assignee by tagging them in an issue comment before taking over or reassigning the issue.
+
 ## Commit Style
 Format: `type(scope): description`. Both type and scope are required.

← c332b534 fix(cli): route live cache through typed upserts (#751) · back to Cli Printing Press · fix(cli): infer bearer auth from prose-only specs (#753) 92d303ac →