@agentsfleet/orly 0.5.0

package/audits/agents-md.sh

@@ -0,0 +1,353 @@
+#!/usr/bin/env bash
+# Deterministic audit for AGENTS.md.
+# Exit 0 = all checks pass. Non-zero = regression — see FAIL lines on stderr.
+#
+# Run before every AGENTS.md change (and from the pre-commit hook).
+# Each check asserts an invariant that, if broken, would re-introduce a
+# concrete failure mode the operating model already paid for.
+
+set -uo pipefail
+
+ROOT="$(cd "$(dirname "$0")/.." && pwd)"
+AGENTS="$ROOT/AGENTS.md"
+FIXTURES="$ROOT/audits/fixtures"
+FAIL=0
+
+# Expectation tables (EXPECTED_LABELS, REQUIRED_GATES, EXTS, FORBIDDEN_KEYS,
+# CONFORM_KEYS, DOTFILES_RESIDENT, LIFECYCLE_HEADERS, NAMED_SCENARIOS,
+# RULE_EXTENSION_STEPS, AWK_PROG) live in the sibling data file — split out
+# to keep this audit under the LENGTH GATE cap. Data drift is itself caught
+# by the gate-parity + named-scenario-parity checks below.
+DATA="$ROOT/audits/data.sh"
+[[ -f "$DATA" ]] || { echo "FAIL: $DATA missing (audit data tables)" >&2; exit 2; }
+# shellcheck source=audits/data.sh
+. "$DATA"
+SEEN_LABELS=()
+
+# Colours — disable when stdout is not a TTY (e.g. piped, hook).
+if [[ -t 1 ]]; then
+  C_GREEN=$'\033[32m'; C_RED=$'\033[31m'; C_YELLOW=$'\033[33m'
+  C_BLUE=$'\033[34m'; C_BOLD=$'\033[1m';  C_RESET=$'\033[0m'
+else
+  C_GREEN=''; C_RED=''; C_YELLOW=''; C_BLUE=''; C_BOLD=''; C_RESET=''
+fi
+
+fail() { printf '%s🔴 FAIL%s: %s\n' "$C_RED" "$C_RESET" "$*" >&2; FAIL=1; SEEN_LABELS+=("$*"); }
+pass() { printf '%s🟢 PASS%s: %s\n' "$C_GREEN" "$C_RESET" "$*";       SEEN_LABELS+=("$*"); }
+warn() { printf '%s🟡 WARN%s: %s\n' "$C_YELLOW" "$C_RESET" "$*" >&2; }
+info() { printf '%s🔆 %s%s\n' "$C_BLUE" "$*" "$C_RESET"; }
+
+info "Auditing $AGENTS"
+
+[[ -f "$AGENTS" ]] || { echo "FAIL: $AGENTS missing" >&2; exit 2; }
+
+# ---------------------------------------------------------------------------
+# 1. Dispatch inventory — every dispatch entry (REQUIRED_DISPATCH in data) has
+#    a row in the AGENTS.md dispatch table, with the entry name as the table's
+#    SECOND column ("| <trigger> | `<entry>` | …"). This is the same column the
+#    parity check (check 9b) counts, so inventory and parity agree by
+#    construction — a renamed/dropped entry fails here AND there.
+# ---------------------------------------------------------------------------
+bt='`'   # backtick held in a var — keeps it explicit inside the regex
+missing_dispatch=0
+for e in "${REQUIRED_DISPATCH[@]}"; do
+  grep -qE "^\|[^|]*\| *${bt}${e}${bt} *\|" "$AGENTS" \
+    || { fail "dispatch entry missing from table: $e"; missing_dispatch=1; }
+done
+[[ $missing_dispatch -eq 0 ]] && pass "dispatch inventory (${#REQUIRED_DISPATCH[@]} entries present in table)"
+
+# ---------------------------------------------------------------------------
+# 2. Trigger surface — every source/config language has a mention (EXTS in data).
+# ---------------------------------------------------------------------------
+missing_exts=0
+for ext in "${EXTS[@]}"; do
+  grep -qF "$ext" "$AGENTS" || { fail "trigger surface missing extension: $ext"; missing_exts=1; }
+done
+[[ $missing_exts -eq 0 ]] && pass "trigger surface (${#EXTS[@]} extensions named)"
+
+# ---------------------------------------------------------------------------
+# 3. Override syntax present file-wide (every gate either has an Override:
+#    line or an explicit "no override" marker).
+# ---------------------------------------------------------------------------
+override_hits=$(grep -cE 'Override|no override|SKIPPED per' "$AGENTS")
+if [[ $override_hits -lt 7 ]]; then
+  fail "override-syntax mentions only $override_hits — expected ≥ 7"
+else
+  pass "override syntax ($override_hits mentions)"
+fi
+
+# ---------------------------------------------------------------------------
+# 4. Always-forbidden invariance — six hard bans (FORBIDDEN_KEYS in data).
+# ---------------------------------------------------------------------------
+missing_bans=0
+for k in "${FORBIDDEN_KEYS[@]}"; do
+  grep -qF "$k" "$AGENTS" || { fail "always-forbidden item missing: $k"; missing_bans=1; }
+done
+[[ $missing_bans -eq 0 ]] && pass "always-forbidden list (${#FORBIDDEN_KEYS[@]} bans present)"
+
+# ---------------------------------------------------------------------------
+# 5. Skill-chain order — /orly-write-unit-test → runtime review → babysit.
+#    Anchored to within the CHORE(close) section so a stray earlier mention
+#    cannot satisfy the check.
+# ---------------------------------------------------------------------------
+awk '
+  /^### CHORE \(close\)/                  { in_section=1; next }
+  /^### |^## /                            { if (in_section) in_section=0 }
+  in_section && /\/orly-write-unit-test/  && !a { a=NR }
+  in_section && /gstack/           && a && !b { b=NR }
+  in_section && /orly-babysit-prs/&& b && !c { c=NR }
+  END { exit (a && b && c && a<b && b<c) ? 0 : 1 }
+' "$AGENTS" \
+  && pass "skill-chain ordering (anchored to CHORE(close))" \
+  || fail "skill chain not in order within CHORE(close): /orly-write-unit-test → gstack /review → orly-babysit-prs"
+
+# One route for every runtime. A per-runtime split re-introduces the
+# collapsing-two-near-named-steps failure SOUL.md records; assert the
+# single route and that both pre-PR test skills are named.
+review_routes_missing=0
+grep -qF 'One route, every runtime: gstack `/review`.' "$AGENTS" \
+  || { fail "single gstack review route missing"; review_routes_missing=1; }
+grep -qF '/orly-write-integration-test' "$AGENTS" \
+  || { fail "/orly-write-integration-test missing from the pre-PR skill chain"; review_routes_missing=1; }
+[[ $review_routes_missing -eq 0 ]] && pass "unified review route + both test skills"
+
+# ---------------------------------------------------------------------------
+# 6. CONFORM rows — every gate keyword in the verdict block (CONFORM_KEYS).
+# ---------------------------------------------------------------------------
+missing_rows=0
+for kw in "${CONFORM_KEYS[@]}"; do
+  grep -qF "$kw" "$AGENTS" || { fail "CONFORM row missing: $kw"; missing_rows=1; }
+done
+[[ $missing_rows -eq 0 ]] && pass "CONFORM coverage (${#CONFORM_KEYS[@]} rows present)"
+
+# ---------------------------------------------------------------------------
+# 7. Cross-references — dotfiles-resident docs must exist (DOTFILES_RESIDENT
+#    in data). Project-side docs (AUTH.md, architecture/, changelog.mdx) live
+#    in each project repo, not here, so they're excluded from this check.
+# ---------------------------------------------------------------------------
+broken_refs=0
+for doc in "${DOTFILES_RESIDENT[@]}"; do
+  [[ -f "$ROOT/$doc" ]] || { fail "dotfiles-resident ref missing: $doc"; broken_refs=1; }
+done
+[[ $broken_refs -eq 0 ]] && pass "cross-references (dotfiles-resident docs exist)"
+
+# ---------------------------------------------------------------------------
+# 8. Combined-audit smoke — the awk pass (AWK_PROG in data) flags real
+#    violations and ignores clean diffs. Fixtures live in audits/fixtures/.
+# ---------------------------------------------------------------------------
+if [[ -f "$FIXTURES/dirty.diff" && -f "$FIXTURES/clean.diff" ]]; then
+  # Fixture content fingerprint — guards against well-meaning rewrites
+  # that "fix" dirty.diff to be clean (which would silently break the smoke).
+  grep -qF "M40_001"  "$FIXTURES/dirty.diff" || fail "fixture dirty.diff missing M40_001 marker"
+  grep -qE '<button>' "$FIXTURES/dirty.diff" || fail "fixture dirty.diff missing raw <button>"
+  ! grep -qF "M40_001"  "$FIXTURES/clean.diff" || fail "fixture clean.diff has milestone-id leak"
+  ! grep -qE '<button>' "$FIXTURES/clean.diff" || fail "fixture clean.diff has raw <button>"
+
+  dirty_hits=$(awk "$AWK_PROG" "$FIXTURES/dirty.diff" | wc -l | tr -d ' ')
+  clean_hits=$(awk "$AWK_PROG" "$FIXTURES/clean.diff" | wc -l | tr -d ' ')
+
+  # Pin exact expected counts — protects against false-positive "smoke ok"
+  # where a rigged dirty.diff produces ≥1 hit on an unrelated token.
+  if [[ $dirty_hits -eq 4 ]]; then
+    pass "audit fixture: dirty diff flagged exactly 4 hits"
+  else
+    fail "audit fixture: dirty diff flagged $dirty_hits hits (expected 4)"
+  fi
+  if [[ $clean_hits -eq 0 ]]; then
+    pass "audit fixture: clean diff produced 0 hits"
+  else
+    fail "audit fixture: clean diff falsely flagged ($clean_hits hits)"
+  fi
+else
+  fail "audit fixture files missing under $FIXTURES/"
+fi
+
+# ---------------------------------------------------------------------------
+# 9b. Dispatch parity — the three sources of truth must agree: dispatch/*.md
+#     bodies on disk, dispatch-table rows in AGENTS.md, and REQUIRED_DISPATCH
+#     (check #1). The check also asserts docs/gates/ is EMPTY — the dissolved-
+#     gate end state — so a half-done switchover (a leftover card) hard-fails.
+#     The logic lives in the sibling parity-dispatch.sh so the model-B sandbox
+#     test (evals/test-dispatch-parity.sh) can exercise it in isolation; this
+#     keeps the body completeness + existence guarantee that the old per-card
+#     gate-body check used to provide (each REQUIRED_DISPATCH entry must resolve
+#     to a real dispatch/<entry>.md).
+# ---------------------------------------------------------------------------
+. "$ROOT/audits/parity-dispatch.sh"
+parity_out=$(check_dispatch_parity "$ROOT"); parity_rc=$?
+if [[ $parity_rc -eq 0 ]]; then
+  pass "dispatch parity ${parity_out#PASS: dispatch parity }"
+else
+  printf '%s\n' "$parity_out" >&2
+  fail "dispatch parity mismatch (see FAIL lines above)"
+fi
+
+# ---------------------------------------------------------------------------
+# 10. audits/agents-md.md presence + basic shape (questionnaire layer).
+# ---------------------------------------------------------------------------
+INV="$ROOT/audits/agents-md.md"
+if [[ -f "$INV" ]]; then
+  inv_scenarios=$(grep -cE '^### Scenario [0-9]+' "$INV")
+  if [[ $inv_scenarios -ge 8 ]]; then
+    pass "audits/agents-md.md present ($inv_scenarios scenarios)"
+  else
+    fail "audits/agents-md.md only $inv_scenarios scenarios — expected ≥ 8"
+  fi
+else
+  fail "audits/agents-md.md missing"
+fi
+
+# ---------------------------------------------------------------------------
+# 11. Lifecycle stage headers — all present in AGENTS.md (LIFECYCLE_HEADERS).
+# ---------------------------------------------------------------------------
+missing_stages=0
+for h in "${LIFECYCLE_HEADERS[@]}"; do
+  grep -qF "$h" "$AGENTS" || { fail "lifecycle stage missing: $h"; missing_stages=1; }
+done
+[[ $missing_stages -eq 0 ]] && pass "lifecycle stages (${#LIFECYCLE_HEADERS[@]} headers present)"
+
+# 11b. Lifecycle anchors — load-bearing strings in BOTH essence + runbook.
+. "$ROOT/audits/lifecycle-anchors.sh"
+anchors_out=$(check_lifecycle_anchors "$ROOT")
+if [[ $? -eq 0 ]]; then pass "lifecycle anchors (${#LIFECYCLE_ANCHORS[@]} strings in essence + runbook)"; else
+  printf '%s\n' "$anchors_out" >&2; fail "lifecycle anchors (see FAIL lines above)"; fi
+
+# 12. Named scenarios exist by title (NAMED_SCENARIOS in data) — catches a
+#     renamed/removed high-value scenario hiding behind a stable count.
+INV="$ROOT/audits/agents-md.md"
+missing_scenarios=0
+if [[ -f "$INV" ]]; then
+  for s in "${NAMED_SCENARIOS[@]}"; do
+    grep -qF "$s" "$INV" || { fail "audits/agents-md.md missing scenario keyword: $s"; missing_scenarios=1; }
+  done
+  # Parity — the keyword array must keep pace with the actual scenario count,
+  # so a newly-added scenario can't sit unguarded (this is exactly how
+  # scenarios 20-22 slipped past the keyword list before this check existed).
+  actual_scenarios=$(grep -cE '^### Scenario [0-9]+' "$INV")
+  if [[ "${#NAMED_SCENARIOS[@]}" -ne "$actual_scenarios" ]]; then
+    fail "named-scenario parity: array has ${#NAMED_SCENARIOS[@]} keywords but audits/agents-md.md has $actual_scenarios scenarios (every scenario needs a keyword guard)"
+    missing_scenarios=1
+  fi
+  [[ $missing_scenarios -eq 0 ]] && pass "named scenarios (${#NAMED_SCENARIOS[@]} keywords ↔ $actual_scenarios scenarios, parity holds)"
+else
+  fail "audits/agents-md.md missing"
+fi
+
+# ---------------------------------------------------------------------------
+# 13. Hook trigger coverage — pre-commit AND pre-push must reference
+#     AGENTS.md AND dispatch/ so ruleset changes can never silently
+#     bypass either layer (dispatch/ replaces the dissolved docs/gates/).
+# ---------------------------------------------------------------------------
+PRE_COMMIT="$ROOT/.githooks/pre-commit"
+PRE_PUSH="$ROOT/.githooks/pre-push"
+hook_fail=0
+for hook in "$PRE_COMMIT" "$PRE_PUSH"; do
+  name=$(basename "$hook")
+  if [[ ! -f "$hook" ]]; then
+    fail "hook missing: .githooks/$name"; hook_fail=1; continue
+  fi
+  grep -qE 'AGENTS(\\)?\.md' "$hook" || { fail "$name missing AGENTS.md trigger reference"; hook_fail=1; }
+  grep -qF "dispatch/"  "$hook" || { fail "$name missing dispatch/ trigger reference"; hook_fail=1; }
+  for token in 'package\.json' 'bun\.lock' 'tsconfig\.json' 'fixtures/'; do
+    grep -qF "$token" "$hook" || { fail "$name missing $token trigger reference"; hook_fail=1; }
+  done
+done
+[[ $hook_fail -eq 0 ]] && pass "hook triggers (.githooks/pre-commit + pre-push both gate rules, package, toolchain, and fixtures)"
+
+# ---------------------------------------------------------------------------
+# 14. Rule extension protocol — AGENTS.md MUST document the 4-step recipe
+#     for landing a new rules file or gate body, AND that recipe must still
+#     enumerate all four wiring steps. Mere section-presence is not enough:
+#     the protocol is the only thing tying a new gate to the doc-reads table,
+#     the questionnaire, the DOTFILES_RESIDENT audit list, and `make audit`.
+#     If a step silently drops out of the recipe, gates can be added without
+#     that linkage — the same class of drift that hid UFS/DESIGN-TOKEN.
+# ---------------------------------------------------------------------------
+if grep -qF "Rule extension protocol" "$AGENTS"; then
+  protocol_line=$(grep -F "Rule extension protocol" "$AGENTS" | head -1)
+  rep_fail=0
+  for step in "${RULE_EXTENSION_STEPS[@]}"; do
+    grep -qF "$step" <<<"$protocol_line" || { fail "rule extension protocol missing step keyword: $step"; rep_fail=1; }
+  done
+  [[ $rep_fail -eq 0 ]] && pass "rule extension protocol section present (all 4 wiring steps enumerated)"
+else
+  fail "AGENTS.md missing 'Rule extension protocol' section"
+fi
+
+# ---------------------------------------------------------------------------
+# 15. Identity handles — AGENTS.md MUST identify the human (Kishore / Indy)
+#     and the agent (Oracle / Orly) so addressing resolves unambiguously.
+# ---------------------------------------------------------------------------
+if grep -qF "human is Kishore" "$AGENTS" && grep -qF "Orly" "$AGENTS"; then
+  pass "identity handles (Kishore/Indy ↔ Oracle/Orly present)"
+else
+  fail "identity handles: AGENTS.md missing 'human is Kishore' or 'Orly'"
+fi
+
+# ---------------------------------------------------------------------------
+# 15b. Memory discipline — auto-memory is retired in favour of dispatch + repo
+#      docs + HANDOFF. The section MUST keep three load-bearing facts so a
+#      future edit can't silently re-enable the per-session memory tax or drop
+#      the routing that replaces it: the disable flag, the never-write rule, and
+#      the dispatch-first routing target.
+# ---------------------------------------------------------------------------
+md_fail=0
+grep -qF "## Memory Discipline" "$AGENTS"      || { fail "memory discipline: section header missing"; md_fail=1; }
+grep -qF "autoMemoryEnabled" "$AGENTS"         || { fail "memory discipline: autoMemoryEnabled disable flag not documented"; md_fail=1; }
+grep -qiE "NEVER write to .*memory" "$AGENTS"  || { fail "memory discipline: never-write-memory rule missing"; md_fail=1; }
+grep -qF 'dispatch/<entry>.md' "$AGENTS"       || { fail "memory discipline: dispatch-first routing missing"; md_fail=1; }
+[[ $md_fail -eq 0 ]] && pass "memory discipline (disable flag + never-write + dispatch routing present)"
+
+# ---------------------------------------------------------------------------
+# 15c. Rule-path residence — citations resolve inside the installing repo
+#      (audits/rule-paths.sh; incident: an M143 worktree agent resolved a
+#      dotfiles rule doc against the product repo and designed from memory).
+# ---------------------------------------------------------------------------
+. "$ROOT/audits/rule-paths.sh"
+res_out=$(check_rule_residence "$ROOT")
+if [[ $? -eq 0 ]]; then pass "rule-path residence (doctrine + anchors + zero relative hrefs)"; else
+  printf '%s\n' "$res_out" >&2; fail "rule-path residence (see FAIL lines above)"; fi
+
+# ---------------------------------------------------------------------------
+# 16. Size cap — soft guard against drift back to bloat.
+#     Generated metadata is included in the measured file.
+#
+#     40 KiB, raised from 32 KiB (Aug 22, 2026) on Indy's call: the render had
+#     reached the old cap exactly, so every new rule cost an existing one, and
+#     the next thing to cut would have been triggers rather than gloss. The cap
+#     exists for attention, not capacity — a rule the agent skims past enforces
+#     nothing — so it stays a real ceiling, just one with room to work in.
+# ---------------------------------------------------------------------------
+SIZE=$(wc -c < "$AGENTS" | tr -d ' ')
+LIMIT=${AGENTS_MD_SIZE_LIMIT:-40960}
+if [[ $SIZE -le $LIMIT ]]; then
+  pass "size $SIZE bytes (limit $LIMIT)"
+else
+  fail "size $SIZE bytes exceeds limit $LIMIT (override via AGENTS_MD_SIZE_LIMIT=...)"
+fi
+
+# ---------------------------------------------------------------------------
+# Self-fingerprint — every EXPECTED_LABELS entry must have been emitted by
+# at least one pass/fail call. Catches the case where someone deletes a
+# check from the script — the script then runs successfully but with
+# fewer invariants enforced, which is exactly the kind of silent
+# weakening this audit exists to prevent.
+# ---------------------------------------------------------------------------
+fp_fail=0
+for label in "${EXPECTED_LABELS[@]}"; do
+  found=0
+  for seen in "${SEEN_LABELS[@]}"; do
+    [[ "$seen" == *"$label"* ]] && { found=1; break; }
+  done
+  [[ $found -eq 1 ]] || { fail "self-fingerprint: expected check '$label' did not run"; fp_fail=1; }
+done
+[[ $fp_fail -eq 0 ]] && pass "self-fingerprint (${#EXPECTED_LABELS[@]} expected checks ran)"
+
+echo
+if [[ $FAIL -eq 0 ]]; then
+  printf '%s✅ ALL CHECKS PASSED%s\n' "$C_GREEN$C_BOLD" "$C_RESET"
+  exit 0
+else
+  printf '%s🔴 REGRESSION DETECTED%s — see FAIL lines above\n' "$C_RED$C_BOLD" "$C_RESET"
+  exit 1
+fi

