Colonizer v0.2.17

Colonizer v0.2.17

What's new

• Observability can replay archived colonies (--include-archive) and write an offline export to a file (colonizer observability export). Both observability backfill and the new observability export accept --include-archive, which also reads colonies that live only in the local log archive: the latest revision of each bundle, only the ledgers the exporter already reads (events, harness, gateway, findings — credential files are never opened), with disk winning when a colony exists in both places and ids derived from the bundle's original host id so a replay still matches what was exported live; archived colonies export structure only. Watch the retention window (#606): a sweep can delete bundles before a backfill reads them. colonizer observability export --out FILE|DIR writes the OTLP/JSON requests the exporter would have sent — one request per line, files 0600, an existing directory getting logs.jsonl and traces.jsonl inside — without contacting any backend, for an OpenTelemetry Collector to replay elsewhere or as a support bundle; --since/--until/--signals logs,traces narrow it, and --content includes conversation text only after a typed yes on a terminal — the flag stands in for the install switch, so an organisation's opt-in and each colony's sensitivity still apply. (#859)
• A fleet owner may relay members' synced history to its own observability backend, and members are told before they push.
• understand-anything: a shared knowledge graph, built once per commit of main and handed to every colony on the repository. An org's ua_graph setting — off by default, read like merge_prs (owner/name, an org's name, or *) — names the repositories the mothership builds a graph for. A dedicated "Knowledge graph" colony runs the full /understand pass the cost guard refuses everywhere else: once, then incrementally whenever a 10-minute tick sees main move past the stored graph (a failed pass is retried at most once an hour). Every colony on the repository then finds the newest graph at .ua/knowledge-graph.json — bound read-only when its base is the graph's commit, else a writable copy plus a note in its brief to refresh only the changed files — and .ua/ stays git-excluded either way. The graph colony's cost runs through the model router like any colony's and shows on the cockpit's Code page ("Open knowledge graph" for the raw JSON, owner-only, "graph jobs: $X"), as does GET /api/understand-anything/graphs/{owner}/{name}. Until the pinned plugin is prebuilt host-side — /understand needs packages/core/dist/index.js, which the pin ships as TypeScript source; a follow-up issue tracks the build — the graph colony refuses to launch. (#1015)
• Observability: the exporter add-on installs itself — colonizer add observability. The
• One untaggable release no longer blocks every later tag. The release train's tag job now skips an older merged release that fails the gate when a newer release commit supersedes it (a notice, not a failure), and the gate accepts fragments that landed on main while the release pull request was open, since they belong to the next release. A fragment that was there when the release was cut still blocks its tag. node scripts/release-prep.mjs tags prints what the job would do. (#1396)
• The Release workflow runs the same history-aware changelog gate as the release train, so a tag whose leftover fragments landed during the release freeze publishes instead of failing at "Check the changelog covers the tag".

Prebuilt Colonizer for Linux x86_64 (with KVM) and Apple Silicon Macs, built from a730a0c.

curl -fsSL https://colonizer.dev/install.sh | sh

The installer checks the archive against SHA256SUMS. It fetches the Claude Agent SDK from the npm registry, and on a Mac the Linux build of Claude Code, from Anthropic's own channels: neither is in the release. Guide: https://colonizer.dev/docs/install

Each artifact, SHA256SUMS included, also carries a build-provenance attestation recording the commit that built it. Verify one with:

gh attestation verify colonizer-<platform>.tar.gz --repo Colonizer-dev/harness

Here is linux-x86_64 or darwin-arm64.

Apple Silicon Macs can also use Colonizer-arm64.dmg: an unsigned app, so macOS asks you to approve it once (System Settings > Privacy & Security > Open Anyway). The curl installer above is the recommended path.

a596817a734ed88e6a0ab357dbe9861d7abd67511a1ba965bc5ddcbf0ece43ae  colonizer-darwin-arm64.tar.gz
42035c3a4852706821365d807f093e19936c00169191163b91a3a09c331073a4  colonizer-linux-x86_64.tar.gz
19304c78fb5e728141ca54cb83c1352ed517462ef4242e20b9ddeeed2a9c7643  Colonizer-arm64.dmg
e608fc5270f739c657807725e98bb82718ed357c20b7a93746ce20ba65bad8f6  install.sh