v0.5.7 — elastic topology and coherent work delivery

OpenRig v0.5.7 — elastic topology and coherent work delivery

OpenRig 0.5.7 makes a running topology easier to create and reshape without
hand-authoring YAML, and gives agents a coherent, addressable install of the
work they are joining.

Elastic topology lifecycle

• Create without YAML. Start a rig from public CLI inputs without first
  authoring a RigSpec.
• Grow the topology in place. Add one or several members to an existing
  pod, or create and populate a new pod, with mixed outcomes reported
  honestly.
• Keep the declaration faithful. Spec show/export preserves the topology,
  including a member's declared agent-image source, so save and recreate do
  not silently change how that member launches.
• Shrink safely. Removal refuses while a target owns active work. An
  explicit drain fallback preserves queue-item identity and state, verifies
  that the fallback session is live, and removes only the intended seat or
  pod. Ordinary no-work cleanup remains direct.

Coherent work delivery

• Composable product-journey SDLC. The shipped work model composes world,
  project, mission, and slice context instead of requiring one monolithic
  briefing.
• Useful work-install defaults. Fresh project, mission, and slice
  scaffolds provide conventional Markdown and manifest files without
  overwriting authored content.
• Optional YAML enrichment. A project manifest can add an authored intent
  and ordered context addresses. Invalid optional values warn explicitly and
  retain the safe default install.
• Addressable Markdown loading. Installed skills can resolve precise
  Markdown sections by relative address, including through normal symlinked
  plugin projections.
• Explicit project identity. Agents can select and switch between projects
  without carrying context across roots; ambiguous, duplicate, and unknown
  identities refuse instead of guessing.
• Complete public plugin-only skill catalog. Every cataloged public skill
  supplied only by a plugin is projected with the helper files its
  instructions reference.

Verification performed

• Targeted Node 22 daemon and CLI lifecycle/work-install suites and affected
  package builds passed throughout the surviving release range, with
  independent QA and scope/maintainability review at the completed user-story
  boundaries.
• The product cut at 14e785197 was packaged and installed in an isolated VM.
  Daemon health reported that exact clean commit, SQLite quick_check passed,
  and the existing ready topology was preserved across cutover.
• Disposable public CLI journeys covered create, grow, faithful export,
  guarded shrink, explicit drain fallback, and project/mission/slice work
  installation. A fresh agent session reconstructed the current five-piece
  work frontier through the installed command without cross-project leakage.
• A bounded TUI smoke opened the live topology, exercised help and basic
  navigation, and exited cleanly.
• The final release-note-only cut carries no product-source change from the
  validated product cut. Its package assembly, hash-bound surface review, and
  substance-gate receipt are release-manager gates that must pass before tag or
  publication.

Operator notes

• Database migration head is 077_node_session_source; normal daemon startup
  applies the ordered migration list automatically. No manual migration step
  is required.
• Run the exact-cut substance gate and retain its durable receipt before any
  tag, GitHub Release, or npm publication. Candidate QA does not imply those
  publication acts occurred.

Known limitations

• Restore-honesty and disaster-path work are deferred to 0.5.8.