package/audits/cross-tier-rates.sh

@@ -0,0 +1,105 @@
+#!/usr/bin/env bash
+# cross-tier-rates.sh — pin numeric parity of the rate constants
+# across Zig + three TypeScript surfaces.
+#
+# RULE UFS extension. The shipped billing surface depends on these constants
+# having identical numeric values everywhere they appear:
+#
+#   RUN_NANOS_PER_SEC         — per-second run rate (both postures) in nanos
+#
+# Two free-trial constants were pinned here and are both gone. FREE_TRIAL_END_MS
+# went when the boundary moved onto the tenant row; FREE_TRIAL_STAGE_NANOS went
+# when the trial mechanism was removed outright, because a rate that could
+# silently price a metered slice to zero was worth deleting rather than
+# guarding. The free allowance is wallet credit now — a balance, not a rate —
+# so there is no cross-tier number to pin for it.
+#
+# Files (one definition site per constant per file):
+#
+#   src/agentsfleetd/state/tenant_billing.zig       — server enforces the charge
+#   ui/packages/website/src/lib/rates.ts    — pricing page display
+#   ui/packages/app/lib/types.ts            — dashboard display
+#   cli/src/constants/billing.ts    — `agentsfleet doctor --json` billing block
+#
+# A drift between any two = a billing-display lie or a server-vs-CLI disagreement.
+# Zig is the source of truth (server enforces); the three TS surfaces echo it.
+#
+# Fires in: make harness-verify, make harness-verify-all.
+# Exits 0 clean, 1 on any drift.
+
+set -euo pipefail
+
+ROOT="$(git rev-parse --show-toplevel)"
+cd "$ROOT"
+
+readonly NAMES=(
+  RUN_NANOS_PER_SEC
+)
+
+readonly FILES=(
+  src/agentsfleetd/state/tenant_billing.zig
+  ui/packages/website/src/lib/rates.ts
+  ui/packages/app/lib/types.ts
+  cli/src/constants/billing.ts
+)
+
+# Extract the numeric value bound to `name` in `file`. Matches definition
+# sites only — `^(pub |export )?const NAME` — not usages elsewhere in the
+# file. Normalises: strips underscores (Zig `1_000_000`, TS `1_000_000`),
+# strips the bigint `n` suffix (TS `1_000_000n`), trims whitespace.
+extract_value() {
+  local file="$1" name="$2"
+  grep -E "^[[:space:]]*(pub |export )?const ${name}\\b" "$file" 2>/dev/null \
+    | head -1 \
+    | sed -E "s|.*=[[:space:]]*||; s|[;,].*||; s|//.*||; s|[[:space:]_n]||g"
+}
+
+FAIL=0
+violations=()
+
+printf "audit-cross-tier-rates: pinning %d constants across %d files\n" \
+  "${#NAMES[@]}" "${#FILES[@]}"
+
+for name in "${NAMES[@]}"; do
+  expected=""
+  expected_file=""
+  for file in "${FILES[@]}"; do
+    if [[ ! -f "$file" ]]; then
+      violations+=("MISSING_FILE: $file")
+      FAIL=1
+      continue
+    fi
+    val="$(extract_value "$file" "$name")"
+    if [[ -z "$val" ]]; then
+      violations+=("MISSING_CONST: $name not defined in $file")
+      FAIL=1
+      continue
+    fi
+    if [[ -z "$expected" ]]; then
+      expected="$val"
+      expected_file="$file"
+      continue
+    fi
+    if [[ "$val" != "$expected" ]]; then
+      violations+=("DRIFT: $name = $val in $file vs $expected in $expected_file")
+      FAIL=1
+    fi
+  done
+  if [[ -n "$expected" ]]; then
+    printf "  OK   %-26s = %s\n" "$name" "$expected"
+  fi
+done
+
+if [[ $FAIL -ne 0 ]]; then
+  printf "\nFAIL: cross-tier rate drift detected:\n" >&2
+  for v in "${violations[@]}"; do
+    printf "  %s\n" "$v" >&2
+  done
+  printf "\nFix: align all four files on the canonical Zig value\n" >&2
+  printf "     (src/agentsfleetd/state/tenant_billing.zig is the server-side enforcer).\n" >&2
+  exit 1
+fi
+
+printf "OK:   all %d rate constants pin across %d files\n" \
+  "${#NAMES[@]}" "${#FILES[@]}"
+exit 0

