@agentsfleet/orly 0.5.0

package/docs/DISPATCH_REVIEW_DISPOSITION.md

@@ -0,0 +1,65 @@
+# Dispatch Review — Finding Disposition
+
+Date: Jun 04, 2026
+Companion to `DISPATCH_ARCHITECTURE.md` (v2). Source: the 7-lens adversarial
+CTO review (38 confirmed, 22 refuted) + the v2 coverage check.
+
+Every **confirmed** finding, with its v2 disposition — so the 38 that survived
+cross-examination are tracked in the repo, not just in an ephemeral run log.
+
+- **resolved** — v2 has a concrete mechanism that closes it (section cited).
+- **partial** — v2 SPECIFIES the fix; implementation is pending (**Stage 0** /
+  §13 acceptance criteria). NOT a doc defect: the v1-era WIP code (`lib.sh`,
+  `write_zig.sh`) has not yet been reworked to the spec. The 17 partials ARE
+  the Stage-0 backlog.
+- **Refuted (22, excluded here):** raised criticisms the skeptic layer disproved
+  (bogus / already-handled / speculative). Not real problems — not tracked.
+
+Coverage: **21 resolved · 17 partial · 0 unresolved · 0 regressed** (of 38).
+Severity: P0 9R/10P · P1 10R/6P · P2 2R/1P.
+
+| # | Sev | Dimension | Finding | v2 status | v2 §refs |
+|---|---|---|---|---|---|
+| 1 | P0 | cross-repo | Dissolving docs/gates/ hard-fails the repo's own audit (gate-parity check) — the determinism | resolved | §0, §13, §8, §9 |
+| 2 | P0 | cross-repo | Dissolving gates breaks the LLM-judge eval golden-set the proposal claims to extend | partial | §13, §6.2, §8 |
+| 3 | P0 | cross-repo | dispatch/write_zig.sh delegates to leaf scripts that cannot run where the dispatch lives —  | partial | §0, §10, §10.3, §13, §6.3, §7 |
+| 4 | P0 | determinism-feasibility | `--staged` file discovery and leaf-check scope read two different git repos — CWD vs RESOLVE | partial | §0, §10, §10.4, §7 |
+| 5 | P0 | drift-coherence | Coherence audit proves symbol presence, not rule enforcement — the central anti-drift claim  | resolved | §0, §1, §12, §2, §3, §3.1, §4, §6.1, §6.3 |
+| 6 | P0 | drift-coherence | Missing leaf helper returns exit 0 with a 🟣 row — a deterministic check silently becomes a n | partial | §0, §10, §12, §14, §6.3 |
+| 7 | P0 | drift-coherence | Dissolving docs/gates/ and renaming ZIG_RULES.md/BUN_RULES.md detonates the in-repo invarian | resolved | §0, §11, §8, §9 |
+| 8 | P0 | ergonomics-robustness | Invariance audit's gate-parity check hard-fails the moment docs/gates/ is dissolved — the ve | resolved | §0, §13, §8, §9 |
+| 9 | P0 | ergonomics-robustness | DOTFILES_RESIDENT and seven referencing docs still point at docs/ZIG_RULES.md / BUN_RULES.md | partial | §6.5, §8 |
+| 10 | P0 | ergonomics-robustness | dispatch_run_helper returns 0 when the leaf script is absent — silent false-green in the rep | partial | §0, §10.2, §10.3, §12, §14, §6.1, §6.3 |
+| 11 | P0 | eval-loop | §6.2 "extend existing audits/llmevals/" is a category error — the existing harness is an ex | partial | §0, §13, §6.2, §6.3 |
+| 12 | P0 | eval-loop | Dissolving docs/gates/ deletes the context the existing llmevals harness embeds in every pro | resolved | §13, §14, §6.2, §8, §9 |
+| 13 | P0 | eval-loop | agents-md.sh is hard-bound to docs/gates/ in four checks; dissolving the directory mak | resolved | §13, §8, §9 |
+| 14 | P0 | gate-dissolution | Dissolving docs/gates/ hard-fails the no-override Invariance Suite Gate — the audit asserts  | partial | §0, §13, §5, §8, §9 |
+| 15 | P0 | gate-dissolution | Cross-cutting non-language gates have no coherent home in a per-language facade model — and  | resolved | §0, §5 |
+| 16 | P0 | gate-dissolution | "merge-then-delete, nothing unique dies" has no proving mechanism — the coherence audit chec | partial | §13, §14, §2, §6.5, §9 |
+| 17 | P0 | yellow-mechanism | Dissolving docs/gates/ detonates the deterministic invariance audit — every gate-parity, gat | resolved | §0, §13, §8, §9 |
+| 18 | P0 | yellow-mechanism | 🟡 JUDGMENT has zero machine backstop and the one prose backstop (CONFORM) has no row  | partial | §0, §1, §11, §16 |
+| 19 | P0 | yellow-mechanism | DOTFILES_RESIDENT + cross-reference + cross-agent-eval all pin docs/ZIG_RULES.md & BUN_RULES | resolved | §8, §9 |
+| 20 | P1 | cross-repo | §11 cross-repo blast-radius enumeration is materially incomplete — it omits the audit/eval/s | resolved | §0, §10, §11, §13, §6.3, §8 |
+| 21 | P1 | cross-repo | The negative-test harness (test-audit) copies and asserts on specific gate bodies that the d | resolved | §13, §8, §9 |
+| 22 | P1 | cross-repo | audits/agents-md.md hardcodes docs/gates/ paths and a 'Scope (M70)' per-body requirement; d | partial | §6.5, §8 |
+| 23 | P1 | cross-repo | The dispatch absorbs the FILE cap but silently drops the function/method length sub-gate the | resolved | §0, §13, §5 |
+| 24 | P1 | determinism-feasibility | 🟡 'blocks the turn not the script' has no machine enforcement — the determinism anchor canno | partial | §0, §11, §3.1, §6.2 |
+| 25 | P1 | determinism-feasibility | Merge-then-delete of 20 gate cards into prose will silently drop machine-relevant trigger de | partial | §0, §13, §5, §6.3, §6.5, §9 |
+| 26 | P1 | drift-coherence | llmevals (latent-space eval) loses its rule context the moment gates dissolve — and the prop | resolved | §13, §14, §6.2, §8, §9 |
+| 27 | P1 | drift-coherence | 'Merge-then-delete, nothing unique dies' is an unverifiable promise — no mechanism diffs gat | resolved | §0, §12, §2, §6.5, §9 |
+| 28 | P1 | ergonomics-robustness | Hook path mismatch: proposal wires .git/hooks/pre-commit but the canonical, audited hook is  | resolved | §0, §13, §14, §7, §8 |
+| 29 | P1 | eval-loop | 🟡 YELLOW is redefined to mean the opposite of its established meaning in HARNESS_VERIFY_OUTP | resolved | §0, §11, §12, §13, §3.1, §4, §8 |
+| 30 | P1 | eval-loop | dispatch-coverage.sh asserts a scenario EXISTS, not that it is discriminating — one pa | partial | §3, §6.1, §6.3 |
+| 31 | P1 | gate-dissolution | llmevals harness cat's docs/gates/*.md into every model prompt under set -e — dissolving the | resolved | §13, §14, §6.2, §6.5, §8 |
+| 32 | P1 | gate-dissolution | DOTFILES_RESIDENT and EXECUTE_DOC_READS still hard-reference docs/ZIG_RULES.md and docs/BUN_ | resolved | §0, §11, §13, §8, §9 |
+| 33 | P1 | gate-dissolution | The 🟡-blocks-the-turn-not-the-script mechanism has no enforcer — it relies on agent self-rep | partial | §0, §11, §16, §3.1, §6.2 |
+| 34 | P1 | yellow-mechanism | The coherence audit (the proposal's keystone) does not exist and is under-specified to the p | resolved | §13, §3, §6.3 |
+| 35 | P1 | yellow-mechanism | Rule-extension protocol is now violated by the proposal's own structure and the gloss map re | partial | §13, §6.4, §8 |
+| 36 | P2 | cross-repo | Gloss map has a silent FLL/LENGTH duplication and the architecture-doc gloss table omits hal | resolved | §12, §13, §6.3, §6.4 |
+| 37 | P2 | ergonomics-robustness | pre-commit latency: 5 dispatch each shell out to git diff + multiple full-tree audits on ev | partial | §7 |
+| 38 | P2 | eval-loop | dispatch_run_helper calls ufs.sh --all on the WHOLE tree per edit, contradicting the " | resolved | §7 |
+
+**Refuted ≠ dropped.** The 22 refuted findings were independently disproven by
+a skeptic agent (try-to-refute pass); excluding them is the quality filter, not
+an oversight. As Stage 0 reworks the code + adds the eval/audit scripts, the
+partial rows flip to resolved.

package/docs/DOCUMENTATION_RULES.md

@@ -0,0 +1,209 @@
+# Documentation rules
+
+> Parent: [`../AGENTS.md`](../AGENTS.md) §Documentation voice. Read this before
+> any narrower guide such as `CHANGELOG_VOICE.md` or before editing documentation
+> about the dispatch model.
+
+These rules govern customer-facing `agentsfleet` documentation. They keep pages
+short, accurate, and usable by a first-day reader. Compliance is binary. A
+rejection cites the Documentation (DOC) rule identifier that failed.
+
+## Scope and precedence
+
+- **DOC-S1 — Published pages.** A standalone Markdown JSX (MDX) file listed in
+  `docs.json` follows every applicable rule in this document.
+- **DOC-S2 — Generated API pages.** OpenAPI source follows the reference-page
+  intent through summaries, descriptions, parameters, examples, responses, and
+  stable errors. Generated pages do not need MDX front matter.
+- **DOC-S3 — Fragments.** `snippets/*.mdx` files are reusable fragments. They
+  follow language and content rules, but not page front matter or skeletons.
+- **DOC-S4 — Changelog archive.** `changelog.mdx` follows
+  `CHANGELOG_VOICE.md`. Historical entries are not rewritten and do not follow
+  the page skeletons below.
+- **DOC-S5 — Repository terms win.** Write the product as `agentsfleet`. Use the
+  repository glossary and content boundaries when they are stricter than this
+  document.
+- **DOC-S6 — Source wins.** Runtime code is the source of truth. OpenAPI and the
+  command-line interface follow runtime behavior. Published pages follow all
+  three.
+
+## Required front matter
+
+Every published page carries these fields:
+
+```yaml
+type: tutorial | how-to | reference | explanation | troubleshooting
+audience: user | operator | contributor
+verified: YYYY-MM-DD
+product_version: x.y.z
+executable: true | false
+```
+
+- **DOC-F1 — Valid values.** Use only the values shown above.
+- **DOC-F2 — Freshness.** `verified` records the last source check, not the last
+  prose edit. `product_version` matches the repository's configured docs
+  version.
+- **DOC-F3 — Executable pages.** Set `executable: true` only when the page
+  contains runnable commands that the repository checker can validate.
+
+## Required page skeletons
+
+Use the headings in the listed order. The page may add a heading only when the
+task cannot be completed clearly without it.
+
+| Type | Required headings, in order |
+|---|---|
+| tutorial | What you will build → Before you begin → Steps → Verify it works → What you learned → Related pages |
+| how-to | What this does → Before you begin → Steps → Verify it works → Common problems → Remove or undo → Related pages |
+| reference | Synopsis → Example with output → Options → Errors → Related pages |
+| explanation | What it is → Why it exists → How it behaves → Limits → Related pages |
+| troubleshooting | Symptom → Why it happened → How to fix it → How to prevent it |
+
+- **DOC-P1 — One purpose.** Pick the page type that matches the reader's goal.
+  Do not mix a tutorial and full reference on one page.
+- **DOC-P2 — Honest empty sections.** If a required section does not apply,
+  state that in one sentence. Do not invent behavior to fill a heading.
+
+## Language
+
+1. **DOC-01 — First-day reader.** Assume no product knowledge.
+2. **DOC-02 — Short sentences.** Use one idea per sentence. Prose sentences have
+   at most 25 words.
+3. **DOC-03 — Short paragraphs.** Use at most three sentences per paragraph.
+4. **DOC-04 — Active voice.** You act, or `agentsfleet` acts. Do not write “the
+   system”.
+5. **DOC-05 — Plain words.** Do not use “utilise”, “facilitate”, “leverage”,
+   “orchestrate”, “instantiate”, “terminate”, “provision”, “execute”, “persist”,
+   “hydrate”, or “artifact”. Prefer “use”, “help”, “manage”, “create”, “stop”,
+   “run”, “save”, “load”, or “file”.
+6. **DOC-06 — Precise meaning.** Never simplify a sentence if the shorter form
+   changes its meaning. Define a necessary technical term in the glossary.
+7. **DOC-07 — No marketing words.** Do not use “powerful”, “revolutionary”,
+   “enterprise-grade”, “seamless”, “cutting-edge”, “robust”, “next-generation”,
+   “world-class”, or “intelligent”.
+8. **DOC-08 — Explain automation.** “Automatically” and “as needed” must state
+   the trigger, timing, and effect.
+9. **DOC-09 — One name.** Use one canonical name for each concept. The project
+   glossary wins.
+10. **DOC-10 — Expand abbreviations.** Expand each non-obvious abbreviation once
+    per page, such as Secure Shell (SSH).
+11. **DOC-11 — Customer language.** State the user-visible action. Keep internal
+    queue, lease, process, and storage mechanics out of customer pages.
+12. **DOC-12 — Clear referents.** Every pronoun names one clear subject. Repeat
+    the noun when the reference could be ambiguous.
+13. **DOC-13 — Reading level.** Target grade 8 prose. Code and tables are exempt.
+14. **DOC-14 — One dialect.** Use one spelling dialect across all pages.
+
+### DOC-14b — No AI slop
+
+Cut these on sight. They read as machine prose and they hide the point.
+
+| Pattern | Example to kill | Write instead |
+|---|---|---|
+| Binary contrast | "This is not X. It's Y." | State Y. |
+| Throat-clearing | "Here's the thing," "Let me be clear" | The point. |
+| Faux-insight | "What most people get wrong" | The claim, standing alone. |
+| Colon reveal | "The detail that makes it work: a second pass." | A plain sentence. |
+| Superficial `-ing` | "adds search, highlighting our commitment" | "adds search, so you find old drafts." |
+| Importance puffery | "marks a pivotal moment" | The fact; let the reader judge. |
+| Weasel attribution | "experts agree", "studies show" | Name the source or cut the claim. |
+| Fake-profound kicker | a closing metaphor or mic-drop | End on the last concrete sentence. |
+| Summary recap | "In conclusion", "Overall" | Stop. The reader was just there. |
+
+Also banned, on top of DOC-05 and DOC-07: delve, foster, elevate, harness,
+supercharge, embark, ever-evolving, tapestry, realm, paradigm shift, game
+changer. Em dashes are not a rhythm crutch: none in short copy, at most two per
+long page, and only where they beat a comma or a period.
+
+## Content
+
+15. **DOC-15 — Command output.** Every runnable command is followed by its
+    expected output. Mark changing output as `<varies>`.
+16. **DOC-16 — Placeholders.** Use `<UPPER_SNAKE>` placeholders. State where each
+    value comes from in the sentence before or after the example.
+17. **DOC-17 — Fake credentials.** Example credentials are clearly fake, such as
+    `af_test_00000000`.
+18. **DOC-18 — Destructive actions.** Warn before the command. State what is
+    lost. Show `--dry-run` first when the command supports it.
+19. **DOC-19 — Complete options.** Every option states its effect, default,
+    unit, and valid range. Write “none” when no default or range exists.
+20. **DOC-20 — Resource lifecycle.** Every resource states who creates, owns,
+    and deletes it. State the limit and the behavior at that limit.
+21. **DOC-21 — Failure behavior.** Every feature states what fails, what retries,
+    the retry count and delay, what data is lost, and what survives.
+22. **DOC-22 — Audience boundary.** User pages state guarantees, not internals.
+    Operator pages state exact dependencies and versions.
+23. **DOC-23 — Units and time.** Numbers carry units. Dates use ISO 8601. Times
+    use Coordinated Universal Time (UTC).
+24. **DOC-24 — Stable errors.** Every product error has a stable Identifier (ID)
+    and an anchor that explains why it happened, how to fix it, and how to
+    prevent it.
+
+## Structure
+
+25. **DOC-25 — Heading order.** Use one level-one (H1) heading. Do not skip heading levels.
+    Page renames require redirects.
+26. **DOC-26 — Procedures.** Use numbered lists. Each item carries one action.
+    Each runnable block carries one command.
+27. **DOC-27 — Tables.** Use tables for comparisons. Never put procedures in a
+    table.
+28. **DOC-28 — Fence intent.** Use `bash` for runnable commands, `yaml` or `json`
+    for configuration, and `text` for output.
+29. **DOC-29 — Self-contained task.** A page completes its stated task alone.
+    Links add depth and never hide a prerequisite.
+30. **DOC-30 — User interface paths.** Write paths as **Settings → API Keys →
+    Create Key**. Screenshots never carry unique instructions.
+
+## Freshness
+
+31. **DOC-31 — Required version fields.** `verified` and `product_version` are
+    mandatory. A page two releases stale is rejected until rechecked.
+32. **DOC-32 — Runnable examples.** Repository checks run the fenced commands on
+    every `executable: true` page for each release. A failing example blocks the
+    release.
+
+## Enforcement
+
+33. **DOC-33 — Mechanical checks.** Pre-commit checks block banned words,
+    undefined abbreviations, long sentences, long paragraphs, missing front
+    matter, missing or unordered sections, command blocks without output,
+    options without defaults, heading violations, and procedures in tables.
+34. **DOC-34 — Review checks.** Review checks one-idea sentences, pronoun
+    clarity, resource lifecycle, failure behavior, implementation leaks, and
+    meaning preserved by simplification.
+35. **DOC-35 — Exceptions.** A page may list at most three exceptions in front
+    matter. Each uses `lint-ignore: DOC-NN — reason`. Review recurring exceptions
+    as a rule defect instead of copying them forward.
+
+## Reading joy — contributor architecture sets
+
+These apply to contributor-facing architecture sets (`docs/architecture/**`,
+`AUTH*.md`, `development.md`) in product repos, on top of everything above
+where the two do not conflict. They exist so those pages stay a pleasure to
+read, not just correct.
+
+36. **DOC-36 — Answer first.** A Facts table or a "read this when" line opens
+    the page. Reasoning follows the answer, never the other way around.
+37. **DOC-37 — Questions are the index.** The set's index maps a reader's
+    question or symptom to one section. No two index rows share a target.
+38. **DOC-38 — One fact, one home.** A fact lives on the page that owns it;
+    every other mention is a pointer. Nothing to reconcile, nothing to drift.
+39. **DOC-39 — Pictures where structure beats prose.** Topology gets a box
+    diagram, flows get a sequence, comparisons get a table, reasoning stays
+    prose. A diagram's borders align; a broken box is a defect, not a style.
+40. **DOC-40 — Color that means something.** Typed callouts (note, tip,
+    important, warning) for asides by kind; real brand marks where a product
+    is named; concept emoji only in tables and lists. Never inside headings —
+    specs cite heading text verbatim.
+41. **DOC-41 — Errors say what to do.** A failure is a code, its cause, and
+    the exact fix command, linking to the published error registry when the
+    user-facing page carries more.
+42. **DOC-42 — Same zoom, named lens.** When one story is told at several
+    zoom levels, the page names each lens and when to read it, and the lenses
+    do not repeat each other.
+
+## Closing standard
+
+A page is complete when a human and a Large Language Model (LLM) can answer how,
+what, and why without guessing. The source check, page check, and reviewer must
+all pass.

package/docs/EXECUTE_DOC_READS.md

@@ -0,0 +1,29 @@
+# EXECUTE — Doc reads by trigger
+
+> Parent: [`../AGENTS.md`](../AGENTS.md) §EXECUTE. Each dispatch entry's trigger header reads its façade — sectioned: scan headers, read the sections the diff shape touches; this table is the canonical trigger→doc map, enforced by the `📖 DOC READ: <path>` proof-line.
+
+Every triggered document requires one `📖 DOC READ: <path>` proof-line **per turn** — before the turn's first triggering edit — citing §N applied, or the cited-skip variant when nothing in the doc applies. Auto-mode and prior-turn reads never excuse the line (already-loaded sections are cited, not re-read); a triggering turn without the line is a violation regardless of whether the edits happen to be clean.
+
+| Trigger | Read |
+|---|---|
+| Always (universal) | `docs/greptile-learnings/RULES.md` — at EXECUTE start read the Rule-code gloss legend + the sections named by the spec's "Applicable Rules" list (canonical); the full file belongs to `/review`, not EXECUTE. On sub-task shape change, section-scan (`grep -n "^## "`) and read only newly-touched sections, cited in the proof-line — never the full file again. |
+| `core/**`, `packs/**`, `schemas/**`, `src/**`, `registry.json`, agent-home instruction links, repository rules synchronization, or governance hooks | `dispatch/edit_rules.md` + `docs/ORLY_ARCHITECTURE.md` — canonical sources, profiles, snapshots, refusal boundaries, and evidence. |
+| Lifecycle stage transition (CHORE(open)/PLAN/CHORE(close)/LAND, worktree setup, milestone bootstrap) | `dispatch/lifecycle.md` — the entered stage's runbook section only (section-scan; fires on the transition itself, not on an Edit/Write). |
+| Any source file (cross-cutting authoring) | `dispatch/write_any.md` — length, logging, milestone-id, error-registry, UFS, greptile read, legacy-workaround family. |
+| Spec's "Applicable Rules" | Each rule (canonical). Missing → the cross-cutting codes of `dispatch/write_any.md` are the floor; surface omission. |
+| `*.zig` | `dispatch/write_zig.md`. ZIG GATE per edit. |
+| `*.ts`/`*.tsx`/`*.js`/`*.jsx` | `dispatch/write_ts_adhere_bun.md` — TS FILE SHAPE DECISION (§1) at PLAN, const/import/Bun-primitive discipline, anti-patterns. |
+| `*.rs` | `dispatch/write_rust.md` — ownership, error variants, feature combinations, and contention tests. | <!-- oracle-packs:language.rust -->
+| `*.py` | `dispatch/write_python.md` — parsing boundaries, resource ownership, and specific exceptions. |
+| `*.sh` | `dispatch/write_shell.md` — quoting, array arguments, cleanup, input safety, and shell compatibility. |
+| `*.mdx` | `dispatch/write_mdx.md` — structure, front matter, links, code fences, accessibility, and Mintlify isolation. | <!-- oracle-packs:language.mdx -->
+| Log emit (any language; see LOGGING GATE triggers) | `docs/LOGGING_STANDARD.md` — wire format (logfmt), severity ladder, error-code embedding, scope/event discipline, PII redaction, §10A tightenings. LOGGING GATE per edit. |
+| Lifecycle method in `*.zig` (`init|deinit|close|release|destroy|shutdown|dispose|free`) | `docs/LIFECYCLE_PATTERNS.md` — init/deinit pairing, errdefer placement, allocator ownership, defer/errdefer mutual exclusion, §10A tightenings. LIFECYCLE GATE per edit. |
+| `src/agentsfleetd/http/handlers/**` or `public/openapi/**` | `docs/REST_API_DESIGN_GUIDELINES.md` — Quick Checklist; §1–§5 (URL/method/body/response/error), §6 (OpenAPI), §7 (6-place route registration), §8 (`Hx` handler interface), §10 (pre-PR gates). |
+| `ui/packages/**/*.{tsx,jsx,css}`, `app/**/*.{tsx,jsx,css}`, `components/**/*.{tsx,jsx,css}`, repo-root `globals.css`, or any file changing visual tokens / motion / typography | `DESIGN.md` (repo root) or `docs/DESIGN_SYSTEM.md` — whichever the repo carries. Design system source of truth: typography stack, color tokens, the single accent and its currency rule, motion signature, spacing/density, component principles, CLI palette mapping. DOC READ proof-line per turn. |
+| `*.tsx` / `*.jsx` under `ui/packages/{app,website}/` | `dispatch/write_ts_adhere_bun.md` (Design Tokens) — token-utility table (text/tracking/leading/max-w/min-w/spacing/motion/radius/color). DESIGN TOKEN GATE fires per edit; audit via project-side `audits/design-tokens.sh`. |
+| Auth-flow | `docs/AUTH.md`. |
+| Published `*.mdx`, reusable Markdown JSX (MDX) fragment, customer readme, or public OpenAPI prose | `dispatch/write_documentation.md` → `docs/DOCUMENTATION_RULES.md` — establish page, fragment, API, or changelog scope before narrower guides. |
+| Changelog `<Update>` / release note (`changelog.mdx`) | First `dispatch/write_documentation.md`, then `dispatch/write_changelog.md` → `docs/CHANGELOG_VOICE.md`; internal-only ⇒ no entry. |
+| `schema/*.sql` / migration | `dispatch/write_sql.md` + `docs/SCHEMA_CONVENTIONS.md` — naming/type conventions, schema/migration rules + Schema Table Removal Guard. Re-print Schema Guard output. |
+| Any spec under `docs/v*/{pending,active,done}/` or `docs/TEMPLATE.md` | `docs/TEMPLATE.md` "Prohibited" section — no time/effort estimates, no complexity ratings, no percentage-complete, no owners/dates. SPEC TEMPLATE GATE per edit. |

package/docs/HARNESS_VERIFY_OUTPUT.md

@@ -0,0 +1,40 @@
+# CONFORM — Required output block
+
+> Parent: [`../AGENTS.md`](../AGENTS.md) §CONFORM. This file retains its name
+> because `agentsfleet` retains the repository command `make harness-verify`.
+
+Runs after EXECUTE, before VERIFY. Aggregates every gate verdict; lifecycle cannot advance without enumerating the audit. Any "fail" / remaining violations → return to EXECUTE.
+
+## Combined end-of-turn audit
+
+Single awk over `git diff -U0 HEAD`, replaces 4 separate self-audits. For every `+` line:
+
+- Emit `MS-ID:` hits when file is source/config and matches `M[0-9]+_[0-9]+|§[0-9]+(\.[0-9]+)+|\bT[0-9]+\b|\bdim [0-9]+\.[0-9]+\b`.
+- Emit `PUB:` hits when `*.zig` and line matches `^\+(pub | *pub fn | *[A-Z][a-zA-Z]+,$)`.
+- Emit `UI:` hits when under `ui/packages/app/**.{tsx,jsx}` and line contains `<(section|button|input|dialog|article|nav|header|form)\b`.
+
+Non-empty = address before CONFORM passes.
+
+## Required output
+
+Verdict cells use ✅ pass · 🟣 n/a · 🔴 fail · 🟡 violations addressed.
+
+```
+🔴 CONFORM: <branch>
+| Gate                 | Verdict                       |
+| FILE SHAPE           | ✅ pass | 🟣 n/a               |
+| PUB GATE             | ✅ pass | 🟣 n/a               |
+| LENGTH GATE          | ✅ pass | 🟡 files at cap: …    |
+| MILESTONE-ID GATE    | ✅ pass — combined audit, 0 hits |
+| ZIG GATE             | ✅ pass | 🟣 n/a               |
+| UI GATE              | ✅ pass | 🟣 n/a               |
+| DESIGN TOKEN GATE    | ✅ pass | 🟡 N arbitraries addressed | 🔴 N unresolved |
+| UFS GATE             | ✅ pass | 🟡 N violations addressed | 🔴 N unresolved |
+| SCHEMA GUARD         | ✅ pass | 🟣 n/a               |
+| GREPTILE GATE        | ✅ pass | 🟡 N violations addressed |
+| Architecture consult | ✅ doc updated same commit | 🟣 n/a |
+| Coverage             | ✅ backend N% ≥ min · UI N% ≥ min | 🟣 n/a |
+| /orly-write-unit-test     | ✅ clean | 🟡 N tests added   |
+```
+
+Any 🔴 in the table → return to EXECUTE; the lifecycle does NOT advance.