Gitmoot v0.9.1.3
The brain gets a memory of its own memory: this release ships the append-only brain changelog end to end — every fact mutation is journaled, browsable from a new dashboard view, and queryable from the CLI — alongside keychain-secured pipeline credentials and transcript retention.
What's new since v0.9.1.2
- Brain changelog (#988). A
memory_eventsjournal records every brain mutation (create, update, retire, unretire, supersede, confirm, promote, ingest, cluster changes) in the same transaction as the mutation itself — edits keep the previous content, so "what did this fact say before?" finally has an answer.gitmoot memory logreads the feed (--key/--agent/--repo/--kind/--since),memory log --idtells one fact's full biography, andmemory log backfillidempotently synthesizes history from pre-existing tombstones. - Brain page: Graph | Changelog switcher. The
/braindashboard gains a second view — a day-grouped, live-updating ledger with per-kind expansions (before/after diffs on edits, retirement reasons, successor links), fact biographies, burst collapse for groom sweeps, deep links, and full mobile support. Served by cursor-paged/api/brain/eventsand/api/brain/fact(which resolves retired and superseded facts too). - Keychain credentials for pipelines (#874, #968, #974, #982). A registry of named keys with per-pipeline grants and override resolution, proxied keys for shell stages, pipeline-owned
env_file+ per-stageenv_keyssecret injection, a names-only Keys projection on pipeline detail, and a Config-page Keychain section (registry, grants, file status). - Transcripts grow up (#904, #989 P1). Opt-in retention with universal teeing and trajectory JSONL export, plus round-2 styled rendering and deterministic Markdown export.
- Pipeline polish. Produce stages declare read-only inputs via
reads:(#965) with Claude runtime hook resources auto-allowlisted (#983); the run-detail DAG renders stage deps horizontally (#969); descriptions show inpipeline list(#973). - Daemon reliability. Runtime-session leases heartbeat while in-process runners are live (#986); dangling repo checkouts self-heal to the primary (#959); the stale-task reconciler logs its tick counts (#913).
Upgrading
gitmoot update on a released build, or download gitmoot_<os>_<arch> from the release assets (sha256sums included). After upgrading, run gitmoot memory log backfill once per home to seed the journal from your existing facts — repeat runs are no-ops.