package/audits/data.sh

@@ -0,0 +1,185 @@
+# shellcheck shell=bash
+# Data tables for audits/agents-md.sh — the expectation lists every
+# check asserts against, plus the combined-audit awk program. Split out of
+# the main audit (LENGTH GATE: keeps agents-md.sh under the 350-line
+# cap; data and logic separate cleanly). Sourced, never executed directly.
+#
+# Adding a dispatch entry/scenario/rule? Update the matching array HERE; the
+# audit's dispatch-parity + named-scenario-parity checks fail loudly if a table
+# drifts out of sync with AGENTS.md / dispatch/ / audits/agents-md.md.
+
+# Self-fingerprint — every label here MUST be emitted by a pass/fail call in
+# the audit. Deleting a check without updating this list trips the final
+# self-fingerprint check. This is the script auditing itself.
+EXPECTED_LABELS=(
+  "dispatch inventory"
+  "trigger surface"
+  "override syntax"
+  "always-forbidden list"
+  "skill-chain ordering"
+  "CONFORM coverage"
+  "cross-references"
+  "audit fixture: dirty diff"
+  "audit fixture: clean diff"
+  "dispatch parity"
+  "audits/agents-md.md present"
+  "lifecycle stages"
+  "named scenarios"
+  "hook triggers"
+  "rule extension protocol"
+  "identity handles"
+  "memory discipline"
+  "rule-path residence"
+  "lifecycle anchors"
+  "size"
+)
+
+# Check 1 (dispatch inventory) + check 9b (dispatch parity) — dispatch
+# entries that replaced the 20 dissolved gate cards. Source of truth for both
+# the inventory loop in agents-md.sh and check_dispatch_parity
+# (audits/parity-dispatch.sh). Each name has a dispatch/<name>.md and a row in
+# the AGENTS.md dispatch table (entry name in the 2nd column). Keep 1:1 with
+# dispatch/*.md.
+REQUIRED_DISPATCH=(
+  "write_zig" "write_ts_adhere_bun" "write_sql" "write_any"
+  "write_spec" "write_http" "write_auth" "write_changelog"
+  "write_documentation" "verify" "name_architecture" "edit_rules"
+  "write_rust" "write_go" "write_python" "write_shell" "write_mdx"
+  "lifecycle"
+)
+
+# Check 2 — every source/config language has at least one mention.
+EXTS=( ".zig" ".ts" ".tsx" ".js" ".jsx" ".py" ".rs" ".go" ".sh" ".sql" )
+
+# Check 4 — the six hard bans must remain.
+FORBIDDEN_KEYS=(
+  "no-verify"               # hooks/signing
+  "Plaintext secrets"       # entity tables
+  "Static strings in SQL"   # schema literals
+  "Resolving/printing credentials"
+  "Force-push default"
+  "core paths"              # install-process launches in core paths
+)
+
+# Check 6 — every gate's keyword appears in the CONFORM verdict block.
+CONFORM_KEYS=(
+  "FILE SHAPE" "PUB GATE" "LENGTH GATE" "MILESTONE-ID GATE"
+  "ZIG GATE" "UI GATE" "DESIGN TOKEN GATE"
+  "SCHEMA GUARD" "GREPTILE GATE"
+  "Architecture consult"
+)
+
+# Check 7 — dotfiles-resident docs + dispatch façades referenced by AGENTS.md
+# must exist on disk. The per-language Zig/Bun standards docs were dropped —
+# dissolved into dispatch/write_zig.md and dispatch/write_ts_adhere_bun.md
+# respectively. The dispatch façades are listed so the AGENTS.md dispatch-table
+# refs are checked. The docs/* entries double as the residence classifier for
+# check 15c (audits/rule-paths.sh): these paths are cited through the
+# ~/Projects/dotfiles/ anchor in every consumer-facing surface.
+DOTFILES_RESIDENT=(
+  "docs/TEMPLATE.md"
+  "docs/REST_API_DESIGN_GUIDELINES.md"
+  "docs/LOGGING_STANDARD.md"
+  "docs/LIFECYCLE_PATTERNS.md"
+  "docs/DOCUMENTATION_RULES.md"
+  "docs/ORLY_ARCHITECTURE.md"
+  "docs/CHANGELOG_VOICE.md"
+  "docs/EXECUTE_DOC_READS.md"
+  "docs/VERIFY_TIERS.md"
+  "docs/HARNESS_VERIFY_OUTPUT.md"
+  "docs/SCHEMA_CONVENTIONS.md"
+  "docs/greptile-learnings/RULES.md"
+  "dispatch/write_zig.md"
+  "dispatch/write_ts_adhere_bun.md"
+  "dispatch/write_rust.md"
+  "dispatch/write_go.md"
+  "dispatch/write_python.md"
+  "dispatch/write_shell.md"
+  "dispatch/write_mdx.md"
+  "dispatch/write_sql.md"
+  "dispatch/write_any.md"
+  "dispatch/write_spec.md"
+  "dispatch/write_http.md"
+  "dispatch/write_auth.md"
+  "dispatch/write_changelog.md"
+  "dispatch/write_documentation.md"
+  "dispatch/verify.md"
+  "dispatch/name_architecture.md"
+  "dispatch/edit_rules.md"
+  "dispatch/lifecycle.md"
+)
+
+# Check 11 — every lifecycle stage header is present in AGENTS.md.
+LIFECYCLE_HEADERS=(
+  "### CHORE (open)"
+  "### PLAN"
+  "### EXECUTE"
+  "### CONFORM"
+  "### VERIFY"
+  "### REVIEW"
+  "### DOCUMENT"
+  "### COMMIT"
+  "### CHORE (close)"
+)
+
+# Check 11b — load-bearing lifecycle strings that must exist in BOTH the
+# rendered AGENTS.md (stage essence) and dispatch/lifecycle.md (the runbook).
+# Consumed by audits/lifecycle-anchors.sh; a string dropped from either side
+# is semantic drift the inventory parity check cannot see.
+LIFECYCLE_ANCHORS=(
+  "Test Baseline:"
+  '`pwd` + `git worktree list`'
+  "user-acked verbatim quote"
+  "make check-version"
+  "RULE ORP"
+  "git status -uall"
+  "never force-push an open PR branch"
+)
+
+# Check 12 — each scenario must exist by keyword; array size must equal the
+# actual scenario count (parity). Keep this list 1:1 with audits/agents-md.md.
+NAMED_SCENARIOS=(
+  "New spec"                 # Scenario 1
+  "Brainstorming"            # Scenario 2
+  "human spots and steers"   # Scenario 3
+  "UI"                       # Scenario 4 (covers UI/Zig/TS/JS/shell/CI)
+  "Handover"                 # Scenario 5
+  "Conformance and verification lifecycle"  # Scenario 6
+  "orly-babysit-prs"      # Scenario 7
+  "/orly-write-unit-test"         # Scenario 8
+  "Hot-fix"                  # Scenario 9
+  "Dotfiles"                 # Scenario 10
+  "Schema"                   # Scenario 11
+  "Auto-mode boundary"       # Scenario 12
+  "Invariance Suite"         # Scenario 13
+  "Communication"            # Scenario 14
+  "Architecture-edit"        # Scenario 15
+  "Credentials"              # Scenario 16
+  "DB discipline"            # Scenario 17
+  "worktree isolation"       # Scenario 18
+  "combined audit"           # Scenario 19
+  "Rule extension protocol"  # Scenario 20
+  "Gate-flag triage"         # Scenario 21
+  "Pre-commit audit scope"   # Scenario 22
+  "Agent comprehension"      # Scenario 23
+  "Memory routing"           # Scenario 24
+  "Allocator & concurrency discipline"  # Scenario 25
+  "Rules propagation"        # Scenario 26
+  "Rule-path"                # Scenario 27
+  "Rule-enforcement ledger"  # Scenario 28
+)
+
+# Check 14 — the Rule-extension protocol must enumerate all four wiring steps.
+RULE_EXTENSION_STEPS=( "doc-reads" "audits/agents-md.md" "DOTFILES_RESIDENT" "make audit" )
+
+# Check 8 — combined-audit smoke: flags MS-ID / PUB / UI violations in a diff.
+read -r -d '' AWK_PROG <<'AWKEOF' || true
+/^\+\+\+ b\// { f=$2; sub("^b/","",f); next }
+/^\+/ {
+  if (f ~ /\.(zig|sql|ts|tsx|js|jsx|py|rs|go|sh|toml|yaml|json)$/ && f !~ /^(docs|node_modules|vendor|third_party)\//) {
+    if (match($0, /M[0-9]+_[0-9]+|§[0-9]+(\.[0-9]+)+|\bT[0-9]+\b|\bdim [0-9]+\.[0-9]+\b/)) print "MS-ID:" f
+  }
+  if (f ~ /\.zig$/ && $0 ~ /^\+(pub | *pub fn | *[A-Z][a-zA-Z]+,$)/) print "PUB:" f
+  if (f ~ /^ui\/packages\/app\/.*\.(tsx|jsx)$/ && $0 ~ /<(section|button|input|dialog|article|nav|header|form)\b/) print "UI:" f
+}
+AWKEOF