@agentsfleet/orly 0.5.0

package/dispatch/write_zig.sh

@@ -0,0 +1,40 @@
+#!/usr/bin/env bash
+# dispatch/write_zig.sh — the Zig dispatch, DETERMINISTIC façade.
+#
+# Pairs with dispatch/write_zig.md (the LATENT façade — prose the agent reads).
+# This .sh runs the mechanically-checkable subset of the Zig discipline and
+# emits ONE verdict block. The latent trigger ("about to write a *.zig file")
+# dispatches here; everything below is deterministic and re-runnable — same
+# input, same verdict, no calendar/branch dependence.
+#
+#   dispatch/write_zig.sh <file.zig> [...]   # explicit targets (EXECUTE)
+#   dispatch/write_zig.sh --staged           # staged *.zig (CONFORM, pre-commit)
+#
+# Layering:  AGENTS.md → write_zig.md (latent) → write_zig.sh (this) → audits/*.sh
+# Signals:   🟢 pass · 🔴 fail (blocks) · 🤔 DECIDE (judgment; blocks the TURN, not the script)
+# Exit:      0 = mechanical gates pass · 1 = ≥1 failed · 2 = usage error.
+
+source "$(dirname "${BASH_SOURCE[0]}")/lib.sh"
+
+dispatch_init "ZIG" '*.zig'
+dispatch_resolve_files "$@"
+dispatch_header
+
+# ── deterministic gates ────────────────────────────────────────────
+dispatch_length_gate 350                                       # FLL — write_zig.md §Length
+# UFS — universal rule enforced once by write_any (see write_any.sh); not re-run here
+dispatch_run_helper "DEINIT" "deinit-pairs.sh" "--staged" # write_zig.md §Multi-Step Init
+dispatch_run_helper "SQLMOD" "sql-mod.sh"      "--staged" # write_zig.md §SQLMOD — inline SQL → domain sql.zig
+
+# ── delegations (checker lives in the product repo, not dotfiles) ───
+dispatch_delegate "PUB"      "make lint (zlint unused-decls)"
+dispatch_delegate "DRAIN"    "make check-pg-drain (lint-zig.py)"
+dispatch_delegate "XCOMPILE" "zig build -Dtarget=x86_64-linux && aarch64-linux"
+
+# ── judgment gates (no script can decide; agent states verdict in chat) ──
+dispatch_judgment "TGU"  "result type with distinct failure modes? union(enum) with payload, not optional-field struct"
+dispatch_judgment "ARCH" "naming a stream/queue/schema? grep docs/architecture/ first"
+dispatch_judgment "FSD"  "new/reshaped *.zig file? file-as-struct vs operations-over-value — decide at PLAN, one-sentence why-not"
+dispatch_judgment "DIDEM" "type with a cleanup contract? a test proving deinit is idempotent (or single-shot ownership asserted)"
+
+dispatch_verdict

package/docs/CHANGELOG_VOICE.md

@@ -0,0 +1,18 @@
+# Changelog voice (Mintlify-style)
+
+> Parent: [`../AGENTS.md`](../AGENTS.md) §Owner & Style.
+> Prerequisite: read [`DOCUMENTATION_RULES.md`](./DOCUMENTATION_RULES.md) first.
+> Changelog history keeps its archive exception; this file adds the narrower voice.
+
+Editing `~/Projects/docs/changelog.mdx` or any other Mintlify `<Update>` block.
+
+- **One headline per entry, no marketing words.** Apply Documentation rule 07
+  (`DOC-07`) from `DOCUMENTATION_RULES.md`. Also ban "magical", "we are pleased
+  to", and "we're excited to" in changelog entries. The change speaks for itself.
+- **Lead paragraph states the change, not the announcement.** A reader has 30 seconds; they should know what changed in the first sentence. ✅ "Pricing collapses to one number per surface." ❌ "Today we're shipping single-rate pricing."
+- **Bullets follow `**Bold lead-noun** — consequence-first clause`.** One bullet, one fact. Three "and"s in a sentence → split it. Code names always in backticks (functions, paths, env vars, routes, error codes, tables).
+- **Internal cleanup / refactor entries get the most aggressive trimming.** One lead paragraph + one bullet list. Skip "Test coverage" sections unless the test count is the headline. Indy's exact direction: *"Keep internal code cleanup, refactor to a minimal."*
+- **Never drop load-bearing facts.** Error codes (`UZ-AUTH-003`), endpoint paths + method + body shape + status code, env var names + defaults, schema column / table names, CLI subcommand + flag names, migration steps, money amounts. Tighten prose, not meaning.
+- **Historical entries are archives.** Brevity-pass them; never rewrite the past. A typo correction (e.g. `$0.001` → `$0.01` when it was never true) is allowed and must be called out in the commit message.
+- **Rate constants flow through three pinned files only:** `src/agentsfleetd/state/tenant_billing.zig`, `ui/packages/website/src/lib/rates.ts`, `~/Projects/docs/snippets/rates.mdx`. Bumping a rate requires a paired Pull Request (PR) across the docs repo — there is no automated guard. In `*.mdx`, use `import { STARTER_CREDIT, EVENT_RATE, STAGE_RATE } from "/snippets/rates.mdx"` instead of hand-typing `$5`.
+- **The Mintlify reference Indy pasted (May 1 / May 8 entries) is canonical voice.** Mirror its rhythm, not its product nouns.