Skip to content

v0.12.0 — Governed active-goal closure and runtime recovery

Choose a tag to compare

View all tags
@phenomenoner phenomenoner released this 22 Jul 10:18
· 5 commits to main since this release
v0.12.0
7e20a31

Highlights

  • Active goals now resolve each source turn through one durable outcome: an exact-lane continuation, a visible parked blocker, or typed non-delivery. A denied continuation can no longer appear as silent success.
  • AppX PowerShell replacement is distinguished from ordinary shell failures. Eligible exact-authority work can recover once in a fresh runtime; ambiguous, repeated, or observation-only cases park visibly.
  • Parent runtime receipts include bounded child lifecycle summaries without copying child prompts, prose, channel identities, complete commands, or secrets.
  • trace accepts the canonical --queue-id selector while retaining the legacy --id spelling. Supplying both fails closed.
  • Worker status now excludes durable parked rows from open downstream work, matching runtime scheduling and health semantics. Parked work remains visible through runtime waiting state and trace, and becomes actionable again after a durable retry or resolution.

Verification

  • Independent review returned PASS for the exact release commit and staged binary.
  • Fresh serial workspace tests passed: 135 CLI tests, 1,301 core tests, and integration suites of 5, 1, 4, 9, 1, 5, and 4 tests, with no failures.
  • Formatting, workspace all-target checks, clippy, schema and invariant catalogs, scenario catalog, and public hygiene checks passed. Clippy reports only pre-existing repository warnings.
  • Guarded live deployment verified the exact staged binary hash, ready/live health, nine fresh supervised services, no open runtime, cron, or worker work, idle Telegram and Discord outboxes, and a ready cutover receipt.
  • A controlled provider-visible Discord replay produced one visible authority-conflict park, one delivered parent message, no continuation child or intent, no duplicate delivery after restart, and a terminal trace with no diagnostics.

Compatibility and limits

  • Goal autonomy remains observation-only unless an exact reviewed lane is explicitly activated. Authority conflicts intentionally require operator reconciliation.
  • Existing trace --id callers remain compatible; new automation should use trace --queue-id.
  • Rollback binary, configuration, and non-secret state artifacts were retained during deployment.
Assets 2
Loading