Skip to main content

v2.25.0

Retired since. The work-plane surfaces this release added — orun epic, orun work import, the approval-sealed brief — were removed whole in a later release. This page is kept as the historical record.

Release notes for orun v2.25.0.

Highlights​

Work gains a shape: Initiative → Design → Epic → Milestone → Task. This release ships the orun half of the planning hierarchy (orun-work v4, cluster WH): the model and oracle, the approval-sealed epic brief, a 15-tool work MCP plane, and an importer that reads the hierarchy your specs/ tree already writes.

One rule governs the whole evolution — split by truth source. Review, approval, and adoption are decisions: authored, attributed coordination events, human-only where it matters. Progress, drift, and health are facts: folds nobody can edit. The v2 delivery fold — Draft → Ready → In Progress → In Review → Done → Released, derived from the two logs — is untouched and frozen; v4 is purely additive.

  • The five-noun model in the oracle. internal/worklens gains the design item kind, <epic>#<key> milestone sub-items, 8 new coordination kinds (27 total), the intent-ladder fold (Draft / In Review / Approved@revision / ApprovedDrifted / Adopted / Superseded — coordination events only), ladderHash, and rollup folds: milestone progress, epic execution, initiative health with named evidence. approved, approval_revoked, and adoption validate actor user at write time — an agent approval is unrepresentable in the model.
  • orun epic pull <slug>[@sha256:…] — the strict superset of orun spec pull: fetch the EpicSnapshot a human approval sealed server-side (doc revision, milestone ladder + hash, informative task contracts, approval record, log cursors), verify sha256(bytes) == id, and materialize a read-only .orun/epics/<slug>/{snapshot.json,BRIEF.md}. An unapproved epic has no brief. See orun epic.
  • The MCP grows 9 → 15 work tools. New reads: epic_brief, initiative_get, design_get, milestone_get. New writes: design_propose (a Draft design + structured proposal, applied AND flagged — the contract_propose discipline) and task_regenerate (re-plan one milestone in one verdict batch; planned tasks cancel, in-flight tasks survive). task_create gains milestone. The forbidden-tool sweep extends: no status, pin, lifecycle, approve, or adopt tool exists, asserted by test across the merged 40-tool roster.
  • Import learns the hierarchy it already reads. orun work import now maps epic folders → epics, implementation-plan.md ## <KEY> — <Title> headings → milestones (Goal / Done-when / Deps → the milestone contract), checklist items → tasks inside their milestone, and roadmap.md cluster rows → initiatives. Idempotent, with key-preserving migration: a v2-imported workspace upgrades in place — existing tasks keep their keys and history and attach to the newly minted milestones. Import writes intent, never decisions: no lifecycle, no reviews, no approvals.
orun work import specs/ --dry-run     # initiatives / specs / milestones / tasks
orun work import specs/ --workspace my-org
orun epic pull payments-v2            # the brief an approval sealed

Dogfood numbers​

The full workspace fold plus every rollup (delivery fold + per-epic intent fold + milestone/execution rollups) over this repo's real specs/ tree — 18 epics, 73 milestones, 73 tasks — runs in ~1.4 ms/round in the Go oracle, budget-gated in CI at 250 ms. Lifecycle-at-read stays cheap; no materialization needed at this scale.

Compatibility​

  • Everything v2/v3 keeps working byte-for-byte. The delivery fold, claim join, and observation vocabulary are frozen (V4-1); the v2 conformance fixtures pass unmodified, replayed identically by the Go oracle and the cloud TS fold.
  • orun spec pull remains unchanged; orun epic pull is its superset for approved epics.
  • Existing MCP clients keep working: the 9 prior work tools keep their names, schemas, and semantics — the roster simply grows to 15 work + 25 platform = 40.
  • orun work import re-runs on a v2-imported workspace are a migration, not a re-import: same keys, same history, new levels.

The cloud half — schema, approval/review API, the drill-down console (portfolio → initiative → epic → milestone → task), designs, and the sealed-brief endpoint — ships in Orun Cloud (specs/epics/orun-work-v4/ in the orun-cloud repo, milestones WH0–WH6).