release: v0.2.0

Author: jarimustonen

CHANGELOG.md

@@ -4,10 +4,7 @@ All notable changes to `orchestratectl` are documented here. The format
 follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the
 project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
-
-> **0.2.0 in progress — breaking.** Entries below accumulate toward the 0.2 simplification release
-> (per `docs/decisions/0001-thin-supervisor-vs-harden.md`); they include breaking CLI removals.
+## [0.2.0] - 2026-08-16
 
 ### Removed
 
@@ -21,6 +18,10 @@ project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ### Added
 
+- **Thin supervisor A6/A1/A5 — explicit worker-exit facts, typed outcomes, and attention-required visibility.** Workers now launch through a thin `run-worker` shim that records the true child exit status/signal as a durable `worker.exited` fact. The supervisor consumes a typed outcome table instead of the old pid×pane×branch×activity-clock inference: `run merge` is the only success truth; non-zero/signal exits fail with work preserved; exit-0-without-merge becomes visible `attention_required`, not done or failed. `run wait` now settles on that non-terminal attention state, and `run show` / `run list` surface resume hints without mutating the run terminal. The idle-unmerged / git-reconcile auto-success heuristics are gone.
+- **Teardown safety hardening for non-merge outcomes.** Non-explicit-merge teardown now fails closed when it cannot prove cleanup is safe: dirty worktrees are preserved, git errors preserve instead of remove, detached-HEAD / stale-branch / no-branch worktrees with unique committed work are preserved, and source-relative branch checks are no longer the only guard. This closes the review-found data-loss edges introduced by relying on committed-branch reachability alone.
+- **Run-report provenance and rollup correctness.** New `ReportOrigin` provenance distinguishes Agent, Supervisor, and RunMerge-authored reports. Outcome classification, reducer merge adoption, and the landed/report-marker fallback now trust typed `RunMerge` origin and only honor legacy `via` markers when the origin field is genuinely absent, keeping old runs readable while preventing forged merge markers. Supervisor run rollup is now log-authoritative for leaf nodes rather than projection-scan based, so a crash-interrupted node projection cannot make the run terminalize while a log-visible node is still live.
+- **Bundled skill install guard for pi.dev.** The `stint-start` and `stint-handoff` bundled skill descriptions are trimmed below pi.dev's 1024-character description limit while keeping their Finnish/English trigger phrases and disambiguators, and a unit test now rejects any bundled skill description over that limit.
 - **`config` noun — inspect the config file path and effective resolved config with per-key source (`config-subcommand`).** Follow-up to `run-create-harness-flag` (which introduced `~/.orchestratectl/config.toml` `[harness]` but no inspection surface). Two read-only verbs per AGENTS-AI-FIRST-CLI §8: `orchestratectl config path` prints the config file location (with `exists`, whether or not the file is present — so a caller never has to guess where to write settings), and `orchestratectl config show` prints the effective resolved configuration as per-key rows — `harness.default` plus one `harness.<kind>` per creatable run kind — each carrying its `source` (`env | file | default`) so an agent can reason about **why** a value is what it is. The harness rows reuse the existing `harness::select` precedence resolver verbatim (per-kind override → section default → built-in), so `config show` never re-implements resolution; an `ORCHESTRATECTL_HARNESS` override honestly shadows every row to `source: "env"`. Each row carries a `secret` flag and the §8 redaction contract (`--show-secrets` to reveal, warning on stderr) is wired for future secret-valued keys, though none exist today. Strict validation: a bad harness value in the file fails the command loudly (`invalid_harness`) rather than being silently laundered. Both verbs support `--output json|jsonl|text`; the payloads carry `schema_version_config`. Never mutates the config file.
 - **`run merge --report-file` no longer blocks a clean merge on a malformed *advisory* report field (`merge-report-schema-lenience`).** The terminal §7.3 report was validated strictly *before* the git merge, so an advisory-field typo (the recurring `title`/`detail` instead of `spinoff_proposals[].proposed_title`/`proposed_kind`/`rationale`) rejected the whole report and blocked the merge of already-committed, reviewed code. `run merge` now validates leniently: the required, correctness-bearing fields (`success`, the `cancelled`/`reason` §7.7 cross-constraints, root-object shape) stay **strict** — a violation there still returns `schema_violation` (now carrying its structured `expected` hint) and performs no merge — but the advisory sections (`summary`, `discussion_items`, `spinoff_proposals`, `wrap_up_recommendations`) **degrade gracefully**: a malformed element is dropped from the persisted report and surfaced as a machine-readable `report_advisory_warnings[]` entry (plus a human-readable `warnings` line), never a merge blocker. Also visible under `--dry-run`, which doubles as a report-file preflight. Merge authorization/provenance is unchanged — `run merge` stamps the authoritative `ReportOrigin::RunMerge` after validation; `node report` and merge-recovery keep strict validation. (New `octl_core::sanitize_report_advisory`; 3-model `/llm-review` + `/assess-findings` applied.)
 - **Thin supervisor A5 follow-up — per-node branch-preserving `run cancel --node` for fan-out (`per-node-run`).** `orchestratectl run cancel <run-id> --node <node-id>` cancels exactly ONE live node of a multi-node fan-out — for unblocking a single stuck child without killing the batch (design §2.5). It appends only that node's terminal cancel `node.report` and **no** `run.status`: the run stays live while its siblings run, and the supervisor's rollup terminalizes the batch (`done | failed | cancelled`) only once every node has settled. The cancelled node classifies as `TerminalOutcome::Cancelled` → `Teardown::SourceRelative`, so its branch + worktree are preserved (invariant 5) — never force-deleted. The node set is resolved log-authoritatively (a node whose projection write was crash-interrupted is still cancellable; an absent id is a `node_not_found` user error), and the operation is idempotent: a duplicate per-node cancel converges/no-ops without a second report. The supervisor rollup now returns `cancelled` (not `failed`) when every terminal node was cancelled and none failed. The whole-run `run cancel <run-id>` form is unchanged. (design.md §2.5/§2.6.)

