Release 0.1.25: verification and consumer adoption

[DorianZheng]

TL;DR

Prepare 0.1.25 by correcting misleading lifecycle tests and oversized prompts, then verify installation separately from the release merge.

Scope

Resolve #176, #189, and #190 without weakening approval, publication, or timeout contracts. Validate the shared auditor reminder on a live supported host. Preserve held consumers and unrelated worktree changes during adoption.

Related work and lessons

• The FIFO dossier case already distinguishes bounded file rejection from the following synchronous audit. Apply that distinction to request metadata; a two-second whole-audit alarm conflates phases.
• The watcher signal case polls for startup but signals even when readiness was never observed. Require the actual startup event before asserting shutdown behavior. A controlled three-second startup delay exposes the missing precondition.
• Existing prompt budgets bound complete documents. Native timed-question plus PR recovery rendering measures 1,249 bytes against 1,200. Shorten duplicated prose while retaining evidence, human approval, and fail-closed semantics; do not enlarge limits.
• Bats descriptor-lifetime guidance distinguishes process completion from inherited descriptor lifetime. Keep child cleanup explicit; importing a test framework would not solve these boundary mistakes.
• Monitor documentation bounds single-prompt monitors to ten minutes. Verify actual tool delivery and dossier completion separately; fixture assertions alone cannot establish model compliance.

How it works

Keep the two-second FIFO replacement check; supervise completion of the subsequent audit separately. Require watcher startup before sending TERM, with a bounded readiness failure and explicit cleanup. Keep terminal-event/orphan assertions intact.

Reduce commit criteria and PR acknowledgment prose inside existing budgets. Preserve source validation, uncertainty findings, advisory separation, native question routing, and exact human replies. No writing-skill changes or fallback scheduler.

Validation

Reproduce existing failures and controlled delayed-audit/startup cases first. For production prompt edits, restore all non-test files to baseline and observe the existing public-boundary failures, then restore the complete changes and rerun. Run syntax, ShellCheck, focused suites, all plugin suites, host parity, architecture, installer/bootstrap, and guidance checks. Record live-host limitations explicitly.

Delivery

• Verification fixes, meaningful maintenance docs, and five synchronized version manifests in PR #194; 136 changed lines.
• Independent review and release PR #194, merged as 9d6f618cbbd176ef7c906cccd60dd94fba5db82c.
• Merge the Align auditor history schema and instructions with runtime checks #180/test: isolate verdict audit fixtures from installed model CLIs #149 follow-up fixes: PR #198, merged as 13a58110e5c884f590dd0d8b351233a5fd623766.
• Refresh the valid, main-following consumer inventory; preserve holds and unrelated changes.
• Install the revision containing fix(release): prepare 0.1.25 verification #194 and the merged Align auditor history schema and instructions with runtime checks #180/test: isolate verdict audit fixtures from installed model CLIs #149 fixes; verify recorded revision, hook paths, and managed guidance.
• Refresh host plugins; verify version, exact Claude project records, and Codex cache contents and hook discovery.
• Record exclusions and failures, and document required session reloads or new tasks.
• Complete live auditor deadline qualification tracked in test(audit): qualify live finish reminders before hard timeout #197.