OpenRig v0.5.13

Status: published.

The source, the annotated v0.5.13 tag, this GitHub Release, and
@openrig/cli@0.5.13 on npm are all published. npm publication completed on
2026-09-10 and the registry lists 0.5.13 as latest; the published tarball was
verified byte-identical to the accepted release archive. Exact-cut substance
review and release verification are complete for this cut. Adoption so far is
VM-only; no parent or general adoption is established or authorized.

Note: the in-repo docs/releases/v0.5.13.md and CHANGELOG.md carry
"release candidate, unpublished" wording. That text is frozen inside the
published commit and is historical, not the current public status.

OpenRig 0.5.13 connects the human TUI journey: enter the instance, choose a
project, read its current instructions, understand what needs your decision,
and deliberately open the terminals you need. Scoped oversight and explicit
Git context updates help agents work from the right instructions while keeping
authority, evidence and local authorship visible.

Start with something useful

Bare interactive rig exposes Help, Skip and local reading while startup
checks are running, when the daemon is down, or when its state is unverified.
Selected project, mission and slice intent can be read from disk without
pretending it is live queue, execution or topology data. Read failures and
source provenance stay visible. Starting a daemon or returning seats to work
remains a deliberate action; reading and skipping do not imply consent.

Read the current source and find your way back

PROJECTS keeps a selected project's identity and root through missions,
slices and source views, including projects with the same display name.
An unavailable source is reported for that project instead of substituting
another project's work. Refresh reads the current file.

The shared reader shows source paths, modification/hash information and
bounded content, with scrolling, local links, heading links and Back.
HTTP(S) links show a selectable destination for copying; no browser is opened.
Missing, unreadable, binary or out-of-root files remain named errors. Large files show the
1 MiB returned-content limit; a heading absent from a truncated prefix is
not claimed absent from the whole file. Back restores the prior reading
and navigation position.

Know what needs your decision

ATTENTION separates Action required from Updates. Human requests
and explicit blockers show the request, urgency, scope and work it would
unblock. Outcome and health updates retain their own source and history.
Open the detail or linked evidence to understand it; viewing a request is
not approval or delivery, and closing a queue item is not proof of a
completed product outcome. Missing or incomplete reads stay visible.

Preview terminals before opening them

TERMINALS lists saved and derived views with their members and resolved
layout. A preview is passive. Deliberate Open uses the inspected plan and
reports opened, absent or degraded members, including partial failures.
Help and side trips return to the same preview and page. The observed native
provider journey uses Herdr; broader provider limits are listed below.

CONFIG keeps full values, defaults and source/override provenance readable.
Help supplies command descriptions, grammar and examples, including during
startup failures. Narrow views retain scrolling and return controls. Health
keeps INFO severity separate from Unknown assessment, exposes stale and
unavailable reads, and explains that an empty findings list is not a healthy
verdict. The complete empty-health explanation is readable at 80 columns.

Choose oversight for the work in front of you

Human-led work is quiet by default for process-only diagnosis. Explicit
delegation can enable that oversight during planning as well as execution,
subject to the existing diagnosis policy and delivery prerequisites. Ordinary
work reminders and operational health retain their behavior. Scope, phase
and posture come from explicit sources; unresolved identity stays unknown.

Use rig mode effective with an explicit scope to inspect the result.
The scoped operating posture reference
describes selection and precedence. A posture preference grants no execution
authority. Correction records can retain selected current guidance and
distinguish an assessment, an action actually taken and a later observed
effect. These are supported mechanics, not evidence of improved judgment:
natural behavioral effect remains UNOBSERVED, and human time cost remains
UNMEASURED. No cure or reduced recurrence is claimed.

Update context without discarding local authorship

rig context add <repository-path-or-URL> --git retains the relationship
between a Git source, its checkout and a selected context pack. Use --pack
when selecting a pack within a repository. Existing Git credentials apply.

Use rig context source inspect <ref> to inspect local changes, conflicts,
revision and selection without fetching. rig context source update <ref>
explicitly fetches and merges upstream before selecting clean content.
Committed local work survives an ordinary merge. Dirty work, conflicting
changes, unavailable upstreams or edits to the served selection cause a
named refusal rather than a reset or overwrite. Resolve and commit, or abort
the merge, in the retained checkout before retrying; the prior served
selection remains available during a conflict. Updates do not push.

Checkout history, selected served bytes and actual agent consumption remain
different facts. Read the selected bytes with rig context get <ref> and
check the intended consumer. This does not automatically synchronize every
context library or adopt guidance into running agents.

Operator notes and validation limits

Root, CLI, daemon and web-UI package versions are 0.5.13. The terminal TUI
retains its independent 0.1.0 version. Node requirements are unchanged.
The ordered migration head advances from 079 to
080_scoped_operating_posture, extending the existing mode-binding store
with scoped human-led/delegated choices while preserving legacy rows.
Use the supported upgrade and continuity procedure when adoption is
authorized; preparing this candidate performs no live migration or restart.

Accepted development evidence connects the journey at 140×42 and 80×24,
including unavailable/Unknown controls, two-project isolation, current-source
reading, deliberate native terminal opening and Git conflict preservation.
Those observations retain their original development cuts and attribution.
Version, release-note and package checks are separate from those journeys;
they are not a new whole-release usability study.

• Simultaneous default TUI clients can replace one another's programmatic
  control-socket address. This remains a known, unfixed limitation, judged
  nonblocking for the demonstrated single-client human journey. Unique test
  sockets do not prove product-level multi-client isolation; historical lost
  requests remain unverified.
• Native terminal proof covers Herdr. SSH login, cmux end-to-end behavior
  and effects on a parent host remain unverified. Existing native continuity
  evidence is reused only for unchanged paths, not new provider coverage.
• A private shutdown timed out while closing connections; clean completion
  and pending effects remain unverified. Earlier sandbox public-start failures
  remain recorded failures despite a later successful managed private start.
• Synthetic findings and requests exercise mechanics, not natural behavioral
  improvement or real human approval/delivery. No unfamiliar-human study,
  real-host reboot or all-platform run is established.
• Exact-cut verification and publication authorization are complete for this
  cut, and the substance receipt binding was re-measured at the publishing seat.
  npm availability was subsequently confirmed and the registry artifact verified
  byte-identical to the accepted archive. Nothing here authorizes adoption beyond
  the VM-only adoption already recorded.

Install

npm install -g @openrig/cli@0.5.13

Release identity

• Commit: bda26cb90def54b844260f12a63ce9cabc50509c
• Tree: ee5b73d91f1c21c6a8edb0457e9875ff196ba9da
• Previous public main: b6c8d8f0444bc721d0ba4062a7384d25601c1c6f (fast-forward, 31 commits)