Cargo.lock

@@ -3,7 +3,7 @@ resolver = "2"
 members = ["crates/octl-core", "crates/octl-cli"]
 
 [workspace.package]
-version = "0.1.8"
+version = "0.2.0"
 edition = "2021"
 rust-version = "1.85"
 license = "MIT"

Cargo.toml

@@ -21,7 +21,7 @@ path = "src/main.rs"
 workspace = true
 
 [dependencies]
-octl-core = { path = "../octl-core", version = "=0.1.8" }
+octl-core = { path = "../octl-core", version = "=0.2.0" }
 clap = { workspace = true }
 serde = { workspace = true }
 serde_json = { workspace = true }

crates/octl-cli/Cargo.toml

@@ -5,72 +5,72 @@ expression: value
 {
   "schema_version": 1,
   "data": {
-    "version": "0.1.8",
+    "version": "0.2.0",
     "commit": "[COMMIT]",
     "skills": [
       {
         "name": "orchestratectl-overview",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "octl-run-overview",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "octl-spawn-spinoff",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "worktree-spinoff",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "worktree-merge",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "worktree-research",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "worktree-technical-decision",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "worktree-bug-analysis",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "worktree",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "worktree-status",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "stint-start",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "stint-handoff",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       },
       {
         "name": "fan-out",
-        "cli_version": "0.1.8",
+        "cli_version": "0.2.0",
         "schema_version": 1
       }
     ],

crates/octl-cli/tests/snapshots/envelope_snapshots__version_json.snap

@@ -2,4 +2,4 @@
 source: crates/octl-cli/tests/envelope_snapshots.rs
 expression: value
 ---
-{"schema_version":1,"data":{"version":"0.1.8","commit":"[COMMIT]","skills":[{"name":"orchestratectl-overview","cli_version":"0.1.8","schema_version":1},{"name":"octl-run-overview","cli_version":"0.1.8","schema_version":1},{"name":"octl-spawn-spinoff","cli_version":"0.1.8","schema_version":1},{"name":"worktree-spinoff","cli_version":"0.1.8","schema_version":1},{"name":"worktree-merge","cli_version":"0.1.8","schema_version":1},{"name":"worktree-research","cli_version":"0.1.8","schema_version":1},{"name":"worktree-technical-decision","cli_version":"0.1.8","schema_version":1},{"name":"worktree-bug-analysis","cli_version":"0.1.8","schema_version":1},{"name":"worktree","cli_version":"0.1.8","schema_version":1},{"name":"worktree-status","cli_version":"0.1.8","schema_version":1},{"name":"stint-start","cli_version":"0.1.8","schema_version":1},{"name":"stint-handoff","cli_version":"0.1.8","schema_version":1},{"name":"fan-out","cli_version":"0.1.8","schema_version":1}],"schema_version":1,"supported_schemas":[1],"state_schema_version":1,"supported_state_schemas":[1]},"warnings":[]}
+{"schema_version":1,"data":{"version":"0.2.0","commit":"[COMMIT]","skills":[{"name":"orchestratectl-overview","cli_version":"0.2.0","schema_version":1},{"name":"octl-run-overview","cli_version":"0.2.0","schema_version":1},{"name":"octl-spawn-spinoff","cli_version":"0.2.0","schema_version":1},{"name":"worktree-spinoff","cli_version":"0.2.0","schema_version":1},{"name":"worktree-merge","cli_version":"0.2.0","schema_version":1},{"name":"worktree-research","cli_version":"0.2.0","schema_version":1},{"name":"worktree-technical-decision","cli_version":"0.2.0","schema_version":1},{"name":"worktree-bug-analysis","cli_version":"0.2.0","schema_version":1},{"name":"worktree","cli_version":"0.2.0","schema_version":1},{"name":"worktree-status","cli_version":"0.2.0","schema_version":1},{"name":"stint-start","cli_version":"0.2.0","schema_version":1},{"name":"stint-handoff","cli_version":"0.2.0","schema_version":1},{"name":"fan-out","cli_version":"0.2.0","schema_version":1}],"schema_version":1,"supported_schemas":[1],"state_schema_version":1,"supported_state_schemas":[1]},"warnings":[]}

crates/octl-cli/tests/snapshots/envelope_snapshots__version_jsonl.snap

@@ -2,7 +2,7 @@
 source: crates/octl-cli/tests/envelope_snapshots.rs
 expression: value
 ---
-orchestratectl 0.1.8
+orchestratectl 0.2.0
 commit:                  [COMMIT]
 envelope schema:         1
 supported envelopes:     1