Update

dot_pi/agent/AGENTS.md

@@ -18,8 +18,13 @@
 
 ## Delegation
 
+- Do not perform reconnaissance, behavior tracing, external documentation lookup, or design analysis directly in the main session when a matching agent exists. Inline `bash`/`read`/`webfetch`/`websearch` work is only acceptable for trivial lookups and for single-file, behavior-obvious changes.
 - Default to `worker` for non-trivial implementation. Give it the desired outcome, constraints, and verification criteria; it may locate code, investigate nearby behavior, and make routine implementation decisions. Keep direct main-agent edits for trivial changes or work the worker cannot safely perform with its available tools.
-- After `explore` or `architect` resolves an uncertainty, hand implementation to `worker` rather than implementing the plan in the main session. Return reviewer findings to `worker` for fixes when possible. Escalate unresolved product decisions, cross-cutting design, or difficult root causes instead of forcing a worker to guess.
+- Prefer delegating to `explore` before editing any file not already read in full this session when the change touches more than one module, or when the root cause of a bug is not yet established.
+- Prefer delegating to `research` before relying on any external API, CLI flag, protocol, or version-specific behavior that has not been confirmed in this session; do not answer such questions from memory or with direct `webfetch`/`websearch`.
+- Prefer delegating to `architect` before multi-file changes, schema or API changes, migrations, or any non-trivial design decision; skip only for single-file, behavior-obvious edits.
+- After `explore`, `research`, or `architect` resolves an uncertainty, hand implementation to `worker` rather than implementing the plan in the main session. Return reviewer findings to `worker` for fixes when possible. Escalate unresolved product decisions, cross-cutting design, or difficult root causes instead of forcing a worker to guess.
+- Prefer delegating to `reviewer` for large or multi-file changes, and in particular when `architect` was involved in the design; for small or behavior-obvious changes, reviewer review is usually not worth the overhead.
 - Unless currently acting as the delegated `submitter` agent, MUST delegate every requested Git commit, Git push, or Perforce submit to `submitter` through tasker after implementation and validation are complete.
 - Unless currently acting as `submitter`, NEVER run `git commit`, `git push`, or `p4 submit` directly.
 - When the user requests individual commits, implement and validate each unit, then invoke `submitter` sequentially before starting the next unit.
@@ -27,7 +32,7 @@
 
 ## Code Quality
 
-- Inspect relevant code before editing. Start with search, symbols, and targeted reads.
+- Inspect relevant code before editing. Start with search, symbols, and targeted reads for trivial changes; for anything broader, follow the mandatory `explore`/`architect` delegation rules above instead of inspecting inline.
 - Read a file in full before making wide-ranging changes to that file or when surrounding context affects correctness.
 - For investigations and audits, read complete files only when needed to validate behavior; do not rely solely on search snippets.
 - Avoid rereading unchanged content already present in the current context.

dot_pi/agent/settings.json

@@ -1,5 +1,5 @@
 {
-  "lastChangelogVersion": "0.99.2",
+  "lastChangelogVersion": "1.0.0",
   "theme": "system",
   "defaultProvider": "opencode-go",
   "defaultModel": "glm-5.3-flash",
@@ -20,7 +20,8 @@
     "git:github.com/pmcc/pi-tasker",
     "git:github.com/pmcc/pi-web",
     "git:github.com/pmcc/pi-swatches",
-    "git:github.com/pmcc/pi-chromium"
+    "git:github.com/pmcc/pi-chromium",
+    "git:github.com/pmcc/pi-annoter"
   ],
   "deviceId": "72eeb731-7b7a-499a-a852-2f6bb0cbeb98"
 }