@rungs/cli 0.2.0 → 0.3.1

package/README.md

@@ -138,6 +138,10 @@ reported as diverged and left alone.
 | `rungs setup git [path]` | Install the merge drivers `.gitattributes` names |
 | `rungs modules` | List the set and audit the manifests |
 | `rungs backlog archive` | Move finished items to `archive/`, repointing every link that cites them |
+| `rungs session start <branch>` | Cut a branch and worktree from the last **verified** merge, not the tip |
+| `rungs preflight [path]` | Did the integration branch change files *you* changed? |
+| `rungs land <branch>` | Merge → verify the merged tree → advance with a compare-and-swap, or refuse and park it |
+| `rungs worktrees [path]` | Which worktrees are merged, prunable, or merged and still dirty |
 
 | Option | Effect |
 | --- | --- |
@@ -169,6 +173,10 @@ you when you are installing above your level.
 | **4** docs that restate each other | `doc-authority` |
 | **5** 5+ concurrent sessions | `concurrency` |
 
+The last four commands are the `concurrency` loop. They drive git, which nothing else in rungs
+does — [ADR-0009](docs/decisions/ADR-0009-rungs-drives-git.md) sets the rules they obey: verify
+before you advance, never destroy (only refuse), and never hold the integration branch.
+
 `concurrency` refuses to install without `--confirm-threshold`, because below
 five simultaneous sessions every mechanism in it costs more than it returns.
 Selling rung 5 to a rung-1 repo is the most likely way this tool does harm.
@@ -212,22 +220,27 @@ Four promises that shape everything else:
 
 ## Status
 
-**Next release: v0.2.0** — assembled from [`changelog.d/0.2.0.md`](changelog.d/0.2.0.md) and
-prepared in [`package.json`](package.json), untagged until the
-[release runbook](docs/design/release-runbook.md) is run to completion. That number is checked
-against the manifest by the `docs-version-claims` gate, so this sentence cannot drift from what
-ships.
+**Current release: v0.3.1** — that number is checked against [`package.json`](package.json) by the
+`docs-version-claims` gate, so this sentence cannot drift from what ships — and the gate fails if
+the sentence is reworded out of existence, because a claim nothing checks any more should not look
+the same as a claim that passes.
+
+It deliberately does **not** say "and it is on npm". Whether this version is tagged and published
+is a fact about the registry, not about the manifest, and it was wrong here for two days once
+already.
 
-What is **published** is deliberately not restated here. It lives on
-[the versions page](https://docs.rungscli.com/versions/), which is the one place that tracks it —
-this file and the roadmap both carried their own copy and both said `v0.1.2` for two days after
-v0.1.3 went to npm.
+Whether a release is **pending**, and what npm currently serves, live on
+[the versions page](https://docs.rungscli.com/versions/) — the one place that tracks them. This
+file and the roadmap both carried their own copy and both said `v0.1.2` for two days after v0.1.3
+went to npm. Cutting the next one follows the [release runbook](docs/design/release-runbook.md).
 
-rungs is installed in its own repo and its gates run on every change — 25 pass,
-0 fail (`rungs check`, 2026-08-17). A clean consumer has also installed the packed
-artifact and completed the doctor → init → add → check → render → upgrade/eject
-journey locally. Detection is [verified against all four source repos](docs/design/detection-verification.md).
-Not yet done: an install from the public registry and a cross-platform release matrix.
+rungs is installed in its own repo and its 29 gates run on every change — 29 pass,
+0 fail (`rungs check`, 2026-08-17). A clean consumer has installed from the **public
+registry** and run the binary, and another completed the doctor → init → add → check →
+render → upgrade/eject journey from a packed artifact. Detection is
+[verified against all four source repos](docs/design/detection-verification.md).
+Not yet done: a cross-platform release matrix — only Windows is verified — and writing
+to a repo rungs did not scaffold.
 
 Expect module *contents* to move. The command surface is settled.
 
@@ -248,7 +261,7 @@ nobody paid for does not ship.
 | [`docs/design/`](docs/design/README.md) | Product brief, module catalogue, verification |
 | [`docs/decisions/`](docs/decisions/README.md) | ADRs |
 | [`modules/`](modules/README.md) | The fifteen modules |
-| [`src/`](src/) | The CLI, ~4,700 lines (`wc -l src/*.ts`, 2026-08-17; held within 10% by `docs-version-claims`) |
+| [`src/`](src/) | The CLI, ~5,100 lines (`wc -l src/*.ts`, 2026-08-17; held within 10% by `docs-version-claims`) |
 
 ## Licence