merge 7c09200b-2b88-4b7a-bbf3-c07b1ff10bf4

diff --git a/.forge/wiki/docs/AGENTS.md b/.forge/wiki/docs/AGENTS.mdindex abe7837..f42fc76 100644--- a/.forge/wiki/docs/AGENTS.md+++ b/.forge/wiki/docs/AGENTS.md@@ -28,10 +28,12 @@ into `$CARGO_HOME/bin` (else `~/.cargo/bin`).2828 ## Reading order2929 3030 1. `AGENTS.md` — this file31-2. `OUTLINE.md` — the what/why; read once before any work32-3. `PLAN.md` — the how/when; find your chunk, obey its contract exactly31+2. `.forge/wiki/docs/OUTLINE.md` — the what/why; read once before any work32+3. `.forge/wiki/docs/PLAN.md` — the how/when; find your chunk, obey its contract exactly3333 4. `spec/` at repo root — frozen schema (exists after M0); the only source of truth for formats3434 35+Canonical agent contract: `f0rge --skill` (single source of truth; skill.md body == SKILL_TEXT, golden test; 1000B budget).36+3537 ## Philosophies (non-negotiable)3638 3739 - **Bitter lesson.** The forge stays dumb; agent intelligence does the work.@@ -52,8 +54,9 @@ into `$CARGO_HOME/bin` (else `~/.cargo/bin`).5254 - **CI is just scripts.** Steps are executable files in filename order;5355   first nonzero exit is the verdict. Posture (local/docker) is explicit,5456   never implicit.55-- **Merges are agent work.** `f0rge merge` applies, runs CI, lists what56-  conflicted, stops. Resolution is your job, not machinery's.57+- **Merges are agent work.** `f0rge merge` CI-gates the patch in a scratch worktree, NEVER58+  touches main or branches; the ORCHESTRATOR fast-forwards the applied sha and deletes59+  the branch; conflicts are reconciled by the agent; you do not merge your own work onto main.5760 - **One owner, many agents.** You are never the authority. The owner — or5861   an agent they explicitly delegated to — merges. You do not merge your own5962   work onto main.@@ -87,8 +90,8 @@ into `$CARGO_HOME/bin` (else `~/.cargo/bin`).8790   offending file name.8891 - Output: `--json` compact, fixed field order documented in repo-root `spec/`; empty8992   result is `[]` or `{}`, never prose. Human mode is a thin aligned view90-  of the same data. Hard budgets: PLAN.md §M2 table — `f0rge` ≤ 12 lines,91-  `-h` ≤ 8 lines, `--skill` ≤ 30 lines, errors 1 line.93+  of the same data. Hard budgets: PLAN [M2] table in wiki — `f0rge` ≤300B/12ln,94+  `-h` ≤250B/8ln, `--skill` ≤1000B/30ln, errors 1 line.9295 - Tests: golden fixtures + e2e against temp repos; every SEC fixture from9396   PLAN §5 has a test; budget tests byte-count output.9497 - Keep it boring: std over crates, fewer deps over more, dumb over clever.