Gitmoot v0.9.1.2

Highlights

Pipelines became a platform. This release completes the pipeline-share arc:

Chain pipelines on success (#922) — trigger: {kind: pipeline, pipeline: A} runs B exactly once per newly-succeeded run of A: durable cursor advanced transactionally with the run creation, no backfill on enable, add-time cycle detection, after: A mode chips. The built-in memory chain now runs on real ordering instead of a clock stagger.
Groups (#934) — free-form group: display field with repo-name fallback; built-in memory pipelines ship under "Gitmoot System". The dashboard renders collapsible group sections (Ledger Line): collapsed-by-default rows with enabled fractions, health dots and due hints; per-group expansion persists.
Descriptions (#940) — pipelines explain their own scope; shown in pipeline show and above the stage graph on the detail page.
Export/import bundles (#935) — pipeline export/import: a directory bundle carrying the verbatim spec (repo parameterized, comments preserved), agent template snapshots, and a requirements manifest with write-authority re-consent. Imports land disabled after a printed requirements report. Zero credential material by construction.
GitHub publish/pull (#941) — pipeline remote set / publish --create (private by default, no-op republish) / pull --list / pull: share a working pipeline as easily as an agent template.

The board and the galaxy stopped lying.

Tasks wedged in blocked/implementing with an open PR are auto-promoted to pr_open, so "Needs you" can no longer miss a PR awaiting review (#920).
Clicking any agent in the Galaxy opens its dossier — runtime, model, role, capabilities, policy, health, today's jobs and tokens, template — with a graceful "ephemeral worker" card for one-off agents (#951).

Operability

The daemon surfaces build skew — a running daemon serving old code is now visible (#932).
CI race-shard timings are reconciled instead of discarded, keeping the 13-lane split honest (#930).
Task-board reconciliation hardening (#953) and cache tier-2 (#956).

Includes the pipeline_trigger_states migration (applies automatically on first start).
To adopt groups/descriptions on pre-existing default memory pipelines, re-add their specs (install-defaults skips existing rows).