Skip to content

OpenRig v0.5.8

Choose a tag to compare

View all tags
@mvschwarz mvschwarz released this 03 Sep 00:17
· 2072 commits to main since this release
v0.5.8
8b46e65

OpenRig v0.5.8 — recoverable operations and visible work

OpenRig 0.5.8 makes long-running rigs easier to recover, understand, and
operate. It adds exact selected-rig recovery after an abrupt outage, makes the
current mission and its execution story visible to agents and operators, and
tightens the diagnostics and guardrails that keep live state honest.

Recovery and topology lifecycle

  • Recover the selected rig after an outage. Restore now rejects stale
    native identity, uses real provider-session evidence, and avoids substituting
    a fresh or wrong occupant or starting unrelated sibling rigs.
  • Use one topology-creation path. Public creation and growth converge on the
    same daemon effect while preserving member working-directory overrides.
  • Keep topology declarations useful. Rigs expose honest self-description,
    workspace declarations survive export, and a validated workspace declaration
    can be applied to an existing rig without changing its topology.

Mission and context visibility

  • Open mission execution from SCOPES. A selected mission now shows a
    readable DONE / NOW / NEXT / ATTENTION story, truthful working-lane
    and evidence-gap counts, bounded overflow, and stable mission switching.
  • Install the work that is actually current. Work-install resolves complete
    files and dot-form slice IDs, and refocus derives the seat's typed current
    mission and slice instead of asking the agent to reconstruct them from
    memory.
  • Discover shipped capability. The public capability world and its
    addressable context are available through the installed context routes.

Operational honesty and safer setup

  • Wake once for the state that needs attention. Park timers retire on every
    exit path, new park episodes supersede old timers, and idle-gate watchdogs use
    the same arbitrated activity oracle as the rest of the system.
  • Diagnose the mechanism that is actually live. Producer-link health derives
    from effective endpoints, topology freshness is bounded, and synthetic model
    records no longer create false model-divergence findings.
  • Preserve user-owned Codex configuration. Managed TOML projection refuses
    malformed or root-scoped fragments before write and preserves user tables
    across valid collisions.
  • Keep upgrades agent-led. The shipped upgrade skill supplies bounded
    inspection, verified database backup, and contained managed-plugin refresh
    helpers while leaving cutover judgment with the operating agent.
  • Trust clean-checkout results. The documented daemon test gate and the
    same-SHA long-lived gate now agree on deterministic source truth.

Operator / setup notes

  • Root, CLI, daemon, and web UI package versions advance to 0.5.8. The
    terminal TUI keeps its independent 0.1.0 version.
  • Database migration head advances from 077_node_session_source to
    078_idle_gate_fired_condition; normal daemon startup applies it
    automatically. No manual migration step is required.
  • Existing rigs do not need a topology rewrite. The new workspace-only apply
    path deliberately leaves members, pods, edges, and running sessions alone.

Known limitations

  • Selected-rig recovery does not cover total database plus filesystem loss or
    fleet-wide automatic restart.
  • The existing-rig workspace story does not validate target_repo; that
    separate concern remains outside this release contract.
  • A pre-existing backend attention_required state is not part of the bounded
    TUI topology-freshness work.

Release verification

  • Independent QA and review exercised the final SCOPES execution journey at
    110 and 160 columns, including mission selection, readable evidence gaps,
    bounded overflow, slice drill-in, and Escape navigation.
  • Recovery testing used real Claude and Codex occupants across current, stale,
    absent, and insufficient-evidence states. It also covers native-session
    identity changing within the same OpenRig occupant record.
  • The accepted product tree was replayed as a linear public lineage rooted on
    0.5.7. Every author and committer uses the project noreply identity, and the
    replayed product tree is byte-identical to the accepted local-main tree.
  • Release acceptance includes package assembly, a hash-bound per-file
    substance review, and installed-runtime QA and review against the exact
    private cut.
Assets 2
Loading