Skip to content

v0.9.0

Choose a tag to compare

@edseabolt edseabolt released this 31 Oct 20:20
· 270 commits to dev since this release
e29f3d0

turnstile v0.9.0

This release is about the gate knowing what it's gating: enforcement state is now task-scoped and keyed to the active plan, escalation to the human runs through an explicit ask-first ladder with sticky task-scoped releases, and the parent's own hands — its write/edit tools and file-writing bash commands — pass through the same gate the children do. Shadow mode is gone for good, and interrupted reviews recover from the journal instead of dying with the session.

Breaking

  • Shadow mode removed — the observe/meta-mode config keys are gone; there is one enforcement mode, and config carrying the removed keys is rejected with a diagnostic (#220).
  • Escalation defaults to block-only release — the new escalation: ask|block key replaces the old implicit behavior: block (default) releases only on your explicit approval, ask prompts (#224).
  • Task-scoped gate state — gate state is keyed on the active plan, and the plan-gate task arm splits by escalation mode (#231). Legacy durable plan approvals are re-keyed transparently on replay, and opencode-turnstile status surfaces the migration as a table advisory (#237, issue #230).

New: hands-on gate

The parent session's own write/edit calls — and bash commands that write files (heredocs, tee, redirection, sed -i, dd) — now route through the same escalation ladder the pipeline uses. Registered pipeline children stay exempt, heredoc-bearing commands cap at telemetry, and scratch temp-dir targets are exempt while symlink-chain depth exhaustion fails toward gating (#218, #229, #231).

New: governance redesign (#231)

  • Prompt intent classification — the plugin classifies each admitted prompt's intent and nudges pipeline entry accordingly, with a policy head + intent nudge on the session.context primary-turn draft.
  • Ask-first ladder — escalations ask before they block; releases are sticky for the task scope and restored from the journal on replay.
  • Maintenance dispatch — a dedicated maintenance path with spec-region plan keying, hardened eligibility, and an MNT column in status.
  • Child re-seeding — child edges are journaled at setParent and re-seeded on setup, so a journaled agent upgrade re-journals the edge (#231).

Fixed

  • fix(replay): recover interrupted review state from the journal, restore task fingerprints on gate rows, and attribute verdict replay to the emitting agent (#236, issue #232)
  • fix(classifier): skip tee dev and fd-dup operands, dd of= dev targets, and prefix words
  • fix(registration): agent-name precedence for pipeline-child registration; delivery agent resolves input echo before event.agent
  • fix(persistence): gate-events trace renamed to .log
  • Docs: factual-defect fixes across README/usage/architecture/AGENTS/skills and source docstrings; d01/d02/d04 diagrams synced with code and re-rendered (#238)

Notes

Zero runtime dependencies, as always. Host compatibility: ≥2.0.22, <3.0.0 — 2.2.5 now verified and in the tested list. Full docs: README, usage, architecture, SECURITY.