From 83c06b6aff326f79bc0798cf74d27f3a0caf11bf Mon Sep 17 00:00:00 2001 From: Sam Catlow Date: Tue, 22 Sep 2026 17:17:58 +1000 Subject: [PATCH] feat(release): one release stream, one version, one page per version CHANGELOG.archied.md and CHANGELOG.archie.md were two version streams that drifted: a release that moved both components had two numbers, two pages and two tags, and a reader had to visit two files to learn what shipped. The merged history holds 65 versions from 64 archied and 34 archie sections -- 33 that both components released, 31 only archied, one only archie -- so 98 published pages become 65. A version's date is the newest of its sections' dates, and a component whose own date differs carries it on its label, because the history has two dates and the merge must not invent one. `## [Unreleased]` is not a release: it gets no page, and it stays at the top of the file. A level-two heading is where the merge could silently drop a section, so the merge is verified by content rather than by the generator: section counts per source, the merged version set against the exact union, and every source `###` title present both as a substring and, after stripping the component prefix, as an identical heading. Counting `##` headings rather than releases overcounts by one here, which is how the empty `[Unreleased]` block was caught. - newsgen reads one file and writes `docs/news/.md`, the index, the canonical `releases.json`, and `docs/news/redirects.json`. The redirect table is what keeps the retired `/news///` URLs alive; it is generated beside the pages so it cannot drift from them. - release.sh takes one `--version`, keeps commit and tag (the Woodpecker pipeline that will own them does not exist yet), and exits 3 when the commit set justifies no release, so a pipeline can finish green without tagging. - The consumers of the two files follow: the deploy workflow's tag gate and release-notes extraction, the zip contents, the update check's changelog links, the packaged-path note, the docs skill, and newsgen's tests. The per-component detail survives as labelled sections inside each release, so a reader still learns whether archied or the agent changed; what goes away is the separate numbers and the separate pages. --- .../skills/archie-docs-and-writing/SKILL.md | 14 +- .github/workflows/deploy.yml | 37 +- CHANGELOG.archie.md | 431 ---- CHANGELOG.archied.md | 1276 ------------ CHANGELOG.md | 1819 ++++++++++++++++- Taskfile.yml | 31 +- docs/architecture/configuration.md | 2 +- docs/data/generated/dev-docs.json | 4 +- docs/news/{archied => }/1.0.0.md | 11 +- docs/news/{archied => }/1.1.0.md | 17 +- docs/news/{archied => }/1.10.0.md | 6 +- docs/news/{archied => }/1.11.0.md | 6 +- docs/news/{archied => }/1.11.1.md | 6 +- docs/news/{archied => }/1.12.0.md | 6 +- docs/news/1.13.0.md | 7 + docs/news/{archied => }/1.14.0.md | 6 +- docs/news/{archied => }/1.15.0.md | 6 +- docs/news/{archie => }/1.16.0.md | 35 +- docs/news/1.16.1.md | 7 + docs/news/{archie => }/1.17.0.md | 11 +- docs/news/{archied => }/1.17.1.md | 6 +- docs/news/{archied => }/1.18.0.md | 11 +- docs/news/{archied => }/1.19.0.md | 6 +- docs/news/{archied => }/1.19.1.md | 6 +- docs/news/{archied => }/1.19.10.md | 6 +- docs/news/{archied => }/1.19.2.md | 6 +- docs/news/{archied => }/1.19.3.md | 6 +- docs/news/{archied => }/1.19.4.md | 6 +- docs/news/{archied => }/1.19.5.md | 24 +- docs/news/{archied => }/1.19.6.md | 6 +- docs/news/1.19.7.md | 11 + docs/news/{archied => }/1.19.8.md | 6 +- docs/news/{archied => }/1.19.9.md | 10 +- docs/news/{archied => }/1.2.0.md | 30 +- docs/news/{archied => }/1.20.0.md | 18 +- docs/news/{archied => }/1.21.0.md | 19 +- docs/news/{archied => }/1.22.0.md | 6 +- docs/news/{archied => }/1.23.0.md | 48 +- docs/news/{archied => }/1.24.0.md | 6 +- docs/news/{archied => }/1.25.0.md | 11 +- docs/news/{archied => }/1.26.0.md | 52 +- docs/news/{archied => }/1.27.0.md | 18 +- docs/news/{archied => }/1.28.0.md | 35 +- docs/news/{archied => }/1.29.0.md | 22 +- docs/news/{archie => }/1.3.0.md | 11 +- docs/news/1.3.1.md | 7 + docs/news/{archied => }/1.30.0.md | 39 +- docs/news/{archied => }/1.31.0.md | 50 +- docs/news/{archied => }/1.32.0.md | 18 +- docs/news/{archied => }/1.32.1.md | 6 +- docs/news/{archied => }/1.33.0.md | 6 +- docs/news/{archied => }/1.34.0.md | 6 +- docs/news/{archied => }/1.35.0.md | 22 +- docs/news/{archied => }/1.36.0.md | 8 +- docs/news/{archied => }/1.37.0.md | 12 +- docs/news/{archie => }/1.4.0.md | 10 +- docs/news/1.4.1.md | 7 + docs/news/{archied => }/1.5.0.md | 6 +- docs/news/{archied => }/1.6.0.md | 6 +- docs/news/{archied => }/1.7.0.md | 6 +- docs/news/{archied => }/1.8.0.md | 6 +- docs/news/1.9.0.md | 20 + docs/news/{archied => }/1.9.1.md | 10 +- docs/news/{archied => }/1.9.10.md | 6 +- docs/news/1.9.11.md | 7 + docs/news/1.9.2.md | 11 + docs/news/1.9.3.md | 15 + docs/news/1.9.4.md | 12 + docs/news/{archied => }/1.9.5.md | 12 +- docs/news/1.9.6.md | 11 + docs/news/1.9.7.md | 11 + docs/news/1.9.8.md | 11 + docs/news/1.9.9.md | 11 + docs/news/archie/1.0.0.md | 6 - docs/news/archie/1.1.0.md | 12 - docs/news/archie/1.16.1.md | 5 - docs/news/archie/1.18.0.md | 6 - docs/news/archie/1.19.5.md | 19 - docs/news/archie/1.19.7.md | 5 - docs/news/archie/1.19.9.md | 5 - docs/news/archie/1.2.0.md | 25 - docs/news/archie/1.20.0.md | 13 - docs/news/archie/1.21.0.md | 14 - docs/news/archie/1.23.0.md | 35 - docs/news/archie/1.25.0.md | 6 - docs/news/archie/1.26.0.md | 47 - docs/news/archie/1.27.0.md | 7 - docs/news/archie/1.28.0.md | 20 - docs/news/archie/1.29.0.md | 11 - docs/news/archie/1.30.0.md | 20 - docs/news/archie/1.31.0.md | 29 - docs/news/archie/1.32.0.md | 13 - docs/news/archie/1.35.0.md | 13 - docs/news/archie/1.9.0.md | 10 - docs/news/archie/1.9.1.md | 5 - docs/news/archie/1.9.2.md | 5 - docs/news/archie/1.9.3.md | 7 - docs/news/archie/1.9.4.md | 5 - docs/news/archie/1.9.5.md | 7 - docs/news/archie/1.9.6.md | 5 - docs/news/archie/1.9.7.md | 5 - docs/news/archie/1.9.8.md | 5 - docs/news/archie/1.9.9.md | 5 - docs/news/archied/1.13.0.md | 5 - docs/news/archied/1.16.0.md | 30 - docs/news/archied/1.17.0.md | 6 - docs/news/archied/1.19.7.md | 5 - docs/news/archied/1.3.0.md | 6 - docs/news/archied/1.3.1.md | 5 - docs/news/archied/1.4.0.md | 5 - docs/news/archied/1.4.1.md | 5 - docs/news/archied/1.9.0.md | 9 - docs/news/archied/1.9.11.md | 5 - docs/news/archied/1.9.2.md | 5 - docs/news/archied/1.9.3.md | 7 - docs/news/archied/1.9.4.md | 6 - docs/news/archied/1.9.6.md | 5 - docs/news/archied/1.9.7.md | 5 - docs/news/archied/1.9.8.md | 5 - docs/news/archied/1.9.9.md | 5 - docs/news/index.md | 165 +- docs/news/redirects.json | 132 ++ docs/news/releases.json | 491 +---- docs/prds/release-stream-and-commit-rules.md | 7 + internal/releaseannounce/announcer_test.go | 14 +- mkdocs.yml | 3 +- scripts/archie-update-check | 4 +- tools/newsgen/changelog.go | 69 +- tools/newsgen/changelog_test.go | 37 +- tools/newsgen/main.go | 103 +- tools/newsgen/main_test.go | 91 +- tools/newsgen/render.go | 49 +- tools/newsgen/render_test.go | 60 +- tools/release.sh | 240 +-- 134 files changed, 3189 insertions(+), 3241 deletions(-) delete mode 100644 CHANGELOG.archie.md delete mode 100644 CHANGELOG.archied.md rename docs/news/{archied => }/1.0.0.md (51%) rename docs/news/{archied => }/1.1.0.md (78%) rename docs/news/{archied => }/1.10.0.md (93%) rename docs/news/{archied => }/1.11.0.md (90%) rename docs/news/{archied => }/1.11.1.md (67%) rename docs/news/{archied => }/1.12.0.md (82%) create mode 100644 docs/news/1.13.0.md rename docs/news/{archied => }/1.14.0.md (62%) rename docs/news/{archied => }/1.15.0.md (97%) rename docs/news/{archie => }/1.16.0.md (55%) create mode 100644 docs/news/1.16.1.md rename docs/news/{archie => }/1.17.0.md (68%) rename docs/news/{archied => }/1.17.1.md (63%) rename docs/news/{archied => }/1.18.0.md (65%) rename docs/news/{archied => }/1.19.0.md (67%) rename docs/news/{archied => }/1.19.1.md (59%) rename docs/news/{archied => }/1.19.10.md (50%) rename docs/news/{archied => }/1.19.2.md (51%) rename docs/news/{archied => }/1.19.3.md (71%) rename docs/news/{archied => }/1.19.4.md (50%) rename docs/news/{archied => }/1.19.5.md (57%) rename docs/news/{archied => }/1.19.6.md (53%) create mode 100644 docs/news/1.19.7.md rename docs/news/{archied => }/1.19.8.md (78%) rename docs/news/{archied => }/1.19.9.md (75%) rename docs/news/{archied => }/1.2.0.md (62%) rename docs/news/{archied => }/1.20.0.md (67%) rename docs/news/{archied => }/1.21.0.md (58%) rename docs/news/{archied => }/1.22.0.md (83%) rename docs/news/{archied => }/1.23.0.md (63%) rename docs/news/{archied => }/1.24.0.md (93%) rename docs/news/{archied => }/1.25.0.md (76%) rename docs/news/{archied => }/1.26.0.md (66%) rename docs/news/{archied => }/1.27.0.md (84%) rename docs/news/{archied => }/1.28.0.md (67%) rename docs/news/{archied => }/1.29.0.md (81%) rename docs/news/{archie => }/1.3.0.md (78%) create mode 100644 docs/news/1.3.1.md rename docs/news/{archied => }/1.30.0.md (79%) rename docs/news/{archied => }/1.31.0.md (75%) rename docs/news/{archied => }/1.32.0.md (70%) rename docs/news/{archied => }/1.32.1.md (92%) rename docs/news/{archied => }/1.33.0.md (92%) rename docs/news/{archied => }/1.34.0.md (92%) rename docs/news/{archied => }/1.35.0.md (76%) rename docs/news/{archied => }/1.36.0.md (85%) rename docs/news/{archied => }/1.37.0.md (88%) rename docs/news/{archie => }/1.4.0.md (88%) create mode 100644 docs/news/1.4.1.md rename docs/news/{archied => }/1.5.0.md (96%) rename docs/news/{archied => }/1.6.0.md (90%) rename docs/news/{archied => }/1.7.0.md (96%) rename docs/news/{archied => }/1.8.0.md (93%) create mode 100644 docs/news/1.9.0.md rename docs/news/{archied => }/1.9.1.md (59%) rename docs/news/{archied => }/1.9.10.md (81%) create mode 100644 docs/news/1.9.11.md create mode 100644 docs/news/1.9.2.md create mode 100644 docs/news/1.9.3.md create mode 100644 docs/news/1.9.4.md rename docs/news/{archied => }/1.9.5.md (65%) create mode 100644 docs/news/1.9.6.md create mode 100644 docs/news/1.9.7.md create mode 100644 docs/news/1.9.8.md create mode 100644 docs/news/1.9.9.md delete mode 100644 docs/news/archie/1.0.0.md delete mode 100644 docs/news/archie/1.1.0.md delete mode 100644 docs/news/archie/1.16.1.md delete mode 100644 docs/news/archie/1.18.0.md delete mode 100644 docs/news/archie/1.19.5.md delete mode 100644 docs/news/archie/1.19.7.md delete mode 100644 docs/news/archie/1.19.9.md delete mode 100644 docs/news/archie/1.2.0.md delete mode 100644 docs/news/archie/1.20.0.md delete mode 100644 docs/news/archie/1.21.0.md delete mode 100644 docs/news/archie/1.23.0.md delete mode 100644 docs/news/archie/1.25.0.md delete mode 100644 docs/news/archie/1.26.0.md delete mode 100644 docs/news/archie/1.27.0.md delete mode 100644 docs/news/archie/1.28.0.md delete mode 100644 docs/news/archie/1.29.0.md delete mode 100644 docs/news/archie/1.30.0.md delete mode 100644 docs/news/archie/1.31.0.md delete mode 100644 docs/news/archie/1.32.0.md delete mode 100644 docs/news/archie/1.35.0.md delete mode 100644 docs/news/archie/1.9.0.md delete mode 100644 docs/news/archie/1.9.1.md delete mode 100644 docs/news/archie/1.9.2.md delete mode 100644 docs/news/archie/1.9.3.md delete mode 100644 docs/news/archie/1.9.4.md delete mode 100644 docs/news/archie/1.9.5.md delete mode 100644 docs/news/archie/1.9.6.md delete mode 100644 docs/news/archie/1.9.7.md delete mode 100644 docs/news/archie/1.9.8.md delete mode 100644 docs/news/archie/1.9.9.md delete mode 100644 docs/news/archied/1.13.0.md delete mode 100644 docs/news/archied/1.16.0.md delete mode 100644 docs/news/archied/1.17.0.md delete mode 100644 docs/news/archied/1.19.7.md delete mode 100644 docs/news/archied/1.3.0.md delete mode 100644 docs/news/archied/1.3.1.md delete mode 100644 docs/news/archied/1.4.0.md delete mode 100644 docs/news/archied/1.4.1.md delete mode 100644 docs/news/archied/1.9.0.md delete mode 100644 docs/news/archied/1.9.11.md delete mode 100644 docs/news/archied/1.9.2.md delete mode 100644 docs/news/archied/1.9.3.md delete mode 100644 docs/news/archied/1.9.4.md delete mode 100644 docs/news/archied/1.9.6.md delete mode 100644 docs/news/archied/1.9.7.md delete mode 100644 docs/news/archied/1.9.8.md delete mode 100644 docs/news/archied/1.9.9.md create mode 100644 docs/news/redirects.json diff --git a/.agents/skills/archie-docs-and-writing/SKILL.md b/.agents/skills/archie-docs-and-writing/SKILL.md index b16cf752c..f7b17c995 100644 --- a/.agents/skills/archie-docs-and-writing/SKILL.md +++ b/.agents/skills/archie-docs-and-writing/SKILL.md @@ -47,7 +47,7 @@ Verified on 2026-09-18: | `docs/architecture/*.md` | Focused target decisions, active review procedure, migration inventory | Read each file's status | | `docs/architecture/migration-decisions.md` | `OPEN` migration inventory constrained by approved decisions | Close a question only after code-grounded review | | `docs/archive/` | `HISTORICAL` material | Mine rationale and failure evidence | -| `CHANGELOG.md`, `CHANGELOG.archied.md`, `CHANGELOG.archie.md` | Component release-note index and packaged runtime inputs | Keep gateway and agent-runtime entries separate; `internal/releaseannounce` parses version headings | +| `CHANGELOG.md` | Release stream and packaged runtime input | One file holds every release; `internal/releaseannounce` parses version headings | | `tools/docsgen` | Current, partial generator in nested `tools` Go module | Treat its flags and tests—not planned PRD commands—as executable truth | | `docs/data/generated/contracts.json` | Current working-tree `GENERATED` output | Regenerate; never edit by hand | | `docs/` | Repository documentation only | Nothing builds, renders, or publishes it; Markdown is the artifact | @@ -119,15 +119,15 @@ Distinguish evidence strength: ## Maintain component changelogs -Keep gateway behavior in `CHANGELOG.archied.md` and agent-runtime behavior in -`CHANGELOG.archie.md`; keep `CHANGELOG.md` as their index. -`Dockerfile.archied` copies both component files to `/usr/share/archie/`, and +Keep every release's notes in `CHANGELOG.md`; a release is one version, and +the components' entries are labelled sections inside it. +`Dockerfile.archied` copies it to `/usr/share/archie/`, and `internal/releaseannounce.changelogSection` parses a version heading. -Version-heading format is settled as of 2026-09-18: both component changelogs -use `## [1.27.0]` with no `v` prefix, `changelogSection` searches for +Version-heading format is settled as of 2026-09-18: the changelog uses +`## [1.27.0]` with no `v` prefix, `changelogSection` searches for `## []`, and `.github/workflows/deploy.yml` gates each release tag with -`grep -q "^## \[$ver\]" CHANGELOG..md`. The earlier +`grep -q "^## \[$ver\]" CHANGELOG.md`. The earlier `vX.Y.Z`-vs-`X.Y.Z` contradiction involved `.gitea/workflows/deploy.yml`, which was dropped (`dd9bddc2 ci: build and push images to GHCR, drop the Gitea workflow`), so that question is `HISTORICAL`, not `OPEN`. The remaining guard is diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index ff59af4f7..3c4589bbe 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -6,7 +6,7 @@ name: deploy on: push: branches: [main] - tags: ["archied/v*", "archie/v*"] + tags: ["archied/v*", "archie/v*", "v*"] # Rapid successive pushes to main (a release commit right after its # preceding fix, say) previously queued a full gate+build for each one, @@ -46,12 +46,12 @@ jobs: - name: Resolve archied tag at HEAD id: release_tag run: | - version="$(git tag --points-at HEAD --list 'archied/v*' | sed 's|^archied/v||' | sort -V | tail -1)" + version="$(git tag --points-at HEAD --list 'archied/v*' --list 'v*' | sed -e 's|^archied/v||' -e 's|^v||' | sort -V | tail -1)" echo "archied_version=$version" >> "$GITHUB_OUTPUT" if [ -n "$version" ]; then echo "archied release at HEAD: $version" else - echo "no archied tag at HEAD; distribution zip will be skipped" + echo "no release tag at HEAD; distribution zip will be skipped" fi - name: Set up Go @@ -111,21 +111,22 @@ jobs: fail=0 for tag in $(git tag --points-at HEAD); do case "$tag" in - archied/v*) - # Strip the "v" too: tags are archied/vX.Y.Z, changelog - # sections are "## [X.Y.Z]" (see tools/release.sh). - ver="${tag#archied/v}" - echo " archied tag $tag -> looking for [$ver] in CHANGELOG.archied.md" - grep -q "^## \\[$ver\\]" CHANGELOG.archied.md || { - echo " FAIL: CHANGELOG.archied.md has no [$ver] section" + v*) + ver="${tag#v}" + echo " release tag $tag -> looking for [$ver] in CHANGELOG.md" + grep -q "^## \\[$ver\\]" CHANGELOG.md || { + echo " FAIL: CHANGELOG.md has no [$ver] section" fail=1 } ;; - archie/v*) - ver="${tag#archie/v}" - echo " archie tag $tag -> looking for [$ver] in CHANGELOG.archie.md" - grep -q "^## \\[$ver\\]" CHANGELOG.archie.md || { - echo " FAIL: CHANGELOG.archie.md has no [$ver] section" + archied/v* | archie/v*) + # Legacy per-component tags. History is not re-tagged, and the + # merged CHANGELOG.md carries every component's versions, so the + # section is found there rather than in a component file. + ver="${tag#*/v}" + echo " legacy tag $tag -> looking for [$ver] in CHANGELOG.md" + grep -q "^## \\[$ver\\]" CHANGELOG.md || { + echo " FAIL: CHANGELOG.md has no [$ver] section" fail=1 } ;; @@ -290,7 +291,7 @@ jobs: name="archie-core-archied-v${{ steps.version.outputs.version }}-linux-amd64" mkdir -p "$name" cp dist/archied dist/archie-gateway dist/archie-state-store dist/archie-ui dist/archie-messaging dist/archie-playbooks "$name/" - cp deployments/INSTRUCTIONS.md CHANGELOG.md CHANGELOG.archied.md CHANGELOG.archie.md "$name/" + cp deployments/INSTRUCTIONS.md CHANGELOG.md "$name/" # README.md doesn't exist yet in this repo; include it once it does # rather than fail the release on its absence. [ -f README.md ] && cp README.md "$name/" @@ -332,9 +333,9 @@ jobs: index($0, hdr) == 1 { printing = 1 } printing && /^## \[/ && index($0, hdr) != 1 { exit } printing { print } - ' CHANGELOG.archied.md > "$notes" + ' CHANGELOG.md > "$notes" if ! [ -s "$notes" ]; then - echo "no [$version] section extracted from CHANGELOG.archied.md" >&2 + echo "no [$version] section extracted from CHANGELOG.md" >&2 exit 1 fi # Idempotent: --clobber replaces the asset and leaves the notes diff --git a/CHANGELOG.archie.md b/CHANGELOG.archie.md deleted file mode 100644 index 48994f745..000000000 --- a/CHANGELOG.archie.md +++ /dev/null @@ -1,431 +0,0 @@ -# archie-agent changelog - -## [1.35.0] - 2026-09-22 - -The sandboxed runtime links the same shared packages as archied, so this release carries the -channel-lifecycle store contract and the stricter action-load errors with it: - -- The channel-status store contract (`PutChannelStatus`/`ListChannelStatus`) and its replace-the-set - semantics. -- Authoritative module ids and stricter action load errors: a misspelled result field, an unknown id, - or a dynamic `actions` read now fails the playbook load rather than the dispatch. - -archied and archie-agent move together in this release. - -## [1.32.0] - 2026-09-22 - -The sandboxed runtime links `storecontract` and `staterpc`, so it carries the dispatch-ledger -contract alongside archied: - -- The shared `store.ErrAlreadyDispatched` sentinel now describes both dedup ledgers -- - `binding_dispatches` per `(binding_id, capture_id)`, and `playbook_dispatches` per - `(playbook_id, playbook_version, event_id, action_id)`. Each is an at-most-once guarantee. -- `RecordPlaybookDispatch` is part of the store contract the runtime builds against. - -archied and archie-agent move together in this release. - -## [1.31.0] - 2026-09-22 - -The sandboxed runtime links the same shared packages as archied, so this -release carries the control-plane and workflow changes alongside it: - -- Runtime administration over the State Store's gRPC server, resource history, - and control-plane apply status on the store contract. -- The shared step vocabulary, owned by a family manager registered at each - composition root, and `gate.diff-rules` in place of `.archie/gate.go` - (fails closed on a change it never read). -- The workflow pin crosses the wire. - -Runtime-specific changes: - -- `refactor(plugin)`: the unused `Registry` type is deleted. -- `yaegiutil` refuses incomplete Yaegi interface wrappers at load rather than - running them. -- The runtime config overlay is deleted. -- The state store dial installs client keepalive, and the server policy accepts - the dialer's pings. -- The MCP client supports per-server `parallel_tool_calls`. -- A late max-uptime callback no longer resurrects teardown state. -- A webhook route path no longer becomes a sender identity. - -Note: the `archie-agent` image is rebuilt by this tag through CI -(`.github/workflows/deploy.yml`); a gateway-only release would not have rebuilt -it. `docker compose pull agent` is required to pick it up. - -## [1.30.0] - 2026-09-20 - -- The sandboxed runtime picks up line-anchored review comments: a finding is - posted against the line it is about, with a suggested fix where it has one, - and a suggestion is rejected unless it is single-line -- GitHub applies a - multi-line suggestion only up to its first line, silently corrupting the - file (#891). -- `diff_cap_lines` is an optional value in the shared config the runtime - reconstructs, so an explicit `0` means "no cap" rather than being rewritten - to the default. **Behaviour change** for a repo that set `0` expecting - unlimited and was silently getting 400 (#899). -- A diff-cap park names a remedy that exists: a parked task's actions are - retry, abandon and reject, so the reason no longer says "approve manually". -- A released container is not torn down twice -- the reaper no longer deletes - teardown bookkeeping before `Release` is finished with it (#893). -- Build toolchain: `gofumpt` and `golangci-lint` are pinned as one matched - pair, and `task fmt` uses the same engine the gate checks with, so the - runtime's own gate is satisfiable (#901). - -## [1.29.0] - 2026-09-19 - -- The sandboxed runtime picks up the review-reaction envelope and its - owned-PR authorization, so an agent can only react to reviews on pull - requests it opened itself. -- `google.golang.org/grpc` bumped past `v1.84.0` to patch - [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443) (shared dependency - with `archied`; the pre-release commit is pinned pending a stable - `v1.85.0`). - -## [1.28.0] - 2026-09-19 - -- The sandboxed runtime picks up the attempt-attribution contract, so the events - and changes an agent produces are recorded against the attempt that produced - them. -- `grep` can use the workspace codesearch index. -- A worktree is handed back on every sandbox exit, and container teardown is - claimed once — a released container's reaper is cancelled rather than - re-firing during the grace period. -- Retries recover from worktree path-type conflicts instead of failing - opaquely. -- A parked workflow run records its park reason in its own log. -- Triage criteria distinguish the workflows, and a workflow is required when a - code change is needed. -- Namespaced forge labels match when routing by kind. -- The `ARCHIE_REACTIONS` fan-out stream is provisioned. -- Collection fields decoded over the State Store gRPC contract are never nil - slices, so an empty collection marshals as `[]` rather than `null`. - -## [1.27.0] - 2026-09-17 - -- The per-task runtime picks up the new State Store task-log read contract, so - the sandboxed agents share one log-reading path with the daemon and the - dashboard. - -## [1.26.0] - 2026-09-17 - -- feat(config): add [scheduling] config block -- fix(webui): count every chat front-end in the published projection -- fix(scheduling): respect configuration ownership -- feat(ratelimit): wire per-identity inbound rate limiting into the gateway -- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it -- fix(daemon): carry kind/label routing bindings to the process that routes -- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone -- fix(logging): keep the live descriptor open across a failed rotation -- fix(agentworker): wire configured tool-result policy into worker's LoopRunner -- refactor(staterpc): delete the superseded single-token auth interceptor -- refactor(tools): delete unreachable dispatch/gating engine -- feat(channels): wire chat.webhook route config through to the gateway -- refactor(tools): delete unreachable AST-based tool discovery -- refactor(tools): delete unused plugin-tool registration API from builtin.Registry -- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted) -- fix(staterpc): preserve marshal_error marker in eventDataJSON -- fix(gate): validate finding level and share the blocking threshold -- fix(tools/provider/mcp): preserve MCP binary tool results for delivery -- refactor(tools/mcp): delete unreachable MCP adaptation path -- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path -- refactor(skillbuild): delete dead AugmentRegistry path -- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout -- refactor(binding): delete dead Matcher.Overlaps method -- refactor(forge): delete dead CreateIssue surface -- fix(mcp): cancel in-flight SSE reconnect on Stop -- fix(container): enforce MaxUptime lifetime cap with a timer -- refactor(forge): delete the unwired RepliesAfter surface -- refactor(config): delete the two decoded-but-unread policy fields - -The runtime carries a smaller, more focused set of changes than the same -version's archied entry: agent-side tool-result policy is now wired into the -worker's loop, MCP binary tool results survive to delivery, the container -`MaxUptime` lifetime cap is enforced with a timer, and a scheduled run records -completion so it does not re-fire each tick. - -Note that several bullets above name config, webui and ratelimit packages. Those -are attributed here by the release tool's package-closure rule (`go list -deps` -over the agent binary), not because the agent owns them; the substantive -runtime changes are the worker, MCP, container and scheduling fixes. - -This entry also confirms the removal of the dead `IncrementRetryCount` State -Store RPC, which the agent reaches through `staterpc` rather than by calling it -directly. - -## [1.25.0] - 2026-09-15 - -- chore: no user-facing changes; versioned so the 1.25.0 release tags both - components at the same commit - -## [1.23.0] - 2026-09-12 - -The agent runtime now reaches task state through the State Store gRPC contract -(`STATE_STORE_URL`/`STATE_STORE_TOKEN`, injected by the daemon) instead of the -NATS `storerpc` transport, which is deleted. Credentials handed to a task -container are scoped to that task rather than being the daemon's own token. -Running a 1.23.0 daemon against an older agent image will not work; rebuild or -pull the `archie-agent` image with this release. - -- feat(state-store): generalize storerpc as the State Store gRPC contract (#770) -- feat(state-store): stand up archie-state-store binary and own archie.db (#771) -- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774) -- fix(state-store): task-scope container credentials, stream large capture lists, validate Update -- fix(staterpc): attach the bearer token to State Store streams -- feat(staterpc): carry the dashboard's configuration snapshot -- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754) -- refactor(store): move the producer-owned contracts to internal/contracts/store/v1 -- feat(contracts): add gateway service seams and protobuf toolchain -- fix(gateway): drop services.gateway.mode, remote is the only transport -- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview) -- feat(gateway): operator-triggered PR review with selectable reviewer model -- feat(workflow): surface adversarial review findings on the PR body -- feat(workflow): review calibration, checked properties and style nits out of contract -- fix(workflow): order findings before footer; test the report stash -- fix(archied): share one PR reviewer across channels; harden forge and worktree -- feat(worktree): Resume re-syncs a worktree onto its branch tip -- feat(telegram): support secret refs for bot tokens (#705) -- feat(gateway): wire progressive tool disclosure (bridge tools) -- feat(archied): serve the daemon's own health endpoint -- feat(archieui): standalone UI process over remote Gateway and State Store -- refactor(archied): move webhook capture intake to the process that owns work intake -- refactor(ui): sever the archie-ui binary from every daemon runtime package -- fix(archieui): resolve service tokens from env, without requiring a config file - -## [1.21.0] - 2026-09-03 - -- feat(workflow): make kind-to-workflow routing YAML-overridable -- feat(workflow): route arbitrary forge labels to workflows via playbook YAML -- feat(workflow): load kind/label bindings from multiple playbook directories -- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive -- feat(eda): Module position first slice -- registry + side-effect-free log kind -- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch -- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch -- fix(binding): split ValidateForUpdate so edits can preserve the secret -- refactor(eda): extract helpers to satisfy cyclop/gocognit gates -- fix(eda): make playbook key collision reporting deterministic - -## [1.20.0] - 2026-09-03 - -- fix: baseline gate repair (go test ./... -count=1) -- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler -- feat(image): define provider-neutral image capability contract and config -- fix(workflow): stop discarding baseline-fix commits as 'no changes' -- fix(workflow): net cache hits from token totals, trim gate-retry output -- feat(workflow): dynamic triage instead of defaulting every task to implement -- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated -- feat(store): encrypt playbook binding secrets at rest -- fix(store): satisfy makezero when building cipher payload - -## [1.19.9] - 2026-09-02 - -- feat(config): config surface for memory engine selection - -## [1.19.7] - 2026-09-02 - -- fix(logging): make Tail/Page allocation bound explicit for CodeQL - -## [1.19.5] - 2026-09-01 - -- feat(tasks): allow rejecting a task from any non-terminal state -- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta -- fix: go.mod bumped to 1.27.0 and stupid tests removed -- refactor: go modernisation fixes -- refactor: remove unused Operator param. -- fix(plugin): add missing CLAUDE.md reference to plugin engine rule -- fix(app): repoint archied wiring contract test at internal/app/archied -- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet -- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui -- fix(app): repoint capability-host wiring contract test at internal/app/archied -- refactor(lint): extract more helpers to clear nestif/gocyclo findings -- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult -- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization -- fix(lint): noctx fixes and dead-code cleanup -- feat(workflow): adversarial self-review stage before PR open - -## [1.18.0] - 2026-08-28 - -- feat(logging): cursor pagination and filtering for task_logs -- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29 - -## [1.17.0] - 2026-08-25 - -- Compact task history against the selected model's real context capacity without imposing a token cap. -- Preserve completed steps and billed usage when a later provider call fails; failed compaction now keeps the original history and continues. -- Persist detailed agent-stage usage through the daemon-owned store before lossy live event fan-out. -- Apply configured or forge-derived author and committer identity to sandboxed task commits. - -## [1.16.1] - 2026-08-25 - -- fix(agentworker): reconcile task clone ownership after commits - -## [1.16.0] - 2026-08-25 - -**Version realigned with `archied`.** This release jumps from 1.9.9 to 1.16.0 -to put the two components on matching numbers; there are no 1.10-1.15 agent -releases. It clears the accumulated runtime backlog in one cut rather than -bundling it as a rider on a later change, so the list below spans several -weeks of work rather than one session's. - -Highlights: - -- feat(nats): run an embedded server when no external NATS is configured, and - expose the embedded broker to managed task workers -- feat(deployment): default to managed NATS workers; the daemon requires a - full-task worker handoff and the legacy in-process, subprocess and - single-stage execution paths are gone -- feat(forge): GitHub webhook receiver for immediate issue dispatch, with - dedup regression proof; unbound webhook events are stored retention-bounded -- feat(webui): payload field mapping -- bind JSON paths to named fields and - preview before saving -- feat(scheduling): ticker engine with configurable interval and pools -- feat(storage): persist agent project state -- feat(agent): stamp archie-agent's build and report it back to the daemon -- feat(tools): `generate_video` via MiniMax, gated behind config, and - `MultimodalResult.URLs` for remote-hosted media -- feat(workflow): define the adversarial-review findings contract - -Fixes: - -- fix(worktree): bind publication to dispatch grants; reset retries to a - pristine base; reject diffs without a merge base; clean untracked files when - `.git` is a gitdir file; post-push metadata resilience, cancellation and - branch naming -- fix(container): persist the npm cache for per-task MCP servers -- fix(agentexec): recover omitted finish calls -- fix(agentworker): move JSONL decode into storage, unblocking CI -- fix(telegram): compact tool output and drop turn caps -- fix(webui): give dashboard-initiated updates a phase-2 report; restore the - provider gate and dashboard token accounting -- refactor: remove dead `BasePlatformAdapter` code and legacy execution paths - -Shared with archied 1.16.0 (these packages are in both closures): - -- feat(telegram): send local files as uploads, not fetchable URLs -- fix(webui,sendfile): close three holes the adversarial review found -- fix(webui): validate mutation Origin against the effective external scheme - -## [1.9.9] - 2026-08-18 - -- chore: no user-facing changes - -## [1.9.8] - 2026-08-17 - -- chore: no user-facing changes - -## [1.9.7] - 2026-08-17 - -- chore: no user-facing changes - -## [1.9.6] - 2026-08-16 - -- chore: no user-facing changes - -## [1.9.5] - 2026-08-16 - -- refactor: decompose the daemon bootstrap into phased wiring (no behaviour change; complexity-driven restructure) -- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity -- fix(tools): avoid predeclared `max` names - -## [1.9.4] - 2026-08-15 - -- chore: no user-facing changes - -## [1.9.3] - 2026-08-15 - -- fix(logging): resolve error attrs to their message string, not {} -- fix(agentworker): back off before refetching a nak'd stage message -- feat(agentexec,workflow): surface tool calls on the task timeline - -## [1.9.2] - 2026-08-15 - -- fix(worktree): force checkout so retry recovers from a dirty worktree - -## [1.9.1] - 2026-08-15 - -- fix(agentworker): forward workflow events across the NATS worker boundary - -## [1.9.0] - 2026-08-15 - -- fix(agent): resolve git dubious-ownership in sandbox containers -- feat(agent): mark the mounted worktree as a git safe directory -- fix(agent): route git safe.directory setup through markWorktreeSafe -- feat(chat): show tool calls inline and stream replies into one message -- refactor(agent): move worker runtime into application layer -- fix(config,webui): make show_tool_calls one cross-channel setting - -## [1.4.0] - 2026-08-10 - -- feat(gateway): tool-approval gate, session tools for chat, and /delete command -- feat(gateway): make chat turns durable and idempotent -- feat(webui): lifecycle-safe task controls with atomic retry and archive -- feat(logging,workflow): daemon log feed and executable workflow registry -- fix(store,gateway): taskstate constants and mobile jump-to search -- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams -- fix(build): install ripgrep where grep.go actually needs it on PATH -- fix(workflow): carry gate output into the baseline park error -- feat(logging): add a per-task log sink -- feat(agentexec): publish agent-side logs to the task's system subject -- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed -- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool -- refactor(store): replace legacy persistence with SQLite -- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe -- feat(config): SIGHUP-triggered reload with requires-restart warnings -- feat(config): surface overlay state, shadowed keys, and per-row reset -- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state -- fix(config): preserve nil slices in Clone to avoid spurious reload warnings - -## [1.3.0] - 2026-08-08 - -- feat(curator): engine family contract, registry, and runtime -- feat(curator): trigger accounting — primary-input wake path -- feat(logging): optional rotating log file -- feat(daemon): identity-scoped isolation -- fix(secrets): wire provider credentials through engines -- fix(store): surface task timestamps and tag the summary structs -- fix(tools): let an optional provider fail without taking the daemon down -- fix(tools): report a cancelled find walk as an error, not empty results -- fix(worktree): name the missing forge credential when a push fails -- fix: close the duplicate-work loop and the dead paths around it -- perf(tools): drop the embedded ripgrep binaries -- refactor: one definition of what approving or declining a task means -- refactor: move workflow into its own domain - -## [1.2.0] - 2026-07-31 - -- feat: add MCP client capabilities to archied and archie-agent -- fix: Transition() ignores `from` status guard, allowing lost updates -- fix: skillscript.Run ignores context, cannot be canceled/timed out -- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup -- fix(indexing): surface index config properly and stop silent degradation -- refactor(worktree): replace git shell-out with go-git v6 -- fix(worktreerpc): bound handler contexts and drop the git binary from tests -- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries -- refactor: route tasks on a typed kind, not forge labels -- fix(natsrpc): make RegisterAll wait for the server to see subscriptions -- refactor(config): move loading into infrastructure/configuration -- refactor: add internal/eventbus as the broker-neutral messaging contract -- feat(tools): lift tau's file and shell tools into the tool registry -- feat: make /stop cancel the running chat turn -- fix: kill the whole process group when a shell command is cancelled -- feat: refuse unrecoverable shell commands -- feat: make /stop reach running agent tasks -- fix: use errors.Is/As for context errors and cleanup -- fix(grep): distinguish ripgrep exit 1 from a failed search -- fix(docker): slim both images and repair unreachable Go tooling -- fix(container): write the task boot brief under .git - -## [1.1.0] - 2026-07-27 - -- feat: add streamed agent execution with typed message events -- feat: add MCP client transports and managed tool-provider discovery -- feat: add memory context scrubbing and normalized memory tool schemas -- feat: add plugin metadata extraction from `metadata.archie.plugins` -- feat: add configurable container networking for daemon-launched runtimes -- fix: preserve valid UTF-8 when clipping runtime output -- fix: make MCP stdio lifecycle, retries, and timeout handling race-safe -- fix: enforce a zero-finding lint and vet baseline - -## [1.0.0] - 2026-07-22 - -- feat: ship the isolated agent runtime, NATS RPC boundary, workflow execution, skills, and plugin support -- feat: publish the `archie-agent` container image to the Gitea registry diff --git a/CHANGELOG.archied.md b/CHANGELOG.archied.md deleted file mode 100644 index 058c16124..000000000 --- a/CHANGELOG.archied.md +++ /dev/null @@ -1,1276 +0,0 @@ -# archied changelog - -## [1.37.0] - 2026-09-22 - -### A request is attributed to the identity that made it - -- **A browser can sign in, and an action taken through it records the person.** The dashboard validates a - provider-issued token, resolves it to an identity, and attaches it to the request; the task-action record - then names the actor. `Authenticate` and the sign-in callback share one resolver, so a browser sign-in - cannot be accepted on terms a presented token would be refused on. -- **archie issues no session.** The callback stores the provider's own token in an HttpOnly cookie and every - later request re-verifies it, so nothing archie holds can outlive the provider's decision and there is no - session table to expire, revoke or get wrong. -- **The event kind describes the actor.** A person's approval records `human_approved` as that person; an - agent's records `agent_approved`; an action with no authorising principal records `task_approved` with the - attribution fields **empty**. Nothing is credited to an identity that did not act, and an unattributed - action is recorded as unattributed rather than guessed. -- The acting identity is derived from the presented credential and **never** from a request field: a body - carrying `actor`, `actor_id`, `identity` and an `X-Archie-Actor` header still cannot choose it. - -### A host install now works, and an update refuses a host it cannot keep consistent - -- `install.sh` writes and enables **all five** host units; previously it seeded only `archied.service`, so a - fresh host ran one service of five and an operator applied the rest by hand from a runbook. The runbook is - a description again: it names the units and points at `systemctl --user cat`. -- **Every host binary reports its version**, and the updater reads all of them **before it can report - "nothing to install"**. A host whose binaries disagree is refused, naming each one: a newer messaging - binary beside an older state store crash-loops against a service the older store does not serve, and that - install previously looked healthy from the updater's point of view. -- The packaged, installer and updater command lists are pinned by a test, so a service added to one and not - the others fails the gate instead of shipping a partial install. - -### A release image can be traced to a commit - -- The publish step derives the commit by **dereferencing the ref** rather than reading `github.sha`, because - every release tag in this repository is annotated and a tag's object id is not a commit. An immutable - `sha-` tag is published alongside `:latest`, and a build with no release tag is stamped - `dev+` rather than a bare `dev` that identified nothing. - -### Curator definitions are data, not a second registry - -- Curator definitions may come from configuration or code and run through **one** engine into the existing - registry — no parallel authority and no second config reader. A definition declares its tools, and an - unknown tool name fails rather than widening the set silently. - -## [1.36.0] - 2026-09-22 - -### The dashboard declares tools an in-browser agent can call - -- The dashboard registers **seven WebMCP tools**. Read-only: `list_tasks`, `get_task`, - `recent_events`, `daemon_health`. Recovery: `retry_task`, `stop_task`, `cancel_task`. An agent - operating the dashboard now reads structured state and recovers stuck work instead of scraping the - UI. -- Every tool wraps the same `ui/src/lib/api.ts` client the dashboard itself calls, so an agent and a - person exercise one path rather than two. -- `archie-ui` cannot be attributed to the agent that called it: a page can invoke its own tools, so an - agent's call and a page script's call reach the server identically. Tools therefore record the - signed-in identity and a source, and **never** that an agent acted. - -### Binaries built by the development build task can be updated - -- `task build` passed the `installtype` stamp for three of six commands, so `archie-messaging`, - `archie-state-store` and `archie-ui` were built without it. An unstamped binary reports `unknown` - and the self-update path **refuses rather than guesses**, which is how an operator ends up unable to - update with `install type is unknown` and no way forward. All six are stamped now, and a test reads - the build task and fails naming any command line that omits it. - -## [1.35.0] - 2026-09-22 - -### The Messaging Service is severed from the store and workflow runtime - -- `cmd/archie-messaging` no longer links `modernc.org/sqlite`, `internal/store`, - `internal/domain/workflow` or `internal/agentexec`. All four arrived through a single import of - `internal/app/controlplane`; the client half now lives in - `internal/infrastructure/controlplanerpc`, and the app package keeps the server, the registry, the - seeds, the validators and the schema derivation. -- The resource documents are type-aliased back into the app package, so there is one definition read - under two names rather than a copy per side. - -### Channel lifecycle reaches the dashboard - -- The Messaging Service reports each channel's state, recorded **per channel**: one channel's failure - marks only itself, a channel that cannot start is marked failed **with its reason** rather than only - logged, and one that returns is marked stopped. `internal/channels/status.Manager` reports each channel's state. -- `PutChannelStatus`/`ListChannelStatus` carry that to the dashboard, following the config-snapshot - split. The store **replaces the reported set**, so a channel the reporter stops mentioning is - deleted rather than left as a stale `running`; an empty report clears the table, because hosting no - channels is a fact worth reporting; and an id-less row is refused, since it could never be replaced - or removed by a later report. -- `Service.ReloadChannel` routes to the channel's own seam and refuses a channel that cannot reload - with a reason rather than accepting and ignoring it. `ReloadSupported` was previously declared **by - name**, so a channel could advertise reload with nothing behind it; one function now decides both. - -### Action playbooks: a second playbook shape, with typed results - -- A playbook is now one of two shapes: a **workflow playbook** (exactly one `workflow` action, - unchanged) or an **action playbook** (one or more `module` actions in order). A playbook does not - mix them. -- `args` and `when` share one compilation path and one evaluation context, and `actions.` is typed - by the kind that action runs, so a misspelled result field, an unknown id, a map index, `in`, a - comprehension, or a shape-foreign key (`kind` on a `workflow` action, `workflow` on a `module` - action) is a **load failure** rather than a dispatch failure. -- **Action playbooks load but do not run yet.** Routing arrives with the first side-effecting - position; the daemon warns at load rather than accepting them silently. -- The CEL environment is built per playbook, because result typing depends on the ids a playbook - declares. -- `ModuleRegistry.DecodeResult` turns a kind's flat map result into its typed `Result` before a later - expression reads it. Without it a typed read evaluated against a shape the run never produces, and - so silently read null. - -## [1.34.0] - 2026-09-22 - -### Dashboard: an actionable authentication failure state - -- An unauthenticated **document** request now receives a self-contained HTML page with a - paste-the-token form, instead of plain text. Previously the whole dashboard -- `index.html`, the - bundle and every asset -- sat behind the token check, so a bookmarked bare URL returned a - `text/plain` "unauthorised: open the dashboard URL archied logged at startup", the SPA never ran, - and none of the dashboard's existing failure surfaces were reachable at all. -- The response is still **401**, with `Cache-Control: no-store` and a CSP. It is deliberately not a - 200: a login page served as success would be cacheable, would read as healthy to anything that - checks status alone, and a shared cache could hand it to the wrong person. -- API and stream callers are unaffected. `application/json`, `*/*` and `text/event-stream` requests - keep the plain-text 401, with a test pinning that split so an XHR or an `EventSource` reconnect can - never start receiving a page. -- The auth banner gains a **Retry** action that re-runs the dashboard's bootstrap reads, so a - recovered session is actionable without a browser-level reload. It deliberately does not re-drive - the SSE stream, which already reports its own reconnect state. -- The page's guidance stays generic: it points at the dashboard URL the daemon logs rather than - naming where the token is stored, so the HTTP layer is not coupled to the token file's location. - -## [1.33.0] - 2026-09-22 - -### EDA: playbook action arguments are compiled at load (J2) - -- A playbook action may now declare `args`, compiled as CEL expressions when the playbook loads. - `args` and `when` share one compilation path and one evaluation context, so an expression written - for one works in the other. -- **Behaviour change:** an `args` expression that does not compile is a **load failure**, not a - runtime miss — the same reject-at-load rule already applied to a binding collision and to an - unknown `actions.`. In practice, a daemon loading a playbook with a malformed `args` block - fails at startup rather than part-way through a dispatch. -- Compiling several arguments now reports the **first** bad key deterministically (keys are sorted). - Previously it ranged a map, so the reported bad key could differ between runs and the failure was - not reproducible. -- `args` is deliberately **inert** for now: parsed, compiled and stored, but no shipped position - consumes it yet. A consumer arrives with the first side-effecting position. - -**Not yet decided:** how an `args` evaluation failure behaves at dispatch. The `when` predicate rule -(error, skip, log) does not obviously transfer, because `args` is data rather than a predicate, and -silently skipping an action whose arguments failed to evaluate would be a silent failure of exactly -the kind this release train has been removing. It currently propagates the error to the caller, and -that asymmetry is documented at the code. Ratifying it against a real consumer is tracked separately. - -## [1.32.1] - 2026-09-22 - -### Host packaging: `archie-messaging` now ships and updates - -- `cmd/archie-messaging` is included in the distribution zip, and `scripts/archie-update-install` - installs and restarts it. -- **Why this mattered.** v1.30.0 moved Telegram, email and webhook out of `archied` and into - `archie-messaging`, but nothing packaged the new binary. A host install that upgraded across - v1.30.0 therefore ran on with **no messaging process at all**: `archied` logged that it stopped - serving the telegram gateway, nothing replaced it, and Telegram stayed dead — with no error - logged anywhere, because nothing was failing. The process simply did not exist. -- The host component set was enumerated in four places — the zip's build loop, the zip's copy list, - the installer's service list, and the installer's binary list — and `archie-messaging` was missing - from all four. The duplication was the defect: a single test now derives the host-run commands - from `cmd/` and asserts that all four lists agree with it, so adding or extracting a process fails - until it is packaged. -- `deployments/systemd-user-service.md` gains the messaging unit. That is load-bearing rather than - cosmetic: the updater refuses an update when a service unit is missing and tells the operator to - create one from that document, which previously had nothing to offer. - -**Upgrade note:** a host that reached v1.30.0 without a messaging unit has been running with no -Telegram, email or webhook. Updating to this release installs and starts `archie-messaging`. - -## [1.32.0] - 2026-09-22 - -### EDA: playbook action ids, and a dispatch idempotency ledger - -- **Action ids (J1).** Every action a later action references must now carry an `id`. Ids are - validated at load -- unique and stable-identifier-shaped -- and a `when`/`args` expression - naming an unknown `actions.` is a **load failure**, not a runtime miss, the same - reject-at-load rule already applied to a binding collision. -- **Reference classification is strict at load.** A map-index reference (`actions[expr]`), a - non-literal index, and a reference to an unknown prior id are all rejected when the playbook - loads; references are classified by identifier versus static access, and the when-compilation - helper is shared between the load-time and runtime paths. -- **Dispatch idempotency ledger.** A `playbook_dispatches` row records a dispatch against - `(playbook_id, playbook_version, event_id, action_id)`, written with `INSERT OR IGNORE` and - surfaced through the shared `store.ErrAlreadyDispatched` sentinel. Module, channel and forge - action positions are therefore at-most-once, which is what unblocks the side-effecting - positions that were previously rejected at load. -- **The ledger is wired into production.** `stateStoreDeps` constructs `Deps.PlaybookDispatcher`, - so the ledger RPCs no longer answer `Unavailable` in a running daemon. This defect was found - by the pre-release review of this change rather than by its tests. - -**Behaviour change:** a playbook whose actions reference `actions.` without declaring that -id, declare a duplicate id, or index `actions` with a non-literal value now fails to load -instead of failing at dispatch time. - -## [1.31.0] - 2026-09-22 - -### Dashboard replaced: Preact -> Vue 3 + shadcn-vue - -The dashboard is now a Vue 3 application built on shadcn-vue. This is the -large piece of this release; it touches every page. - -- History routing, a grouped topbar built from components, the violet palette - with self-hosted Geist, and a command palette with live tasks. -- Chat is a FAB-opened panel that behaves like a chat window and scrolls its - transcript with `MessageScroller`. -- Task actions and dangerous approvals are deliberate; the task detail page is - a single head strip with honest states; the run page settles its head around - an attempts pager, which is hidden for zero or one attempt. -- Appearance and System navigation were refined, with a four-column appearance - grid on wide screens. -- A copy pass removed redundant tails and restating descriptions, empty states - derive their own titles, and a stuck log read surfaces as an error rather - than eternal loading. -- The capture pane is bound to the list it sits beside and reads beside it, - not over it. - -### Events is one page with three tabs - -- Inspector, Bindings and Mappings are now tabs of a single **Events** page. -- The nav entry is always live, the tabs prune by capability, and the three old - paths survive as bookmarks that redirect to their tab. -- Tab selection lives in one module (`ui/src/events/tab-selection.ts`) that the - page uses, rather than a copy of it. -- `feat(tools)`: a capture-intake sender exists for exercising the Events - surfaces. - -### The channel travels with the message - -`SessionSource.Platform` -- the first component of the session natural key, and -the column `GetByChannel` filters on -- was a constant `"web"`, because one -Router serves every channel and named itself after its own. Two things followed: -the per-user identity policy was real code that no production call site reached -with a real channel name, and a curator pass's write to agent-user memory could -not be read back by the turn that wrote it, because that turn resolved no -`UserID`. - -- The frontends now name the channel they carry (`telegram`, `email`, - `webhook`, `web`), the channel rides the message, and the Gateway stamps the - session from it -- falling back to its own name when a sender names none, - which is what every existing row holds. -- Identity resolution reads the platform off the inbound, so `carriesPersonIdentity` - decides something in production: telegram and email resolve a person, the - dashboard and a webhook resolve nothing, and an unknown platform fails closed. -- **Behaviour change:** a chat whose active session came from `/new` or - `/branch` re-resolves once, because session lookup now filters on the - channel's real name. A chat without `/new` re-resolves onto the same - deterministic id and heals silently. -- Deliberately unchanged: `TurnRunnerConfig.Channel` still keys tool - availability, so no channel gains or loses a tool in this release. - -### Control plane: runtime administration, history, and derived schemas - -- The State Store's gRPC server now carries runtime administration, and each - process reports which settings version it is running; the dashboard shows it. -- Resource history is exposed so edits can be reviewed and rolled back, and - resource schemas are derived from the documents they describe -- the document - editor reads the derived schema (labels from `title`, `format: duration` -> - `1m0s`, hints from `doc`), and the abandoned schema-driven card is deleted. -- A live settings replacement is checked before it is switched to, the daemon's - state surfaces are folded into one boot step, and a SIGHUP reload re-applies - database-owned settings. -- Forge intake settings that nothing reads are now rejected at load. - -### Configuration: judged where it is owned - -- The runtime config overlay is deleted; database-owned settings are judged at - the layer that owns them rather than on the file load path. -- A file overlay no longer drops the fields it omits inside a map entry, and a - kind with no stored value leaves the file's value in force. -- The default config path is resolved in one place, and the channel document - has its own shape. - -### State Store: offline backup, restore, validate and rollback - -- New offline backup / restore / validate / rollback path. -- `validate` runs boot's own gate; it no longer replaces the database, reads a - kind the store does not hold as its seed, or touches the daemon's log. -- The recovery control-plane server is built on the shared step vocabulary. - -### Workflow: one step vocabulary and a `gate.diff-rules` replacement - -- The step vocabulary is owned by a family manager registered at each - composition root, replacing `.archie/gate.go` with `gate.diff-rules`, which - fails closed on a change it never read. -- Workflow roots are pinned and the dead vocabulary is removed; the workflow pin - crosses the wire. -- The schedules resource skips the legacy cron jobs it cannot hold, and the - scheduling policy carries the label its trigger pairs with. - -### EDA: the playbook coordinator reaches production selection - -- The playbook coordinator is wired into production workflow selection, so a - matching playbook decides a real task's workflow at the daemon's definition - pin, inheriting idempotency from `TaskEnvelope`. - -### Reliability and operations - -- `cronstore` writes a schedule interval as a duration, not nanoseconds -- a - persisted `1m` no longer round-trips as `60000000000`. -- Worktrees are cut from the mapped base branch, and the Gateway's worktree - manager is built so it serves `review_pr`. -- A late max-uptime callback no longer resurrects teardown state. -- The state store dial installs client keepalive, and its server policy accepts - the dialer's pings; control-plane watch streams re-establish themselves after - they end. -- `/status` serves only the health facts a reply can carry; the daemon reports - systemd readiness and loop-driven watchdog heartbeats. -- A webhook route path no longer becomes a sender identity. -- A chat session compresses when a turn crosses its context budget. -- The MCP client supports per-server `parallel_tool_calls`, carried through the - tool-settings projection. -- Resource request-ID idempotency keys are scoped to their kind. -- The session curator addresses memory by the deployment's bot user. - -## [1.30.0] - 2026-09-20 - -### Messaging Service extraction completed - -Telegram, email and webhook no longer run inside the daemon. They run in -`archie-messaging` and reach the daemon through the Gateway's `ChatContract` -over gRPC; the daemon builds no channel and no `gateway.Router` (#899). - -- The operator surface is re-wired in the extracted service: `/update` (built - from its own `[chat.telegram]` commands), the update-report relay, the - `show_tool_calls` projection, and `/restart`'s config reload, which - re-resolves the token and allowlist from this service's own file and refuses - a reload that resolves to an empty token. -- `/version` is sourced from the Gateway through a new `ChatSnapshot.Version` - field. `cmd/archie-messaging` deliberately takes no version ldflags, so it - cannot report a partial upgrade as a matched one. -- Channel configuration is validated at composition, so a configured-but- - invalid front-end fails the service instead of being silently dropped. -- The inbound rate limiter moves to the Gateway, which now owns the only - Router and is therefore the one place a per-sender budget can apply to every - channel's turns. - -`RunningVersions` and `ReleaseAnnouncements` are deliberately left unwired: -both need a component's real running version, and the only versions this -process can obtain are another binary's stamps. See -`docs/architecture/migration-decisions.md`. - -### Configuration - -- `diff_cap_lines = 0` now switches the cap off, as the dashboard and the - workflow step have always documented. It was a plain `int`, so the defaults - pass could not tell an absent key from an explicit `0` and rewrote both to - 400 -- the documented way to disable the cap was unreachable. **Behaviour - change:** a config that set `0` was silently getting 400 and will now get no - cap. -- The same ambiguity was failing open per identity: `configForIdentity` - assigned the identity's value unconditionally, so an identity that merely - omitted `diff_cap_lines` overwrote the shared cap with the zero value and - disabled the safety rail entirely. An identity now overrides only when it - sets the key. -- A diff-cap park no longer tells the operator to "approve manually". A parked - task's actions are retry, abandon and reject, so there is no approve path out - of diff-cap; it now names the two things that work. -- `[health].dependency_timeout` makes the daemon's readiness probe timeout - configurable, matching the extracted services. - -### Chat rendering - -- `/status` and `/tasks` are line-oriented reports but separated lines with a - plain newline, which is CommonMark's soft wrap: the Telegram renderer joined - them into one run-on paragraph. The renderer implements CommonMark's hard - line break and the reports use it. Ordinary prose still soft-wraps. -- A park reason is capped to its first line in the `/tasks` list. It carries - whatever the failing stage reported, which for a lint gate is a whole tool - log; unbounded, one parked task pushed every other task out of the reply. The - full reason is unchanged on the task, in `task_list` and on the dashboard. - -### Review - -- Review findings are posted as line-anchored PR comments with suggested fixes, - and a suggestion must be single-line -- GitHub applies a multi-line suggestion - only up to its first line, silently corrupting the file (#891). -- The remediate workflow handles PR review comments and requested changes. - -### /status health surface - -`/status` reports the live broker connection and the last-known outcome of this -process's chat-model calls, alongside the queue depth and runtime block (#892). - -- A provider error is flattened and capped, so a multiline or oversized error - cannot break the one-line-per-fact layout. -- Concurrent model calls no longer reorder: the completion time is taken before - the lock, so the newer outcome wins rather than whichever goroutine stored - last. -- Curator model calls are recorded too. They bypass the chat path, so a daemon - whose only recent model traffic was curator work reported "no calls attempted - yet" while the provider was demonstrably reachable. -- Title generation does not record health. It runs detached under its own - bound and its error is swallowed, so a cosmetic timeout was overwriting the - line with "failed". - -**Known limitation:** the container, poll and channel sections cannot render. -Those facts live in the daemon, but the only Router lives in the Gateway -process, which has no container pool and no poll loop. The command description -says what actually appears; restoring the rest needs a cross-process health -contract. - -### Dashboard and containers - -- The served lifecycle vocabulary reaches an already-painted page, the page - registry matches the routes, and the build verifies `ui/dist` is fresh - instead of never looking at it (#890, #898). -- The container reaper no longer deletes teardown bookkeeping early, so a - released container is not torn down twice (#893). - -### Build - -- `task fmt` runs `golangci-lint fmt` -- the same engine and configuration the - gate checks with. Standalone `gofumpt` cannot reproduce gci's import - grouping, so formatting and linting could not converge and no command - satisfied the gate (#901). -- `goimports` is deliberately absent from the formatter set: it re-reads and - re-parses the module index once per file, ~135s across this tree. - -### Fixed - -- `Config.Clone` left the new diff-cap pointers aliased, so a clone could write - through to the published snapshot (#902). -- A curator asking for a completion on a daemon with no configured provider - panicked the process; it now returns an error. - -## [1.29.0] - 2026-09-19 - -### Security - -- `google.golang.org/grpc` bumped past `v1.84.0` to patch - [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443), a server panic via a - missing `:authority`/`Host` header reachable through `archied`'s gRPC - gateway server. No stable release carries the fix yet, so this pins the - pre-release commit that does (`v1.85.0-dev.0.20260825072537-93e31b48545e`) - until `grpc-go` cuts `v1.85.0`. - -### Memory engine unification - -One memory engine, addressed by four typed scopes (global, agent, user, -agent-user), replaces the two disconnected stores that previously existed: -a chat-tool-written store nothing ever read back, and a curator-written store -with no scope model. - -- `internal/domain/memory` is a CRUD contract (`Create`/`Get`/`Query`/`List`/ - `Update`/`Forget`/`Revisions`) with retained revisions; updates supersede - rather than overwrite, so a crash mid-write leaves a recoverable extra - history entry, never a lost prior state (#886). -- The chat turn reads its subject's scopes synchronously before the prompt is - built, rendering recalled records into a `` block; a failing or - panicking engine degrades to no memory block rather than failing the turn - (#887). -- The model writes memory through four id-addressed tools - (`memory_create`/`update`/`delete`/`list`), scoped to the turn's own - resolved identity -- the model chooses the scope kind, never the ids, so it - has no path to write into another user's memory (#888). -- The session curator now derives the agent-user scope from the session's own - user-role messages, instead of keying facts by a session id that stops - meaning anything once the session ends. -- A channel with no resolvable user (dashboard, webhook) reads and writes only - global and agent scope; a webhook's route path is never treated as a user - identity. -- Fixed a review finding on the read path: the per-scope record limit was - being applied as one shared total across all scopes rather than per scope, - and the rendered block's byte cap was checked before template escaping - rather than after, letting the escaped block exceed it. - -### Work intake - -- feat(workintake): define review reaction envelope -- feat(workintake): authorize review reactions by owned PR - -### Cleanup - -- Deleted the unwired plugin capability-host health surface - (`Host.Health`/`Host.Manifests`/`ModuleStatus`) and the `Module.Health` - chain it fed -- including the `mcp`/`builtin` tool-provider health - implementations and their aggregation in `tools/provider.Registry` -- none - of which had ever had a production caller (#882). - -## [1.28.0] - 2026-09-19 - -### Task detail and attempt attribution - -- New per-run task detail page, showing each attempt's own events, changes and - configuration rather than a single merged view. -- Events, changes and config are attributed to the attempt that produced them; - `Event` carries `attempt` and `ReadTaskLogRequest` carries `stage`. -- The task detail page remounts when the task id changes, so switching tasks - does not leave the previous one's data on screen. - -### Configuration - -- Services are keyed by name through a registry, so the State Store and Gateway - listen addresses are configurable rather than fixed. -- A partial overlay no longer clears the fields it omits — an overlay that set - one key was wiping the rest. -- The Services map is cloned on publish, so an overlay can no longer mutate the - snapshot other readers are holding. -- The service context is enforced at registration. - -### Logging and park reasons - -- A parked run's reason is recorded in its own attempt log, in both the daemon - and the workflow, so "why did this park?" is answerable from the task itself. -- `TaskRegistry.Write` takes the caller's context. - -### Worktrees and containers - -- Retries recover from path-type conflicts instead of failing opaquely, and the - underlying cause is no longer masked. -- The worktree is handed back on every sandbox exit. -- A container's max-uptime reaper is cancelled on release, the cap stays active - through the grace period, and teardown is claimed once rather than by - cancelling a timer. - -### Daemon and startup - -- Every identity's forge and repos are swept at startup, including the root - forge. -- A cancelled startup is no longer reported as an exhausted sweep budget; an - exhausted budget names itself as the cause. - -### Other - -- `grep` can use the workspace codesearch index. -- Forge labels are matched when namespaced, so label-driven routing works for - namespaced labels. -- Triage is given criteria for choosing between workflows, and a workflow is - required when a code change is needed. -- The Telegram adapter restart callback is wired into the chat router. -- The `ARCHIE_REACTIONS` fan-out stream is provisioned and bounded by age. -- `archie-ui` exits cleanly when graceful shutdown overruns its deadline. -- The dashboard's event pump retries priming until the State Store answers. -- The update writer emits the agent version sidecar with a real newline. -- The UI finishes its Preact port; the imperative DOM layer is deleted. -- Collection fields decoded over the State Store gRPC contract are never nil - slices, so an empty collection marshals as `[]` rather than `null`. - -## [1.27.0] - 2026-09-17 - -### Dashboard task logs - -- Task logs are readable from the dashboard again, through a new State Store - read contract (`ReadTaskLog`, `StreamTaskLogContent`) rather than the UI - process reaching into the daemon's log files. Wired server-side by the - standalone state-store process. -- Added `GET /api/tasks/{id}/logs/download`, serving an attempt's raw log as a - `task--attempt-.log` attachment. -- A process that cannot read logs and an attempt that recorded no log are now - distinguishable ("cannot read" answers 503, "no log" answers 404) instead of - both rendering as a claim about a configuration setting. - -### Telegram output - -- Tool results are summarised rather than quoted: a search reports how many - matches came back, a truncated result reports the tool's own total. The - renderer no longer states a count it computed from its own truncated sample. -- Repeated successful tool calls collapse into one counted entry. -- The tool-activity block is capped to a third of the live frame, keeps the - newest lines, and marks what it dropped with a `+N earlier` indicator. Every - line that fits is kept. -- Every clamped answer marks its cut with an ellipsis, including the opening - frame, which previously appeared to begin mid-sentence. -- An error response from the log download no longer ships as a `.log` file. - -### Readiness and shutdown - -- The disk probe reports per-filesystem results and checks the root filesystem - as well as the work directory, so a full root is no longer invisible. -- A path shared by several disk targets keeps the strictest requirement any - target places on it, so an optional target can no longer mask a required one. -- The shutdown-watchdog test no longer races the Go scheduler, which was - intermittently failing the quality gate and parking work unrelated to it. - -### Other - -- Messages persist the channel-native sender id. -- go-telegram/bot bumped to v1.27.0, fixing a streaming bug where the multipart - body could not be replayed and `sendMessage`/`editMessageText` failed until - the connection dropped. - -## [1.26.0] - 2026-09-17 - -- fix(webui): publish per-identity forges so multi-identity task rows keep their links -- feat(config): add [scheduling] config block -- feat(configuration): translate [scheduling] into scheduling.EngineConfig -- feat(cronevents): adapt the events bus to scheduling.Sink -- fix(webui): count every chat front-end in the published projection -- fix(scheduling): respect configuration ownership -- feat(ratelimit): wire per-identity inbound rate limiting into the gateway -- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it -- fix(store): keep an empty binding secret empty so a partial edit cannot erase it -- fix(archied): stop advertising review_pr when no reviewer can run -- fix(daemon): carry kind/label routing bindings to the process that routes -- feat(configuration): add archied setup, the caller the first-run flow was built for -- fix(configuration): stop letting a secret value be set from the command line -- feat(configuration): let setup reference a secret without carrying its value -- fix(archied): disable a provider whose credential is missing instead of refusing to boot -- refactor(install): install.sh delegates config generation, and tests stop reading hand-written configs -- fix(daemon): guard binding dispatch loop against nil dispatcher/creator -- fix(webui): enforce CSRF/origin gate on binding and mapping mutations -- fix(secret): recover a panicking secret engine instead of crashing -- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone -- fix(email): stop dropping the first paragraph of plain-text bodies -- fix(logging): keep the live descriptor open across a failed rotation -- feat(configuration): report config keys no decode target consumed -- feat(archied): warn at boot when the config file has unrecognised keys -- feat(archied): wire the scheduling ticker engine at boot -- fix(agentworker): wire configured tool-result policy into worker's LoopRunner -- refactor(staterpc): delete the superseded single-token auth interceptor -- refactor(memory): delete the unreachable fence scrubber -- fix(channels): delete unreachable Telegram webhook delivery mode -- fix(gateway): delete unwired Router.Dangerous approval path -- refactor(gateway): delete orphaned SessionState goal/steer/queue machinery -- refactor(archied): delete the daemon's unused webui.Server and UI adapters -- refactor(tools): delete unreachable dispatch/gating engine -- feat(channels): wire chat.webhook route config through to the gateway -- refactor(tools): delete unreachable AST-based tool discovery -- refactor(tools): delete unused plugin-tool registration API from builtin.Registry -- feat(channels): wire ConfigSchema/ValidateConfig into a startup validation loop -- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted) -- fix(curator): populate PassInput.Since with the prior pass time -- fix(memory): install the threat scanner the composition root never wired -- fix(staterpc): preserve marshal_error marker in eventDataJSON -- fix(gate): validate finding level and share the blocking threshold -- fix(scheduling): record a completed run so a recurring job stops re-firing every tick -- fix(releaseupdate): don't treat empty available as deferred -- fix(tools/provider/mcp): preserve MCP binary tool results for delivery -- refactor(gateway): share sensitive-key markers with webhookguard -- refactor(daemon): remove unreachable SQLite poll/drain path -- refactor(tools/mcp): delete unreachable MCP adaptation path -- fix(taskactions): resolve max_retries from the task's owning identity -- fix(daemon): forward configured MCP servers to task agents -- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path -- refactor(skillbuild): delete dead AugmentRegistry path -- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout -- refactor(binding): delete dead Matcher.Overlaps method -- refactor(forge): delete dead CreateIssue surface -- fix(mcp): cancel in-flight SSE reconnect on Stop -- fix(container): enforce MaxUptime lifetime cap with a timer -- refactor(store): use taskstate status constants in SQL -- fix(ui): unbreak binding approve and the two deletes, and centralise the client -- fix(tools): stop testing on the text of other files, and ungate contractaudit -- refactor(forge): delete the unwired RepliesAfter surface -- refactor(config): delete the two decoded-but-unread policy fields - -This release is dominated by dead-code removal and the completion of the -scheduling capability. Roughly half the commits delete surfaces that no longer -had a caller: the unreachable SQLite poll/drain path, the unwired MCP -adaptation path, the AST-based tool discovery, the superseded single-token auth -interceptor, and several dead forge and binding methods. The -`IncrementRetryCount` State Store RPC is gone with them -- a breaking change to -the wire contract, accepted because nothing called it. - -The cron/scheduling epic lands its remaining slices: the `[scheduling]` config -block, its translation into the engine's own settings, the events-bus sink -adapter, and the boot wiring that starts the ticker. A recurring job now records -a completed run, so it stops re-firing on every tick. - -Operator-facing work: `archied setup` gives the first-run flow the caller it was -built for, configuration no longer accepts a secret value from the command line, -and a provider whose credential is missing is disabled rather than refusing to -boot. A secret engine that panics is now recovered instead of crashing the -daemon. - -## [1.25.0] - 2026-09-15 - -- fix(update): resolve releases without a checkout, and fail loudly when it cannot -- fix(update): back up the task store the daemon actually uses, or refuse -- fix(update): build each component from its own approved release tag - -Components are independently versioned, so the newest `archied/v*` and -`archie/v*` tags usually sit on different commits. The installer required both -tags to resolve to one commit whenever both components changed, which refused -every update once the two newest releases diverged -- a deployment stuck on -1.22.0 could not take any update. Each component now builds from its own -approved tag. - -## [1.24.0] - 2026-09-12 - -Makes 1.23.0 deployable. That release split archied into separate processes, -but the self-updater still installed only the `archied` binary and restarted -only `archied.service`, so updating to it left the State Store, Gateway and UI -on the previous release. archied cannot boot without a reachable State Store, -so the update failed its health check and rolled back. Update to this release -rather than to 1.23.0. - -If your host does not yet run the four units in -`deployments/systemd-user-service.md`, create them first: the updater now -refuses, naming what is missing, instead of installing binaries onto a host it -would leave broken. - -- fix(update): install and cycle every process in the release -- fix(telegram): stop the relay corrupting identifiers and code - -Also in this release, though outside the version-stamped package closure: - -- ci(deploy): produce a complete distribution zip on every release. No zip was - built for v1.23.0 at all, and the zip omitted `archie-ui`. - -## [1.23.0] - 2026-09-12 - -Archied is no longer a single process. The State Store (`archie-state-store`) -now owns `archie.db` outright, the Gateway serves its contract over -authenticated gRPC, and the dashboard ships as a standalone UI Service -(`archie-ui`). Upgrading is not a binary swap: these processes must be running -and addressable before `archied` will start clean. See `deployments/` for the -supported profiles. - -### Service decomposition - -- feat(contracts): add gateway service seams and protobuf toolchain -- feat(gateway): extract ChatContract service -- feat(gateway): delete in-process ChatContract path, make remote the only mode -- feat(gateway): authenticate the gRPC contract and allow off-loopback listeners -- fix(gateway): drop services.gateway.mode, remote is the only transport -- feat(state-store): generalize storerpc as the State Store gRPC contract (#770) -- feat(state-store): stand up archie-state-store binary and own archie.db (#771) -- refactor(state-store): migrate capture/mapping/binding consumers to State Store (#772) -- refactor(state-store): migrate workflow/intake/task lifecycle consumers to State Store (#773) -- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774) -- fix(state-store): task-scope container credentials, stream large capture lists, validate Update -- feat(archieui): standalone UI process over remote Gateway and State Store -- refactor(archied): cut the dashboard over to the archie-ui process -- refactor(ui): sever the archie-ui binary from every daemon runtime package -- refactor(archied): move the update relay to the process that owns updates -- refactor(archied): move webhook capture intake to the process that owns work intake -- feat(archieui): mount the capture intake receiver over the State Store -- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754) -- refactor(store): move the producer-owned contracts to internal/contracts/store/v1 -- feat(messaging): migrate gateway session persistence onto domain types -- feat(gateway): flip channel boundary onto messaging.Message - -### Pull request review - -- feat(gateway): operator-triggered PR review with selectable reviewer model -- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview) -- feat(workflow): surface adversarial review findings on the PR body -- feat(workflow): review calibration, checked properties and style nits out of contract -- fix(archied): share one PR reviewer across channels; harden forge and worktree -- fix(workflow): order findings before footer; test the report stash - -### Dashboard - -- feat(webui): render configuration from a published snapshot -- feat(staterpc): carry the dashboard's configuration snapshot -- refactor(webui): take configuration off the dashboard server -- feat(webui): report which dashboard sections a process can serve -- feat(webui): deliver live dashboard events by polling the State Store cursor -- feat(webui): route dashboard task actions through the Gateway contract -- feat(gateway): give the dashboard operator its own task-action contract -- feat(webui): add /health and /health/detailed readiness endpoints (#717) -- fix(webui): distinguish refused vs broken task actions, handle 401 (#753) - -### Daemon, gateway and workflow - -- feat(archied): add shutdown watchdog that force-exits a hung graceful shutdown (#716) -- feat(archied): serve the daemon's own health endpoint -- feat(drain): honour external drain marker with instantiation epoch (#718) -- feat(gateway): wire progressive tool disclosure (bridge tools) -- feat(gateway): render workspace, managed repos and operator into chat env -- feat(gateway): add session_transcript tool for full JSON export -- feat(gateway): consolidate task actions and repair daemon default path -- feat(eda): thread Playbook ID/Version and DispatchInput task identity -- feat(worktree): Resume re-syncs a worktree onto its branch tip -- fix(staterpc): attach the bearer token to State Store streams -- fix(archieui): resolve service tokens from env, without requiring a config file -- fix(archied): initialize conversation persistence on daemon startup -- fix(archied): preserve channel turn ledger with remote gateway -- fix(gateway): share NATS and session ownership -- fix(update): probe the dashboard's real address after a self-update -- fix(store): migrate binding owner and repo columns - -## [1.22.0] - 2026-09-03 - -- feat(telegram): support secret refs for bot tokens (#705) -- fix(update): make daemon rollback schema-safe (#704) -- fix(archied): preserve ephemeral gateway ports (#707) -- fix(webui): bound log limit parsing and add endpoint regression coverage (#706) -- fix(deps): upgrade x/crypto to v0.56.0 for security fixes (#708) - -## [1.21.0] - 2026-09-03 - -- feat(workflow): make kind-to-workflow routing YAML-overridable -- feat(workflow): route arbitrary forge labels to workflows via playbook YAML -- feat(workflow): load kind/label bindings from multiple playbook directories -- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive -- feat(eda): Module position first slice -- registry + side-effect-free log kind -- feat(eda): CEL expression environment (compile/validate at load, evaluate at dispatch) -- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch -- fix(skillcurator): document and scope the intentional nilerr in reviewOne -- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch -- feat(webui): bindings dashboard UI; fix app-wide Preact render regression -- fix(binding): split ValidateForUpdate so edits can preserve the secret -- refactor(ui): extract Pill to ui/src/base/, closing archie-core-mlro -- refactor(eda): extract helpers to satisfy cyclop/gocognit gates -- fix(webui): stretch HEALTH row cards to equal height -- fix(eda): make playbook key collision reporting deterministic -- fix(gateway): split /status (health) and /tasks (work) apart - -## [1.20.0] - 2026-09-03 - -- fix: baseline gate repair (go test ./... -count=1) -- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler -- feat(image): define provider-neutral image capability contract and config -- fix(channels): call MarkRunning once a channel is actually up -- fix(workflow): stop discarding baseline-fix commits as 'no changes' -- fix(webui): wire the Logs page to per-task attempt-log detail -- fix(workflow): net cache hits from token totals, trim gate-retry output -- feat(workflow): dynamic triage instead of defaulting every task to implement -- fix(gateway): stop SOUL from forging the prompt invariant tags -- fix(curator): stop curator actions from serializing a zero timestamp -- feat(webui): hand-author the configuration field descriptor catalog -- feat(webui): attach the config field schema to GET /api/config -- feat(webui): render scalar config sections generically from the schema -- feat(webui): surface allow_concurrent/max_retries/review_enabled on the repositories card -- feat(webui): inline editing for per-repo allow_concurrent/max_retries/review_enabled -- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated -- fix: resolve golangci-lint funlen, nilerr, and empty branch issues -- feat(store): encrypt playbook binding secrets at rest -- feat(webhook): harden captured payload redaction -- fix(store): satisfy makezero when building cipher payload -- feat(webui): refactor chat module to Preact component and add unit tests - -## [1.19.10] - 2026-09-02 - -- feat(curator): session-memory curator reference implementation - -## [1.19.9] - 2026-09-02 - -- feat(memory): typed memory engine contract, registry, and registrar -- feat(memory): builtin engine implementing the domain/memory contract -- feat(config): config surface for memory engine selection -- feat(daemon): wire the domain/memory engine registry at boot -- feat(curator): bind curators to memory engines -- fix(config): reject memory.provider instead of silently ignoring it -- feat(curator): skill curator reference implementation - -## [1.19.8] - 2026-09-02 - -- fix(update): drop dev-facing wording from the unconfirmed-update message -- fix(telegram): stop adjacent rich blocks from rendering glued together -- fix(telegram): send undelivered-media fallback after finalize as its own message - -## [1.19.7] - 2026-09-02 - -- fix(logging): make Tail/Page allocation bound explicit for CodeQL - -## [1.19.6] - 2026-09-02 - -- fix(build): stamp gatewayVersion/runtimeVersion in the right package - -## [1.19.5] - 2026-09-01 - -- feat(webui): dashboard-aware chat — Archie sees the page, points you there -- fix(telegram): drop retry_after bandaid, bump go-telegram/bot to v1.24.0 -- feat(curator): track and expose recent activity per curator -- fix: go.mod bumped to 1.27.0 and stupid tests removed -- refactor: remove unnecessary AI-generated scaffolding -- refactor: go modernisation fixes -- refactor: remove unused Operator param. -- fix(gateway): fix broken system prompt template and scrub real telegram ID from tests -- fix(plugin): add missing CLAUDE.md reference to plugin engine rule -- fix(app): repoint archied wiring contract test at internal/app/archied -- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet -- fix(config): standardize Provenance to pointer receivers (recvcheck) -- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui -- fix(app): repoint capability-host wiring contract test at internal/app/archied -- refactor(lint): extract more helpers to clear nestif/gocyclo findings -- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult -- refactor(lint): split TurnRunner.Run and dispatchLocal further -- refactor(lint): extract markdownBlockParser and list/quote helpers in richblocks.go -- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization -- fix(lint): noctx fixes and dead-code cleanup -- feat(workflow): adversarial self-review stage before PR open - -## [1.19.4] - 2026-08-28 - -- refactor(telegram): render replies as structured rich blocks - -## [1.19.3] - 2026-08-28 - -- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta -- feat(dashboard): render task actions, statuses and filters from the server catalog - -## [1.19.2] - 2026-08-28 - -- feat(tasks): allow rejecting a task from any non-terminal state - -## [1.19.1] - 2026-08-27 - -- fix(telegram): keep Markdown headings/lists as blocks and strip Markdown on plain fallback - -## [1.19.0] - 2026-08-28 - -- feat(logging): cursor pagination and filtering for task_logs -- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29 - -## [1.18.0] - 2026-08-25 - -- Fix concurrent chat-turn claims so SQLite writer contention no longer leaks as `SQLITE_BUSY`. -- Make task timelines operationally useful with stage outcomes, durations, retry context, and durable per-stage token economics. -- Return canonical repository, issue, and pull-request URLs for each task's owning GitHub or Gitea identity. -- Preserve per-identity commit attribution and real model context limits across daemon-to-worker dispatch. - -## [1.17.1] - 2026-08-25 - -- fix(update): remove source checkout dependency -- fix(gateway): make UUIDv7 session references unambiguous - -## [1.17.0] - 2026-08-25 - -- fix(webui): add nil receiver guard to Server.trustForwardedHeaders -- fix(chat): restore transcript and update replay - -## [1.16.0] - 2026-08-25 - -**The agent can hand you a file, and the dashboard works behind a reverse -proxy.** Media delivery was fetch-by-URL only, so a file the agent produced -locally — a transcript, a log dump, a screenshot — was passed to Telegram as -a URL it could not fetch: the send did nothing and reported success. The new -`send_file` tool plus upload-by-reader delivery closes that, and every layer -that cannot deliver now says so rather than staying silent. Dashboard -mutations behind a TLS-terminating proxy were refused as cross-origin; -forwarded headers are now honoured, but only under an explicit opt-in that is -off by default. - -- feat(telegram): deliver a local file as an uploaded attachment, choosing - upload-by-reader or fetch-by-URL per attachment; `send_file` resolves paths - under the same confinement policy the read tool applies, so sending cannot - reach what reading cannot -- feat(gateway): `task_action` chat tool for operator task management — - abandon, archive, retry, stop, cancel, approve and reject from chat, on the - same action path and state machine as the dashboard -- fix(webui): validate mutation `Origin` against the effective external - scheme and host. `X-Forwarded-Proto`/`-Host` are honoured only when - `web.trust_forwarded_headers` is set, which is off by default and safe only - behind a proxy that overwrites or strips untrusted forwarded headers -- fix(webui): report a local file the dashboard chat cannot upload as - undelivered instead of dropping the event, which had reproduced the exact - silent non-delivery `send_file` was built to end -- fix(daemon): detach terminal state transitions and cleanup from a cancelled - context, so a stopped task still records its outcome - -## [1.15.0] - 2026-08-24 - -**Autonomous workflows now have exactly one production execution path.** Every -task is handed complete to a scoped `archie-agent` container over core NATS; -`archied` no longer runs an agent loop in-process. Embedded NATS is the -default and generates a per-start token, binding to the resolved Docker bridge -so managed workers can reach it; external NATS changes only broker placement. -The legacy `[agent]` section and `containers.enabled` still decode for -migration but can no longer select an execution path, and a reloaded -`nats.url` is logged as requiring a restart. Operators upgrading from a -`agent.mode = inprocess` configuration get the managed-worker topology -automatically; see `deployments/` for the supported profiles. - -- feat(nats): expose the embedded broker to managed task containers behind a - generated per-start credential -- fix(daemon): park before worktree access when the container pool or task - transport is unavailable, rather than silently executing locally -- refactor(agentexec): remove the in-process, subprocess and single-stage - execution paths -- fix(worktree): report a successful push as successful even when writing - local upstream tracking metadata afterwards fails, so a published branch no - longer parks the task as failed -- fix(worktree): honour context cancellation in `CommitAll`, so a cancelled - task can no longer stage or commit -- fix(daemon): remove the worktree when a task completes with no changes, - which previously leaked a full clone per no-change task; parked worktrees - are still retained for post-mortems -- fix(worktree): derive the branch prefix from the issue title before falling - back to labels, matching the documented contract -- fix(worktree): clean untracked files when `.git` is a gitdir file -- fix(agentexec): recover agents that end a turn without the required finish - call -- feat(scheduling): ticker engine with a configurable interval and pools -- fix(telegram): keep tool-call context when compacting tool output (#609) -- feat(workflow): add the adversarial-review findings contract, where only a - confirmed finding blocks and "review found nothing" is distinct from - "review did not run" (contract only; no review stage runs yet) - -## [1.14.0] - 2026-08-23 - -- fix(telegram): compact tool output and drop turn caps -- fix(update): install only approved components - -## [1.13.0] - 2026-08-23 - -- fix(telegram): render tool progress as bounded code blocks - -## [1.12.0] - 2026-08-23 - -- fix(webui): give dashboard-initiated updates a phase-2 report -- feat(agent): stamp archie-agent's build and report it back to the daemon -- feat(releaseupdate): enrich components with install type and reference -- feat(webui): surface per-component update status on /api/version and Configuration - -## [1.11.1] - 2026-08-23 - -- fix(update): wire Telegram personas and survive callback cancellation -- fix(webui): theme the Workflows 'Start work' form controls - -## [1.11.0] - 2026-08-23 - -- feat(forge): make webhook intake observable and deduplicate concurrent delivery -- fix(telegram): preserve code fences across message splits -- fix(gateway): replay completed-duplicate turns with their tool activity -- feat(storage): persist agent project state across sessions -- fix(container): persist npm cache for per-task MCP servers -- fix(worktree): bind publication to dispatch grants, reset retries to a pristine base, and reject diffs without a merge base -- feat(media): deliver generated media through Telegram with link fallback in the dashboard -- feat(tools): generate videos through MiniMax, gated by provider configuration - -## [1.10.0] - 2026-08-22 - -- feat(forge): GitHub webhook receiver for immediate issue dispatch -- feat(webhookguard): shared HMAC, rate-limit, and redaction mechanics -- feat(nats): run an embedded server when no external NATS is configured -- feat(capture): store unbound webhook events, retention-bounded -- feat(webui): event inspector -- see captured payloads in the dashboard -- feat(webui): payload field mapping -- bind JSON paths to named fields, preview before saving -- fix(webui): stop the capture live-event notification duplicating payloads into the unbounded events table -- fix(update): verify an update took effect instead of trusting the report (#530) -- fix(daemon): refuse to poll on an empty label-trigger match (#529) -- fix(gateway): stop persona from asserting unverified claims as fact (#528) -- fix(gateway): stop ClaimTurn's insert-race branch losing its own retry read -- fix: restore provider gate and dashboard token accounting -- fix: address simple findings from a repo-wide golangci-lint sweep - -## [1.9.11] - 2026-08-19 - -- fix(mcp): persist npx package cache across daemon restarts - -## [1.9.10] - 2026-08-19 - -- feat(update): `/update` now streams live progress while an update installs, reports a clear version summary (previous/installed, daemon/agent) once the build succeeds, and automatically rolls back and reports the outcome if the restarted daemon fails its post-update health check - -## [1.9.9] - 2026-08-18 - -- fix(telegram): drain live renderer in concurrency test - -## [1.9.8] - 2026-08-17 - -- chore: no user-facing changes - -## [1.9.7] - 2026-08-17 - -- chore: no user-facing changes - -## [1.9.6] - 2026-08-16 - -- fix(update): stamp install type and bound retry backoff - -## [1.9.5] - 2026-08-16 - -- refactor(archied): decompose the daemon bootstrap into phased wiring (no behaviour change; splits the ~950-line run() into focused setup phases so complexity linting passes) -- refactor(archied): extract the config overlay boot helper and thread context through chat gateway setup -- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity -- fix(tools): avoid predeclared `max` names -- fix(email): use context-aware test networking -- fix(indexing): remove the unused code search test runner -- fix(tests): use contexts and type assertions in overlay and gateway tests -- docs(architecture): document the memory engine family - -## [1.9.4] - 2026-08-15 - -- feat(gateway): polish /status command response format -- fix(telegram): preserve URL boundaries in responses - -## [1.9.3] - 2026-08-15 - -- fix(webui): scroll selected command into view on keyboard navigation -- fix(logging): resolve error attrs to their message string, not {} -- feat(agentexec,workflow): surface tool calls on the task timeline - -## [1.9.2] - 2026-08-15 - -- fix(worktree): force checkout so retry recovers from a dirty worktree - -## [1.9.1] - 2026-08-15 - -- fix(agentworker): forward workflow events across the NATS worker boundary -- fix(webui): filter turn_completed noise from the Live Activity SSE feed -- feat(releaseupdate): stamp install type at build time, fail closed on unknown - -## [1.9.0] - 2026-08-15 - -- fix(webui): style tool-call failure from a structured field, not a string prefix -- fix(config,webui): make show_tool_calls one cross-channel setting -- fix(telegram): guarantee no message is stranded on gateway stop/restart -- fix(telegram): use NewRequestWithContext to satisfy noctx -- refactor(webui): decompose handleSSE to cut cognitive complexity - -## [1.8.0] - 2026-08-15 - -- feat(archied): add -version so the installed build can be read from a shell -- fix(webui): rebuild the Configuration page layout so values stop colliding -- fix(webui): size Configuration key/value lists to their own content -- fix(webui): keep Configuration rows full width, hug only the label column -- fix(webui): cap and centre the Configuration page instead of its lists -- fix(webui): preserve encoded redirect path characters -- feat(chat): show tool calls inline and stream replies into one message -- fix(chat): harden inline tool call streaming -- refactor(agent): move worker runtime into application layer -- fix(telegram): harden live-reply delivery against /stop and multi-byte content -- fix(telegram): keep tool activity visible and mark failed/empty turns -- fix(config): de-duplicate disabled-forge predicate, export ForgeDisabled - -## [1.7.0] - 2026-08-10 - -- fix(build): install ripgrep where grep.go actually needs it on PATH -- fix(webui): Send button no longer passes its click event to sendMessage -- feat(webui): Enter sends, Shift+Enter inserts a newline -- fix(chat): stop showing raw 501 banner for unconfigured update-check -- fix(chat): give chat page a real height budget instead of a floor -- fix(workflow): carry gate output into the baseline park error -- feat(logging): add a per-task log sink -- feat(agentexec): publish agent-side logs to the task's system subject -- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed -- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool -- refactor(gateway): persist conversations in sqlite -- refactor(store): replace legacy persistence with SQLite -- fix(webui): tighten configuration KV row spacing -- fix(gateway): harden session recovery paths -- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe -- feat(config): SIGHUP-triggered reload with requires-restart warnings -- fix(config): share one config Holder between daemon and dashboard; re-apply model catalog on reload -- fix(config): complete the reloadable allowlist and pin it against ForTask -- feat(config): runtime config overlay store, PATCH /api/config, and the `--no-config-overlay` recovery flag -- feat(webui): inline config editing on the Configuration page -- feat(config): surface overlay state, shadowed keys, and per-row reset -- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state -- fix(config): preserve nil slices in Clone to avoid spurious reload warnings - -## [Unreleased] - -## [1.6.0] - 2026-08-09 - -- feat(gateway): tool-approval gate, session tools for chat, and /delete command -- fix(webui): close open-redirect in dashboard token-exchange handler -- feat(gateway): make chat turns durable and idempotent -- feat(webui): lifecycle-safe task controls with atomic retry and archive -- feat(config,channels): format-neutral config resolution and truthful channel state -- feat(logging,workflow): daemon log feed and executable workflow registry -- fix(store,gateway): taskstate constants and mobile jump-to search -- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams -- fix(ui): hide inactive chat command menu - -## [1.5.0] - 2026-08-08 - -- feat(curator): engine family contract, registry, and runtime -- feat(curator): trigger accounting — primary-input wake path -- feat(setup): interactive setup steps with a TTY-gated prompter -- feat(webui): rebuild the dashboard and add chat -- feat(daemon): identity-scoped isolation plus gateway session titles and /delete -- feat(logging): optional rotating log file -- feat(configuration): export Validate for the setup flow -- fix(gateway): durable message identity with a SQLite store -- fix(gateway): consistent message ordering and paged search -- fix(gateway): stop /compress destroying history it should have kept -- fix(gateway): do not answer a redelivered message twice -- fix(gateway): claim the session slot before writing it, not after -- fix(gateway): keep /topic off from poisoning the session cache -- fix(gateway): resolve the most recently active session, not an arbitrary one -- fix(gateway): give branch-inherited messages their own identity -- fix(gateway): make both backends agree on newest-first -- fix(store): honour the transition guard in production persistence -- fix(store): move ID counters away from the reserved metadata namespace -- fix(store): surface task timestamps and tag the summary structs -- fix(telegram): pause the update loop when rate limited -- fix(memory): fail startup on an unusable memory directory -- fix(tools): let an optional provider fail without taking the daemon down -- fix(tools): report a cancelled find walk as an error, not empty results -- fix(worktree): name the missing forge credential when a push fails -- fix(tomlwrite): recognise table headers carrying a trailing comment -- fix: close the duplicate-work loop and the dead paths around it -- perf(tools): drop the embedded ripgrep binaries -- refactor: one definition of what approving or declining a task means -- refactor: move workflow into its own domain - -## [1.4.1] - 2026-07-31 - -- fix(catalog): match SDK provider fallback - -## [1.4.0] - 2026-07-31 - -- fix(secrets): wire provider credentials through engines - -## [1.3.1] - 2026-07-31 - -- fix(telegram): omit empty model picker markup - -## [1.3.0] - 2026-07-31 - -- fix(memory): replace framework-specific names with generic equivalents -- feat: unify provider and model selection - -## [1.2.0] - 2026-07-31 - -- feat: add MCP client capabilities to archied and archie-agent -- fix: handleSummary ignores errors from WorkflowStats/StageStats/TokensByDay -- feat: establish Archie identity and use stable callback tokens -- refactor(telegram): keep one model selector command -- fix: handleSSE silently swallows EventsSince backlog fetch errors -- fix: Transition() ignores `from` status guard, allowing lost updates -- fix: skillscript.Run ignores context, cannot be canceled/timed out -- feat(telegram): report installed component versions -- feat(telegram): add approved component updates -- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup -- feat(chat): real system prompt for Archie — identity, tools, env -- feat(indexing): port tau's codesearch workspace index -- fix(indexing): surface index config properly and stop silent degradation -- refactor(worktree): replace git shell-out with go-git v6 -- fix(worktreerpc): bound handler contexts and drop the git binary from tests -- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries -- refactor: route tasks on a typed kind, not forge labels -- fix(natsrpc): make RegisterAll wait for the server to see subscriptions -- refactor(config): move loading into infrastructure/configuration -- fix(telegram): publish all executable session commands in menu and help -- fix(telegram): publish the restored gateway commands -- refactor: add internal/eventbus as the broker-neutral messaging contract -- fix(chat): operator name from config, session wiring, prompt rules -- feat(tools): lift tau's file and shell tools into the tool registry -- feat: make /stop cancel the running chat turn -- fix: kill the whole process group when a shell command is cancelled -- feat: refuse unrecoverable shell commands -- feat: make /stop reach running agent tasks -- fix(chat): temper prompt brevity rules with warmth -- fix: use errors.Is/As for context errors and cleanup -- fix(grep): distinguish ripgrep exit 1 from a failed search -- fix(archied): disable the forge on a missing credential, not the daemon -- fix: restore /model parsing and close the 6d4e0be autofix audit -- feat: embed config.example.toml and add comment-preserving TOML writer -- fix(docker): install unzip and Node 24 so MCP servers can start -- fix(docker): slim both images and repair unreachable Go tooling -- fix(container): write the task boot brief under .git -- fix(telegram): drop pending updates before long polling - -## [1.1.0] - 2026-07-27 - -- feat: add the Telegram gateway with persistent sessions, topic-thread support, streamed rich replies, typing indicators, and Markdown rendering -- feat: add `/spawn`, `/approve`, and `/cancel` for chat-driven task control -- feat: provide a comprehensive `/help` guide whose command list stays aligned with Telegram's published menu and Archie's executable command surface -- feat: add `/provider` and provider-filtered `/model` selectors that switch the provider and model used by subsequent live chat turns -- feat: include the active provider and full model reference in `/status` -- feat: notify authorized Telegram users once when a newly tagged component release is installed -- feat: add `/restart` to reload and relaunch the Telegram gateway without interrupting in-flight daemon tasks -- feat: add deny-by-default Telegram sender authorization and native command-menu publication -- feat: connect Desktop Commander through Archie's managed MCP client so chat can use workspace file and process tools -- feat: add multi-identity daemon configuration, persona routing, an email channel, and webhook platform support -- feat: add durable task, session, message, and memory persistence -- feat: add memory synchronization, prefetch, context scrubbing, threat scanning, and built-in memory tools -- feat: add tool guardrails, classification, budgets, availability filtering, and disclosure controls -- feat: add feature-based YAML configuration with `conf.d` overlay loading -- feat: add typed secret-engine registration and Yaegi extension support -- fix: reject unknown slash commands locally instead of allowing the LLM to fabricate command behavior -- fix: publish Telegram commands to default, private-chat, and group-chat scopes so stale commands inherited with the bot token cannot shadow Archie's menu -- fix: drain the SDK's full event stream so streamed Telegram replies cannot deadlock -- fix: use standard newline-delimited JSON framing for MCP stdio clients -- fix: make MCP stdio shutdown and timeout handling race-safe -- fix: restore legacy `[forge].token_env` compatibility and required container environment passthrough -- fix: make the agent-container Docker network explicitly configurable - -## [1.0.0] - 2026-07-22 - -- feat: ship the resident forge-polling daemon, deterministic workflow engine, isolated worktrees, quality gates, Gitea integration, Docker/NATS worker split, plugin loading, and skills support -- feat: publish `archied` and `archie-agent` container images to the Gitea registry diff --git a/CHANGELOG.md b/CHANGELOG.md index 88d49301e..b1480b5d7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,10 +1,1815 @@ -# Changelogs +# Changelog -Archie has two independently versioned components: +The release stream. One version covers whatever changed; a +release's per-component sections are labelled beneath its heading. -- [CHANGELOG.archied.md](CHANGELOG.archied.md) — `archied`, the user-facing gateway and control plane. -- [CHANGELOG.archie.md](CHANGELOG.archie.md) — `archie-agent`, the agent runtime. +## [Unreleased] -Release tags use `archied/vX.Y.Z` and `archie/vX.Y.Z`. The gateway combines -the matching component entries when it reports an installed or available -update. +## [1.37.0] - 2026-09-22 + +### archied — A request is attributed to the identity that made it + +- **A browser can sign in, and an action taken through it records the person.** The dashboard validates a + provider-issued token, resolves it to an identity, and attaches it to the request; the task-action record + then names the actor. `Authenticate` and the sign-in callback share one resolver, so a browser sign-in + cannot be accepted on terms a presented token would be refused on. +- **archie issues no session.** The callback stores the provider's own token in an HttpOnly cookie and every + later request re-verifies it, so nothing archie holds can outlive the provider's decision and there is no + session table to expire, revoke or get wrong. +- **The event kind describes the actor.** A person's approval records `human_approved` as that person; an + agent's records `agent_approved`; an action with no authorising principal records `task_approved` with the + attribution fields **empty**. Nothing is credited to an identity that did not act, and an unattributed + action is recorded as unattributed rather than guessed. +- The acting identity is derived from the presented credential and **never** from a request field: a body + carrying `actor`, `actor_id`, `identity` and an `X-Archie-Actor` header still cannot choose it. + +### archied — A host install now works, and an update refuses a host it cannot keep consistent + +- `install.sh` writes and enables **all five** host units; previously it seeded only `archied.service`, so a + fresh host ran one service of five and an operator applied the rest by hand from a runbook. The runbook is + a description again: it names the units and points at `systemctl --user cat`. +- **Every host binary reports its version**, and the updater reads all of them **before it can report + "nothing to install"**. A host whose binaries disagree is refused, naming each one: a newer messaging + binary beside an older state store crash-loops against a service the older store does not serve, and that + install previously looked healthy from the updater's point of view. +- The packaged, installer and updater command lists are pinned by a test, so a service added to one and not + the others fails the gate instead of shipping a partial install. + +### archied — A release image can be traced to a commit + +- The publish step derives the commit by **dereferencing the ref** rather than reading `github.sha`, because + every release tag in this repository is annotated and a tag's object id is not a commit. An immutable + `sha-` tag is published alongside `:latest`, and a build with no release tag is stamped + `dev+` rather than a bare `dev` that identified nothing. + +### archied — Curator definitions are data, not a second registry + +- Curator definitions may come from configuration or code and run through **one** engine into the existing + registry — no parallel authority and no second config reader. A definition declares its tools, and an + unknown tool name fails rather than widening the set silently. + +## [1.36.0] - 2026-09-22 + +### archied — The dashboard declares tools an in-browser agent can call + +- The dashboard registers **seven WebMCP tools**. Read-only: `list_tasks`, `get_task`, + `recent_events`, `daemon_health`. Recovery: `retry_task`, `stop_task`, `cancel_task`. An agent + operating the dashboard now reads structured state and recovers stuck work instead of scraping the + UI. +- Every tool wraps the same `ui/src/lib/api.ts` client the dashboard itself calls, so an agent and a + person exercise one path rather than two. +- `archie-ui` cannot be attributed to the agent that called it: a page can invoke its own tools, so an + agent's call and a page script's call reach the server identically. Tools therefore record the + signed-in identity and a source, and **never** that an agent acted. + +### archied — Binaries built by the development build task can be updated + +- `task build` passed the `installtype` stamp for three of six commands, so `archie-messaging`, + `archie-state-store` and `archie-ui` were built without it. An unstamped binary reports `unknown` + and the self-update path **refuses rather than guesses**, which is how an operator ends up unable to + update with `install type is unknown` and no way forward. All six are stamped now, and a test reads + the build task and fails naming any command line that omits it. + +## [1.35.0] - 2026-09-22 + +### archied — The Messaging Service is severed from the store and workflow runtime + +- `cmd/archie-messaging` no longer links `modernc.org/sqlite`, `internal/store`, + `internal/domain/workflow` or `internal/agentexec`. All four arrived through a single import of + `internal/app/controlplane`; the client half now lives in + `internal/infrastructure/controlplanerpc`, and the app package keeps the server, the registry, the + seeds, the validators and the schema derivation. +- The resource documents are type-aliased back into the app package, so there is one definition read + under two names rather than a copy per side. + +### archied — Channel lifecycle reaches the dashboard + +- The Messaging Service reports each channel's state, recorded **per channel**: one channel's failure + marks only itself, a channel that cannot start is marked failed **with its reason** rather than only + logged, and one that returns is marked stopped. `internal/channels/status.Manager` reports each channel's state. +- `PutChannelStatus`/`ListChannelStatus` carry that to the dashboard, following the config-snapshot + split. The store **replaces the reported set**, so a channel the reporter stops mentioning is + deleted rather than left as a stale `running`; an empty report clears the table, because hosting no + channels is a fact worth reporting; and an id-less row is refused, since it could never be replaced + or removed by a later report. +- `Service.ReloadChannel` routes to the channel's own seam and refuses a channel that cannot reload + with a reason rather than accepting and ignoring it. `ReloadSupported` was previously declared **by + name**, so a channel could advertise reload with nothing behind it; one function now decides both. + +### archied — Action playbooks: a second playbook shape, with typed results + +- A playbook is now one of two shapes: a **workflow playbook** (exactly one `workflow` action, + unchanged) or an **action playbook** (one or more `module` actions in order). A playbook does not + mix them. +- `args` and `when` share one compilation path and one evaluation context, and `actions.` is typed + by the kind that action runs, so a misspelled result field, an unknown id, a map index, `in`, a + comprehension, or a shape-foreign key (`kind` on a `workflow` action, `workflow` on a `module` + action) is a **load failure** rather than a dispatch failure. +- **Action playbooks load but do not run yet.** Routing arrives with the first side-effecting + position; the daemon warns at load rather than accepting them silently. +- The CEL environment is built per playbook, because result typing depends on the ids a playbook + declares. +- `ModuleRegistry.DecodeResult` turns a kind's flat map result into its typed `Result` before a later + expression reads it. Without it a typed read evaluated against a shape the run never produces, and + so silently read null. + +### archie-agent + +The sandboxed runtime links the same shared packages as archied, so this release carries the +channel-lifecycle store contract and the stricter action-load errors with it: + +- The channel-status store contract (`PutChannelStatus`/`ListChannelStatus`) and its replace-the-set + semantics. +- Authoritative module ids and stricter action load errors: a misspelled result field, an unknown id, + or a dynamic `actions` read now fails the playbook load rather than the dispatch. + +archied and archie-agent move together in this release. + +## [1.34.0] - 2026-09-22 + +### archied — Dashboard: an actionable authentication failure state + +- An unauthenticated **document** request now receives a self-contained HTML page with a + paste-the-token form, instead of plain text. Previously the whole dashboard -- `index.html`, the + bundle and every asset -- sat behind the token check, so a bookmarked bare URL returned a + `text/plain` "unauthorised: open the dashboard URL archied logged at startup", the SPA never ran, + and none of the dashboard's existing failure surfaces were reachable at all. +- The response is still **401**, with `Cache-Control: no-store` and a CSP. It is deliberately not a + 200: a login page served as success would be cacheable, would read as healthy to anything that + checks status alone, and a shared cache could hand it to the wrong person. +- API and stream callers are unaffected. `application/json`, `*/*` and `text/event-stream` requests + keep the plain-text 401, with a test pinning that split so an XHR or an `EventSource` reconnect can + never start receiving a page. +- The auth banner gains a **Retry** action that re-runs the dashboard's bootstrap reads, so a + recovered session is actionable without a browser-level reload. It deliberately does not re-drive + the SSE stream, which already reports its own reconnect state. +- The page's guidance stays generic: it points at the dashboard URL the daemon logs rather than + naming where the token is stored, so the HTTP layer is not coupled to the token file's location. + +## [1.33.0] - 2026-09-22 + +### archied — EDA: playbook action arguments are compiled at load (J2) + +- A playbook action may now declare `args`, compiled as CEL expressions when the playbook loads. + `args` and `when` share one compilation path and one evaluation context, so an expression written + for one works in the other. +- **Behaviour change:** an `args` expression that does not compile is a **load failure**, not a + runtime miss — the same reject-at-load rule already applied to a binding collision and to an + unknown `actions.`. In practice, a daemon loading a playbook with a malformed `args` block + fails at startup rather than part-way through a dispatch. +- Compiling several arguments now reports the **first** bad key deterministically (keys are sorted). + Previously it ranged a map, so the reported bad key could differ between runs and the failure was + not reproducible. +- `args` is deliberately **inert** for now: parsed, compiled and stored, but no shipped position + consumes it yet. A consumer arrives with the first side-effecting position. + +**Not yet decided:** how an `args` evaluation failure behaves at dispatch. The `when` predicate rule +(error, skip, log) does not obviously transfer, because `args` is data rather than a predicate, and +silently skipping an action whose arguments failed to evaluate would be a silent failure of exactly +the kind this release train has been removing. It currently propagates the error to the caller, and +that asymmetry is documented at the code. Ratifying it against a real consumer is tracked separately. + +## [1.32.1] - 2026-09-22 + +### archied — Host packaging: `archie-messaging` now ships and updates + +- `cmd/archie-messaging` is included in the distribution zip, and `scripts/archie-update-install` + installs and restarts it. +- **Why this mattered.** v1.30.0 moved Telegram, email and webhook out of `archied` and into + `archie-messaging`, but nothing packaged the new binary. A host install that upgraded across + v1.30.0 therefore ran on with **no messaging process at all**: `archied` logged that it stopped + serving the telegram gateway, nothing replaced it, and Telegram stayed dead — with no error + logged anywhere, because nothing was failing. The process simply did not exist. +- The host component set was enumerated in four places — the zip's build loop, the zip's copy list, + the installer's service list, and the installer's binary list — and `archie-messaging` was missing + from all four. The duplication was the defect: a single test now derives the host-run commands + from `cmd/` and asserts that all four lists agree with it, so adding or extracting a process fails + until it is packaged. +- `deployments/systemd-user-service.md` gains the messaging unit. That is load-bearing rather than + cosmetic: the updater refuses an update when a service unit is missing and tells the operator to + create one from that document, which previously had nothing to offer. + +**Upgrade note:** a host that reached v1.30.0 without a messaging unit has been running with no +Telegram, email or webhook. Updating to this release installs and starts `archie-messaging`. + +## [1.32.0] - 2026-09-22 + +### archied — EDA: playbook action ids, and a dispatch idempotency ledger + +- **Action ids (J1).** Every action a later action references must now carry an `id`. Ids are + validated at load -- unique and stable-identifier-shaped -- and a `when`/`args` expression + naming an unknown `actions.` is a **load failure**, not a runtime miss, the same + reject-at-load rule already applied to a binding collision. +- **Reference classification is strict at load.** A map-index reference (`actions[expr]`), a + non-literal index, and a reference to an unknown prior id are all rejected when the playbook + loads; references are classified by identifier versus static access, and the when-compilation + helper is shared between the load-time and runtime paths. +- **Dispatch idempotency ledger.** A `playbook_dispatches` row records a dispatch against + `(playbook_id, playbook_version, event_id, action_id)`, written with `INSERT OR IGNORE` and + surfaced through the shared `store.ErrAlreadyDispatched` sentinel. Module, channel and forge + action positions are therefore at-most-once, which is what unblocks the side-effecting + positions that were previously rejected at load. +- **The ledger is wired into production.** `stateStoreDeps` constructs `Deps.PlaybookDispatcher`, + so the ledger RPCs no longer answer `Unavailable` in a running daemon. This defect was found + by the pre-release review of this change rather than by its tests. + +**Behaviour change:** a playbook whose actions reference `actions.` without declaring that +id, declare a duplicate id, or index `actions` with a non-literal value now fails to load +instead of failing at dispatch time. + +### archie-agent + +The sandboxed runtime links `storecontract` and `staterpc`, so it carries the dispatch-ledger +contract alongside archied: + +- The shared `store.ErrAlreadyDispatched` sentinel now describes both dedup ledgers -- + `binding_dispatches` per `(binding_id, capture_id)`, and `playbook_dispatches` per + `(playbook_id, playbook_version, event_id, action_id)`. Each is an at-most-once guarantee. +- `RecordPlaybookDispatch` is part of the store contract the runtime builds against. + +archied and archie-agent move together in this release. + +## [1.31.0] - 2026-09-22 + +### archied — Dashboard replaced: Preact -> Vue 3 + shadcn-vue + +The dashboard is now a Vue 3 application built on shadcn-vue. This is the +large piece of this release; it touches every page. + +- History routing, a grouped topbar built from components, the violet palette + with self-hosted Geist, and a command palette with live tasks. +- Chat is a FAB-opened panel that behaves like a chat window and scrolls its + transcript with `MessageScroller`. +- Task actions and dangerous approvals are deliberate; the task detail page is + a single head strip with honest states; the run page settles its head around + an attempts pager, which is hidden for zero or one attempt. +- Appearance and System navigation were refined, with a four-column appearance + grid on wide screens. +- A copy pass removed redundant tails and restating descriptions, empty states + derive their own titles, and a stuck log read surfaces as an error rather + than eternal loading. +- The capture pane is bound to the list it sits beside and reads beside it, + not over it. + +### archied — Events is one page with three tabs + +- Inspector, Bindings and Mappings are now tabs of a single **Events** page. +- The nav entry is always live, the tabs prune by capability, and the three old + paths survive as bookmarks that redirect to their tab. +- Tab selection lives in one module (`ui/src/events/tab-selection.ts`) that the + page uses, rather than a copy of it. +- `feat(tools)`: a capture-intake sender exists for exercising the Events + surfaces. + +### archied — The channel travels with the message + +`SessionSource.Platform` -- the first component of the session natural key, and +the column `GetByChannel` filters on -- was a constant `"web"`, because one +Router serves every channel and named itself after its own. Two things followed: +the per-user identity policy was real code that no production call site reached +with a real channel name, and a curator pass's write to agent-user memory could +not be read back by the turn that wrote it, because that turn resolved no +`UserID`. + +- The frontends now name the channel they carry (`telegram`, `email`, + `webhook`, `web`), the channel rides the message, and the Gateway stamps the + session from it -- falling back to its own name when a sender names none, + which is what every existing row holds. +- Identity resolution reads the platform off the inbound, so `carriesPersonIdentity` + decides something in production: telegram and email resolve a person, the + dashboard and a webhook resolve nothing, and an unknown platform fails closed. +- **Behaviour change:** a chat whose active session came from `/new` or + `/branch` re-resolves once, because session lookup now filters on the + channel's real name. A chat without `/new` re-resolves onto the same + deterministic id and heals silently. +- Deliberately unchanged: `TurnRunnerConfig.Channel` still keys tool + availability, so no channel gains or loses a tool in this release. + +### archied — Control plane: runtime administration, history, and derived schemas + +- The State Store's gRPC server now carries runtime administration, and each + process reports which settings version it is running; the dashboard shows it. +- Resource history is exposed so edits can be reviewed and rolled back, and + resource schemas are derived from the documents they describe -- the document + editor reads the derived schema (labels from `title`, `format: duration` -> + `1m0s`, hints from `doc`), and the abandoned schema-driven card is deleted. +- A live settings replacement is checked before it is switched to, the daemon's + state surfaces are folded into one boot step, and a SIGHUP reload re-applies + database-owned settings. +- Forge intake settings that nothing reads are now rejected at load. + +### archied — Configuration: judged where it is owned + +- The runtime config overlay is deleted; database-owned settings are judged at + the layer that owns them rather than on the file load path. +- A file overlay no longer drops the fields it omits inside a map entry, and a + kind with no stored value leaves the file's value in force. +- The default config path is resolved in one place, and the channel document + has its own shape. + +### archied — State Store: offline backup, restore, validate and rollback + +- New offline backup / restore / validate / rollback path. +- `validate` runs boot's own gate; it no longer replaces the database, reads a + kind the store does not hold as its seed, or touches the daemon's log. +- The recovery control-plane server is built on the shared step vocabulary. + +### archied — Workflow: one step vocabulary and a `gate.diff-rules` replacement + +- The step vocabulary is owned by a family manager registered at each + composition root, replacing `.archie/gate.go` with `gate.diff-rules`, which + fails closed on a change it never read. +- Workflow roots are pinned and the dead vocabulary is removed; the workflow pin + crosses the wire. +- The schedules resource skips the legacy cron jobs it cannot hold, and the + scheduling policy carries the label its trigger pairs with. + +### archied — EDA: the playbook coordinator reaches production selection + +- The playbook coordinator is wired into production workflow selection, so a + matching playbook decides a real task's workflow at the daemon's definition + pin, inheriting idempotency from `TaskEnvelope`. + +### archied — Reliability and operations + +- `cronstore` writes a schedule interval as a duration, not nanoseconds -- a + persisted `1m` no longer round-trips as `60000000000`. +- Worktrees are cut from the mapped base branch, and the Gateway's worktree + manager is built so it serves `review_pr`. +- A late max-uptime callback no longer resurrects teardown state. +- The state store dial installs client keepalive, and its server policy accepts + the dialer's pings; control-plane watch streams re-establish themselves after + they end. +- `/status` serves only the health facts a reply can carry; the daemon reports + systemd readiness and loop-driven watchdog heartbeats. +- A webhook route path no longer becomes a sender identity. +- A chat session compresses when a turn crosses its context budget. +- The MCP client supports per-server `parallel_tool_calls`, carried through the + tool-settings projection. +- Resource request-ID idempotency keys are scoped to their kind. +- The session curator addresses memory by the deployment's bot user. + +### archie-agent + +The sandboxed runtime links the same shared packages as archied, so this +release carries the control-plane and workflow changes alongside it: + +- Runtime administration over the State Store's gRPC server, resource history, + and control-plane apply status on the store contract. +- The shared step vocabulary, owned by a family manager registered at each + composition root, and `gate.diff-rules` in place of `.archie/gate.go` + (fails closed on a change it never read). +- The workflow pin crosses the wire. + +Runtime-specific changes: + +- `refactor(plugin)`: the unused `Registry` type is deleted. +- `yaegiutil` refuses incomplete Yaegi interface wrappers at load rather than + running them. +- The runtime config overlay is deleted. +- The state store dial installs client keepalive, and the server policy accepts + the dialer's pings. +- The MCP client supports per-server `parallel_tool_calls`. +- A late max-uptime callback no longer resurrects teardown state. +- A webhook route path no longer becomes a sender identity. + +Note: the `archie-agent` image is rebuilt by this tag through CI +(`.github/workflows/deploy.yml`); a gateway-only release would not have rebuilt +it. `docker compose pull agent` is required to pick it up. + +## [1.30.0] - 2026-09-20 + +### archied — Messaging Service extraction completed + +Telegram, email and webhook no longer run inside the daemon. They run in +`archie-messaging` and reach the daemon through the Gateway's `ChatContract` +over gRPC; the daemon builds no channel and no `gateway.Router` (#899). + +- The operator surface is re-wired in the extracted service: `/update` (built + from its own `[chat.telegram]` commands), the update-report relay, the + `show_tool_calls` projection, and `/restart`'s config reload, which + re-resolves the token and allowlist from this service's own file and refuses + a reload that resolves to an empty token. +- `/version` is sourced from the Gateway through a new `ChatSnapshot.Version` + field. `cmd/archie-messaging` deliberately takes no version ldflags, so it + cannot report a partial upgrade as a matched one. +- Channel configuration is validated at composition, so a configured-but- + invalid front-end fails the service instead of being silently dropped. +- The inbound rate limiter moves to the Gateway, which now owns the only + Router and is therefore the one place a per-sender budget can apply to every + channel's turns. + +`RunningVersions` and `ReleaseAnnouncements` are deliberately left unwired: +both need a component's real running version, and the only versions this +process can obtain are another binary's stamps. See +`docs/architecture/migration-decisions.md`. + +### archied — Configuration + +- `diff_cap_lines = 0` now switches the cap off, as the dashboard and the + workflow step have always documented. It was a plain `int`, so the defaults + pass could not tell an absent key from an explicit `0` and rewrote both to + 400 -- the documented way to disable the cap was unreachable. **Behaviour + change:** a config that set `0` was silently getting 400 and will now get no + cap. +- The same ambiguity was failing open per identity: `configForIdentity` + assigned the identity's value unconditionally, so an identity that merely + omitted `diff_cap_lines` overwrote the shared cap with the zero value and + disabled the safety rail entirely. An identity now overrides only when it + sets the key. +- A diff-cap park no longer tells the operator to "approve manually". A parked + task's actions are retry, abandon and reject, so there is no approve path out + of diff-cap; it now names the two things that work. +- `[health].dependency_timeout` makes the daemon's readiness probe timeout + configurable, matching the extracted services. + +### archied — Chat rendering + +- `/status` and `/tasks` are line-oriented reports but separated lines with a + plain newline, which is CommonMark's soft wrap: the Telegram renderer joined + them into one run-on paragraph. The renderer implements CommonMark's hard + line break and the reports use it. Ordinary prose still soft-wraps. +- A park reason is capped to its first line in the `/tasks` list. It carries + whatever the failing stage reported, which for a lint gate is a whole tool + log; unbounded, one parked task pushed every other task out of the reply. The + full reason is unchanged on the task, in `task_list` and on the dashboard. + +### archied — Review + +- Review findings are posted as line-anchored PR comments with suggested fixes, + and a suggestion must be single-line -- GitHub applies a multi-line suggestion + only up to its first line, silently corrupting the file (#891). +- The remediate workflow handles PR review comments and requested changes. + +### archied — /status health surface + +`/status` reports the live broker connection and the last-known outcome of this +process's chat-model calls, alongside the queue depth and runtime block (#892). + +- A provider error is flattened and capped, so a multiline or oversized error + cannot break the one-line-per-fact layout. +- Concurrent model calls no longer reorder: the completion time is taken before + the lock, so the newer outcome wins rather than whichever goroutine stored + last. +- Curator model calls are recorded too. They bypass the chat path, so a daemon + whose only recent model traffic was curator work reported "no calls attempted + yet" while the provider was demonstrably reachable. +- Title generation does not record health. It runs detached under its own + bound and its error is swallowed, so a cosmetic timeout was overwriting the + line with "failed". + +**Known limitation:** the container, poll and channel sections cannot render. +Those facts live in the daemon, but the only Router lives in the Gateway +process, which has no container pool and no poll loop. The command description +says what actually appears; restoring the rest needs a cross-process health +contract. + +### archied — Dashboard and containers + +- The served lifecycle vocabulary reaches an already-painted page, the page + registry matches the routes, and the build verifies `ui/dist` is fresh + instead of never looking at it (#890, #898). +- The container reaper no longer deletes teardown bookkeeping early, so a + released container is not torn down twice (#893). + +### archied — Build + +- `task fmt` runs `golangci-lint fmt` -- the same engine and configuration the + gate checks with. Standalone `gofumpt` cannot reproduce gci's import + grouping, so formatting and linting could not converge and no command + satisfied the gate (#901). +- `goimports` is deliberately absent from the formatter set: it re-reads and + re-parses the module index once per file, ~135s across this tree. + +### archied — Fixed + +- `Config.Clone` left the new diff-cap pointers aliased, so a clone could write + through to the published snapshot (#902). +- A curator asking for a completion on a daemon with no configured provider + panicked the process; it now returns an error. + +### archie-agent + +- The sandboxed runtime picks up line-anchored review comments: a finding is + posted against the line it is about, with a suggested fix where it has one, + and a suggestion is rejected unless it is single-line -- GitHub applies a + multi-line suggestion only up to its first line, silently corrupting the + file (#891). +- `diff_cap_lines` is an optional value in the shared config the runtime + reconstructs, so an explicit `0` means "no cap" rather than being rewritten + to the default. **Behaviour change** for a repo that set `0` expecting + unlimited and was silently getting 400 (#899). +- A diff-cap park names a remedy that exists: a parked task's actions are + retry, abandon and reject, so the reason no longer says "approve manually". +- A released container is not torn down twice -- the reaper no longer deletes + teardown bookkeeping before `Release` is finished with it (#893). +- Build toolchain: `gofumpt` and `golangci-lint` are pinned as one matched + pair, and `task fmt` uses the same engine the gate checks with, so the + runtime's own gate is satisfiable (#901). + +## [1.29.0] - 2026-09-19 + +### archied — Security + +- `google.golang.org/grpc` bumped past `v1.84.0` to patch + [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443), a server panic via a + missing `:authority`/`Host` header reachable through `archied`'s gRPC + gateway server. No stable release carries the fix yet, so this pins the + pre-release commit that does (`v1.85.0-dev.0.20260825072537-93e31b48545e`) + until `grpc-go` cuts `v1.85.0`. + +### archied — Memory engine unification + +One memory engine, addressed by four typed scopes (global, agent, user, +agent-user), replaces the two disconnected stores that previously existed: +a chat-tool-written store nothing ever read back, and a curator-written store +with no scope model. + +- `internal/domain/memory` is a CRUD contract (`Create`/`Get`/`Query`/`List`/ + `Update`/`Forget`/`Revisions`) with retained revisions; updates supersede + rather than overwrite, so a crash mid-write leaves a recoverable extra + history entry, never a lost prior state (#886). +- The chat turn reads its subject's scopes synchronously before the prompt is + built, rendering recalled records into a `` block; a failing or + panicking engine degrades to no memory block rather than failing the turn + (#887). +- The model writes memory through four id-addressed tools + (`memory_create`/`update`/`delete`/`list`), scoped to the turn's own + resolved identity -- the model chooses the scope kind, never the ids, so it + has no path to write into another user's memory (#888). +- The session curator now derives the agent-user scope from the session's own + user-role messages, instead of keying facts by a session id that stops + meaning anything once the session ends. +- A channel with no resolvable user (dashboard, webhook) reads and writes only + global and agent scope; a webhook's route path is never treated as a user + identity. +- Fixed a review finding on the read path: the per-scope record limit was + being applied as one shared total across all scopes rather than per scope, + and the rendered block's byte cap was checked before template escaping + rather than after, letting the escaped block exceed it. + +### archied — Work intake + +- feat(workintake): define review reaction envelope +- feat(workintake): authorize review reactions by owned PR + +### archied — Cleanup + +- Deleted the unwired plugin capability-host health surface + (`Host.Health`/`Host.Manifests`/`ModuleStatus`) and the `Module.Health` + chain it fed -- including the `mcp`/`builtin` tool-provider health + implementations and their aggregation in `tools/provider.Registry` -- none + of which had ever had a production caller (#882). + +### archie-agent + +- The sandboxed runtime picks up the review-reaction envelope and its + owned-PR authorization, so an agent can only react to reviews on pull + requests it opened itself. +- `google.golang.org/grpc` bumped past `v1.84.0` to patch + [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443) (shared dependency + with `archied`; the pre-release commit is pinned pending a stable + `v1.85.0`). + +## [1.28.0] - 2026-09-19 + +### archied — Task detail and attempt attribution + +- New per-run task detail page, showing each attempt's own events, changes and + configuration rather than a single merged view. +- Events, changes and config are attributed to the attempt that produced them; + `Event` carries `attempt` and `ReadTaskLogRequest` carries `stage`. +- The task detail page remounts when the task id changes, so switching tasks + does not leave the previous one's data on screen. + +### archied — Configuration + +- Services are keyed by name through a registry, so the State Store and Gateway + listen addresses are configurable rather than fixed. +- A partial overlay no longer clears the fields it omits — an overlay that set + one key was wiping the rest. +- The Services map is cloned on publish, so an overlay can no longer mutate the + snapshot other readers are holding. +- The service context is enforced at registration. + +### archied — Logging and park reasons + +- A parked run's reason is recorded in its own attempt log, in both the daemon + and the workflow, so "why did this park?" is answerable from the task itself. +- `TaskRegistry.Write` takes the caller's context. + +### archied — Worktrees and containers + +- Retries recover from path-type conflicts instead of failing opaquely, and the + underlying cause is no longer masked. +- The worktree is handed back on every sandbox exit. +- A container's max-uptime reaper is cancelled on release, the cap stays active + through the grace period, and teardown is claimed once rather than by + cancelling a timer. + +### archied — Daemon and startup + +- Every identity's forge and repos are swept at startup, including the root + forge. +- A cancelled startup is no longer reported as an exhausted sweep budget; an + exhausted budget names itself as the cause. + +### archied — Other + +- `grep` can use the workspace codesearch index. +- Forge labels are matched when namespaced, so label-driven routing works for + namespaced labels. +- Triage is given criteria for choosing between workflows, and a workflow is + required when a code change is needed. +- The Telegram adapter restart callback is wired into the chat router. +- The `ARCHIE_REACTIONS` fan-out stream is provisioned and bounded by age. +- `archie-ui` exits cleanly when graceful shutdown overruns its deadline. +- The dashboard's event pump retries priming until the State Store answers. +- The update writer emits the agent version sidecar with a real newline. +- The UI finishes its Preact port; the imperative DOM layer is deleted. +- Collection fields decoded over the State Store gRPC contract are never nil + slices, so an empty collection marshals as `[]` rather than `null`. + +### archie-agent + +- The sandboxed runtime picks up the attempt-attribution contract, so the events + and changes an agent produces are recorded against the attempt that produced + them. +- `grep` can use the workspace codesearch index. +- A worktree is handed back on every sandbox exit, and container teardown is + claimed once — a released container's reaper is cancelled rather than + re-firing during the grace period. +- Retries recover from worktree path-type conflicts instead of failing + opaquely. +- A parked workflow run records its park reason in its own log. +- Triage criteria distinguish the workflows, and a workflow is required when a + code change is needed. +- Namespaced forge labels match when routing by kind. +- The `ARCHIE_REACTIONS` fan-out stream is provisioned. +- Collection fields decoded over the State Store gRPC contract are never nil + slices, so an empty collection marshals as `[]` rather than `null`. + +## [1.27.0] - 2026-09-17 + +### archied — Dashboard task logs + +- Task logs are readable from the dashboard again, through a new State Store + read contract (`ReadTaskLog`, `StreamTaskLogContent`) rather than the UI + process reaching into the daemon's log files. Wired server-side by the + standalone state-store process. +- Added `GET /api/tasks/{id}/logs/download`, serving an attempt's raw log as a + `task--attempt-.log` attachment. +- A process that cannot read logs and an attempt that recorded no log are now + distinguishable ("cannot read" answers 503, "no log" answers 404) instead of + both rendering as a claim about a configuration setting. + +### archied — Telegram output + +- Tool results are summarised rather than quoted: a search reports how many + matches came back, a truncated result reports the tool's own total. The + renderer no longer states a count it computed from its own truncated sample. +- Repeated successful tool calls collapse into one counted entry. +- The tool-activity block is capped to a third of the live frame, keeps the + newest lines, and marks what it dropped with a `+N earlier` indicator. Every + line that fits is kept. +- Every clamped answer marks its cut with an ellipsis, including the opening + frame, which previously appeared to begin mid-sentence. +- An error response from the log download no longer ships as a `.log` file. + +### archied — Readiness and shutdown + +- The disk probe reports per-filesystem results and checks the root filesystem + as well as the work directory, so a full root is no longer invisible. +- A path shared by several disk targets keeps the strictest requirement any + target places on it, so an optional target can no longer mask a required one. +- The shutdown-watchdog test no longer races the Go scheduler, which was + intermittently failing the quality gate and parking work unrelated to it. + +### archied — Other + +- Messages persist the channel-native sender id. +- go-telegram/bot bumped to v1.27.0, fixing a streaming bug where the multipart + body could not be replayed and `sendMessage`/`editMessageText` failed until + the connection dropped. + +### archie-agent + +- The per-task runtime picks up the new State Store task-log read contract, so + the sandboxed agents share one log-reading path with the daemon and the + dashboard. + +## [1.26.0] - 2026-09-17 + +### archied + +- fix(webui): publish per-identity forges so multi-identity task rows keep their links +- feat(config): add [scheduling] config block +- feat(configuration): translate [scheduling] into scheduling.EngineConfig +- feat(cronevents): adapt the events bus to scheduling.Sink +- fix(webui): count every chat front-end in the published projection +- fix(scheduling): respect configuration ownership +- feat(ratelimit): wire per-identity inbound rate limiting into the gateway +- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it +- fix(store): keep an empty binding secret empty so a partial edit cannot erase it +- fix(archied): stop advertising review_pr when no reviewer can run +- fix(daemon): carry kind/label routing bindings to the process that routes +- feat(configuration): add archied setup, the caller the first-run flow was built for +- fix(configuration): stop letting a secret value be set from the command line +- feat(configuration): let setup reference a secret without carrying its value +- fix(archied): disable a provider whose credential is missing instead of refusing to boot +- refactor(install): install.sh delegates config generation, and tests stop reading hand-written configs +- fix(daemon): guard binding dispatch loop against nil dispatcher/creator +- fix(webui): enforce CSRF/origin gate on binding and mapping mutations +- fix(secret): recover a panicking secret engine instead of crashing +- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone +- fix(email): stop dropping the first paragraph of plain-text bodies +- fix(logging): keep the live descriptor open across a failed rotation +- feat(configuration): report config keys no decode target consumed +- feat(archied): warn at boot when the config file has unrecognised keys +- feat(archied): wire the scheduling ticker engine at boot +- fix(agentworker): wire configured tool-result policy into worker's LoopRunner +- refactor(staterpc): delete the superseded single-token auth interceptor +- refactor(memory): delete the unreachable fence scrubber +- fix(channels): delete unreachable Telegram webhook delivery mode +- fix(gateway): delete unwired Router.Dangerous approval path +- refactor(gateway): delete orphaned SessionState goal/steer/queue machinery +- refactor(archied): delete the daemon's unused webui.Server and UI adapters +- refactor(tools): delete unreachable dispatch/gating engine +- feat(channels): wire chat.webhook route config through to the gateway +- refactor(tools): delete unreachable AST-based tool discovery +- refactor(tools): delete unused plugin-tool registration API from builtin.Registry +- feat(channels): wire ConfigSchema/ValidateConfig into a startup validation loop +- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted) +- fix(curator): populate PassInput.Since with the prior pass time +- fix(memory): install the threat scanner the composition root never wired +- fix(staterpc): preserve marshal_error marker in eventDataJSON +- fix(gate): validate finding level and share the blocking threshold +- fix(scheduling): record a completed run so a recurring job stops re-firing every tick +- fix(releaseupdate): don't treat empty available as deferred +- fix(tools/provider/mcp): preserve MCP binary tool results for delivery +- refactor(gateway): share sensitive-key markers with webhookguard +- refactor(daemon): remove unreachable SQLite poll/drain path +- refactor(tools/mcp): delete unreachable MCP adaptation path +- fix(taskactions): resolve max_retries from the task's owning identity +- fix(daemon): forward configured MCP servers to task agents +- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path +- refactor(skillbuild): delete dead AugmentRegistry path +- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout +- refactor(binding): delete dead Matcher.Overlaps method +- refactor(forge): delete dead CreateIssue surface +- fix(mcp): cancel in-flight SSE reconnect on Stop +- fix(container): enforce MaxUptime lifetime cap with a timer +- refactor(store): use taskstate status constants in SQL +- fix(ui): unbreak binding approve and the two deletes, and centralise the client +- fix(tools): stop testing on the text of other files, and ungate contractaudit +- refactor(forge): delete the unwired RepliesAfter surface +- refactor(config): delete the two decoded-but-unread policy fields + +This release is dominated by dead-code removal and the completion of the +scheduling capability. Roughly half the commits delete surfaces that no longer +had a caller: the unreachable SQLite poll/drain path, the unwired MCP +adaptation path, the AST-based tool discovery, the superseded single-token auth +interceptor, and several dead forge and binding methods. The +`IncrementRetryCount` State Store RPC is gone with them -- a breaking change to +the wire contract, accepted because nothing called it. + +The cron/scheduling epic lands its remaining slices: the `[scheduling]` config +block, its translation into the engine's own settings, the events-bus sink +adapter, and the boot wiring that starts the ticker. A recurring job now records +a completed run, so it stops re-firing on every tick. + +Operator-facing work: `archied setup` gives the first-run flow the caller it was +built for, configuration no longer accepts a secret value from the command line, +and a provider whose credential is missing is disabled rather than refusing to +boot. A secret engine that panics is now recovered instead of crashing the +daemon. + +### archie-agent + +- feat(config): add [scheduling] config block +- fix(webui): count every chat front-end in the published projection +- fix(scheduling): respect configuration ownership +- feat(ratelimit): wire per-identity inbound rate limiting into the gateway +- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it +- fix(daemon): carry kind/label routing bindings to the process that routes +- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone +- fix(logging): keep the live descriptor open across a failed rotation +- fix(agentworker): wire configured tool-result policy into worker's LoopRunner +- refactor(staterpc): delete the superseded single-token auth interceptor +- refactor(tools): delete unreachable dispatch/gating engine +- feat(channels): wire chat.webhook route config through to the gateway +- refactor(tools): delete unreachable AST-based tool discovery +- refactor(tools): delete unused plugin-tool registration API from builtin.Registry +- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted) +- fix(staterpc): preserve marshal_error marker in eventDataJSON +- fix(gate): validate finding level and share the blocking threshold +- fix(tools/provider/mcp): preserve MCP binary tool results for delivery +- refactor(tools/mcp): delete unreachable MCP adaptation path +- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path +- refactor(skillbuild): delete dead AugmentRegistry path +- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout +- refactor(binding): delete dead Matcher.Overlaps method +- refactor(forge): delete dead CreateIssue surface +- fix(mcp): cancel in-flight SSE reconnect on Stop +- fix(container): enforce MaxUptime lifetime cap with a timer +- refactor(forge): delete the unwired RepliesAfter surface +- refactor(config): delete the two decoded-but-unread policy fields + +The runtime carries a smaller, more focused set of changes than the same +version's archied entry: agent-side tool-result policy is now wired into the +worker's loop, MCP binary tool results survive to delivery, the container +`MaxUptime` lifetime cap is enforced with a timer, and a scheduled run records +completion so it does not re-fire each tick. + +Note that several bullets above name config, webui and ratelimit packages. Those +are attributed here by the release tool's package-closure rule (`go list -deps` +over the agent binary), not because the agent owns them; the substantive +runtime changes are the worker, MCP, container and scheduling fixes. + +This entry also confirms the removal of the dead `IncrementRetryCount` State +Store RPC, which the agent reaches through `staterpc` rather than by calling it +directly. + +## [1.25.0] - 2026-09-15 + +### archied + +- fix(update): resolve releases without a checkout, and fail loudly when it cannot +- fix(update): back up the task store the daemon actually uses, or refuse +- fix(update): build each component from its own approved release tag + +Components are independently versioned, so the newest `archied/v*` and +`archie/v*` tags usually sit on different commits. The installer required both +tags to resolve to one commit whenever both components changed, which refused +every update once the two newest releases diverged -- a deployment stuck on +1.22.0 could not take any update. Each component now builds from its own +approved tag. + +### archie-agent + +- chore: no user-facing changes; versioned so the 1.25.0 release tags both + components at the same commit + +## [1.24.0] - 2026-09-12 + +### archied + +Makes 1.23.0 deployable. That release split archied into separate processes, +but the self-updater still installed only the `archied` binary and restarted +only `archied.service`, so updating to it left the State Store, Gateway and UI +on the previous release. archied cannot boot without a reachable State Store, +so the update failed its health check and rolled back. Update to this release +rather than to 1.23.0. + +If your host does not yet run the four units in +`deployments/systemd-user-service.md`, create them first: the updater now +refuses, naming what is missing, instead of installing binaries onto a host it +would leave broken. + +- fix(update): install and cycle every process in the release +- fix(telegram): stop the relay corrupting identifiers and code + +Also in this release, though outside the version-stamped package closure: + +- ci(deploy): produce a complete distribution zip on every release. No zip was + built for v1.23.0 at all, and the zip omitted `archie-ui`. + +## [1.23.0] - 2026-09-12 + +### archied + +Archied is no longer a single process. The State Store (`archie-state-store`) +now owns `archie.db` outright, the Gateway serves its contract over +authenticated gRPC, and the dashboard ships as a standalone UI Service +(`archie-ui`). Upgrading is not a binary swap: these processes must be running +and addressable before `archied` will start clean. See `deployments/` for the +supported profiles. + +### archied — Service decomposition + +- feat(contracts): add gateway service seams and protobuf toolchain +- feat(gateway): extract ChatContract service +- feat(gateway): delete in-process ChatContract path, make remote the only mode +- feat(gateway): authenticate the gRPC contract and allow off-loopback listeners +- fix(gateway): drop services.gateway.mode, remote is the only transport +- feat(state-store): generalize storerpc as the State Store gRPC contract (#770) +- feat(state-store): stand up archie-state-store binary and own archie.db (#771) +- refactor(state-store): migrate capture/mapping/binding consumers to State Store (#772) +- refactor(state-store): migrate workflow/intake/task lifecycle consumers to State Store (#773) +- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774) +- fix(state-store): task-scope container credentials, stream large capture lists, validate Update +- feat(archieui): standalone UI process over remote Gateway and State Store +- refactor(archied): cut the dashboard over to the archie-ui process +- refactor(ui): sever the archie-ui binary from every daemon runtime package +- refactor(archied): move the update relay to the process that owns updates +- refactor(archied): move webhook capture intake to the process that owns work intake +- feat(archieui): mount the capture intake receiver over the State Store +- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754) +- refactor(store): move the producer-owned contracts to internal/contracts/store/v1 +- feat(messaging): migrate gateway session persistence onto domain types +- feat(gateway): flip channel boundary onto messaging.Message + +### archied — Pull request review + +- feat(gateway): operator-triggered PR review with selectable reviewer model +- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview) +- feat(workflow): surface adversarial review findings on the PR body +- feat(workflow): review calibration, checked properties and style nits out of contract +- fix(archied): share one PR reviewer across channels; harden forge and worktree +- fix(workflow): order findings before footer; test the report stash + +### archied — Dashboard + +- feat(webui): render configuration from a published snapshot +- feat(staterpc): carry the dashboard's configuration snapshot +- refactor(webui): take configuration off the dashboard server +- feat(webui): report which dashboard sections a process can serve +- feat(webui): deliver live dashboard events by polling the State Store cursor +- feat(webui): route dashboard task actions through the Gateway contract +- feat(gateway): give the dashboard operator its own task-action contract +- feat(webui): add /health and /health/detailed readiness endpoints (#717) +- fix(webui): distinguish refused vs broken task actions, handle 401 (#753) + +### archied — Daemon, gateway and workflow + +- feat(archied): add shutdown watchdog that force-exits a hung graceful shutdown (#716) +- feat(archied): serve the daemon's own health endpoint +- feat(drain): honour external drain marker with instantiation epoch (#718) +- feat(gateway): wire progressive tool disclosure (bridge tools) +- feat(gateway): render workspace, managed repos and operator into chat env +- feat(gateway): add session_transcript tool for full JSON export +- feat(gateway): consolidate task actions and repair daemon default path +- feat(eda): thread Playbook ID/Version and DispatchInput task identity +- feat(worktree): Resume re-syncs a worktree onto its branch tip +- fix(staterpc): attach the bearer token to State Store streams +- fix(archieui): resolve service tokens from env, without requiring a config file +- fix(archied): initialize conversation persistence on daemon startup +- fix(archied): preserve channel turn ledger with remote gateway +- fix(gateway): share NATS and session ownership +- fix(update): probe the dashboard's real address after a self-update +- fix(store): migrate binding owner and repo columns + +### archie-agent + +The agent runtime now reaches task state through the State Store gRPC contract +(`STATE_STORE_URL`/`STATE_STORE_TOKEN`, injected by the daemon) instead of the +NATS `storerpc` transport, which is deleted. Credentials handed to a task +container are scoped to that task rather than being the daemon's own token. +Running a 1.23.0 daemon against an older agent image will not work; rebuild or +pull the `archie-agent` image with this release. + +- feat(state-store): generalize storerpc as the State Store gRPC contract (#770) +- feat(state-store): stand up archie-state-store binary and own archie.db (#771) +- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774) +- fix(state-store): task-scope container credentials, stream large capture lists, validate Update +- fix(staterpc): attach the bearer token to State Store streams +- feat(staterpc): carry the dashboard's configuration snapshot +- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754) +- refactor(store): move the producer-owned contracts to internal/contracts/store/v1 +- feat(contracts): add gateway service seams and protobuf toolchain +- fix(gateway): drop services.gateway.mode, remote is the only transport +- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview) +- feat(gateway): operator-triggered PR review with selectable reviewer model +- feat(workflow): surface adversarial review findings on the PR body +- feat(workflow): review calibration, checked properties and style nits out of contract +- fix(workflow): order findings before footer; test the report stash +- fix(archied): share one PR reviewer across channels; harden forge and worktree +- feat(worktree): Resume re-syncs a worktree onto its branch tip +- feat(telegram): support secret refs for bot tokens (#705) +- feat(gateway): wire progressive tool disclosure (bridge tools) +- feat(archied): serve the daemon's own health endpoint +- feat(archieui): standalone UI process over remote Gateway and State Store +- refactor(archied): move webhook capture intake to the process that owns work intake +- refactor(ui): sever the archie-ui binary from every daemon runtime package +- fix(archieui): resolve service tokens from env, without requiring a config file + +## [1.22.0] - 2026-09-03 + +### archied + +- feat(telegram): support secret refs for bot tokens (#705) +- fix(update): make daemon rollback schema-safe (#704) +- fix(archied): preserve ephemeral gateway ports (#707) +- fix(webui): bound log limit parsing and add endpoint regression coverage (#706) +- fix(deps): upgrade x/crypto to v0.56.0 for security fixes (#708) + +## [1.21.0] - 2026-09-03 + +### archied + +- feat(workflow): make kind-to-workflow routing YAML-overridable +- feat(workflow): route arbitrary forge labels to workflows via playbook YAML +- feat(workflow): load kind/label bindings from multiple playbook directories +- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive +- feat(eda): Module position first slice -- registry + side-effect-free log kind +- feat(eda): CEL expression environment (compile/validate at load, evaluate at dispatch) +- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch +- fix(skillcurator): document and scope the intentional nilerr in reviewOne +- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch +- feat(webui): bindings dashboard UI; fix app-wide Preact render regression +- fix(binding): split ValidateForUpdate so edits can preserve the secret +- refactor(ui): extract Pill to ui/src/base/, closing archie-core-mlro +- refactor(eda): extract helpers to satisfy cyclop/gocognit gates +- fix(webui): stretch HEALTH row cards to equal height +- fix(eda): make playbook key collision reporting deterministic +- fix(gateway): split /status (health) and /tasks (work) apart + +### archie-agent + +- feat(workflow): make kind-to-workflow routing YAML-overridable +- feat(workflow): route arbitrary forge labels to workflows via playbook YAML +- feat(workflow): load kind/label bindings from multiple playbook directories +- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive +- feat(eda): Module position first slice -- registry + side-effect-free log kind +- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch +- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch +- fix(binding): split ValidateForUpdate so edits can preserve the secret +- refactor(eda): extract helpers to satisfy cyclop/gocognit gates +- fix(eda): make playbook key collision reporting deterministic + +## [1.20.0] - 2026-09-03 + +### archied + +- fix: baseline gate repair (go test ./... -count=1) +- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler +- feat(image): define provider-neutral image capability contract and config +- fix(channels): call MarkRunning once a channel is actually up +- fix(workflow): stop discarding baseline-fix commits as 'no changes' +- fix(webui): wire the Logs page to per-task attempt-log detail +- fix(workflow): net cache hits from token totals, trim gate-retry output +- feat(workflow): dynamic triage instead of defaulting every task to implement +- fix(gateway): stop SOUL from forging the prompt invariant tags +- fix(curator): stop curator actions from serializing a zero timestamp +- feat(webui): hand-author the configuration field descriptor catalog +- feat(webui): attach the config field schema to GET /api/config +- feat(webui): render scalar config sections generically from the schema +- feat(webui): surface allow_concurrent/max_retries/review_enabled on the repositories card +- feat(webui): inline editing for per-repo allow_concurrent/max_retries/review_enabled +- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated +- fix: resolve golangci-lint funlen, nilerr, and empty branch issues +- feat(store): encrypt playbook binding secrets at rest +- feat(webhook): harden captured payload redaction +- fix(store): satisfy makezero when building cipher payload +- feat(webui): refactor chat module to Preact component and add unit tests + +### archie-agent + +- fix: baseline gate repair (go test ./... -count=1) +- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler +- feat(image): define provider-neutral image capability contract and config +- fix(workflow): stop discarding baseline-fix commits as 'no changes' +- fix(workflow): net cache hits from token totals, trim gate-retry output +- feat(workflow): dynamic triage instead of defaulting every task to implement +- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated +- feat(store): encrypt playbook binding secrets at rest +- fix(store): satisfy makezero when building cipher payload + +## [1.19.10] - 2026-09-02 + +### archied + +- feat(curator): session-memory curator reference implementation + +## [1.19.9] - 2026-09-02 + +### archied + +- feat(memory): typed memory engine contract, registry, and registrar +- feat(memory): builtin engine implementing the domain/memory contract +- feat(config): config surface for memory engine selection +- feat(daemon): wire the domain/memory engine registry at boot +- feat(curator): bind curators to memory engines +- fix(config): reject memory.provider instead of silently ignoring it +- feat(curator): skill curator reference implementation + +### archie-agent + +- feat(config): config surface for memory engine selection + +## [1.19.8] - 2026-09-02 + +### archied + +- fix(update): drop dev-facing wording from the unconfirmed-update message +- fix(telegram): stop adjacent rich blocks from rendering glued together +- fix(telegram): send undelivered-media fallback after finalize as its own message + +## [1.19.7] - 2026-09-02 + +### archied + +- fix(logging): make Tail/Page allocation bound explicit for CodeQL + +### archie-agent + +- fix(logging): make Tail/Page allocation bound explicit for CodeQL + +## [1.19.6] - 2026-09-02 + +### archied + +- fix(build): stamp gatewayVersion/runtimeVersion in the right package + +## [1.19.5] - 2026-09-01 + +### archied + +- feat(webui): dashboard-aware chat — Archie sees the page, points you there +- fix(telegram): drop retry_after bandaid, bump go-telegram/bot to v1.24.0 +- feat(curator): track and expose recent activity per curator +- fix: go.mod bumped to 1.27.0 and stupid tests removed +- refactor: remove unnecessary AI-generated scaffolding +- refactor: go modernisation fixes +- refactor: remove unused Operator param. +- fix(gateway): fix broken system prompt template and scrub real telegram ID from tests +- fix(plugin): add missing CLAUDE.md reference to plugin engine rule +- fix(app): repoint archied wiring contract test at internal/app/archied +- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet +- fix(config): standardize Provenance to pointer receivers (recvcheck) +- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui +- fix(app): repoint capability-host wiring contract test at internal/app/archied +- refactor(lint): extract more helpers to clear nestif/gocyclo findings +- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult +- refactor(lint): split TurnRunner.Run and dispatchLocal further +- refactor(lint): extract markdownBlockParser and list/quote helpers in richblocks.go +- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization +- fix(lint): noctx fixes and dead-code cleanup +- feat(workflow): adversarial self-review stage before PR open + +### archie-agent + +- feat(tasks): allow rejecting a task from any non-terminal state +- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta +- fix: go.mod bumped to 1.27.0 and stupid tests removed +- refactor: go modernisation fixes +- refactor: remove unused Operator param. +- fix(plugin): add missing CLAUDE.md reference to plugin engine rule +- fix(app): repoint archied wiring contract test at internal/app/archied +- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet +- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui +- fix(app): repoint capability-host wiring contract test at internal/app/archied +- refactor(lint): extract more helpers to clear nestif/gocyclo findings +- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult +- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization +- fix(lint): noctx fixes and dead-code cleanup +- feat(workflow): adversarial self-review stage before PR open + +## [1.19.4] - 2026-08-28 + +### archied + +- refactor(telegram): render replies as structured rich blocks + +## [1.19.3] - 2026-08-28 + +### archied + +- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta +- feat(dashboard): render task actions, statuses and filters from the server catalog + +## [1.19.2] - 2026-08-28 + +### archied + +- feat(tasks): allow rejecting a task from any non-terminal state + +## [1.19.1] - 2026-08-27 + +### archied + +- fix(telegram): keep Markdown headings/lists as blocks and strip Markdown on plain fallback + +## [1.19.0] - 2026-08-28 + +### archied + +- feat(logging): cursor pagination and filtering for task_logs +- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29 + +## [1.18.0] - 2026-08-28 + +### archied (released 2026-08-25) + +- Fix concurrent chat-turn claims so SQLite writer contention no longer leaks as `SQLITE_BUSY`. +- Make task timelines operationally useful with stage outcomes, durations, retry context, and durable per-stage token economics. +- Return canonical repository, issue, and pull-request URLs for each task's owning GitHub or Gitea identity. +- Preserve per-identity commit attribution and real model context limits across daemon-to-worker dispatch. + +### archie-agent + +- feat(logging): cursor pagination and filtering for task_logs +- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29 + +## [1.17.1] - 2026-08-25 + +### archied + +- fix(update): remove source checkout dependency +- fix(gateway): make UUIDv7 session references unambiguous + +## [1.17.0] - 2026-08-25 + +### archied + +- fix(webui): add nil receiver guard to Server.trustForwardedHeaders +- fix(chat): restore transcript and update replay + +### archie-agent + +- Compact task history against the selected model's real context capacity without imposing a token cap. +- Preserve completed steps and billed usage when a later provider call fails; failed compaction now keeps the original history and continues. +- Persist detailed agent-stage usage through the daemon-owned store before lossy live event fan-out. +- Apply configured or forge-derived author and committer identity to sandboxed task commits. + +## [1.16.1] - 2026-08-25 + +### archie-agent + +- fix(agentworker): reconcile task clone ownership after commits + +## [1.16.0] - 2026-08-25 + +### archied + +**The agent can hand you a file, and the dashboard works behind a reverse +proxy.** Media delivery was fetch-by-URL only, so a file the agent produced +locally — a transcript, a log dump, a screenshot — was passed to Telegram as +a URL it could not fetch: the send did nothing and reported success. The new +`send_file` tool plus upload-by-reader delivery closes that, and every layer +that cannot deliver now says so rather than staying silent. Dashboard +mutations behind a TLS-terminating proxy were refused as cross-origin; +forwarded headers are now honoured, but only under an explicit opt-in that is +off by default. + +- feat(telegram): deliver a local file as an uploaded attachment, choosing + upload-by-reader or fetch-by-URL per attachment; `send_file` resolves paths + under the same confinement policy the read tool applies, so sending cannot + reach what reading cannot +- feat(gateway): `task_action` chat tool for operator task management — + abandon, archive, retry, stop, cancel, approve and reject from chat, on the + same action path and state machine as the dashboard +- fix(webui): validate mutation `Origin` against the effective external + scheme and host. `X-Forwarded-Proto`/`-Host` are honoured only when + `web.trust_forwarded_headers` is set, which is off by default and safe only + behind a proxy that overwrites or strips untrusted forwarded headers +- fix(webui): report a local file the dashboard chat cannot upload as + undelivered instead of dropping the event, which had reproduced the exact + silent non-delivery `send_file` was built to end +- fix(daemon): detach terminal state transitions and cleanup from a cancelled + context, so a stopped task still records its outcome + +### archie-agent + +**Version realigned with `archied`.** This release jumps from 1.9.9 to 1.16.0 +to put the two components on matching numbers; there are no 1.10-1.15 agent +releases. It clears the accumulated runtime backlog in one cut rather than +bundling it as a rider on a later change, so the list below spans several +weeks of work rather than one session's. + +Highlights: + +- feat(nats): run an embedded server when no external NATS is configured, and + expose the embedded broker to managed task workers +- feat(deployment): default to managed NATS workers; the daemon requires a + full-task worker handoff and the legacy in-process, subprocess and + single-stage execution paths are gone +- feat(forge): GitHub webhook receiver for immediate issue dispatch, with + dedup regression proof; unbound webhook events are stored retention-bounded +- feat(webui): payload field mapping -- bind JSON paths to named fields and + preview before saving +- feat(scheduling): ticker engine with configurable interval and pools +- feat(storage): persist agent project state +- feat(agent): stamp archie-agent's build and report it back to the daemon +- feat(tools): `generate_video` via MiniMax, gated behind config, and + `MultimodalResult.URLs` for remote-hosted media +- feat(workflow): define the adversarial-review findings contract + +Fixes: + +- fix(worktree): bind publication to dispatch grants; reset retries to a + pristine base; reject diffs without a merge base; clean untracked files when + `.git` is a gitdir file; post-push metadata resilience, cancellation and + branch naming +- fix(container): persist the npm cache for per-task MCP servers +- fix(agentexec): recover omitted finish calls +- fix(agentworker): move JSONL decode into storage, unblocking CI +- fix(telegram): compact tool output and drop turn caps +- fix(webui): give dashboard-initiated updates a phase-2 report; restore the + provider gate and dashboard token accounting +- refactor: remove dead `BasePlatformAdapter` code and legacy execution paths + +Shared with archied 1.16.0 (these packages are in both closures): + +- feat(telegram): send local files as uploads, not fetchable URLs +- fix(webui,sendfile): close three holes the adversarial review found +- fix(webui): validate mutation Origin against the effective external scheme + +## [1.15.0] - 2026-08-24 + +### archied + +**Autonomous workflows now have exactly one production execution path.** Every +task is handed complete to a scoped `archie-agent` container over core NATS; +`archied` no longer runs an agent loop in-process. Embedded NATS is the +default and generates a per-start token, binding to the resolved Docker bridge +so managed workers can reach it; external NATS changes only broker placement. +The legacy `[agent]` section and `containers.enabled` still decode for +migration but can no longer select an execution path, and a reloaded +`nats.url` is logged as requiring a restart. Operators upgrading from a +`agent.mode = inprocess` configuration get the managed-worker topology +automatically; see `deployments/` for the supported profiles. + +- feat(nats): expose the embedded broker to managed task containers behind a + generated per-start credential +- fix(daemon): park before worktree access when the container pool or task + transport is unavailable, rather than silently executing locally +- refactor(agentexec): remove the in-process, subprocess and single-stage + execution paths +- fix(worktree): report a successful push as successful even when writing + local upstream tracking metadata afterwards fails, so a published branch no + longer parks the task as failed +- fix(worktree): honour context cancellation in `CommitAll`, so a cancelled + task can no longer stage or commit +- fix(daemon): remove the worktree when a task completes with no changes, + which previously leaked a full clone per no-change task; parked worktrees + are still retained for post-mortems +- fix(worktree): derive the branch prefix from the issue title before falling + back to labels, matching the documented contract +- fix(worktree): clean untracked files when `.git` is a gitdir file +- fix(agentexec): recover agents that end a turn without the required finish + call +- feat(scheduling): ticker engine with a configurable interval and pools +- fix(telegram): keep tool-call context when compacting tool output (#609) +- feat(workflow): add the adversarial-review findings contract, where only a + confirmed finding blocks and "review found nothing" is distinct from + "review did not run" (contract only; no review stage runs yet) + +## [1.14.0] - 2026-08-23 + +### archied + +- fix(telegram): compact tool output and drop turn caps +- fix(update): install only approved components + +## [1.13.0] - 2026-08-23 + +### archied + +- fix(telegram): render tool progress as bounded code blocks + +## [1.12.0] - 2026-08-23 + +### archied + +- fix(webui): give dashboard-initiated updates a phase-2 report +- feat(agent): stamp archie-agent's build and report it back to the daemon +- feat(releaseupdate): enrich components with install type and reference +- feat(webui): surface per-component update status on /api/version and Configuration + +## [1.11.1] - 2026-08-23 + +### archied + +- fix(update): wire Telegram personas and survive callback cancellation +- fix(webui): theme the Workflows 'Start work' form controls + +## [1.11.0] - 2026-08-23 + +### archied + +- feat(forge): make webhook intake observable and deduplicate concurrent delivery +- fix(telegram): preserve code fences across message splits +- fix(gateway): replay completed-duplicate turns with their tool activity +- feat(storage): persist agent project state across sessions +- fix(container): persist npm cache for per-task MCP servers +- fix(worktree): bind publication to dispatch grants, reset retries to a pristine base, and reject diffs without a merge base +- feat(media): deliver generated media through Telegram with link fallback in the dashboard +- feat(tools): generate videos through MiniMax, gated by provider configuration + +## [1.10.0] - 2026-08-22 + +### archied + +- feat(forge): GitHub webhook receiver for immediate issue dispatch +- feat(webhookguard): shared HMAC, rate-limit, and redaction mechanics +- feat(nats): run an embedded server when no external NATS is configured +- feat(capture): store unbound webhook events, retention-bounded +- feat(webui): event inspector -- see captured payloads in the dashboard +- feat(webui): payload field mapping -- bind JSON paths to named fields, preview before saving +- fix(webui): stop the capture live-event notification duplicating payloads into the unbounded events table +- fix(update): verify an update took effect instead of trusting the report (#530) +- fix(daemon): refuse to poll on an empty label-trigger match (#529) +- fix(gateway): stop persona from asserting unverified claims as fact (#528) +- fix(gateway): stop ClaimTurn's insert-race branch losing its own retry read +- fix: restore provider gate and dashboard token accounting +- fix: address simple findings from a repo-wide golangci-lint sweep + +## [1.9.11] - 2026-08-19 + +### archied + +- fix(mcp): persist npx package cache across daemon restarts + +## [1.9.10] - 2026-08-19 + +### archied + +- feat(update): `/update` now streams live progress while an update installs, reports a clear version summary (previous/installed, daemon/agent) once the build succeeds, and automatically rolls back and reports the outcome if the restarted daemon fails its post-update health check + +## [1.9.9] - 2026-08-18 + +### archied + +- fix(telegram): drain live renderer in concurrency test + +### archie-agent + +- chore: no user-facing changes + +## [1.9.8] - 2026-08-17 + +### archied + +- chore: no user-facing changes + +### archie-agent + +- chore: no user-facing changes + +## [1.9.7] - 2026-08-17 + +### archied + +- chore: no user-facing changes + +### archie-agent + +- chore: no user-facing changes + +## [1.9.6] - 2026-08-16 + +### archied + +- fix(update): stamp install type and bound retry backoff + +### archie-agent + +- chore: no user-facing changes + +## [1.9.5] - 2026-08-16 + +### archied + +- refactor(archied): decompose the daemon bootstrap into phased wiring (no behaviour change; splits the ~950-line run() into focused setup phases so complexity linting passes) +- refactor(archied): extract the config overlay boot helper and thread context through chat gateway setup +- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity +- fix(tools): avoid predeclared `max` names +- fix(email): use context-aware test networking +- fix(indexing): remove the unused code search test runner +- fix(tests): use contexts and type assertions in overlay and gateway tests +- docs(architecture): document the memory engine family + +### archie-agent + +- refactor: decompose the daemon bootstrap into phased wiring (no behaviour change; complexity-driven restructure) +- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity +- fix(tools): avoid predeclared `max` names + +## [1.9.4] - 2026-08-15 + +### archied + +- feat(gateway): polish /status command response format +- fix(telegram): preserve URL boundaries in responses + +### archie-agent + +- chore: no user-facing changes + +## [1.9.3] - 2026-08-15 + +### archied + +- fix(webui): scroll selected command into view on keyboard navigation +- fix(logging): resolve error attrs to their message string, not {} +- feat(agentexec,workflow): surface tool calls on the task timeline + +### archie-agent + +- fix(logging): resolve error attrs to their message string, not {} +- fix(agentworker): back off before refetching a nak'd stage message +- feat(agentexec,workflow): surface tool calls on the task timeline + +## [1.9.2] - 2026-08-15 + +### archied + +- fix(worktree): force checkout so retry recovers from a dirty worktree + +### archie-agent + +- fix(worktree): force checkout so retry recovers from a dirty worktree + +## [1.9.1] - 2026-08-15 + +### archied + +- fix(agentworker): forward workflow events across the NATS worker boundary +- fix(webui): filter turn_completed noise from the Live Activity SSE feed +- feat(releaseupdate): stamp install type at build time, fail closed on unknown + +### archie-agent + +- fix(agentworker): forward workflow events across the NATS worker boundary + +## [1.9.0] - 2026-08-15 + +### archied + +- fix(webui): style tool-call failure from a structured field, not a string prefix +- fix(config,webui): make show_tool_calls one cross-channel setting +- fix(telegram): guarantee no message is stranded on gateway stop/restart +- fix(telegram): use NewRequestWithContext to satisfy noctx +- refactor(webui): decompose handleSSE to cut cognitive complexity + +### archie-agent + +- fix(agent): resolve git dubious-ownership in sandbox containers +- feat(agent): mark the mounted worktree as a git safe directory +- fix(agent): route git safe.directory setup through markWorktreeSafe +- feat(chat): show tool calls inline and stream replies into one message +- refactor(agent): move worker runtime into application layer +- fix(config,webui): make show_tool_calls one cross-channel setting + +## [1.8.0] - 2026-08-15 + +### archied + +- feat(archied): add -version so the installed build can be read from a shell +- fix(webui): rebuild the Configuration page layout so values stop colliding +- fix(webui): size Configuration key/value lists to their own content +- fix(webui): keep Configuration rows full width, hug only the label column +- fix(webui): cap and centre the Configuration page instead of its lists +- fix(webui): preserve encoded redirect path characters +- feat(chat): show tool calls inline and stream replies into one message +- fix(chat): harden inline tool call streaming +- refactor(agent): move worker runtime into application layer +- fix(telegram): harden live-reply delivery against /stop and multi-byte content +- fix(telegram): keep tool activity visible and mark failed/empty turns +- fix(config): de-duplicate disabled-forge predicate, export ForgeDisabled + +## [1.7.0] - 2026-08-10 + +### archied + +- fix(build): install ripgrep where grep.go actually needs it on PATH +- fix(webui): Send button no longer passes its click event to sendMessage +- feat(webui): Enter sends, Shift+Enter inserts a newline +- fix(chat): stop showing raw 501 banner for unconfigured update-check +- fix(chat): give chat page a real height budget instead of a floor +- fix(workflow): carry gate output into the baseline park error +- feat(logging): add a per-task log sink +- feat(agentexec): publish agent-side logs to the task's system subject +- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed +- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool +- refactor(gateway): persist conversations in sqlite +- refactor(store): replace legacy persistence with SQLite +- fix(webui): tighten configuration KV row spacing +- fix(gateway): harden session recovery paths +- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe +- feat(config): SIGHUP-triggered reload with requires-restart warnings +- fix(config): share one config Holder between daemon and dashboard; re-apply model catalog on reload +- fix(config): complete the reloadable allowlist and pin it against ForTask +- feat(config): runtime config overlay store, PATCH /api/config, and the `--no-config-overlay` recovery flag +- feat(webui): inline config editing on the Configuration page +- feat(config): surface overlay state, shadowed keys, and per-row reset +- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state +- fix(config): preserve nil slices in Clone to avoid spurious reload warnings + +## [1.6.0] - 2026-08-09 + +### archied + +- feat(gateway): tool-approval gate, session tools for chat, and /delete command +- fix(webui): close open-redirect in dashboard token-exchange handler +- feat(gateway): make chat turns durable and idempotent +- feat(webui): lifecycle-safe task controls with atomic retry and archive +- feat(config,channels): format-neutral config resolution and truthful channel state +- feat(logging,workflow): daemon log feed and executable workflow registry +- fix(store,gateway): taskstate constants and mobile jump-to search +- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams +- fix(ui): hide inactive chat command menu + +## [1.5.0] - 2026-08-08 + +### archied + +- feat(curator): engine family contract, registry, and runtime +- feat(curator): trigger accounting — primary-input wake path +- feat(setup): interactive setup steps with a TTY-gated prompter +- feat(webui): rebuild the dashboard and add chat +- feat(daemon): identity-scoped isolation plus gateway session titles and /delete +- feat(logging): optional rotating log file +- feat(configuration): export Validate for the setup flow +- fix(gateway): durable message identity with a SQLite store +- fix(gateway): consistent message ordering and paged search +- fix(gateway): stop /compress destroying history it should have kept +- fix(gateway): do not answer a redelivered message twice +- fix(gateway): claim the session slot before writing it, not after +- fix(gateway): keep /topic off from poisoning the session cache +- fix(gateway): resolve the most recently active session, not an arbitrary one +- fix(gateway): give branch-inherited messages their own identity +- fix(gateway): make both backends agree on newest-first +- fix(store): honour the transition guard in production persistence +- fix(store): move ID counters away from the reserved metadata namespace +- fix(store): surface task timestamps and tag the summary structs +- fix(telegram): pause the update loop when rate limited +- fix(memory): fail startup on an unusable memory directory +- fix(tools): let an optional provider fail without taking the daemon down +- fix(tools): report a cancelled find walk as an error, not empty results +- fix(worktree): name the missing forge credential when a push fails +- fix(tomlwrite): recognise table headers carrying a trailing comment +- fix: close the duplicate-work loop and the dead paths around it +- perf(tools): drop the embedded ripgrep binaries +- refactor: one definition of what approving or declining a task means +- refactor: move workflow into its own domain + +## [1.4.1] - 2026-07-31 + +### archied + +- fix(catalog): match SDK provider fallback + +## [1.4.0] - 2026-08-10 + +### archied (released 2026-07-31) + +- fix(secrets): wire provider credentials through engines + +### archie-agent + +- feat(gateway): tool-approval gate, session tools for chat, and /delete command +- feat(gateway): make chat turns durable and idempotent +- feat(webui): lifecycle-safe task controls with atomic retry and archive +- feat(logging,workflow): daemon log feed and executable workflow registry +- fix(store,gateway): taskstate constants and mobile jump-to search +- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams +- fix(build): install ripgrep where grep.go actually needs it on PATH +- fix(workflow): carry gate output into the baseline park error +- feat(logging): add a per-task log sink +- feat(agentexec): publish agent-side logs to the task's system subject +- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed +- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool +- refactor(store): replace legacy persistence with SQLite +- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe +- feat(config): SIGHUP-triggered reload with requires-restart warnings +- feat(config): surface overlay state, shadowed keys, and per-row reset +- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state +- fix(config): preserve nil slices in Clone to avoid spurious reload warnings + +## [1.3.1] - 2026-07-31 + +### archied + +- fix(telegram): omit empty model picker markup + +## [1.3.0] - 2026-08-08 + +### archied (released 2026-07-31) + +- fix(memory): replace framework-specific names with generic equivalents +- feat: unify provider and model selection + +### archie-agent + +- feat(curator): engine family contract, registry, and runtime +- feat(curator): trigger accounting — primary-input wake path +- feat(logging): optional rotating log file +- feat(daemon): identity-scoped isolation +- fix(secrets): wire provider credentials through engines +- fix(store): surface task timestamps and tag the summary structs +- fix(tools): let an optional provider fail without taking the daemon down +- fix(tools): report a cancelled find walk as an error, not empty results +- fix(worktree): name the missing forge credential when a push fails +- fix: close the duplicate-work loop and the dead paths around it +- perf(tools): drop the embedded ripgrep binaries +- refactor: one definition of what approving or declining a task means +- refactor: move workflow into its own domain + +## [1.2.0] - 2026-07-31 + +### archied + +- feat: add MCP client capabilities to archied and archie-agent +- fix: handleSummary ignores errors from WorkflowStats/StageStats/TokensByDay +- feat: establish Archie identity and use stable callback tokens +- refactor(telegram): keep one model selector command +- fix: handleSSE silently swallows EventsSince backlog fetch errors +- fix: Transition() ignores `from` status guard, allowing lost updates +- fix: skillscript.Run ignores context, cannot be canceled/timed out +- feat(telegram): report installed component versions +- feat(telegram): add approved component updates +- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup +- feat(chat): real system prompt for Archie — identity, tools, env +- feat(indexing): port tau's codesearch workspace index +- fix(indexing): surface index config properly and stop silent degradation +- refactor(worktree): replace git shell-out with go-git v6 +- fix(worktreerpc): bound handler contexts and drop the git binary from tests +- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries +- refactor: route tasks on a typed kind, not forge labels +- fix(natsrpc): make RegisterAll wait for the server to see subscriptions +- refactor(config): move loading into infrastructure/configuration +- fix(telegram): publish all executable session commands in menu and help +- fix(telegram): publish the restored gateway commands +- refactor: add internal/eventbus as the broker-neutral messaging contract +- fix(chat): operator name from config, session wiring, prompt rules +- feat(tools): lift tau's file and shell tools into the tool registry +- feat: make /stop cancel the running chat turn +- fix: kill the whole process group when a shell command is cancelled +- feat: refuse unrecoverable shell commands +- feat: make /stop reach running agent tasks +- fix(chat): temper prompt brevity rules with warmth +- fix: use errors.Is/As for context errors and cleanup +- fix(grep): distinguish ripgrep exit 1 from a failed search +- fix(archied): disable the forge on a missing credential, not the daemon +- fix: restore /model parsing and close the 6d4e0be autofix audit +- feat: embed config.example.toml and add comment-preserving TOML writer +- fix(docker): install unzip and Node 24 so MCP servers can start +- fix(docker): slim both images and repair unreachable Go tooling +- fix(container): write the task boot brief under .git +- fix(telegram): drop pending updates before long polling + +### archie-agent + +- feat: add MCP client capabilities to archied and archie-agent +- fix: Transition() ignores `from` status guard, allowing lost updates +- fix: skillscript.Run ignores context, cannot be canceled/timed out +- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup +- fix(indexing): surface index config properly and stop silent degradation +- refactor(worktree): replace git shell-out with go-git v6 +- fix(worktreerpc): bound handler contexts and drop the git binary from tests +- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries +- refactor: route tasks on a typed kind, not forge labels +- fix(natsrpc): make RegisterAll wait for the server to see subscriptions +- refactor(config): move loading into infrastructure/configuration +- refactor: add internal/eventbus as the broker-neutral messaging contract +- feat(tools): lift tau's file and shell tools into the tool registry +- feat: make /stop cancel the running chat turn +- fix: kill the whole process group when a shell command is cancelled +- feat: refuse unrecoverable shell commands +- feat: make /stop reach running agent tasks +- fix: use errors.Is/As for context errors and cleanup +- fix(grep): distinguish ripgrep exit 1 from a failed search +- fix(docker): slim both images and repair unreachable Go tooling +- fix(container): write the task boot brief under .git + +## [1.1.0] - 2026-07-27 + +### archied + +- feat: add the Telegram gateway with persistent sessions, topic-thread support, streamed rich replies, typing indicators, and Markdown rendering +- feat: add `/spawn`, `/approve`, and `/cancel` for chat-driven task control +- feat: provide a comprehensive `/help` guide whose command list stays aligned with Telegram's published menu and Archie's executable command surface +- feat: add `/provider` and provider-filtered `/model` selectors that switch the provider and model used by subsequent live chat turns +- feat: include the active provider and full model reference in `/status` +- feat: notify authorized Telegram users once when a newly tagged component release is installed +- feat: add `/restart` to reload and relaunch the Telegram gateway without interrupting in-flight daemon tasks +- feat: add deny-by-default Telegram sender authorization and native command-menu publication +- feat: connect Desktop Commander through Archie's managed MCP client so chat can use workspace file and process tools +- feat: add multi-identity daemon configuration, persona routing, an email channel, and webhook platform support +- feat: add durable task, session, message, and memory persistence +- feat: add memory synchronization, prefetch, context scrubbing, threat scanning, and built-in memory tools +- feat: add tool guardrails, classification, budgets, availability filtering, and disclosure controls +- feat: add feature-based YAML configuration with `conf.d` overlay loading +- feat: add typed secret-engine registration and Yaegi extension support +- fix: reject unknown slash commands locally instead of allowing the LLM to fabricate command behavior +- fix: publish Telegram commands to default, private-chat, and group-chat scopes so stale commands inherited with the bot token cannot shadow Archie's menu +- fix: drain the SDK's full event stream so streamed Telegram replies cannot deadlock +- fix: use standard newline-delimited JSON framing for MCP stdio clients +- fix: make MCP stdio shutdown and timeout handling race-safe +- fix: restore legacy `[forge].token_env` compatibility and required container environment passthrough +- fix: make the agent-container Docker network explicitly configurable + +### archie-agent + +- feat: add streamed agent execution with typed message events +- feat: add MCP client transports and managed tool-provider discovery +- feat: add memory context scrubbing and normalized memory tool schemas +- feat: add plugin metadata extraction from `metadata.archie.plugins` +- feat: add configurable container networking for daemon-launched runtimes +- fix: preserve valid UTF-8 when clipping runtime output +- fix: make MCP stdio lifecycle, retries, and timeout handling race-safe +- fix: enforce a zero-finding lint and vet baseline + +## [1.0.0] - 2026-07-22 + +### archied + +- feat: ship the resident forge-polling daemon, deterministic workflow engine, isolated worktrees, quality gates, Gitea integration, Docker/NATS worker split, plugin loading, and skills support +- feat: publish `archied` and `archie-agent` container images to the Gitea registry + +### archie-agent + +- feat: ship the isolated agent runtime, NATS RPC boundary, workflow execution, skills, and plugin support +- feat: publish the `archie-agent` container image to the Gitea registry diff --git a/Taskfile.yml b/Taskfile.yml index 7134b4e95..d059532cf 100644 --- a/Taskfile.yml +++ b/Taskfile.yml @@ -102,12 +102,14 @@ tasks: - go -C tools run -mod=readonly ./prdlint --repo-root .. news: - desc: Regenerate the news page and per-version release notes from the changelogs + desc: Regenerate the news page and per-version release notes from the changelog summary: | - Writes docs/news/releases.json and docs/news/. The JSON is the - canonical, host-neutral fact set every renderer reads; the markdown is - the MkDocs adapter. Both come from CHANGELOG.archied.md and - CHANGELOG.archie.md, so cutting a release adds no writing here. + Writes docs/news/releases.json, docs/news/redirects.json and docs/news/. + The JSON is the canonical, host-neutral fact set every renderer reads; + the redirect table maps the retired /news/// URLs to + the unified page for that version; the markdown is the MkDocs adapter. + All of it comes from CHANGELOG.md, so cutting a release adds no writing + here. The files are committed, so this dirties the tree deliberately: review the diff and commit it with the changelog that produced it. Never @@ -119,14 +121,15 @@ tasks: - go -C tools run -mod=readonly ./newsgen --repo-root .. news:check: - desc: Verify the committed release notes match the changelogs + desc: Verify the committed release notes match the changelog summary: | Derives the release notes in memory and fails when the committed files differ, without modifying the working tree. Runs in `task check`, so a changelog edit cannot land without its regeneration. - A file inside docs/news// that the generator does not produce - is a finding too: that directory is generated, and a hand-written page + A version page the generator does not produce (a page for a release the + changelog no longer carries, or one left in the retired + docs/news// layout) is a finding too; a hand-written news item belongs at the docs/news root instead. cmds: - go -C tools run -mod=readonly ./newsgen check --repo-root .. @@ -539,23 +542,23 @@ tasks: - go -C tools run ./contractaudit --repo-root .. release:preview: - desc: "Show the release notes that would be generated (VERSION=1.2.0, or GATEWAY=/RUNTIME= to version the two components separately)" + desc: "Show the release notes that would be generated (VERSION=1.2.0)" cmds: - - tools/release.sh --gateway {{.GATEWAY | default .VERSION}} --runtime {{.RUNTIME | default .VERSION}} --dry-run + - tools/release.sh --version {{.VERSION}} --dry-run requires: vars: [VERSION] release:prepare: - desc: "Write the generated notes into the changelogs, uncommitted, for editing (VERSION=1.2.0)" + desc: "Write the generated notes into CHANGELOG.md, uncommitted, for editing (VERSION=1.2.0)" cmds: - - tools/release.sh --gateway {{.GATEWAY | default .VERSION}} --runtime {{.RUNTIME | default .VERSION}} --prepare + - tools/release.sh --version {{.VERSION}} --prepare requires: vars: [VERSION] release: - desc: "Freeze the edited changelogs into a release commit and tags (VERSION=1.2.0). Run release:prepare first." + desc: "Freeze the edited changelog into a release commit and tag (VERSION=1.2.0). Run release:prepare first." cmds: - - tools/release.sh --gateway {{.GATEWAY | default .VERSION}} --runtime {{.RUNTIME | default .VERSION}} --tag + - tools/release.sh --version {{.VERSION}} --tag requires: vars: [VERSION] diff --git a/docs/architecture/configuration.md b/docs/architecture/configuration.md index fe7f27980..084dd7a75 100644 --- a/docs/architecture/configuration.md +++ b/docs/architecture/configuration.md @@ -202,7 +202,7 @@ decision; exact setting names are implementation details. | HTTP clients | feasibility notification timeout `10s`; other paths use `http.DefaultClient` | Adapter request policy. Every outbound client requires an explicit timeout profile. | | Workflow routing | labels `bug`, `feature`, `bootstrap`; workflows `tdd`, `feasibility`, `bootstrap`; fallback `implement` | Agent-system routing policy. Workflow identifiers are references, not compiled routing decisions. | | Filesystem/deployment | `.agents/skills`, `.archie/stages`, `.archie/gate.go`, `/data/worktree`, `/data/repo`, cache names/paths and prepared sentinel | Split into deployment settings, repository conventions, and genuine internal protocol markers. Paths an installation may relocate are settings. | -| Packaged release data | `/usr/share/archie/CHANGELOG.archied.md` and `/usr/share/archie/CHANGELOG.archie.md` | Packaging/deployment settings or paths derived from an installation prefix. | +| Packaged release data | `/usr/share/archie/CHANGELOG.md` | Packaging/deployment settings or paths derived from an installation prefix. | | Forge presentation | default label colour `bfd4f2` and state-label colours | Forge adapter presentation settings. | | Fallback system prompt | compiled fallback prompt | Agent-system default content, versioned and replaceable through its owning settings; safety constraints remain policy/code. | | Default paths and identities | config path, data paths, listen addresses, model roles and workflow names | Typed defaults belonging to their respective owners, never global constants consumed throughout the application. | diff --git a/docs/data/generated/dev-docs.json b/docs/data/generated/dev-docs.json index feedcd729..0a8d39231 100644 --- a/docs/data/generated/dev-docs.json +++ b/docs/data/generated/dev-docs.json @@ -28,7 +28,7 @@ "url": "/dev/architecture/configuration/", "title": "Configuration", "section": "Architecture", - "body": "# Configuration\n\n**Status:** Approved; existing-type assignment is ongoing \n**Date:** 2026-07-28 \n**Tracking issue:** [#73](https://github.com/samcharles93/archie-core/issues/73)\n\n## Ownership\n\nConfiguration has two separate responsibilities:\n\n1. `internal/infrastructure/configuration` loads files, environment variables,\n secret references, overlays, and compatibility representations.\n2. Each domain and plugin owns the typed runtime settings required for its\n behaviour.\n\n`internal/app` translates external input into those settings, validates\ncross-capability combinations, and supplies each component only its own\nsettings.\n\nThe following are prohibited:\n\n- passing complete application configuration into a domain;\n- making a domain depend on TOML, YAML, environment-variable names, secret\n references, or a configuration library;\n- defining a central runtime configuration type imported across the system;\n- placing plugin options in an unrelated global configuration model.\n\n## Private input document\n\n`internal/infrastructure/configuration` MAY use a complete decoded document\nwhile discovering files, decoding sections, and applying overlays. It is an\ninput-boundary DTO only.\n\nThe document:\n\n- remains private to the configuration infrastructure;\n- is composed from separately defined feature sections;\n- is immediately translated by application composition;\n- is never returned as the application's runtime model;\n- is never passed through runtime components.\n\nExternal DTOs and domain runtime settings are separate types.\n\nPlugins supply external configuration definitions through a narrow extension\ncontract. The core loader MUST NOT gain a field or recognized filename for every\nplugin.\n\nInvalid configuration input MUST NOT replace active valid settings or terminate\nunaffected capabilities. Configuration changes use the candidate validation,\npromotion, audit, and recovery requirements in\n[safe-change-and-recovery.md](/dev/architecture/safe-change-and-recovery/).\n\n## Dissolution of `internal/config`\n\n`internal/config` has no target location. It MUST be dissolved and MUST NOT\nsurvive as a shared package, configuration domain, or renamed global model.\n\nIts loading behaviour moves to `internal/infrastructure/configuration`. Existing\ntypes and methods are reassigned by behaviour. Repository execution policy,\ndispatch policy, retry policy, ecosystem defaults, tool policy, memory settings,\nindexing settings, provider settings, and channel settings move to their\nrespective owners.\n\n## Repository settings\n\nThe existing `config.Repo` MUST NOT move intact into a repository domain or\nshared settings package. A managed repository is an application association:\n\n- work intake owns which repository references an identity monitors;\n- task execution owns gates, preflight, test protection, ecosystem behaviour,\n and change limits;\n- task lifecycle owns retry behaviour;\n- scheduling owns concurrency policy;\n- workspace management owns base branch and persistent-storage requirements.\n\nApplication composition correlates these settings by repository reference. No\ndomain receives a universal repository profile.\n\n## Documentation\n\nGenerated configuration reference describes external sections and their owning\ncapabilities. It MUST NOT establish a global Go configuration structure as the\npublic contract.\n\n## Value classification rule\n\nEvery value that controls behaviour MUST have an explicit owner and MUST be\nclassified as exactly one of:\n\n1. **Invariant** — changing it changes the meaning of the program, a wire\n protocol, or a domain concept. It may be a Go constant.\n2. **Runtime setting** — an operator, identity, domain, plugin, or deployment\n may legitimately choose a different value. It is typed configuration owned by\n the affected capability.\n3. **Policy value** — it expresses what is allowed, limited, routed, retried,\n protected, or gated. Its typed definition belongs to the owning domain and it\n is evaluated through the policy system.\n4. **Derived value** — it is computed from other settings and is not\n independently mutable.\n5. **Runtime state** — it changes as the application operates, such as the\n active model for a conversation. It is changed by a domain command and is not\n configuration merely because it can be changed.\n\nAn unclassified behavioural literal is a defect.\n\n`const` MUST NOT be used merely because a value currently has one default.\nConstants are reserved for actual invariants: enum discriminants, protocol\nversions, fixed compatibility tokens, and values whose alteration would change\nthe program's semantics rather than configure an installation.\n\nIn Go, a constant is a compile-time value and does not represent mutable runtime\nstorage. It generally has no address that can be observed or changed.\nArchitecturally, a constant therefore asserts that the value cannot change for\nthe lifetime of the application. Any value that may legitimately change while\nthe application is running, between application instances, or between\ndeployments is not a constant.\n\nA runtime setting may have a default, but the default is not its only access\npath. The owner exposes a typed settings structure, validation, and a\n`DefaultSettings` constructor or equivalent. Private constants used to implement\ndefaults do not turn those defaults into invariants and MUST NOT be consumed\ndirectly by runtime code.\n\nEach runtime setting and policy value MUST declare:\n\n- its owner;\n- type, units, validation constraints, and safe bounds;\n- default and derivation, if any;\n- whether it is startup-only, live-reloadable, or restart-required;\n- whether it may differ by installation, identity, repository, workflow,\n channel, or plugin instance;\n- whether it is secret, sensitive, or safe to report;\n- its current source, effective value, version, and last-known-good version;\n- the command and identity required to change it.\n\n## Current configuration migration ledger\n\nThis ledger records the current meanings hidden inside `internal/config`. It is\nthe source inventory for dissolving that package; rows are split where the\nexisting structure combines different owners.\n\n| Current values | Current location | Target owner and requirement |\n| ----------------------------------------------------------------------------------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `WorkDir`, `DBPath` | root `Config` | Workspace/storage infrastructure settings. `DBPath` is the prefix for independent task and conversation SQLite files. Defaults derive from the platform data directory. |\n| `SkillsDir`, `PluginDir` | root `Config` | Skill and plugin infrastructure settings, independently typed. |\n| `PollInterval` | root `Config` | Work-intake scheduling setting; not a daemon-wide constant. |\n| `Label`, `BotUser`, `BotEmail` | root `Config` | Identity and dispatch associations. `BotEmail` may be derived from the selected forge account but remains overrideable. |\n| `MaxRetries` | root `Config`, `Repo` | Retry policy owned by the operation being retried. The duplicate global/repository representation must disappear. |\n| `DiffCapLines` | root `Config` | Agent-change policy value. |\n| `MaxSteps`, `WallClock`, `GateMaxFailures` | `Budgets` | Workflow-execution policy, with units and zero/unlimited semantics made explicit. |\n| `Class`, `APIKeyEnv`, `BaseURL` | `Provider` | Provider instance settings. Secret lookup becomes a `SecretRef`, not an environment variable name leaking into the provider domain. |\n| `Mode`, `Command`, `Env` | `LegacyAgent` | Decode-only compatibility input for the removed executor selector. Delete after the config migration window; it has no runtime settings owner. |\n| `Type`, `Host`, `Token` / `TokenEnv` (older form) | `Forge` | Forge adapter settings. The older `TokenEnv` input is accepted only at the loader boundary. |\n| `Trigger`, `AckReaction`, label names | `Dispatch` | Work-intake and forge presentation policy. Label vocabulary is configurable per forge/identity association. |\n| `Engine` | `MemoryConfig` | Memory engine selection. `internal/domain/memory` is the only engine family; per-engine settings remain owned and validated by that engine. |\n| `Name`, `Transport`, `Command`, `Args`, `WorkDir`, `URL` | `MCPServer` | One typed MCP server instance specification. Transport-specific variants must reject fields belonging to other variants. |\n| `MaxResultChars` | `ToolPolicy` | Tool-execution policy values, not generic daemon configuration. |\n| `URL`, `TokenEnv` | `NATSConfig` | NATS transport settings with a secret reference replacing the environment-name field. |\n| `Image`, `MaxConcurrency`, `MaxUptime`, `VolumeTTL`, `PullPolicy`, `Network` | `ContainerConfig` | Mandatory managed-worker infrastructure settings and resource policy. The legacy `enabled` input is decode-only. |\n| model mappings, email, webhook, Telegram | `ChatConfig` | Separate channel instance settings plus channel-routing associations; there is no chat-wide settings owner. |\n| `AllowedUserIDs`, `Token` / `TokenEnv` (older form), update commands | Telegram config | Telegram adapter settings and access policy. `Token` is the preferred `secret.SecretRef`; `TokenEnv` remains a backwards-compatible fallback. |\n| listen/relay addresses | email config | Email adapter instance settings. |\n| webhook target | `Notify` | Notification adapter instance settings. |\n| web listen address | `Web` | Web transport settings. |\n| `listen` under `[services.state]` and `[services.gateway]` | `ServiceConnection` | The bind address of the process that owns the service. Read only by that process, and defaulted to the address its clients dial so the pair cannot drift. |\n| index directory and database path | `Indexing` | Index infrastructure settings, derived from storage settings unless explicitly overridden. |\n| forge, dispatch, models, providers, containers, memory, tools, indexing and repositories | `IdentityConfig` | Existing composite duplicates unrelated settings. Replace it with associations from an `IdentityID` to independently owned configured instances. |\n| owner, name, base, gate, protection, ecosystem, preflight, storage, retry and concurrency | `Repo` | Split across work intake, workspace, workflow execution, policy, gate, and scheduling as described in Repository settings. |\n| `TaskConfig`, `TaskForge` | worker snapshot | Replace with the minimum immutable, versioned WorkflowExecution input assembled by the application. It is not a second configuration model. |\n| `Extra` and arbitrary maps | root/provider config | Allowed only at an extension boundary whose owning plugin/provider supplies schema and validation. Core configuration never consumes an untyped catch-all. |\n\n## Behavioural literals and incorrectly fixed values\n\nThe following current values affect useful behaviour but are not represented as\nowned typed settings or policy. They MUST be classified and migrated before the\nold configuration package is removed. The listed target is the architectural\ndecision; exact setting names are implementation details.\n\n| Capability | Values fixed in current code | Required classification |\n| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Chat agent | maximum steps `8` in `cmd/archied` | Workflow/chat execution policy. |\n| Context compression | enabled, threshold `0.5`, context size `128000`, protect first `3` and last `20`, compression marker, token estimate of four characters per token | Model/context runtime settings. The marker is presentation; the estimate is provider/model strategy, not a universal truth. |\n| Tool guardrails | escalation thresholds `3`, `5`, `10`, `2` | Tool-use policy with named meanings and bounded defaults. |\n| Tool output | per-result cap `50000` characters, no aggregate turn cap, preview `500` characters | Tool-execution resource and presentation settings. Per-result spill/truncation remains; turn continuation is not character- or token-gated. |\n| Pairing/access | code TTL `1h`, maximum pending `3`, rate window `10m`, failures `5`, lockout `1h`, maximum lockout `24h` | Access policy. Code length/alphabet and salt length require an explicit security-constraint decision; they are not automatically valid constants. |\n| NATS daemon consumer | stream `ARCHIE_TASKS`, consumer `archie-daemon`, deduplication `2m`, poll `2s`, deliveries `3`, acknowledgement wait `5m`, inactive threshold `24h`, subjects | NATS topology settings plus delivery policy. Subject grammar or protocol headers may be invariants only if declared as versioned wire contracts. |\n| NATS worker consumer | stream `ARCHIE_TASKS`, consumer `archie-agent`, deduplication `2m`, poll `5s`, acknowledgement wait `30m`, deliveries `3`, inactive threshold `24h`, queue group and retry delay `1s` | Worker transport settings and delivery/retry policy. Shared stream defaults must have one owner rather than two copies. |\n| Worker readiness | readiness timeout `20s`, retry delay `250ms` | Worker lifecycle and retry policy. |\n| Execution/RPC | agent execution `30m`, task-run RPC `60s`, worktree RPC `15m` | Per-operation timeout policy. |\n| Indexing | build timeout `10m`, metadata timeout `5s` | Index operation policy. |\n| Plugin/tool cleanup | plugin rollback `10s`, tool-provider cleanup `10s`, MCP-provider cleanup `10s` | Lifecycle shutdown/rollback policy owned by each engine, with a shared policy vocabulary where appropriate. |\n| Memory read path | per-scope record limit `20`, rendered `\u003cmemory\u003e` block byte cap `8192` | Memory read policy owned by the engine family (`internal/domain/memory`). |\n| Built-in memory store | per-file size limit `100KiB`, query result limit `100` | Split into memory resource policy, input policy, and presentation settings. |\n| Memory safety scanner | compiled prompt-injection and sensitive-data patterns with fixed warn/block consequences | Versioned memory-domain policy definitions. Patterns and consequences must be inspectable and replaceable without editing scanner code. |\n| MCP stdio | initial backoff `500ms`, maximum backoff `30s`, unlimited default retries, send and shutdown `5s` | MCP transport retry, request, and lifecycle policy. Unlimited retries must be explicit rather than a zero-value accident. |\n| MCP SSE/HTTP | reconnect `1s` to `30s`, POST/request timeout `30s` | MCP transport settings and retry policy. |\n| Message framing | MCP frame `4MiB`, worker protocol frame `8MiB`, diagnostic `64KiB`, media/base64 `64MiB` | Resource/security policy unless a published wire protocol mandates the limit. Limits must be configurable only within safe bounds. |\n| Webhooks and web UI | webhook bind `0.0.0.0:8644`, webhook shutdown `5s`, web read-header `5s`, web shutdown `2s` | Transport instance and lifecycle settings. |\n| Telegram | typing refresh `4s`, draft interval `700ms`, update-action TTL `10m` | Telegram adapter presentation and lifecycle settings. |\n| Telegram limits | message length `4000` and callback/update prefixes | Record the upstream platform constraint and version it as an adapter compatibility limit; prefixes may remain wire constants when changing them would invalidate outstanding callbacks. |\n| Containers | stop and pull timeouts `10s` and `30s` | Container lifecycle policy. |\n| HTTP clients | feasibility notification timeout `10s`; other paths use `http.DefaultClient` | Adapter request policy. Every outbound client requires an explicit timeout profile. |\n| Workflow routing | labels `bug`, `feature`, `bootstrap`; workflows `tdd`, `feasibility`, `bootstrap`; fallback `implement` | Agent-system routing policy. Workflow identifiers are references, not compiled routing decisions. |\n| Filesystem/deployment | `.agents/skills`, `.archie/stages`, `.archie/gate.go`, `/data/worktree`, `/data/repo`, cache names/paths and prepared sentinel | Split into deployment settings, repository conventions, and genuine internal protocol markers. Paths an installation may relocate are settings. |\n| Packaged release data | `/usr/share/archie/CHANGELOG.archied.md` and `/usr/share/archie/CHANGELOG.archie.md` | Packaging/deployment settings or paths derived from an installation prefix. |\n| Forge presentation | default label colour `bfd4f2` and state-label colours | Forge adapter presentation settings. |\n| Fallback system prompt | compiled fallback prompt | Agent-system default content, versioned and replaceable through its owning settings; safety constraints remain policy/code. |\n| Default paths and identities | config path, data paths, listen addresses, model roles and workflow names | Typed defaults belonging to their respective owners, never global constants consumed throughout the application. |\n\nThis inventory is intentionally broader than exported Go `const` declarations. A\nliteral hidden in a constructor, timeout, switch, retry loop, path join, prompt,\nlabel map, or client setup restricts behaviour just as effectively as an\nincorrectly used constant.\n\n## Constants that may remain\n\nA value may remain constant only when its owner documents why runtime variation\nwould be invalid. Typical valid cases are:\n\n- domain enum values and state names;\n- a versioned wire-protocol version or framing token;\n- reserved internal headers and callback prefixes that peers must interpret\n identically;\n- compile-time mathematical relationships;\n- sentinel errors and internal type identifiers.\n\nNames such as a stream, consumer, label, workflow, file, directory, network,\nmodel role, timeout, retry count, capacity, size limit, colour, prompt, command,\nor executable are not invariants merely because the current application has only\none of them.\n\nArchitecture tests SHOULD reject exported behavioural constants outside approved\ninvariant packages and SHOULD detect direct consumption of private default\nconstants outside their owning `DefaultSettings` construction.\n\n## Current mutation and reload ledger\n\nThe application currently changes behavioural values through unrelated paths:\n\n| Current change seam | Current behaviour | Required target |\n| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Telegram `/restart` in `cmd/archied` | Re-reads the global document and directly replaces Telegram token and allowed-user IDs; failure retains old values. | Submit a Telegram-settings candidate through the universal change protocol. Validate the complete candidate, promote atomically, audit the acting identity, and retain last-known-good. |\n| Active model selection | `chatModelManager.SetActiveModel` changes a model reference. | A conversation/session command changing runtime state. Validate against configured model instances and audit it; do not rewrite configuration. |\n| Active provider selection | `chatModelManager.SetActiveProvider` changes provider selection. | A conversation/session command changing runtime state, with the same distinction from provider-instance configuration. |\n| Persona selection | `PersonaRegistry.SetActive` mutates an in-memory per-session choice. | Agent-system session state. Persistence and audit requirements are owned by that domain, not the configuration loader. |\n| File and environment overlays | Applied while loading `internal/config`; defaults are filled by mutation in `finalize`. | Configuration-infrastructure input processing that produces separately typed candidates. Defaults and derivations remain visible in provenance. |\n| SIGHUP config reload (2026-08) | Re-resolves the file config, re-applies the database layer over it, validates, then atomically republishes through `config.Holder`. A failed reload, whether the file or the control plane caused it, keeps the running config and records `last_error`/`last_error_at` in `/api/config`. | Candidate promotion with last-known-good retention: the running snapshot is untouched on failure. A bounded observation period and actor audit are not yet implemented. |\n| Control-plane resource command (2026-09) | `ControlPlaneService.Command` validates a whole resource document against its owning feature, then writes it with an audit record (actor, source, request ID, expected version) under optimistic concurrency. Hosted on the State Store's gRPC server; the Web UI and messaging channels are its only clients. See `docs/prds/runtime-control-plane.md`. | Met for validate-stage-promote, actor audit and versioned history. Per-field health observation and validate-before-switch on live apply are not yet implemented. |\n\nAny further mutation seam discovered during migration MUST be added here before\nit is changed. Direct field assignment on a live settings object is prohibited.\n\n## Universal change protocol\n\nChanging configuration is an application command performed by an identity. It\nMUST:\n\n1. resolve the target owner and current version;\n2. parse into that owner's typed settings;\n3. validate syntax, semantic constraints, policy, references, and safe bounds;\n4. stage a candidate without altering the active value;\n5. run owner-defined readiness and health checks;\n6. atomically promote the candidate and record actor, source, reason, diff,\n prior version, and new version;\n7. observe the affected capability for a bounded period;\n8. retain the new version on success, or automatically restore last-known-good\n on failure;\n9. report the rejected or rolled-back candidate without terminating unaffected\n capabilities.\n\nStartup loading uses the same candidate rules. A bad user value therefore does\nnot partially mutate the application or make a previously healthy capability\nunavailable.\n\nSettings that cannot safely reload in-process are marked restart-required. The\nchange may still be validated and versioned immediately, but promotion occurs\nthrough a controlled restart with the same health and rollback semantics.\n\n## Implemented runtime reload and settings writes (2026-09)\n\nTwo mechanisms change behavioural values at runtime: SIGHUP re-reads the file\nconfig, and the control plane owns every database-backed setting. The dashboard\nruntime overlay that used to sit between them was deleted once the control plane\ncovered its surface; `-config-overlay` names a file overlay and is unrelated.\n\n### Published snapshot: `config.Holder`\n\nThe running configuration is a published snapshot held in `config.Holder`\n(`internal/config/holder.go`). Get returns a value under RLock; Set replaces the\nwhole snapshot. A published Config is immutable: reload constructs a fresh one\nand calls Set. `config.Clone` deep-copies every reference-type field so a failed\ndecode cannot mutate the published snapshot's shared maps. `Holder.Get` panics\non a nil receiver — a forgotten `NewHolder` must fail loudly, not boot a daemon\nthat silently runs on an empty config.\n\n### The reloadable-field criterion\n\nThe diff-and-warn on reload asks whether a changed field takes effect without a\nrestart. The criterion is: **a field is reloadable when every consumer re-reads\nit.** That question read as \"what does the daemon re-read\" while the daemon owned\nthe only Holder; it stopped being sufficient when webui began sharing that\nHolder, because webui handlers re-read on every request. The allowlist lives in\n`cmd/archied/reload.go` and is deliberately a deny-by-default list: a field added\nto Config later defaults to requires-restart, forcing whoever adds it to decide\ndeliberately. A reload that changes any non-allowlisted field logs\n\"requires a restart\" with the field names; a fully-applied reload logs Info.\n\n### SIGHUP reload\n\nSIGHUP re-resolves the file config, re-applies the database layer over it\n(`boot.runtimeConfig`, the same call boot makes), validates, and atomically\nrepublishes through the shared Holder. A failed reload keeps the running config\nand records `last_error`/`last_error_at` in `/api/config` so the stale state is\nvisible where the operator is looking. The three poll tickers re-read\n`PollInterval` per iteration and reset on change, so a reloaded interval\ngenuinely takes effect.\n\n### Settings writes go through the control plane\n\nDatabase-backed settings are read and written through\n`ControlPlaneService` on the State Store's gRPC server: catalog, query,\ncommand, watch. Each feature owns its resource's validation and commands;\nstorage writes versions and audit records only. `docs/prds/runtime-control-plane.md`\nis the specification.\n\nTwo properties matter to anyone changing this area:\n\n- **Bootstrap stays file-owned.** The daemon reads the file config first and\n layers database resources over it at boot (`boot.loadRuntimeConfig`). Values\n the daemon needs before it can reach the State Store — the database path,\n listen addresses, credentials — stay file-only by design.\n- **Reload re-reads them.** SIGHUP resolves the file document and then runs the\n same `boot.runtimeConfig` layering boot does, so a reload cannot revert a\n database-owned setting to its file value. A control plane that cannot answer\n fails the reload rather than publishing the file's values over the running\n ones. Workflow execution budgets arrive on a watch rather than in a resource\n query, so boot records the last published settings and the reload re-applies\n them from there.\n\n## Completion criteria\n\nThe configuration rearchitecture is complete only when:\n\n- `internal/config` no longer exists;\n- every behavioural value has one classification and owner;\n- every current field and hard-coded value in the ledgers has a recorded\n disposition;\n- domains and plugins receive only their typed settings;\n- all changes use semantic commands and the universal change protocol;\n- active, candidate, rejected, rolled-back, and last-known-good versions are\n queryable with secret-safe provenance;\n- generated documentation lists every external key, default, constraint,\n mutability class, owner, and deprecation;\n- architecture tests prevent a new central runtime configuration model, direct\n live-setting mutation, and incorrectly fixed behavioural values.\n\n## Startup policy: missing credential degrades, invalid config is fatal\n\nDecided 2026-07-30. Recovered 2026-08-09 from the pre-migration issue tracker.\n\nA missing **credential** disables a capability. Only an **invalid config** stops\nthe daemon. \"Forge is a feature, not a requirement.\"\n\nBefore `518a1a0`, an unresolvable forge token did `return 1` in\n`cmd/archied/main.go`, so a chat-only user who never configured GitHub got no\nchat, no gateway, nothing — and under a systemd unit with `Restart=on-failure`\nand no start limit it crash-looped every five seconds with the error scrolling\npast unread. Forge construction now lives in `resolveForge`, shared by the\nprimary forge and every configured identity, and degrades to `forge.NewNoop`\nwith a warning. The identity path had the same defect and was worse: one\nidentity's missing credential killed all the others.\n\nMalformed configuration still fails fast in `configuration.Validate`, well\nbefore this point. That distinction is the whole design.\n\nApply the same reasoning to any future capability credential, LLM keys\nespecially: start, report the capability as unavailable, let the operator see it.\nGuarded by `TestResolveForgeDegradesInsteadOfFailing`.\n\n**Known consequence, tracked separately:** `worktree.Manager` still receives the\nempty token, so pushes fail late rather than at startup.\n\n## Config generation belongs to `archied setup`, not `install.sh`\n\nDecided 2026-07-30 ([#368](https://github.com/samcharles93/archie-core/issues/368)).\nRecovered 2026-08-09 from the pre-migration issue tracker.\n\n`install.sh` must stop generating `config.toml`; `archied setup` owns it. The\ninstaller hand-rolling TOML has already drifted from the schema once: the\ngenerated-config branch hardcoded `key = ARCHIE_GITHUB_TOKEN` and\n`host = ${GITEA_URL}` regardless of the answers given, so choosing Gitea produced\na config naming a token the installer never wrote (archied then exited 1), and\nchoosing GitHub pointed `host` at `gitea.example.com`. `61a5b35` patched this\nwith a `forge_block` shell helper shared by both config paths — that helper is a\n**workaround**, deleted by\n[#72](https://github.com/samcharles93/archie-core/issues/72). The durable fix is\nthat the code writing the config is the code that reads it.\n\nWhy Go and not Python: the installer must run where nothing is installed yet, and\n`python3` with `tomllib` means 3.11+, which is not safe on LTS distros. `archied`\nis already being built two steps earlier.\n\n**Key constraint for the port:** `BurntSushi/toml` does **not** survive a\ndecode/encode round trip with comments intact, and `config.example.toml` carries\ndocumentation users are meant to hand-edit. Decide the write strategy\n([#412](https://github.com/samcharles93/archie-core/issues/412)) before writing\nany prompting code. Do not port a separate `config.yaml`/`auth.yaml` secret\nsplit — Archie already has `secret.SecretRef{engine,key}`, so setup writes the\nreference to TOML and the value to the secret engine.\n" + "body": "# Configuration\n\n**Status:** Approved; existing-type assignment is ongoing \n**Date:** 2026-07-28 \n**Tracking issue:** [#73](https://github.com/samcharles93/archie-core/issues/73)\n\n## Ownership\n\nConfiguration has two separate responsibilities:\n\n1. `internal/infrastructure/configuration` loads files, environment variables,\n secret references, overlays, and compatibility representations.\n2. Each domain and plugin owns the typed runtime settings required for its\n behaviour.\n\n`internal/app` translates external input into those settings, validates\ncross-capability combinations, and supplies each component only its own\nsettings.\n\nThe following are prohibited:\n\n- passing complete application configuration into a domain;\n- making a domain depend on TOML, YAML, environment-variable names, secret\n references, or a configuration library;\n- defining a central runtime configuration type imported across the system;\n- placing plugin options in an unrelated global configuration model.\n\n## Private input document\n\n`internal/infrastructure/configuration` MAY use a complete decoded document\nwhile discovering files, decoding sections, and applying overlays. It is an\ninput-boundary DTO only.\n\nThe document:\n\n- remains private to the configuration infrastructure;\n- is composed from separately defined feature sections;\n- is immediately translated by application composition;\n- is never returned as the application's runtime model;\n- is never passed through runtime components.\n\nExternal DTOs and domain runtime settings are separate types.\n\nPlugins supply external configuration definitions through a narrow extension\ncontract. The core loader MUST NOT gain a field or recognized filename for every\nplugin.\n\nInvalid configuration input MUST NOT replace active valid settings or terminate\nunaffected capabilities. Configuration changes use the candidate validation,\npromotion, audit, and recovery requirements in\n[safe-change-and-recovery.md](/dev/architecture/safe-change-and-recovery/).\n\n## Dissolution of `internal/config`\n\n`internal/config` has no target location. It MUST be dissolved and MUST NOT\nsurvive as a shared package, configuration domain, or renamed global model.\n\nIts loading behaviour moves to `internal/infrastructure/configuration`. Existing\ntypes and methods are reassigned by behaviour. Repository execution policy,\ndispatch policy, retry policy, ecosystem defaults, tool policy, memory settings,\nindexing settings, provider settings, and channel settings move to their\nrespective owners.\n\n## Repository settings\n\nThe existing `config.Repo` MUST NOT move intact into a repository domain or\nshared settings package. A managed repository is an application association:\n\n- work intake owns which repository references an identity monitors;\n- task execution owns gates, preflight, test protection, ecosystem behaviour,\n and change limits;\n- task lifecycle owns retry behaviour;\n- scheduling owns concurrency policy;\n- workspace management owns base branch and persistent-storage requirements.\n\nApplication composition correlates these settings by repository reference. No\ndomain receives a universal repository profile.\n\n## Documentation\n\nGenerated configuration reference describes external sections and their owning\ncapabilities. It MUST NOT establish a global Go configuration structure as the\npublic contract.\n\n## Value classification rule\n\nEvery value that controls behaviour MUST have an explicit owner and MUST be\nclassified as exactly one of:\n\n1. **Invariant** — changing it changes the meaning of the program, a wire\n protocol, or a domain concept. It may be a Go constant.\n2. **Runtime setting** — an operator, identity, domain, plugin, or deployment\n may legitimately choose a different value. It is typed configuration owned by\n the affected capability.\n3. **Policy value** — it expresses what is allowed, limited, routed, retried,\n protected, or gated. Its typed definition belongs to the owning domain and it\n is evaluated through the policy system.\n4. **Derived value** — it is computed from other settings and is not\n independently mutable.\n5. **Runtime state** — it changes as the application operates, such as the\n active model for a conversation. It is changed by a domain command and is not\n configuration merely because it can be changed.\n\nAn unclassified behavioural literal is a defect.\n\n`const` MUST NOT be used merely because a value currently has one default.\nConstants are reserved for actual invariants: enum discriminants, protocol\nversions, fixed compatibility tokens, and values whose alteration would change\nthe program's semantics rather than configure an installation.\n\nIn Go, a constant is a compile-time value and does not represent mutable runtime\nstorage. It generally has no address that can be observed or changed.\nArchitecturally, a constant therefore asserts that the value cannot change for\nthe lifetime of the application. Any value that may legitimately change while\nthe application is running, between application instances, or between\ndeployments is not a constant.\n\nA runtime setting may have a default, but the default is not its only access\npath. The owner exposes a typed settings structure, validation, and a\n`DefaultSettings` constructor or equivalent. Private constants used to implement\ndefaults do not turn those defaults into invariants and MUST NOT be consumed\ndirectly by runtime code.\n\nEach runtime setting and policy value MUST declare:\n\n- its owner;\n- type, units, validation constraints, and safe bounds;\n- default and derivation, if any;\n- whether it is startup-only, live-reloadable, or restart-required;\n- whether it may differ by installation, identity, repository, workflow,\n channel, or plugin instance;\n- whether it is secret, sensitive, or safe to report;\n- its current source, effective value, version, and last-known-good version;\n- the command and identity required to change it.\n\n## Current configuration migration ledger\n\nThis ledger records the current meanings hidden inside `internal/config`. It is\nthe source inventory for dissolving that package; rows are split where the\nexisting structure combines different owners.\n\n| Current values | Current location | Target owner and requirement |\n| ----------------------------------------------------------------------------------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `WorkDir`, `DBPath` | root `Config` | Workspace/storage infrastructure settings. `DBPath` is the prefix for independent task and conversation SQLite files. Defaults derive from the platform data directory. |\n| `SkillsDir`, `PluginDir` | root `Config` | Skill and plugin infrastructure settings, independently typed. |\n| `PollInterval` | root `Config` | Work-intake scheduling setting; not a daemon-wide constant. |\n| `Label`, `BotUser`, `BotEmail` | root `Config` | Identity and dispatch associations. `BotEmail` may be derived from the selected forge account but remains overrideable. |\n| `MaxRetries` | root `Config`, `Repo` | Retry policy owned by the operation being retried. The duplicate global/repository representation must disappear. |\n| `DiffCapLines` | root `Config` | Agent-change policy value. |\n| `MaxSteps`, `WallClock`, `GateMaxFailures` | `Budgets` | Workflow-execution policy, with units and zero/unlimited semantics made explicit. |\n| `Class`, `APIKeyEnv`, `BaseURL` | `Provider` | Provider instance settings. Secret lookup becomes a `SecretRef`, not an environment variable name leaking into the provider domain. |\n| `Mode`, `Command`, `Env` | `LegacyAgent` | Decode-only compatibility input for the removed executor selector. Delete after the config migration window; it has no runtime settings owner. |\n| `Type`, `Host`, `Token` / `TokenEnv` (older form) | `Forge` | Forge adapter settings. The older `TokenEnv` input is accepted only at the loader boundary. |\n| `Trigger`, `AckReaction`, label names | `Dispatch` | Work-intake and forge presentation policy. Label vocabulary is configurable per forge/identity association. |\n| `Engine` | `MemoryConfig` | Memory engine selection. `internal/domain/memory` is the only engine family; per-engine settings remain owned and validated by that engine. |\n| `Name`, `Transport`, `Command`, `Args`, `WorkDir`, `URL` | `MCPServer` | One typed MCP server instance specification. Transport-specific variants must reject fields belonging to other variants. |\n| `MaxResultChars` | `ToolPolicy` | Tool-execution policy values, not generic daemon configuration. |\n| `URL`, `TokenEnv` | `NATSConfig` | NATS transport settings with a secret reference replacing the environment-name field. |\n| `Image`, `MaxConcurrency`, `MaxUptime`, `VolumeTTL`, `PullPolicy`, `Network` | `ContainerConfig` | Mandatory managed-worker infrastructure settings and resource policy. The legacy `enabled` input is decode-only. |\n| model mappings, email, webhook, Telegram | `ChatConfig` | Separate channel instance settings plus channel-routing associations; there is no chat-wide settings owner. |\n| `AllowedUserIDs`, `Token` / `TokenEnv` (older form), update commands | Telegram config | Telegram adapter settings and access policy. `Token` is the preferred `secret.SecretRef`; `TokenEnv` remains a backwards-compatible fallback. |\n| listen/relay addresses | email config | Email adapter instance settings. |\n| webhook target | `Notify` | Notification adapter instance settings. |\n| web listen address | `Web` | Web transport settings. |\n| `listen` under `[services.state]` and `[services.gateway]` | `ServiceConnection` | The bind address of the process that owns the service. Read only by that process, and defaulted to the address its clients dial so the pair cannot drift. |\n| index directory and database path | `Indexing` | Index infrastructure settings, derived from storage settings unless explicitly overridden. |\n| forge, dispatch, models, providers, containers, memory, tools, indexing and repositories | `IdentityConfig` | Existing composite duplicates unrelated settings. Replace it with associations from an `IdentityID` to independently owned configured instances. |\n| owner, name, base, gate, protection, ecosystem, preflight, storage, retry and concurrency | `Repo` | Split across work intake, workspace, workflow execution, policy, gate, and scheduling as described in Repository settings. |\n| `TaskConfig`, `TaskForge` | worker snapshot | Replace with the minimum immutable, versioned WorkflowExecution input assembled by the application. It is not a second configuration model. |\n| `Extra` and arbitrary maps | root/provider config | Allowed only at an extension boundary whose owning plugin/provider supplies schema and validation. Core configuration never consumes an untyped catch-all. |\n\n## Behavioural literals and incorrectly fixed values\n\nThe following current values affect useful behaviour but are not represented as\nowned typed settings or policy. They MUST be classified and migrated before the\nold configuration package is removed. The listed target is the architectural\ndecision; exact setting names are implementation details.\n\n| Capability | Values fixed in current code | Required classification |\n| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Chat agent | maximum steps `8` in `cmd/archied` | Workflow/chat execution policy. |\n| Context compression | enabled, threshold `0.5`, context size `128000`, protect first `3` and last `20`, compression marker, token estimate of four characters per token | Model/context runtime settings. The marker is presentation; the estimate is provider/model strategy, not a universal truth. |\n| Tool guardrails | escalation thresholds `3`, `5`, `10`, `2` | Tool-use policy with named meanings and bounded defaults. |\n| Tool output | per-result cap `50000` characters, no aggregate turn cap, preview `500` characters | Tool-execution resource and presentation settings. Per-result spill/truncation remains; turn continuation is not character- or token-gated. |\n| Pairing/access | code TTL `1h`, maximum pending `3`, rate window `10m`, failures `5`, lockout `1h`, maximum lockout `24h` | Access policy. Code length/alphabet and salt length require an explicit security-constraint decision; they are not automatically valid constants. |\n| NATS daemon consumer | stream `ARCHIE_TASKS`, consumer `archie-daemon`, deduplication `2m`, poll `2s`, deliveries `3`, acknowledgement wait `5m`, inactive threshold `24h`, subjects | NATS topology settings plus delivery policy. Subject grammar or protocol headers may be invariants only if declared as versioned wire contracts. |\n| NATS worker consumer | stream `ARCHIE_TASKS`, consumer `archie-agent`, deduplication `2m`, poll `5s`, acknowledgement wait `30m`, deliveries `3`, inactive threshold `24h`, queue group and retry delay `1s` | Worker transport settings and delivery/retry policy. Shared stream defaults must have one owner rather than two copies. |\n| Worker readiness | readiness timeout `20s`, retry delay `250ms` | Worker lifecycle and retry policy. |\n| Execution/RPC | agent execution `30m`, task-run RPC `60s`, worktree RPC `15m` | Per-operation timeout policy. |\n| Indexing | build timeout `10m`, metadata timeout `5s` | Index operation policy. |\n| Plugin/tool cleanup | plugin rollback `10s`, tool-provider cleanup `10s`, MCP-provider cleanup `10s` | Lifecycle shutdown/rollback policy owned by each engine, with a shared policy vocabulary where appropriate. |\n| Memory read path | per-scope record limit `20`, rendered `\u003cmemory\u003e` block byte cap `8192` | Memory read policy owned by the engine family (`internal/domain/memory`). |\n| Built-in memory store | per-file size limit `100KiB`, query result limit `100` | Split into memory resource policy, input policy, and presentation settings. |\n| Memory safety scanner | compiled prompt-injection and sensitive-data patterns with fixed warn/block consequences | Versioned memory-domain policy definitions. Patterns and consequences must be inspectable and replaceable without editing scanner code. |\n| MCP stdio | initial backoff `500ms`, maximum backoff `30s`, unlimited default retries, send and shutdown `5s` | MCP transport retry, request, and lifecycle policy. Unlimited retries must be explicit rather than a zero-value accident. |\n| MCP SSE/HTTP | reconnect `1s` to `30s`, POST/request timeout `30s` | MCP transport settings and retry policy. |\n| Message framing | MCP frame `4MiB`, worker protocol frame `8MiB`, diagnostic `64KiB`, media/base64 `64MiB` | Resource/security policy unless a published wire protocol mandates the limit. Limits must be configurable only within safe bounds. |\n| Webhooks and web UI | webhook bind `0.0.0.0:8644`, webhook shutdown `5s`, web read-header `5s`, web shutdown `2s` | Transport instance and lifecycle settings. |\n| Telegram | typing refresh `4s`, draft interval `700ms`, update-action TTL `10m` | Telegram adapter presentation and lifecycle settings. |\n| Telegram limits | message length `4000` and callback/update prefixes | Record the upstream platform constraint and version it as an adapter compatibility limit; prefixes may remain wire constants when changing them would invalidate outstanding callbacks. |\n| Containers | stop and pull timeouts `10s` and `30s` | Container lifecycle policy. |\n| HTTP clients | feasibility notification timeout `10s`; other paths use `http.DefaultClient` | Adapter request policy. Every outbound client requires an explicit timeout profile. |\n| Workflow routing | labels `bug`, `feature`, `bootstrap`; workflows `tdd`, `feasibility`, `bootstrap`; fallback `implement` | Agent-system routing policy. Workflow identifiers are references, not compiled routing decisions. |\n| Filesystem/deployment | `.agents/skills`, `.archie/stages`, `.archie/gate.go`, `/data/worktree`, `/data/repo`, cache names/paths and prepared sentinel | Split into deployment settings, repository conventions, and genuine internal protocol markers. Paths an installation may relocate are settings. |\n| Packaged release data | `/usr/share/archie/CHANGELOG.md` | Packaging/deployment settings or paths derived from an installation prefix. |\n| Forge presentation | default label colour `bfd4f2` and state-label colours | Forge adapter presentation settings. |\n| Fallback system prompt | compiled fallback prompt | Agent-system default content, versioned and replaceable through its owning settings; safety constraints remain policy/code. |\n| Default paths and identities | config path, data paths, listen addresses, model roles and workflow names | Typed defaults belonging to their respective owners, never global constants consumed throughout the application. |\n\nThis inventory is intentionally broader than exported Go `const` declarations. A\nliteral hidden in a constructor, timeout, switch, retry loop, path join, prompt,\nlabel map, or client setup restricts behaviour just as effectively as an\nincorrectly used constant.\n\n## Constants that may remain\n\nA value may remain constant only when its owner documents why runtime variation\nwould be invalid. Typical valid cases are:\n\n- domain enum values and state names;\n- a versioned wire-protocol version or framing token;\n- reserved internal headers and callback prefixes that peers must interpret\n identically;\n- compile-time mathematical relationships;\n- sentinel errors and internal type identifiers.\n\nNames such as a stream, consumer, label, workflow, file, directory, network,\nmodel role, timeout, retry count, capacity, size limit, colour, prompt, command,\nor executable are not invariants merely because the current application has only\none of them.\n\nArchitecture tests SHOULD reject exported behavioural constants outside approved\ninvariant packages and SHOULD detect direct consumption of private default\nconstants outside their owning `DefaultSettings` construction.\n\n## Current mutation and reload ledger\n\nThe application currently changes behavioural values through unrelated paths:\n\n| Current change seam | Current behaviour | Required target |\n| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Telegram `/restart` in `cmd/archied` | Re-reads the global document and directly replaces Telegram token and allowed-user IDs; failure retains old values. | Submit a Telegram-settings candidate through the universal change protocol. Validate the complete candidate, promote atomically, audit the acting identity, and retain last-known-good. |\n| Active model selection | `chatModelManager.SetActiveModel` changes a model reference. | A conversation/session command changing runtime state. Validate against configured model instances and audit it; do not rewrite configuration. |\n| Active provider selection | `chatModelManager.SetActiveProvider` changes provider selection. | A conversation/session command changing runtime state, with the same distinction from provider-instance configuration. |\n| Persona selection | `PersonaRegistry.SetActive` mutates an in-memory per-session choice. | Agent-system session state. Persistence and audit requirements are owned by that domain, not the configuration loader. |\n| File and environment overlays | Applied while loading `internal/config`; defaults are filled by mutation in `finalize`. | Configuration-infrastructure input processing that produces separately typed candidates. Defaults and derivations remain visible in provenance. |\n| SIGHUP config reload (2026-08) | Re-resolves the file config, re-applies the database layer over it, validates, then atomically republishes through `config.Holder`. A failed reload, whether the file or the control plane caused it, keeps the running config and records `last_error`/`last_error_at` in `/api/config`. | Candidate promotion with last-known-good retention: the running snapshot is untouched on failure. A bounded observation period and actor audit are not yet implemented. |\n| Control-plane resource command (2026-09) | `ControlPlaneService.Command` validates a whole resource document against its owning feature, then writes it with an audit record (actor, source, request ID, expected version) under optimistic concurrency. Hosted on the State Store's gRPC server; the Web UI and messaging channels are its only clients. See `docs/prds/runtime-control-plane.md`. | Met for validate-stage-promote, actor audit and versioned history. Per-field health observation and validate-before-switch on live apply are not yet implemented. |\n\nAny further mutation seam discovered during migration MUST be added here before\nit is changed. Direct field assignment on a live settings object is prohibited.\n\n## Universal change protocol\n\nChanging configuration is an application command performed by an identity. It\nMUST:\n\n1. resolve the target owner and current version;\n2. parse into that owner's typed settings;\n3. validate syntax, semantic constraints, policy, references, and safe bounds;\n4. stage a candidate without altering the active value;\n5. run owner-defined readiness and health checks;\n6. atomically promote the candidate and record actor, source, reason, diff,\n prior version, and new version;\n7. observe the affected capability for a bounded period;\n8. retain the new version on success, or automatically restore last-known-good\n on failure;\n9. report the rejected or rolled-back candidate without terminating unaffected\n capabilities.\n\nStartup loading uses the same candidate rules. A bad user value therefore does\nnot partially mutate the application or make a previously healthy capability\nunavailable.\n\nSettings that cannot safely reload in-process are marked restart-required. The\nchange may still be validated and versioned immediately, but promotion occurs\nthrough a controlled restart with the same health and rollback semantics.\n\n## Implemented runtime reload and settings writes (2026-09)\n\nTwo mechanisms change behavioural values at runtime: SIGHUP re-reads the file\nconfig, and the control plane owns every database-backed setting. The dashboard\nruntime overlay that used to sit between them was deleted once the control plane\ncovered its surface; `-config-overlay` names a file overlay and is unrelated.\n\n### Published snapshot: `config.Holder`\n\nThe running configuration is a published snapshot held in `config.Holder`\n(`internal/config/holder.go`). Get returns a value under RLock; Set replaces the\nwhole snapshot. A published Config is immutable: reload constructs a fresh one\nand calls Set. `config.Clone` deep-copies every reference-type field so a failed\ndecode cannot mutate the published snapshot's shared maps. `Holder.Get` panics\non a nil receiver — a forgotten `NewHolder` must fail loudly, not boot a daemon\nthat silently runs on an empty config.\n\n### The reloadable-field criterion\n\nThe diff-and-warn on reload asks whether a changed field takes effect without a\nrestart. The criterion is: **a field is reloadable when every consumer re-reads\nit.** That question read as \"what does the daemon re-read\" while the daemon owned\nthe only Holder; it stopped being sufficient when webui began sharing that\nHolder, because webui handlers re-read on every request. The allowlist lives in\n`cmd/archied/reload.go` and is deliberately a deny-by-default list: a field added\nto Config later defaults to requires-restart, forcing whoever adds it to decide\ndeliberately. A reload that changes any non-allowlisted field logs\n\"requires a restart\" with the field names; a fully-applied reload logs Info.\n\n### SIGHUP reload\n\nSIGHUP re-resolves the file config, re-applies the database layer over it\n(`boot.runtimeConfig`, the same call boot makes), validates, and atomically\nrepublishes through the shared Holder. A failed reload keeps the running config\nand records `last_error`/`last_error_at` in `/api/config` so the stale state is\nvisible where the operator is looking. The three poll tickers re-read\n`PollInterval` per iteration and reset on change, so a reloaded interval\ngenuinely takes effect.\n\n### Settings writes go through the control plane\n\nDatabase-backed settings are read and written through\n`ControlPlaneService` on the State Store's gRPC server: catalog, query,\ncommand, watch. Each feature owns its resource's validation and commands;\nstorage writes versions and audit records only. `docs/prds/runtime-control-plane.md`\nis the specification.\n\nTwo properties matter to anyone changing this area:\n\n- **Bootstrap stays file-owned.** The daemon reads the file config first and\n layers database resources over it at boot (`boot.loadRuntimeConfig`). Values\n the daemon needs before it can reach the State Store — the database path,\n listen addresses, credentials — stay file-only by design.\n- **Reload re-reads them.** SIGHUP resolves the file document and then runs the\n same `boot.runtimeConfig` layering boot does, so a reload cannot revert a\n database-owned setting to its file value. A control plane that cannot answer\n fails the reload rather than publishing the file's values over the running\n ones. Workflow execution budgets arrive on a watch rather than in a resource\n query, so boot records the last published settings and the reload re-applies\n them from there.\n\n## Completion criteria\n\nThe configuration rearchitecture is complete only when:\n\n- `internal/config` no longer exists;\n- every behavioural value has one classification and owner;\n- every current field and hard-coded value in the ledgers has a recorded\n disposition;\n- domains and plugins receive only their typed settings;\n- all changes use semantic commands and the universal change protocol;\n- active, candidate, rejected, rolled-back, and last-known-good versions are\n queryable with secret-safe provenance;\n- generated documentation lists every external key, default, constraint,\n mutability class, owner, and deprecation;\n- architecture tests prevent a new central runtime configuration model, direct\n live-setting mutation, and incorrectly fixed behavioural values.\n\n## Startup policy: missing credential degrades, invalid config is fatal\n\nDecided 2026-07-30. Recovered 2026-08-09 from the pre-migration issue tracker.\n\nA missing **credential** disables a capability. Only an **invalid config** stops\nthe daemon. \"Forge is a feature, not a requirement.\"\n\nBefore `518a1a0`, an unresolvable forge token did `return 1` in\n`cmd/archied/main.go`, so a chat-only user who never configured GitHub got no\nchat, no gateway, nothing — and under a systemd unit with `Restart=on-failure`\nand no start limit it crash-looped every five seconds with the error scrolling\npast unread. Forge construction now lives in `resolveForge`, shared by the\nprimary forge and every configured identity, and degrades to `forge.NewNoop`\nwith a warning. The identity path had the same defect and was worse: one\nidentity's missing credential killed all the others.\n\nMalformed configuration still fails fast in `configuration.Validate`, well\nbefore this point. That distinction is the whole design.\n\nApply the same reasoning to any future capability credential, LLM keys\nespecially: start, report the capability as unavailable, let the operator see it.\nGuarded by `TestResolveForgeDegradesInsteadOfFailing`.\n\n**Known consequence, tracked separately:** `worktree.Manager` still receives the\nempty token, so pushes fail late rather than at startup.\n\n## Config generation belongs to `archied setup`, not `install.sh`\n\nDecided 2026-07-30 ([#368](https://github.com/samcharles93/archie-core/issues/368)).\nRecovered 2026-08-09 from the pre-migration issue tracker.\n\n`install.sh` must stop generating `config.toml`; `archied setup` owns it. The\ninstaller hand-rolling TOML has already drifted from the schema once: the\ngenerated-config branch hardcoded `key = ARCHIE_GITHUB_TOKEN` and\n`host = ${GITEA_URL}` regardless of the answers given, so choosing Gitea produced\na config naming a token the installer never wrote (archied then exited 1), and\nchoosing GitHub pointed `host` at `gitea.example.com`. `61a5b35` patched this\nwith a `forge_block` shell helper shared by both config paths — that helper is a\n**workaround**, deleted by\n[#72](https://github.com/samcharles93/archie-core/issues/72). The durable fix is\nthat the code writing the config is the code that reads it.\n\nWhy Go and not Python: the installer must run where nothing is installed yet, and\n`python3` with `tomllib` means 3.11+, which is not safe on LTS distros. `archied`\nis already being built two steps earlier.\n\n**Key constraint for the port:** `BurntSushi/toml` does **not** survive a\ndecode/encode round trip with comments intact, and `config.example.toml` carries\ndocumentation users are meant to hand-edit. Decide the write strategy\n([#412](https://github.com/samcharles93/archie-core/issues/412)) before writing\nany prompting code. Do not port a separate `config.yaml`/`auth.yaml` secret\nsplit — Archie already has `secret.SecretRef{engine,key}`, so setup writes the\nreference to TOML and the value to the secret engine.\n" }, { "url": "/dev/architecture/dashboard-agent-tools/", @@ -340,7 +340,7 @@ "url": "/dev/prds/release-stream-and-commit-rules/", "title": "One release stream, one page per version, and commit rules — decision", "section": "PRDs", - "body": "# One release stream, one page per version, and commit rules — decision\n\n**Status:** Draft\n**Date:** 2026-09-22\n**Authority:** `RELEASING.md` for the process this changes, `AGENTS.md` for the\ncommit rules it enforces, and `tools/newsgen` for the artifact shape.\n\n**Supersedes:** `docs/prds/news-and-releases.md`, sections \"Source of truth\" and\n\"Two components\" — one changelog replaces two, and one page per version replaces\none page per component. Its remaining decisions stand.\n\n## Decision\n\n**A release is one version covering whatever changed.** One changelog holds every\nrelease section, one generated page holds every version's notes, and an operator\ncutting a release names one version.\n\n## One changelog\n\nEvery release section lives in `CHANGELOG.md`, newest first. `CHANGELOG.archied.md`\nand `CHANGELOG.archie.md` are deleted, and `CHANGELOG.md` stops being a pointer to\nthem. The changelog is the only source of release prose, and tags are not a source:\nCI and deployment check out shallow, so tags are absent from a site build while the\nchangelog is always present.\n\n### The merged history\n\nTwo version streams become one file, so a version that both components released\ncarries one heading and one date: **the newest date among that version's sections**,\nbecause a version's date is when the last part of it shipped. Where a component's own\ndate differs from it, that component's section label carries its own date, so the\nper-component fact survives the merge rather than being collapsed into the heading.\n\nThis ambiguity is historical only. One version stream with one tag gives a version\nexactly one date, so the rule represents the merged past rather than a design that has\nto hold.\n\nThe merge is verified by content, not by the generator succeeding: the section count\nper source, the merged version set equal to the union of both sources with nothing\nextra, and every section title still present. A generator that agrees with the file it\njust wrote is evidence of nothing.\n\n## One version stream\n\n**`GATEWAY` and `RUNTIME` stop being release inputs.** `release:prepare` and\n`release:tag` take one version, and `tools/release.sh` loses the two flags.\n\nThey may stay as build-time stamps, because a binary must still report what it\ncontains. A release that must name three versions forces an operator to pass skip\nvalues for components that did not change, and that ceremony is what this decision\nremoves — along with the drift it allows, where two components' tags fall a release\napart.\n\n**Per-component detail stays, as sections inside the release.** A reader still needs\nto know whether `archied` or the agent changed; what goes away is the separate\nnumbers and the separate pages, not the information.\n\n**History is not re-tagged.** Existing tags keep their names, because tags are not a\nsource and nothing reads them to build a page. A future reader must not \"fix\" the\nunified changelog by rewriting tags to match it.\n\n## One release page per version\n\n`docs/news/\u003cversion\u003e.md` replaces `docs/news/\u003ccomponent\u003e/\u003cversion\u003e.md`, carrying the\nrelease's per-component sections inside it.\n\n**Every release URL already published keeps working.** `/news/archied/\u003cversion\u003e` and\n`/news/archie/\u003cversion\u003e` route to the unified page for that version. The generator\nemits the redirect table beside the pages so it cannot drift from them; if the\nrenderer needs the table in its own repository, that is a change in that repository\nrather than a hand-maintained list here.\n\n## The reviewer runs between prepare and tag\n\nRelease notes are prose, and the review agent exists to review prose. **`release:tag`\nrefuses to tag when the review has not been run for that version, or when it reports\nat the level.**\n\nThe invocation is verified rather than assumed. `tl rules --lint` reports `corpus ok`\nand exits 0. `tl review \u003cpath\u003e --deadline \u003cms\u003e --max-turns \u003cn\u003e` reports\n`0 findings (0 high, 0 medium) · 1/1 files reviewed · clean` and exits 0 on\n`docs/news/archied/1.36.0.md`.\n\n**`--fail-on` must be passed explicitly.** It defaults to `never`, so an invocation\nwithout it cannot refuse anything and the step would be decorative. `--fail-on high`\nis the level: a medium finding in a release note is worth acting on, and it should not\nstop a release on its own.\n\n**The rule is stated once.** It belongs in the reviewer's own rule set, which\n`tl rules --from-doc` can draft from this document; `RELEASING.md` points at that\nrule beside the step it governs rather than restating it, because two statements of\none rule drift.\n\n## Commit rules and their enforcement\n\n- **Conventional commits**, with the scope taken from the package map.\n- **One logical change per commit.** A commit that does two things is two commits.\n- **The subject is imperative and short**; the body says why the change is right\n rather than restating the diff.\n- **A commit depends on the gate's exit status.** The gate and the commit run as one\n conditional chain, never as separate statements on one command line, where nothing\n reads the gate's status but the operator who typed it.\n- **Enforcement is a `commit-msg` hook** installed by one documented target, plus a\n check in CI over the pushed range, so the rule holds for a person who never\n installed the hook.\n- **Scopes are derived, not invented**, and an unknown scope fails loudly rather than\n being accepted.\n\n## The release pipeline\n\n**A Woodpecker workflow performs the release**: gate, generate the release page, run\nthe reviewer over it, commit the changelog and the generated pages, tag, push,\npublish images, and trigger the site's artifact sync. No step in that list is an\noperator's.\n\n**It triggers on a push to main**, not on a manual run. A pipeline a human must start\nis a pipeline that can be forgotten, which is the property this change removes. The\ntrigger is also not dependent on repairing manual triggering: in this estate a manual\nrun fails with zero steps while the same configuration runs on a push, and the\nestate's own Woodpecker configurations trigger on push with cron, manual or\npull-request events *added* to it rather than instead of it.\n\n**Prerequisite: Woodpecker must watch this repository.** Adding the workflow to the\nrepository and enabling the repository in Woodpecker are two steps, and the second is\na configuration action rather than a file. A release pipeline that is correct and\nnever runs is invisible until someone asks why no release happened, so the repository\nbeing enabled is a prerequisite of this design rather than an assumption behind it.\n\n**One tag, and the duplicate-build problem shrinks as a consequence.** Concurrency\nkeyed on a commit identifier treats an annotated tag as a ref distinct from its\ncommit, which starts three builds for one release. One version and one tag removes\ntwo of those refs. Nothing in the pipeline may depend on a tag object's\nidentity, and this is a consequence of one version stream rather than a separate fix.\n\n### The version is computed, not typed\n\nThe version is derived from the conventional commits since the last release, which is\nwhat the commit rules above exist for.\n\n- `feat` bumps the minor version; `fix`, `perf` and `refactor` bump the patch.\n- **A breaking change bumps the major version.** Its form is `!` after the type or\n scope, as in `feat(api)!:`, and a `BREAKING CHANGE:` trailer — either marks it.\n- `chore`, `docs`, `test`, `style` and `build` bump nothing alone.\n- **No release is a legitimate outcome.** A commit set that justifies no version\n produces no version, and the pipeline reports that rather than inventing one.\n\n### `tools/release.sh` is designed for the pipeline\n\n- **It never prompts.** Every input arrives as an argument or in the environment, so\n it runs with no terminal.\n- **Its version is a result as well as an argument.** It may be given one or asked to\n derive one, and it reports the version it used in a form a pipeline can read.\n- **\"Nothing to release\" has its own exit code**, distinct from failure, so the\n pipeline finishes green without tagging.\n- **It commits and tags nothing.** The pipeline owns the commit, the tag and the push;\n the script writes the notes and reports what it did. A script that pushes cannot be\n run twice safely, and this one runs on every push to main.\n\n### Which CI is authoritative\n\nThree surfaces exist: GitHub Actions, the Gitea workflow files, and Woodpecker.\n\n- **Woodpecker owns releases**, which is the production path this repository's deploy\n workflow already names.\n- **GitHub Actions keeps the checks a pull request needs.**\n- **The Gitea workflow files are retired in favour of Woodpecker** once Woodpecker\n runs the same checks, and are not edited in the meantime: two copies of a pipeline\n diverge.\n- No check lives in two places with neither authoritative. Where a check must run in\n both, the second runs the same file rather than a copy of it.\n\n## Verification\n\n- One changelog file exists, the two component changelogs do not, and the generated\n pages match it.\n- A release prepared with `VERSION` alone writes its notes and tags, with no\n `GATEWAY` or `RUNTIME` input.\n- Every release URL published before this change resolves.\n- `release:tag` refuses after a review that reported at the level, and refuses when\n no review ran.\n- The `commit-msg` hook and the CI range check each refuse a non-conforming subject\n and an unknown scope, with the hook absent and present.\n- A push to main carrying releasable commits produces a version, a release page, a\n tag and a published image with no operator step.\n- A push whose commits justify no release ends green and tags nothing.\n- `tools/release.sh` runs to completion with stdin closed, and exits with its\n distinct code when there is nothing to release.\n- The release workflow reads no tag object's identity, so one release starts one\n build.\n" + "body": "# One release stream, one page per version, and commit rules — decision\n\n**Status:** Draft\n**Date:** 2026-09-22\n**Authority:** `RELEASING.md` for the process this changes, `AGENTS.md` for the\ncommit rules it enforces, and `tools/newsgen` for the artifact shape.\n\n**Supersedes:** `docs/prds/news-and-releases.md`, sections \"Source of truth\" and\n\"Two components\" — one changelog replaces two, and one page per version replaces\none page per component. Its remaining decisions stand.\n\n## Decision\n\n**A release is one version covering whatever changed.** One changelog holds every\nrelease section, one generated page holds every version's notes, and an operator\ncutting a release names one version.\n\n## One changelog\n\nEvery release section lives in `CHANGELOG.md`, newest first. `CHANGELOG.archied.md`\nand `CHANGELOG.archie.md` are deleted, and `CHANGELOG.md` stops being a pointer to\nthem. The changelog is the only source of release prose, and tags are not a source:\nCI and deployment check out shallow, so tags are absent from a site build while the\nchangelog is always present.\n\n### The merged history\n\nTwo version streams become one file, so a version that both components released\ncarries one heading and one date: **the newest date among that version's sections**,\nbecause a version's date is when the last part of it shipped. Where a component's own\ndate differs from it, that component's section label carries its own date, so the\nper-component fact survives the merge rather than being collapsed into the heading.\n\nThe merged history holds 65 versions: 33 that both components released, 31 only\n`archied`, and one only `archie`, from 64 and 34 sections respectively, so 98\npublished pages become 65. `## [Unreleased]` is not a release -- it carries no\nversion and gets no page -- but it stays at the top of the file, because it is\nthe one place unfinished work is recorded. Counting `##` headings rather than\nreleases overcounts by one.\n\nThis ambiguity is historical only. One version stream with one tag gives a version\nexactly one date, so the rule represents the merged past rather than a design that has\nto hold.\n\nThe merge is verified by content, not by the generator succeeding: the section count\nper source, the merged version set equal to the union of both sources with nothing\nextra, and every section title still present. A generator that agrees with the file it\njust wrote is evidence of nothing.\n\n## One version stream\n\n**`GATEWAY` and `RUNTIME` stop being release inputs.** `release:prepare` and\n`release:tag` take one version, and `tools/release.sh` loses the two flags.\n\nThey may stay as build-time stamps, because a binary must still report what it\ncontains. A release that must name three versions forces an operator to pass skip\nvalues for components that did not change, and that ceremony is what this decision\nremoves — along with the drift it allows, where two components' tags fall a release\napart.\n\n**Per-component detail stays, as sections inside the release.** A reader still needs\nto know whether `archied` or the agent changed; what goes away is the separate\nnumbers and the separate pages, not the information.\n\n**History is not re-tagged.** Existing tags keep their names, because tags are not a\nsource and nothing reads them to build a page. A future reader must not \"fix\" the\nunified changelog by rewriting tags to match it.\n\n## One release page per version\n\n`docs/news/\u003cversion\u003e.md` replaces `docs/news/\u003ccomponent\u003e/\u003cversion\u003e.md`, carrying the\nrelease's per-component sections inside it.\n\n**Every release URL already published keeps working.** `/news/archied/\u003cversion\u003e` and\n`/news/archie/\u003cversion\u003e` route to the unified page for that version. The generator\nemits the redirect table beside the pages so it cannot drift from them; if the\nrenderer needs the table in its own repository, that is a change in that repository\nrather than a hand-maintained list here.\n\n## The reviewer runs between prepare and tag\n\nRelease notes are prose, and the review agent exists to review prose. **`release:tag`\nrefuses to tag when the review has not been run for that version, or when it reports\nat the level.**\n\nThe invocation is verified rather than assumed. `tl rules --lint` reports `corpus ok`\nand exits 0. `tl review \u003cpath\u003e --deadline \u003cms\u003e --max-turns \u003cn\u003e` reports\n`0 findings (0 high, 0 medium) · 1/1 files reviewed · clean` and exits 0 on\n`docs/news/archied/1.36.0.md`.\n\n**`--fail-on` must be passed explicitly.** It defaults to `never`, so an invocation\nwithout it cannot refuse anything and the step would be decorative. `--fail-on high`\nis the level: a medium finding in a release note is worth acting on, and it should not\nstop a release on its own.\n\n**The rule is stated once.** It belongs in the reviewer's own rule set, which\n`tl rules --from-doc` can draft from this document; `RELEASING.md` points at that\nrule beside the step it governs rather than restating it, because two statements of\none rule drift.\n\n## Commit rules and their enforcement\n\n- **Conventional commits**, with the scope taken from the package map.\n- **One logical change per commit.** A commit that does two things is two commits.\n- **The subject is imperative and short**; the body says why the change is right\n rather than restating the diff.\n- **A commit depends on the gate's exit status.** The gate and the commit run as one\n conditional chain, never as separate statements on one command line, where nothing\n reads the gate's status but the operator who typed it.\n- **Enforcement is a `commit-msg` hook** installed by one documented target, plus a\n check in CI over the pushed range, so the rule holds for a person who never\n installed the hook.\n- **Scopes are derived, not invented**, and an unknown scope fails loudly rather than\n being accepted.\n\n## The release pipeline\n\n**A Woodpecker workflow performs the release**: gate, generate the release page, run\nthe reviewer over it, commit the changelog and the generated pages, tag, push,\npublish images, and trigger the site's artifact sync. No step in that list is an\noperator's.\n\n**It triggers on a push to main**, not on a manual run. A pipeline a human must start\nis a pipeline that can be forgotten, which is the property this change removes. The\ntrigger is also not dependent on repairing manual triggering: in this estate a manual\nrun fails with zero steps while the same configuration runs on a push, and the\nestate's own Woodpecker configurations trigger on push with cron, manual or\npull-request events *added* to it rather than instead of it.\n\n**Prerequisite: Woodpecker must watch this repository.** Adding the workflow to the\nrepository and enabling the repository in Woodpecker are two steps, and the second is\na configuration action rather than a file. A release pipeline that is correct and\nnever runs is invisible until someone asks why no release happened, so the repository\nbeing enabled is a prerequisite of this design rather than an assumption behind it.\n\n**One tag, and the duplicate-build problem shrinks as a consequence.** Concurrency\nkeyed on a commit identifier treats an annotated tag as a ref distinct from its\ncommit, which starts three builds for one release. One version and one tag removes\ntwo of those refs. Nothing in the pipeline may depend on a tag object's\nidentity, and this is a consequence of one version stream rather than a separate fix.\n\n### The version is computed, not typed\n\nThe version is derived from the conventional commits since the last release, which is\nwhat the commit rules above exist for.\n\n- `feat` bumps the minor version; `fix`, `perf` and `refactor` bump the patch.\n- **A breaking change bumps the major version.** Its form is `!` after the type or\n scope, as in `feat(api)!:`, and a `BREAKING CHANGE:` trailer — either marks it.\n- `chore`, `docs`, `test`, `style` and `build` bump nothing alone.\n- **No release is a legitimate outcome.** A commit set that justifies no version\n produces no version, and the pipeline reports that rather than inventing one.\n\n### `tools/release.sh` is designed for the pipeline\n\n- **It never prompts.** Every input arrives as an argument or in the environment, so\n it runs with no terminal.\n- **Its version is a result as well as an argument.** It may be given one or asked to\n derive one, and it reports the version it used in a form a pipeline can read.\n- **\"Nothing to release\" has its own exit code**, distinct from failure, so the\n pipeline finishes green without tagging.\n- **It commits and tags nothing.** The pipeline owns the commit, the tag and the push;\n the script writes the notes and reports what it did. A script that pushes cannot be\n run twice safely, and this one runs on every push to main.\n\n### Which CI is authoritative\n\nThree surfaces exist: GitHub Actions, the Gitea workflow files, and Woodpecker.\n\n- **Woodpecker owns releases**, which is the production path this repository's deploy\n workflow already names.\n- **GitHub Actions keeps the checks a pull request needs.**\n- **The Gitea workflow files are retired in favour of Woodpecker** once Woodpecker\n runs the same checks, and are not edited in the meantime: two copies of a pipeline\n diverge.\n- No check lives in two places with neither authoritative. Where a check must run in\n both, the second runs the same file rather than a copy of it.\n\n## Verification\n\n- One changelog file exists, the two component changelogs do not, and the generated\n pages match it.\n- A release prepared with `VERSION` alone writes its notes and tags, with no\n `GATEWAY` or `RUNTIME` input.\n- Every release URL published before this change resolves.\n- `release:tag` refuses after a review that reported at the level, and refuses when\n no review ran.\n- The `commit-msg` hook and the CI range check each refuse a non-conforming subject\n and an unknown scope, with the hook absent and present.\n- A push to main carrying releasable commits produces a version, a release page, a\n tag and a published image with no operator step.\n- A push whose commits justify no release ends green and tags nothing.\n- `tools/release.sh` runs to completion with stdin closed, and exits with its\n distinct code when there is nothing to release.\n- The release workflow reads no tag object's identity, so one release starts one\n build.\n" }, { "url": "/dev/prds/review-calibration/", diff --git a/docs/news/archied/1.0.0.md b/docs/news/1.0.0.md similarity index 51% rename from docs/news/archied/1.0.0.md rename to docs/news/1.0.0.md index c64105ebf..d10bad66e 100644 --- a/docs/news/archied/1.0.0.md +++ b/docs/news/1.0.0.md @@ -1,6 +1,13 @@ -# archied 1.0.0 +# 1.0.0 -Released 2026-07-22. [All news](../index.md) +Released 2026-07-22. [All news](index.md) + +### archied - feat: ship the resident forge-polling daemon, deterministic workflow engine, isolated worktrees, quality gates, Gitea integration, Docker/NATS worker split, plugin loading, and skills support - feat: publish `archied` and `archie-agent` container images to the Gitea registry + +### archie-agent + +- feat: ship the isolated agent runtime, NATS RPC boundary, workflow execution, skills, and plugin support +- feat: publish the `archie-agent` container image to the Gitea registry diff --git a/docs/news/archied/1.1.0.md b/docs/news/1.1.0.md similarity index 78% rename from docs/news/archied/1.1.0.md rename to docs/news/1.1.0.md index 12a72ea66..33f226264 100644 --- a/docs/news/archied/1.1.0.md +++ b/docs/news/1.1.0.md @@ -1,6 +1,8 @@ -# archied 1.1.0 +# 1.1.0 -Released 2026-07-27. [All news](../index.md) +Released 2026-07-27. [All news](index.md) + +### archied - feat: add the Telegram gateway with persistent sessions, topic-thread support, streamed rich replies, typing indicators, and Markdown rendering - feat: add `/spawn`, `/approve`, and `/cancel` for chat-driven task control @@ -24,3 +26,14 @@ Released 2026-07-27. [All news](../index.md) - fix: make MCP stdio shutdown and timeout handling race-safe - fix: restore legacy `[forge].token_env` compatibility and required container environment passthrough - fix: make the agent-container Docker network explicitly configurable + +### archie-agent + +- feat: add streamed agent execution with typed message events +- feat: add MCP client transports and managed tool-provider discovery +- feat: add memory context scrubbing and normalized memory tool schemas +- feat: add plugin metadata extraction from `metadata.archie.plugins` +- feat: add configurable container networking for daemon-launched runtimes +- fix: preserve valid UTF-8 when clipping runtime output +- fix: make MCP stdio lifecycle, retries, and timeout handling race-safe +- fix: enforce a zero-finding lint and vet baseline diff --git a/docs/news/archied/1.10.0.md b/docs/news/1.10.0.md similarity index 93% rename from docs/news/archied/1.10.0.md rename to docs/news/1.10.0.md index f2c0e792e..c7293b951 100644 --- a/docs/news/archied/1.10.0.md +++ b/docs/news/1.10.0.md @@ -1,6 +1,8 @@ -# archied 1.10.0 +# 1.10.0 -Released 2026-08-22. [All news](../index.md) +Released 2026-08-22. [All news](index.md) + +### archied - feat(forge): GitHub webhook receiver for immediate issue dispatch - feat(webhookguard): shared HMAC, rate-limit, and redaction mechanics diff --git a/docs/news/archied/1.11.0.md b/docs/news/1.11.0.md similarity index 90% rename from docs/news/archied/1.11.0.md rename to docs/news/1.11.0.md index e60b58b4d..58f8a2e12 100644 --- a/docs/news/archied/1.11.0.md +++ b/docs/news/1.11.0.md @@ -1,6 +1,8 @@ -# archied 1.11.0 +# 1.11.0 -Released 2026-08-23. [All news](../index.md) +Released 2026-08-23. [All news](index.md) + +### archied - feat(forge): make webhook intake observable and deduplicate concurrent delivery - fix(telegram): preserve code fences across message splits diff --git a/docs/news/archied/1.11.1.md b/docs/news/1.11.1.md similarity index 67% rename from docs/news/archied/1.11.1.md rename to docs/news/1.11.1.md index 611e7f868..43d4914c7 100644 --- a/docs/news/archied/1.11.1.md +++ b/docs/news/1.11.1.md @@ -1,6 +1,8 @@ -# archied 1.11.1 +# 1.11.1 -Released 2026-08-23. [All news](../index.md) +Released 2026-08-23. [All news](index.md) + +### archied - fix(update): wire Telegram personas and survive callback cancellation - fix(webui): theme the Workflows 'Start work' form controls diff --git a/docs/news/archied/1.12.0.md b/docs/news/1.12.0.md similarity index 82% rename from docs/news/archied/1.12.0.md rename to docs/news/1.12.0.md index 6ef3ea844..2bd74715c 100644 --- a/docs/news/archied/1.12.0.md +++ b/docs/news/1.12.0.md @@ -1,6 +1,8 @@ -# archied 1.12.0 +# 1.12.0 -Released 2026-08-23. [All news](../index.md) +Released 2026-08-23. [All news](index.md) + +### archied - fix(webui): give dashboard-initiated updates a phase-2 report - feat(agent): stamp archie-agent's build and report it back to the daemon diff --git a/docs/news/1.13.0.md b/docs/news/1.13.0.md new file mode 100644 index 000000000..086cc6a38 --- /dev/null +++ b/docs/news/1.13.0.md @@ -0,0 +1,7 @@ +# 1.13.0 + +Released 2026-08-23. [All news](index.md) + +### archied + +- fix(telegram): render tool progress as bounded code blocks diff --git a/docs/news/archied/1.14.0.md b/docs/news/1.14.0.md similarity index 62% rename from docs/news/archied/1.14.0.md rename to docs/news/1.14.0.md index 332f53a06..0fdd71d80 100644 --- a/docs/news/archied/1.14.0.md +++ b/docs/news/1.14.0.md @@ -1,6 +1,8 @@ -# archied 1.14.0 +# 1.14.0 -Released 2026-08-23. [All news](../index.md) +Released 2026-08-23. [All news](index.md) + +### archied - fix(telegram): compact tool output and drop turn caps - fix(update): install only approved components diff --git a/docs/news/archied/1.15.0.md b/docs/news/1.15.0.md similarity index 97% rename from docs/news/archied/1.15.0.md rename to docs/news/1.15.0.md index a64a7890d..6eda5f1ee 100644 --- a/docs/news/archied/1.15.0.md +++ b/docs/news/1.15.0.md @@ -1,6 +1,8 @@ -# archied 1.15.0 +# 1.15.0 -Released 2026-08-24. [All news](../index.md) +Released 2026-08-24. [All news](index.md) + +### archied **Autonomous workflows now have exactly one production execution path.** Every task is handed complete to a scoped `archie-agent` container over core NATS; diff --git a/docs/news/archie/1.16.0.md b/docs/news/1.16.0.md similarity index 55% rename from docs/news/archie/1.16.0.md rename to docs/news/1.16.0.md index 78a62ced9..2ac424b4c 100644 --- a/docs/news/archie/1.16.0.md +++ b/docs/news/1.16.0.md @@ -1,6 +1,37 @@ -# archie-agent 1.16.0 +# 1.16.0 -Released 2026-08-25. [All news](../index.md) +Released 2026-08-25. [All news](index.md) + +### archied + +**The agent can hand you a file, and the dashboard works behind a reverse +proxy.** Media delivery was fetch-by-URL only, so a file the agent produced +locally — a transcript, a log dump, a screenshot — was passed to Telegram as +a URL it could not fetch: the send did nothing and reported success. The new +`send_file` tool plus upload-by-reader delivery closes that, and every layer +that cannot deliver now says so rather than staying silent. Dashboard +mutations behind a TLS-terminating proxy were refused as cross-origin; +forwarded headers are now honoured, but only under an explicit opt-in that is +off by default. + +- feat(telegram): deliver a local file as an uploaded attachment, choosing + upload-by-reader or fetch-by-URL per attachment; `send_file` resolves paths + under the same confinement policy the read tool applies, so sending cannot + reach what reading cannot +- feat(gateway): `task_action` chat tool for operator task management — + abandon, archive, retry, stop, cancel, approve and reject from chat, on the + same action path and state machine as the dashboard +- fix(webui): validate mutation `Origin` against the effective external + scheme and host. `X-Forwarded-Proto`/`-Host` are honoured only when + `web.trust_forwarded_headers` is set, which is off by default and safe only + behind a proxy that overwrites or strips untrusted forwarded headers +- fix(webui): report a local file the dashboard chat cannot upload as + undelivered instead of dropping the event, which had reproduced the exact + silent non-delivery `send_file` was built to end +- fix(daemon): detach terminal state transitions and cleanup from a cancelled + context, so a stopped task still records its outcome + +### archie-agent **Version realigned with `archied`.** This release jumps from 1.9.9 to 1.16.0 to put the two components on matching numbers; there are no 1.10-1.15 agent diff --git a/docs/news/1.16.1.md b/docs/news/1.16.1.md new file mode 100644 index 000000000..e24fbd835 --- /dev/null +++ b/docs/news/1.16.1.md @@ -0,0 +1,7 @@ +# 1.16.1 + +Released 2026-08-25. [All news](index.md) + +### archie-agent + +- fix(agentworker): reconcile task clone ownership after commits diff --git a/docs/news/archie/1.17.0.md b/docs/news/1.17.0.md similarity index 68% rename from docs/news/archie/1.17.0.md rename to docs/news/1.17.0.md index deb5ad95b..ebef9cbd0 100644 --- a/docs/news/archie/1.17.0.md +++ b/docs/news/1.17.0.md @@ -1,6 +1,13 @@ -# archie-agent 1.17.0 +# 1.17.0 -Released 2026-08-25. [All news](../index.md) +Released 2026-08-25. [All news](index.md) + +### archied + +- fix(webui): add nil receiver guard to Server.trustForwardedHeaders +- fix(chat): restore transcript and update replay + +### archie-agent - Compact task history against the selected model's real context capacity without imposing a token cap. - Preserve completed steps and billed usage when a later provider call fails; failed compaction now keeps the original history and continues. diff --git a/docs/news/archied/1.17.1.md b/docs/news/1.17.1.md similarity index 63% rename from docs/news/archied/1.17.1.md rename to docs/news/1.17.1.md index af38d81c2..30eb38960 100644 --- a/docs/news/archied/1.17.1.md +++ b/docs/news/1.17.1.md @@ -1,6 +1,8 @@ -# archied 1.17.1 +# 1.17.1 -Released 2026-08-25. [All news](../index.md) +Released 2026-08-25. [All news](index.md) + +### archied - fix(update): remove source checkout dependency - fix(gateway): make UUIDv7 session references unambiguous diff --git a/docs/news/archied/1.18.0.md b/docs/news/1.18.0.md similarity index 65% rename from docs/news/archied/1.18.0.md rename to docs/news/1.18.0.md index a1f5493d8..25d616ec1 100644 --- a/docs/news/archied/1.18.0.md +++ b/docs/news/1.18.0.md @@ -1,8 +1,15 @@ -# archied 1.18.0 +# 1.18.0 -Released 2026-08-25. [All news](../index.md) +Released 2026-08-28. [All news](index.md) + +### archied (released 2026-08-25) - Fix concurrent chat-turn claims so SQLite writer contention no longer leaks as `SQLITE_BUSY`. - Make task timelines operationally useful with stage outcomes, durations, retry context, and durable per-stage token economics. - Return canonical repository, issue, and pull-request URLs for each task's owning GitHub or Gitea identity. - Preserve per-identity commit attribution and real model context limits across daemon-to-worker dispatch. + +### archie-agent + +- feat(logging): cursor pagination and filtering for task_logs +- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29 diff --git a/docs/news/archied/1.19.0.md b/docs/news/1.19.0.md similarity index 67% rename from docs/news/archied/1.19.0.md rename to docs/news/1.19.0.md index 8f415da13..694c14a0e 100644 --- a/docs/news/archied/1.19.0.md +++ b/docs/news/1.19.0.md @@ -1,6 +1,8 @@ -# archied 1.19.0 +# 1.19.0 -Released 2026-08-28. [All news](../index.md) +Released 2026-08-28. [All news](index.md) + +### archied - feat(logging): cursor pagination and filtering for task_logs - build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29 diff --git a/docs/news/archied/1.19.1.md b/docs/news/1.19.1.md similarity index 59% rename from docs/news/archied/1.19.1.md rename to docs/news/1.19.1.md index 7f0267f47..a537b5b5e 100644 --- a/docs/news/archied/1.19.1.md +++ b/docs/news/1.19.1.md @@ -1,5 +1,7 @@ -# archied 1.19.1 +# 1.19.1 -Released 2026-08-27. [All news](../index.md) +Released 2026-08-27. [All news](index.md) + +### archied - fix(telegram): keep Markdown headings/lists as blocks and strip Markdown on plain fallback diff --git a/docs/news/archied/1.19.10.md b/docs/news/1.19.10.md similarity index 50% rename from docs/news/archied/1.19.10.md rename to docs/news/1.19.10.md index 98d09bef6..b8a7d03d7 100644 --- a/docs/news/archied/1.19.10.md +++ b/docs/news/1.19.10.md @@ -1,5 +1,7 @@ -# archied 1.19.10 +# 1.19.10 -Released 2026-09-02. [All news](../index.md) +Released 2026-09-02. [All news](index.md) + +### archied - feat(curator): session-memory curator reference implementation diff --git a/docs/news/archied/1.19.2.md b/docs/news/1.19.2.md similarity index 51% rename from docs/news/archied/1.19.2.md rename to docs/news/1.19.2.md index 394d10420..e86823f4e 100644 --- a/docs/news/archied/1.19.2.md +++ b/docs/news/1.19.2.md @@ -1,5 +1,7 @@ -# archied 1.19.2 +# 1.19.2 -Released 2026-08-28. [All news](../index.md) +Released 2026-08-28. [All news](index.md) + +### archied - feat(tasks): allow rejecting a task from any non-terminal state diff --git a/docs/news/archied/1.19.3.md b/docs/news/1.19.3.md similarity index 71% rename from docs/news/archied/1.19.3.md rename to docs/news/1.19.3.md index 34e63d6db..340f30d74 100644 --- a/docs/news/archied/1.19.3.md +++ b/docs/news/1.19.3.md @@ -1,6 +1,8 @@ -# archied 1.19.3 +# 1.19.3 -Released 2026-08-28. [All news](../index.md) +Released 2026-08-28. [All news](index.md) + +### archied - feat(tasks): serve the lifecycle presentation catalog from /api/task-meta - feat(dashboard): render task actions, statuses and filters from the server catalog diff --git a/docs/news/archied/1.19.4.md b/docs/news/1.19.4.md similarity index 50% rename from docs/news/archied/1.19.4.md rename to docs/news/1.19.4.md index 7a36d84a9..f767bb286 100644 --- a/docs/news/archied/1.19.4.md +++ b/docs/news/1.19.4.md @@ -1,5 +1,7 @@ -# archied 1.19.4 +# 1.19.4 -Released 2026-08-28. [All news](../index.md) +Released 2026-08-28. [All news](index.md) + +### archied - refactor(telegram): render replies as structured rich blocks diff --git a/docs/news/archied/1.19.5.md b/docs/news/1.19.5.md similarity index 57% rename from docs/news/archied/1.19.5.md rename to docs/news/1.19.5.md index badb6662b..39917db3b 100644 --- a/docs/news/archied/1.19.5.md +++ b/docs/news/1.19.5.md @@ -1,6 +1,8 @@ -# archied 1.19.5 +# 1.19.5 -Released 2026-09-01. [All news](../index.md) +Released 2026-09-01. [All news](index.md) + +### archied - feat(webui): dashboard-aware chat — Archie sees the page, points you there - fix(telegram): drop retry_after bandaid, bump go-telegram/bot to v1.24.0 @@ -23,3 +25,21 @@ Released 2026-09-01. [All news](../index.md) - refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization - fix(lint): noctx fixes and dead-code cleanup - feat(workflow): adversarial self-review stage before PR open + +### archie-agent + +- feat(tasks): allow rejecting a task from any non-terminal state +- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta +- fix: go.mod bumped to 1.27.0 and stupid tests removed +- refactor: go modernisation fixes +- refactor: remove unused Operator param. +- fix(plugin): add missing CLAUDE.md reference to plugin engine rule +- fix(app): repoint archied wiring contract test at internal/app/archied +- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet +- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui +- fix(app): repoint capability-host wiring contract test at internal/app/archied +- refactor(lint): extract more helpers to clear nestif/gocyclo findings +- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult +- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization +- fix(lint): noctx fixes and dead-code cleanup +- feat(workflow): adversarial self-review stage before PR open diff --git a/docs/news/archied/1.19.6.md b/docs/news/1.19.6.md similarity index 53% rename from docs/news/archied/1.19.6.md rename to docs/news/1.19.6.md index b95ddaaf4..4338474e1 100644 --- a/docs/news/archied/1.19.6.md +++ b/docs/news/1.19.6.md @@ -1,5 +1,7 @@ -# archied 1.19.6 +# 1.19.6 -Released 2026-09-02. [All news](../index.md) +Released 2026-09-02. [All news](index.md) + +### archied - fix(build): stamp gatewayVersion/runtimeVersion in the right package diff --git a/docs/news/1.19.7.md b/docs/news/1.19.7.md new file mode 100644 index 000000000..5506eda16 --- /dev/null +++ b/docs/news/1.19.7.md @@ -0,0 +1,11 @@ +# 1.19.7 + +Released 2026-09-02. [All news](index.md) + +### archied + +- fix(logging): make Tail/Page allocation bound explicit for CodeQL + +### archie-agent + +- fix(logging): make Tail/Page allocation bound explicit for CodeQL diff --git a/docs/news/archied/1.19.8.md b/docs/news/1.19.8.md similarity index 78% rename from docs/news/archied/1.19.8.md rename to docs/news/1.19.8.md index a22edd5a8..72367a02d 100644 --- a/docs/news/archied/1.19.8.md +++ b/docs/news/1.19.8.md @@ -1,6 +1,8 @@ -# archied 1.19.8 +# 1.19.8 -Released 2026-09-02. [All news](../index.md) +Released 2026-09-02. [All news](index.md) + +### archied - fix(update): drop dev-facing wording from the unconfirmed-update message - fix(telegram): stop adjacent rich blocks from rendering glued together diff --git a/docs/news/archied/1.19.9.md b/docs/news/1.19.9.md similarity index 75% rename from docs/news/archied/1.19.9.md rename to docs/news/1.19.9.md index d076bdb89..827239a74 100644 --- a/docs/news/archied/1.19.9.md +++ b/docs/news/1.19.9.md @@ -1,6 +1,8 @@ -# archied 1.19.9 +# 1.19.9 -Released 2026-09-02. [All news](../index.md) +Released 2026-09-02. [All news](index.md) + +### archied - feat(memory): typed memory engine contract, registry, and registrar - feat(memory): builtin engine implementing the domain/memory contract @@ -9,3 +11,7 @@ Released 2026-09-02. [All news](../index.md) - feat(curator): bind curators to memory engines - fix(config): reject memory.provider instead of silently ignoring it - feat(curator): skill curator reference implementation + +### archie-agent + +- feat(config): config surface for memory engine selection diff --git a/docs/news/archied/1.2.0.md b/docs/news/1.2.0.md similarity index 62% rename from docs/news/archied/1.2.0.md rename to docs/news/1.2.0.md index 1d70ea8c0..b488ecf64 100644 --- a/docs/news/archied/1.2.0.md +++ b/docs/news/1.2.0.md @@ -1,6 +1,8 @@ -# archied 1.2.0 +# 1.2.0 -Released 2026-07-31. [All news](../index.md) +Released 2026-07-31. [All news](index.md) + +### archied - feat: add MCP client capabilities to archied and archie-agent - fix: handleSummary ignores errors from WorkflowStats/StageStats/TokensByDay @@ -40,3 +42,27 @@ Released 2026-07-31. [All news](../index.md) - fix(docker): slim both images and repair unreachable Go tooling - fix(container): write the task boot brief under .git - fix(telegram): drop pending updates before long polling + +### archie-agent + +- feat: add MCP client capabilities to archied and archie-agent +- fix: Transition() ignores `from` status guard, allowing lost updates +- fix: skillscript.Run ignores context, cannot be canceled/timed out +- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup +- fix(indexing): surface index config properly and stop silent degradation +- refactor(worktree): replace git shell-out with go-git v6 +- fix(worktreerpc): bound handler contexts and drop the git binary from tests +- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries +- refactor: route tasks on a typed kind, not forge labels +- fix(natsrpc): make RegisterAll wait for the server to see subscriptions +- refactor(config): move loading into infrastructure/configuration +- refactor: add internal/eventbus as the broker-neutral messaging contract +- feat(tools): lift tau's file and shell tools into the tool registry +- feat: make /stop cancel the running chat turn +- fix: kill the whole process group when a shell command is cancelled +- feat: refuse unrecoverable shell commands +- feat: make /stop reach running agent tasks +- fix: use errors.Is/As for context errors and cleanup +- fix(grep): distinguish ripgrep exit 1 from a failed search +- fix(docker): slim both images and repair unreachable Go tooling +- fix(container): write the task boot brief under .git diff --git a/docs/news/archied/1.20.0.md b/docs/news/1.20.0.md similarity index 67% rename from docs/news/archied/1.20.0.md rename to docs/news/1.20.0.md index bb7966e06..f2839084e 100644 --- a/docs/news/archied/1.20.0.md +++ b/docs/news/1.20.0.md @@ -1,6 +1,8 @@ -# archied 1.20.0 +# 1.20.0 -Released 2026-09-03. [All news](../index.md) +Released 2026-09-03. [All news](index.md) + +### archied - fix: baseline gate repair (go test ./... -count=1) - fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler @@ -23,3 +25,15 @@ Released 2026-09-03. [All news](../index.md) - feat(webhook): harden captured payload redaction - fix(store): satisfy makezero when building cipher payload - feat(webui): refactor chat module to Preact component and add unit tests + +### archie-agent + +- fix: baseline gate repair (go test ./... -count=1) +- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler +- feat(image): define provider-neutral image capability contract and config +- fix(workflow): stop discarding baseline-fix commits as 'no changes' +- fix(workflow): net cache hits from token totals, trim gate-retry output +- feat(workflow): dynamic triage instead of defaulting every task to implement +- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated +- feat(store): encrypt playbook binding secrets at rest +- fix(store): satisfy makezero when building cipher payload diff --git a/docs/news/archied/1.21.0.md b/docs/news/1.21.0.md similarity index 58% rename from docs/news/archied/1.21.0.md rename to docs/news/1.21.0.md index 461362c8f..ee627124c 100644 --- a/docs/news/archied/1.21.0.md +++ b/docs/news/1.21.0.md @@ -1,6 +1,8 @@ -# archied 1.21.0 +# 1.21.0 -Released 2026-09-03. [All news](../index.md) +Released 2026-09-03. [All news](index.md) + +### archied - feat(workflow): make kind-to-workflow routing YAML-overridable - feat(workflow): route arbitrary forge labels to workflows via playbook YAML @@ -18,3 +20,16 @@ Released 2026-09-03. [All news](../index.md) - fix(webui): stretch HEALTH row cards to equal height - fix(eda): make playbook key collision reporting deterministic - fix(gateway): split /status (health) and /tasks (work) apart + +### archie-agent + +- feat(workflow): make kind-to-workflow routing YAML-overridable +- feat(workflow): route arbitrary forge labels to workflows via playbook YAML +- feat(workflow): load kind/label bindings from multiple playbook directories +- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive +- feat(eda): Module position first slice -- registry + side-effect-free log kind +- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch +- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch +- fix(binding): split ValidateForUpdate so edits can preserve the secret +- refactor(eda): extract helpers to satisfy cyclop/gocognit gates +- fix(eda): make playbook key collision reporting deterministic diff --git a/docs/news/archied/1.22.0.md b/docs/news/1.22.0.md similarity index 83% rename from docs/news/archied/1.22.0.md rename to docs/news/1.22.0.md index 4d251444d..f6dcfb958 100644 --- a/docs/news/archied/1.22.0.md +++ b/docs/news/1.22.0.md @@ -1,6 +1,8 @@ -# archied 1.22.0 +# 1.22.0 -Released 2026-09-03. [All news](../index.md) +Released 2026-09-03. [All news](index.md) + +### archied - feat(telegram): support secret refs for bot tokens (#705) - fix(update): make daemon rollback schema-safe (#704) diff --git a/docs/news/archied/1.23.0.md b/docs/news/1.23.0.md similarity index 63% rename from docs/news/archied/1.23.0.md rename to docs/news/1.23.0.md index 98f216565..ca6499a14 100644 --- a/docs/news/archied/1.23.0.md +++ b/docs/news/1.23.0.md @@ -1,6 +1,8 @@ -# archied 1.23.0 +# 1.23.0 -Released 2026-09-12. [All news](../index.md) +Released 2026-09-12. [All news](index.md) + +### archied Archied is no longer a single process. The State Store (`archie-state-store`) now owns `archie.db` outright, the Gateway serves its contract over @@ -9,7 +11,7 @@ authenticated gRPC, and the dashboard ships as a standalone UI Service and addressable before `archied` will start clean. See `deployments/` for the supported profiles. -### Service decomposition +### archied — Service decomposition - feat(contracts): add gateway service seams and protobuf toolchain - feat(gateway): extract ChatContract service @@ -33,7 +35,7 @@ supported profiles. - feat(messaging): migrate gateway session persistence onto domain types - feat(gateway): flip channel boundary onto messaging.Message -### Pull request review +### archied — Pull request review - feat(gateway): operator-triggered PR review with selectable reviewer model - feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview) @@ -42,7 +44,7 @@ supported profiles. - fix(archied): share one PR reviewer across channels; harden forge and worktree - fix(workflow): order findings before footer; test the report stash -### Dashboard +### archied — Dashboard - feat(webui): render configuration from a published snapshot - feat(staterpc): carry the dashboard's configuration snapshot @@ -54,7 +56,7 @@ supported profiles. - feat(webui): add /health and /health/detailed readiness endpoints (#717) - fix(webui): distinguish refused vs broken task actions, handle 401 (#753) -### Daemon, gateway and workflow +### archied — Daemon, gateway and workflow - feat(archied): add shutdown watchdog that force-exits a hung graceful shutdown (#716) - feat(archied): serve the daemon's own health endpoint @@ -72,3 +74,37 @@ supported profiles. - fix(gateway): share NATS and session ownership - fix(update): probe the dashboard's real address after a self-update - fix(store): migrate binding owner and repo columns + +### archie-agent + +The agent runtime now reaches task state through the State Store gRPC contract +(`STATE_STORE_URL`/`STATE_STORE_TOKEN`, injected by the daemon) instead of the +NATS `storerpc` transport, which is deleted. Credentials handed to a task +container are scoped to that task rather than being the daemon's own token. +Running a 1.23.0 daemon against an older agent image will not work; rebuild or +pull the `archie-agent` image with this release. + +- feat(state-store): generalize storerpc as the State Store gRPC contract (#770) +- feat(state-store): stand up archie-state-store binary and own archie.db (#771) +- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774) +- fix(state-store): task-scope container credentials, stream large capture lists, validate Update +- fix(staterpc): attach the bearer token to State Store streams +- feat(staterpc): carry the dashboard's configuration snapshot +- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754) +- refactor(store): move the producer-owned contracts to internal/contracts/store/v1 +- feat(contracts): add gateway service seams and protobuf toolchain +- fix(gateway): drop services.gateway.mode, remote is the only transport +- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview) +- feat(gateway): operator-triggered PR review with selectable reviewer model +- feat(workflow): surface adversarial review findings on the PR body +- feat(workflow): review calibration, checked properties and style nits out of contract +- fix(workflow): order findings before footer; test the report stash +- fix(archied): share one PR reviewer across channels; harden forge and worktree +- feat(worktree): Resume re-syncs a worktree onto its branch tip +- feat(telegram): support secret refs for bot tokens (#705) +- feat(gateway): wire progressive tool disclosure (bridge tools) +- feat(archied): serve the daemon's own health endpoint +- feat(archieui): standalone UI process over remote Gateway and State Store +- refactor(archied): move webhook capture intake to the process that owns work intake +- refactor(ui): sever the archie-ui binary from every daemon runtime package +- fix(archieui): resolve service tokens from env, without requiring a config file diff --git a/docs/news/archied/1.24.0.md b/docs/news/1.24.0.md similarity index 93% rename from docs/news/archied/1.24.0.md rename to docs/news/1.24.0.md index 799f2003c..cd7ec8173 100644 --- a/docs/news/archied/1.24.0.md +++ b/docs/news/1.24.0.md @@ -1,6 +1,8 @@ -# archied 1.24.0 +# 1.24.0 -Released 2026-09-12. [All news](../index.md) +Released 2026-09-12. [All news](index.md) + +### archied Makes 1.23.0 deployable. That release split archied into separate processes, but the self-updater still installed only the `archied` binary and restarted diff --git a/docs/news/archied/1.25.0.md b/docs/news/1.25.0.md similarity index 76% rename from docs/news/archied/1.25.0.md rename to docs/news/1.25.0.md index 196ae6299..72fd44fd0 100644 --- a/docs/news/archied/1.25.0.md +++ b/docs/news/1.25.0.md @@ -1,6 +1,8 @@ -# archied 1.25.0 +# 1.25.0 -Released 2026-09-15. [All news](../index.md) +Released 2026-09-15. [All news](index.md) + +### archied - fix(update): resolve releases without a checkout, and fail loudly when it cannot - fix(update): back up the task store the daemon actually uses, or refuse @@ -12,3 +14,8 @@ tags to resolve to one commit whenever both components changed, which refused every update once the two newest releases diverged -- a deployment stuck on 1.22.0 could not take any update. Each component now builds from its own approved tag. + +### archie-agent + +- chore: no user-facing changes; versioned so the 1.25.0 release tags both + components at the same commit diff --git a/docs/news/archied/1.26.0.md b/docs/news/1.26.0.md similarity index 66% rename from docs/news/archied/1.26.0.md rename to docs/news/1.26.0.md index c8040223a..3583a0b8d 100644 --- a/docs/news/archied/1.26.0.md +++ b/docs/news/1.26.0.md @@ -1,6 +1,8 @@ -# archied 1.26.0 +# 1.26.0 -Released 2026-09-17. [All news](../index.md) +Released 2026-09-17. [All news](index.md) + +### archied - fix(webui): publish per-identity forges so multi-identity task rows keep their links - feat(config): add [scheduling] config block @@ -83,3 +85,49 @@ built for, configuration no longer accepts a secret value from the command line, and a provider whose credential is missing is disabled rather than refusing to boot. A secret engine that panics is now recovered instead of crashing the daemon. + +### archie-agent + +- feat(config): add [scheduling] config block +- fix(webui): count every chat front-end in the published projection +- fix(scheduling): respect configuration ownership +- feat(ratelimit): wire per-identity inbound rate limiting into the gateway +- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it +- fix(daemon): carry kind/label routing bindings to the process that routes +- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone +- fix(logging): keep the live descriptor open across a failed rotation +- fix(agentworker): wire configured tool-result policy into worker's LoopRunner +- refactor(staterpc): delete the superseded single-token auth interceptor +- refactor(tools): delete unreachable dispatch/gating engine +- feat(channels): wire chat.webhook route config through to the gateway +- refactor(tools): delete unreachable AST-based tool discovery +- refactor(tools): delete unused plugin-tool registration API from builtin.Registry +- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted) +- fix(staterpc): preserve marshal_error marker in eventDataJSON +- fix(gate): validate finding level and share the blocking threshold +- fix(tools/provider/mcp): preserve MCP binary tool results for delivery +- refactor(tools/mcp): delete unreachable MCP adaptation path +- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path +- refactor(skillbuild): delete dead AugmentRegistry path +- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout +- refactor(binding): delete dead Matcher.Overlaps method +- refactor(forge): delete dead CreateIssue surface +- fix(mcp): cancel in-flight SSE reconnect on Stop +- fix(container): enforce MaxUptime lifetime cap with a timer +- refactor(forge): delete the unwired RepliesAfter surface +- refactor(config): delete the two decoded-but-unread policy fields + +The runtime carries a smaller, more focused set of changes than the same +version's archied entry: agent-side tool-result policy is now wired into the +worker's loop, MCP binary tool results survive to delivery, the container +`MaxUptime` lifetime cap is enforced with a timer, and a scheduled run records +completion so it does not re-fire each tick. + +Note that several bullets above name config, webui and ratelimit packages. Those +are attributed here by the release tool's package-closure rule (`go list -deps` +over the agent binary), not because the agent owns them; the substantive +runtime changes are the worker, MCP, container and scheduling fixes. + +This entry also confirms the removal of the dead `IncrementRetryCount` State +Store RPC, which the agent reaches through `staterpc` rather than by calling it +directly. diff --git a/docs/news/archied/1.27.0.md b/docs/news/1.27.0.md similarity index 84% rename from docs/news/archied/1.27.0.md rename to docs/news/1.27.0.md index 150404c91..a1e9c6802 100644 --- a/docs/news/archied/1.27.0.md +++ b/docs/news/1.27.0.md @@ -1,8 +1,8 @@ -# archied 1.27.0 +# 1.27.0 -Released 2026-09-17. [All news](../index.md) +Released 2026-09-17. [All news](index.md) -### Dashboard task logs +### archied — Dashboard task logs - Task logs are readable from the dashboard again, through a new State Store read contract (`ReadTaskLog`, `StreamTaskLogContent`) rather than the UI @@ -14,7 +14,7 @@ Released 2026-09-17. [All news](../index.md) distinguishable ("cannot read" answers 503, "no log" answers 404) instead of both rendering as a claim about a configuration setting. -### Telegram output +### archied — Telegram output - Tool results are summarised rather than quoted: a search reports how many matches came back, a truncated result reports the tool's own total. The @@ -27,7 +27,7 @@ Released 2026-09-17. [All news](../index.md) frame, which previously appeared to begin mid-sentence. - An error response from the log download no longer ships as a `.log` file. -### Readiness and shutdown +### archied — Readiness and shutdown - The disk probe reports per-filesystem results and checks the root filesystem as well as the work directory, so a full root is no longer invisible. @@ -36,9 +36,15 @@ Released 2026-09-17. [All news](../index.md) - The shutdown-watchdog test no longer races the Go scheduler, which was intermittently failing the quality gate and parking work unrelated to it. -### Other +### archied — Other - Messages persist the channel-native sender id. - go-telegram/bot bumped to v1.27.0, fixing a streaming bug where the multipart body could not be replayed and `sendMessage`/`editMessageText` failed until the connection dropped. + +### archie-agent + +- The per-task runtime picks up the new State Store task-log read contract, so + the sandboxed agents share one log-reading path with the daemon and the + dashboard. diff --git a/docs/news/archied/1.28.0.md b/docs/news/1.28.0.md similarity index 67% rename from docs/news/archied/1.28.0.md rename to docs/news/1.28.0.md index 4de2280c2..adcbd1313 100644 --- a/docs/news/archied/1.28.0.md +++ b/docs/news/1.28.0.md @@ -1,8 +1,8 @@ -# archied 1.28.0 +# 1.28.0 -Released 2026-09-19. [All news](../index.md) +Released 2026-09-19. [All news](index.md) -### Task detail and attempt attribution +### archied — Task detail and attempt attribution - New per-run task detail page, showing each attempt's own events, changes and configuration rather than a single merged view. @@ -11,7 +11,7 @@ Released 2026-09-19. [All news](../index.md) - The task detail page remounts when the task id changes, so switching tasks does not leave the previous one's data on screen. -### Configuration +### archied — Configuration - Services are keyed by name through a registry, so the State Store and Gateway listen addresses are configurable rather than fixed. @@ -21,13 +21,13 @@ Released 2026-09-19. [All news](../index.md) snapshot other readers are holding. - The service context is enforced at registration. -### Logging and park reasons +### archied — Logging and park reasons - A parked run's reason is recorded in its own attempt log, in both the daemon and the workflow, so "why did this park?" is answerable from the task itself. - `TaskRegistry.Write` takes the caller's context. -### Worktrees and containers +### archied — Worktrees and containers - Retries recover from path-type conflicts instead of failing opaquely, and the underlying cause is no longer masked. @@ -36,14 +36,14 @@ Released 2026-09-19. [All news](../index.md) through the grace period, and teardown is claimed once rather than by cancelling a timer. -### Daemon and startup +### archied — Daemon and startup - Every identity's forge and repos are swept at startup, including the root forge. - A cancelled startup is no longer reported as an exhausted sweep budget; an exhausted budget names itself as the cause. -### Other +### archied — Other - `grep` can use the workspace codesearch index. - Forge labels are matched when namespaced, so label-driven routing works for @@ -58,3 +58,22 @@ Released 2026-09-19. [All news](../index.md) - The UI finishes its Preact port; the imperative DOM layer is deleted. - Collection fields decoded over the State Store gRPC contract are never nil slices, so an empty collection marshals as `[]` rather than `null`. + +### archie-agent + +- The sandboxed runtime picks up the attempt-attribution contract, so the events + and changes an agent produces are recorded against the attempt that produced + them. +- `grep` can use the workspace codesearch index. +- A worktree is handed back on every sandbox exit, and container teardown is + claimed once — a released container's reaper is cancelled rather than + re-firing during the grace period. +- Retries recover from worktree path-type conflicts instead of failing + opaquely. +- A parked workflow run records its park reason in its own log. +- Triage criteria distinguish the workflows, and a workflow is required when a + code change is needed. +- Namespaced forge labels match when routing by kind. +- The `ARCHIE_REACTIONS` fan-out stream is provisioned. +- Collection fields decoded over the State Store gRPC contract are never nil + slices, so an empty collection marshals as `[]` rather than `null`. diff --git a/docs/news/archied/1.29.0.md b/docs/news/1.29.0.md similarity index 81% rename from docs/news/archied/1.29.0.md rename to docs/news/1.29.0.md index f7bc3ddac..5e0662ca7 100644 --- a/docs/news/archied/1.29.0.md +++ b/docs/news/1.29.0.md @@ -1,8 +1,8 @@ -# archied 1.29.0 +# 1.29.0 -Released 2026-09-19. [All news](../index.md) +Released 2026-09-19. [All news](index.md) -### Security +### archied — Security - `google.golang.org/grpc` bumped past `v1.84.0` to patch [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443), a server panic via a @@ -11,7 +11,7 @@ Released 2026-09-19. [All news](../index.md) pre-release commit that does (`v1.85.0-dev.0.20260825072537-93e31b48545e`) until `grpc-go` cuts `v1.85.0`. -### Memory engine unification +### archied — Memory engine unification One memory engine, addressed by four typed scopes (global, agent, user, agent-user), replaces the two disconnected stores that previously existed: @@ -41,15 +41,25 @@ with no scope model. and the rendered block's byte cap was checked before template escaping rather than after, letting the escaped block exceed it. -### Work intake +### archied — Work intake - feat(workintake): define review reaction envelope - feat(workintake): authorize review reactions by owned PR -### Cleanup +### archied — Cleanup - Deleted the unwired plugin capability-host health surface (`Host.Health`/`Host.Manifests`/`ModuleStatus`) and the `Module.Health` chain it fed -- including the `mcp`/`builtin` tool-provider health implementations and their aggregation in `tools/provider.Registry` -- none of which had ever had a production caller (#882). + +### archie-agent + +- The sandboxed runtime picks up the review-reaction envelope and its + owned-PR authorization, so an agent can only react to reviews on pull + requests it opened itself. +- `google.golang.org/grpc` bumped past `v1.84.0` to patch + [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443) (shared dependency + with `archied`; the pre-release commit is pinned pending a stable + `v1.85.0`). diff --git a/docs/news/archie/1.3.0.md b/docs/news/1.3.0.md similarity index 78% rename from docs/news/archie/1.3.0.md rename to docs/news/1.3.0.md index 6e05c3d9f..e673d0090 100644 --- a/docs/news/archie/1.3.0.md +++ b/docs/news/1.3.0.md @@ -1,6 +1,13 @@ -# archie-agent 1.3.0 +# 1.3.0 -Released 2026-08-08. [All news](../index.md) +Released 2026-08-08. [All news](index.md) + +### archied (released 2026-07-31) + +- fix(memory): replace framework-specific names with generic equivalents +- feat: unify provider and model selection + +### archie-agent - feat(curator): engine family contract, registry, and runtime - feat(curator): trigger accounting — primary-input wake path diff --git a/docs/news/1.3.1.md b/docs/news/1.3.1.md new file mode 100644 index 000000000..b316c1493 --- /dev/null +++ b/docs/news/1.3.1.md @@ -0,0 +1,7 @@ +# 1.3.1 + +Released 2026-07-31. [All news](index.md) + +### archied + +- fix(telegram): omit empty model picker markup diff --git a/docs/news/archied/1.30.0.md b/docs/news/1.30.0.md similarity index 79% rename from docs/news/archied/1.30.0.md rename to docs/news/1.30.0.md index 4f1709cb3..b7a66ae26 100644 --- a/docs/news/archied/1.30.0.md +++ b/docs/news/1.30.0.md @@ -1,8 +1,8 @@ -# archied 1.30.0 +# 1.30.0 -Released 2026-09-20. [All news](../index.md) +Released 2026-09-20. [All news](index.md) -### Messaging Service extraction completed +### archied — Messaging Service extraction completed Telegram, email and webhook no longer run inside the daemon. They run in `archie-messaging` and reach the daemon through the Gateway's `ChatContract` @@ -27,7 +27,7 @@ both need a component's real running version, and the only versions this process can obtain are another binary's stamps. See `docs/architecture/migration-decisions.md`. -### Configuration +### archied — Configuration - `diff_cap_lines = 0` now switches the cap off, as the dashboard and the workflow step have always documented. It was a plain `int`, so the defaults @@ -46,7 +46,7 @@ process can obtain are another binary's stamps. See - `[health].dependency_timeout` makes the daemon's readiness probe timeout configurable, matching the extracted services. -### Chat rendering +### archied — Chat rendering - `/status` and `/tasks` are line-oriented reports but separated lines with a plain newline, which is CommonMark's soft wrap: the Telegram renderer joined @@ -57,14 +57,14 @@ process can obtain are another binary's stamps. See log; unbounded, one parked task pushed every other task out of the reply. The full reason is unchanged on the task, in `task_list` and on the dashboard. -### Review +### archied — Review - Review findings are posted as line-anchored PR comments with suggested fixes, and a suggestion must be single-line -- GitHub applies a multi-line suggestion only up to its first line, silently corrupting the file (#891). - The remediate workflow handles PR review comments and requested changes. -### /status health surface +### archied — /status health surface `/status` reports the live broker connection and the last-known outcome of this process's chat-model calls, alongside the queue depth and runtime block (#892). @@ -87,7 +87,7 @@ process, which has no container pool and no poll loop. The command description says what actually appears; restoring the rest needs a cross-process health contract. -### Dashboard and containers +### archied — Dashboard and containers - The served lifecycle vocabulary reaches an already-painted page, the page registry matches the routes, and the build verifies `ui/dist` is fresh @@ -95,7 +95,7 @@ contract. - The container reaper no longer deletes teardown bookkeeping early, so a released container is not torn down twice (#893). -### Build +### archied — Build - `task fmt` runs `golangci-lint fmt` -- the same engine and configuration the gate checks with. Standalone `gofumpt` cannot reproduce gci's import @@ -104,9 +104,28 @@ contract. - `goimports` is deliberately absent from the formatter set: it re-reads and re-parses the module index once per file, ~135s across this tree. -### Fixed +### archied — Fixed - `Config.Clone` left the new diff-cap pointers aliased, so a clone could write through to the published snapshot (#902). - A curator asking for a completion on a daemon with no configured provider panicked the process; it now returns an error. + +### archie-agent + +- The sandboxed runtime picks up line-anchored review comments: a finding is + posted against the line it is about, with a suggested fix where it has one, + and a suggestion is rejected unless it is single-line -- GitHub applies a + multi-line suggestion only up to its first line, silently corrupting the + file (#891). +- `diff_cap_lines` is an optional value in the shared config the runtime + reconstructs, so an explicit `0` means "no cap" rather than being rewritten + to the default. **Behaviour change** for a repo that set `0` expecting + unlimited and was silently getting 400 (#899). +- A diff-cap park names a remedy that exists: a parked task's actions are + retry, abandon and reject, so the reason no longer says "approve manually". +- A released container is not torn down twice -- the reaper no longer deletes + teardown bookkeeping before `Release` is finished with it (#893). +- Build toolchain: `gofumpt` and `golangci-lint` are pinned as one matched + pair, and `task fmt` uses the same engine the gate checks with, so the + runtime's own gate is satisfiable (#901). diff --git a/docs/news/archied/1.31.0.md b/docs/news/1.31.0.md similarity index 75% rename from docs/news/archied/1.31.0.md rename to docs/news/1.31.0.md index a2bd80cc1..7f615cf7a 100644 --- a/docs/news/archied/1.31.0.md +++ b/docs/news/1.31.0.md @@ -1,8 +1,8 @@ -# archied 1.31.0 +# 1.31.0 -Released 2026-09-22. [All news](../index.md) +Released 2026-09-22. [All news](index.md) -### Dashboard replaced: Preact -> Vue 3 + shadcn-vue +### archied — Dashboard replaced: Preact -> Vue 3 + shadcn-vue The dashboard is now a Vue 3 application built on shadcn-vue. This is the large piece of this release; it touches every page. @@ -22,7 +22,7 @@ large piece of this release; it touches every page. - The capture pane is bound to the list it sits beside and reads beside it, not over it. -### Events is one page with three tabs +### archied — Events is one page with three tabs - Inspector, Bindings and Mappings are now tabs of a single **Events** page. - The nav entry is always live, the tabs prune by capability, and the three old @@ -32,7 +32,7 @@ large piece of this release; it touches every page. - `feat(tools)`: a capture-intake sender exists for exercising the Events surfaces. -### The channel travels with the message +### archied — The channel travels with the message `SessionSource.Platform` -- the first component of the session natural key, and the column `GetByChannel` filters on -- was a constant `"web"`, because one @@ -56,7 +56,7 @@ not be read back by the turn that wrote it, because that turn resolved no - Deliberately unchanged: `TurnRunnerConfig.Channel` still keys tool availability, so no channel gains or loses a tool in this release. -### Control plane: runtime administration, history, and derived schemas +### archied — Control plane: runtime administration, history, and derived schemas - The State Store's gRPC server now carries runtime administration, and each process reports which settings version it is running; the dashboard shows it. @@ -69,7 +69,7 @@ not be read back by the turn that wrote it, because that turn resolved no database-owned settings. - Forge intake settings that nothing reads are now rejected at load. -### Configuration: judged where it is owned +### archied — Configuration: judged where it is owned - The runtime config overlay is deleted; database-owned settings are judged at the layer that owns them rather than on the file load path. @@ -78,14 +78,14 @@ not be read back by the turn that wrote it, because that turn resolved no - The default config path is resolved in one place, and the channel document has its own shape. -### State Store: offline backup, restore, validate and rollback +### archied — State Store: offline backup, restore, validate and rollback - New offline backup / restore / validate / rollback path. - `validate` runs boot's own gate; it no longer replaces the database, reads a kind the store does not hold as its seed, or touches the daemon's log. - The recovery control-plane server is built on the shared step vocabulary. -### Workflow: one step vocabulary and a `gate.diff-rules` replacement +### archied — Workflow: one step vocabulary and a `gate.diff-rules` replacement - The step vocabulary is owned by a family manager registered at each composition root, replacing `.archie/gate.go` with `gate.diff-rules`, which @@ -95,13 +95,13 @@ not be read back by the turn that wrote it, because that turn resolved no - The schedules resource skips the legacy cron jobs it cannot hold, and the scheduling policy carries the label its trigger pairs with. -### EDA: the playbook coordinator reaches production selection +### archied — EDA: the playbook coordinator reaches production selection - The playbook coordinator is wired into production workflow selection, so a matching playbook decides a real task's workflow at the daemon's definition pin, inheriting idempotency from `TaskEnvelope`. -### Reliability and operations +### archied — Reliability and operations - `cronstore` writes a schedule interval as a duration, not nanoseconds -- a persisted `1m` no longer round-trips as `60000000000`. @@ -119,3 +119,31 @@ not be read back by the turn that wrote it, because that turn resolved no tool-settings projection. - Resource request-ID idempotency keys are scoped to their kind. - The session curator addresses memory by the deployment's bot user. + +### archie-agent + +The sandboxed runtime links the same shared packages as archied, so this +release carries the control-plane and workflow changes alongside it: + +- Runtime administration over the State Store's gRPC server, resource history, + and control-plane apply status on the store contract. +- The shared step vocabulary, owned by a family manager registered at each + composition root, and `gate.diff-rules` in place of `.archie/gate.go` + (fails closed on a change it never read). +- The workflow pin crosses the wire. + +Runtime-specific changes: + +- `refactor(plugin)`: the unused `Registry` type is deleted. +- `yaegiutil` refuses incomplete Yaegi interface wrappers at load rather than + running them. +- The runtime config overlay is deleted. +- The state store dial installs client keepalive, and the server policy accepts + the dialer's pings. +- The MCP client supports per-server `parallel_tool_calls`. +- A late max-uptime callback no longer resurrects teardown state. +- A webhook route path no longer becomes a sender identity. + +Note: the `archie-agent` image is rebuilt by this tag through CI +(`.github/workflows/deploy.yml`); a gateway-only release would not have rebuilt +it. `docker compose pull agent` is required to pick it up. diff --git a/docs/news/archied/1.32.0.md b/docs/news/1.32.0.md similarity index 70% rename from docs/news/archied/1.32.0.md rename to docs/news/1.32.0.md index fc1230dc7..f164c6da9 100644 --- a/docs/news/archied/1.32.0.md +++ b/docs/news/1.32.0.md @@ -1,8 +1,8 @@ -# archied 1.32.0 +# 1.32.0 -Released 2026-09-22. [All news](../index.md) +Released 2026-09-22. [All news](index.md) -### EDA: playbook action ids, and a dispatch idempotency ledger +### archied — EDA: playbook action ids, and a dispatch idempotency ledger - **Action ids (J1).** Every action a later action references must now carry an `id`. Ids are validated at load -- unique and stable-identifier-shaped -- and a `when`/`args` expression @@ -24,3 +24,15 @@ Released 2026-09-22. [All news](../index.md) **Behaviour change:** a playbook whose actions reference `actions.` without declaring that id, declare a duplicate id, or index `actions` with a non-literal value now fails to load instead of failing at dispatch time. + +### archie-agent + +The sandboxed runtime links `storecontract` and `staterpc`, so it carries the dispatch-ledger +contract alongside archied: + +- The shared `store.ErrAlreadyDispatched` sentinel now describes both dedup ledgers -- + `binding_dispatches` per `(binding_id, capture_id)`, and `playbook_dispatches` per + `(playbook_id, playbook_version, event_id, action_id)`. Each is an at-most-once guarantee. +- `RecordPlaybookDispatch` is part of the store contract the runtime builds against. + +archied and archie-agent move together in this release. diff --git a/docs/news/archied/1.32.1.md b/docs/news/1.32.1.md similarity index 92% rename from docs/news/archied/1.32.1.md rename to docs/news/1.32.1.md index 6cc1c39a5..2f057f36f 100644 --- a/docs/news/archied/1.32.1.md +++ b/docs/news/1.32.1.md @@ -1,8 +1,8 @@ -# archied 1.32.1 +# 1.32.1 -Released 2026-09-22. [All news](../index.md) +Released 2026-09-22. [All news](index.md) -### Host packaging: `archie-messaging` now ships and updates +### archied — Host packaging: `archie-messaging` now ships and updates - `cmd/archie-messaging` is included in the distribution zip, and `scripts/archie-update-install` installs and restarts it. diff --git a/docs/news/archied/1.33.0.md b/docs/news/1.33.0.md similarity index 92% rename from docs/news/archied/1.33.0.md rename to docs/news/1.33.0.md index c9e881eb3..a05828b56 100644 --- a/docs/news/archied/1.33.0.md +++ b/docs/news/1.33.0.md @@ -1,8 +1,8 @@ -# archied 1.33.0 +# 1.33.0 -Released 2026-09-22. [All news](../index.md) +Released 2026-09-22. [All news](index.md) -### EDA: playbook action arguments are compiled at load (J2) +### archied — EDA: playbook action arguments are compiled at load (J2) - A playbook action may now declare `args`, compiled as CEL expressions when the playbook loads. `args` and `when` share one compilation path and one evaluation context, so an expression written diff --git a/docs/news/archied/1.34.0.md b/docs/news/1.34.0.md similarity index 92% rename from docs/news/archied/1.34.0.md rename to docs/news/1.34.0.md index 674475cca..95beffe7c 100644 --- a/docs/news/archied/1.34.0.md +++ b/docs/news/1.34.0.md @@ -1,8 +1,8 @@ -# archied 1.34.0 +# 1.34.0 -Released 2026-09-22. [All news](../index.md) +Released 2026-09-22. [All news](index.md) -### Dashboard: an actionable authentication failure state +### archied — Dashboard: an actionable authentication failure state - An unauthenticated **document** request now receives a self-contained HTML page with a paste-the-token form, instead of plain text. Previously the whole dashboard -- `index.html`, the diff --git a/docs/news/archied/1.35.0.md b/docs/news/1.35.0.md similarity index 76% rename from docs/news/archied/1.35.0.md rename to docs/news/1.35.0.md index fc145c0f7..6baa05ffb 100644 --- a/docs/news/archied/1.35.0.md +++ b/docs/news/1.35.0.md @@ -1,8 +1,8 @@ -# archied 1.35.0 +# 1.35.0 -Released 2026-09-22. [All news](../index.md) +Released 2026-09-22. [All news](index.md) -### The Messaging Service is severed from the store and workflow runtime +### archied — The Messaging Service is severed from the store and workflow runtime - `cmd/archie-messaging` no longer links `modernc.org/sqlite`, `internal/store`, `internal/domain/workflow` or `internal/agentexec`. All four arrived through a single import of @@ -12,7 +12,7 @@ Released 2026-09-22. [All news](../index.md) - The resource documents are type-aliased back into the app package, so there is one definition read under two names rather than a copy per side. -### Channel lifecycle reaches the dashboard +### archied — Channel lifecycle reaches the dashboard - The Messaging Service reports each channel's state, recorded **per channel**: one channel's failure marks only itself, a channel that cannot start is marked failed **with its reason** rather than only @@ -26,7 +26,7 @@ Released 2026-09-22. [All news](../index.md) with a reason rather than accepting and ignoring it. `ReloadSupported` was previously declared **by name**, so a channel could advertise reload with nothing behind it; one function now decides both. -### Action playbooks: a second playbook shape, with typed results +### archied — Action playbooks: a second playbook shape, with typed results - A playbook is now one of two shapes: a **workflow playbook** (exactly one `workflow` action, unchanged) or an **action playbook** (one or more `module` actions in order). A playbook does not @@ -42,3 +42,15 @@ Released 2026-09-22. [All news](../index.md) - `ModuleRegistry.DecodeResult` turns a kind's flat map result into its typed `Result` before a later expression reads it. Without it a typed read evaluated against a shape the run never produces, and so silently read null. + +### archie-agent + +The sandboxed runtime links the same shared packages as archied, so this release carries the +channel-lifecycle store contract and the stricter action-load errors with it: + +- The channel-status store contract (`PutChannelStatus`/`ListChannelStatus`) and its replace-the-set + semantics. +- Authoritative module ids and stricter action load errors: a misspelled result field, an unknown id, + or a dynamic `actions` read now fails the playbook load rather than the dispatch. + +archied and archie-agent move together in this release. diff --git a/docs/news/archied/1.36.0.md b/docs/news/1.36.0.md similarity index 85% rename from docs/news/archied/1.36.0.md rename to docs/news/1.36.0.md index f1cf3650b..b26e6ba77 100644 --- a/docs/news/archied/1.36.0.md +++ b/docs/news/1.36.0.md @@ -1,8 +1,8 @@ -# archied 1.36.0 +# 1.36.0 -Released 2026-09-22. [All news](../index.md) +Released 2026-09-22. [All news](index.md) -### The dashboard declares tools an in-browser agent can call +### archied — The dashboard declares tools an in-browser agent can call - The dashboard registers **seven WebMCP tools**. Read-only: `list_tasks`, `get_task`, `recent_events`, `daemon_health`. Recovery: `retry_task`, `stop_task`, `cancel_task`. An agent @@ -14,7 +14,7 @@ Released 2026-09-22. [All news](../index.md) agent's call and a page script's call reach the server identically. Tools therefore record the signed-in identity and a source, and **never** that an agent acted. -### Binaries built by the development build task can be updated +### archied — Binaries built by the development build task can be updated - `task build` passed the `installtype` stamp for three of six commands, so `archie-messaging`, `archie-state-store` and `archie-ui` were built without it. An unstamped binary reports `unknown` diff --git a/docs/news/archied/1.37.0.md b/docs/news/1.37.0.md similarity index 88% rename from docs/news/archied/1.37.0.md rename to docs/news/1.37.0.md index 2303cffe3..412080f89 100644 --- a/docs/news/archied/1.37.0.md +++ b/docs/news/1.37.0.md @@ -1,8 +1,8 @@ -# archied 1.37.0 +# 1.37.0 -Released 2026-09-22. [All news](../index.md) +Released 2026-09-22. [All news](index.md) -### A request is attributed to the identity that made it +### archied — A request is attributed to the identity that made it - **A browser can sign in, and an action taken through it records the person.** The dashboard validates a provider-issued token, resolves it to an identity, and attaches it to the request; the task-action record @@ -18,7 +18,7 @@ Released 2026-09-22. [All news](../index.md) - The acting identity is derived from the presented credential and **never** from a request field: a body carrying `actor`, `actor_id`, `identity` and an `X-Archie-Actor` header still cannot choose it. -### A host install now works, and an update refuses a host it cannot keep consistent +### archied — A host install now works, and an update refuses a host it cannot keep consistent - `install.sh` writes and enables **all five** host units; previously it seeded only `archied.service`, so a fresh host ran one service of five and an operator applied the rest by hand from a runbook. The runbook is @@ -30,14 +30,14 @@ Released 2026-09-22. [All news](../index.md) - The packaged, installer and updater command lists are pinned by a test, so a service added to one and not the others fails the gate instead of shipping a partial install. -### A release image can be traced to a commit +### archied — A release image can be traced to a commit - The publish step derives the commit by **dereferencing the ref** rather than reading `github.sha`, because every release tag in this repository is annotated and a tag's object id is not a commit. An immutable `sha-` tag is published alongside `:latest`, and a build with no release tag is stamped `dev+` rather than a bare `dev` that identified nothing. -### Curator definitions are data, not a second registry +### archied — Curator definitions are data, not a second registry - Curator definitions may come from configuration or code and run through **one** engine into the existing registry — no parallel authority and no second config reader. A definition declares its tools, and an diff --git a/docs/news/archie/1.4.0.md b/docs/news/1.4.0.md similarity index 88% rename from docs/news/archie/1.4.0.md rename to docs/news/1.4.0.md index a4324433a..affd38d24 100644 --- a/docs/news/archie/1.4.0.md +++ b/docs/news/1.4.0.md @@ -1,6 +1,12 @@ -# archie-agent 1.4.0 +# 1.4.0 -Released 2026-08-10. [All news](../index.md) +Released 2026-08-10. [All news](index.md) + +### archied (released 2026-07-31) + +- fix(secrets): wire provider credentials through engines + +### archie-agent - feat(gateway): tool-approval gate, session tools for chat, and /delete command - feat(gateway): make chat turns durable and idempotent diff --git a/docs/news/1.4.1.md b/docs/news/1.4.1.md new file mode 100644 index 000000000..9deb9ce57 --- /dev/null +++ b/docs/news/1.4.1.md @@ -0,0 +1,7 @@ +# 1.4.1 + +Released 2026-07-31. [All news](index.md) + +### archied + +- fix(catalog): match SDK provider fallback diff --git a/docs/news/archied/1.5.0.md b/docs/news/1.5.0.md similarity index 96% rename from docs/news/archied/1.5.0.md rename to docs/news/1.5.0.md index 812393877..aa01251c7 100644 --- a/docs/news/archied/1.5.0.md +++ b/docs/news/1.5.0.md @@ -1,6 +1,8 @@ -# archied 1.5.0 +# 1.5.0 -Released 2026-08-08. [All news](../index.md) +Released 2026-08-08. [All news](index.md) + +### archied - feat(curator): engine family contract, registry, and runtime - feat(curator): trigger accounting — primary-input wake path diff --git a/docs/news/archied/1.6.0.md b/docs/news/1.6.0.md similarity index 90% rename from docs/news/archied/1.6.0.md rename to docs/news/1.6.0.md index 0275fd116..3150c4164 100644 --- a/docs/news/archied/1.6.0.md +++ b/docs/news/1.6.0.md @@ -1,6 +1,8 @@ -# archied 1.6.0 +# 1.6.0 -Released 2026-08-09. [All news](../index.md) +Released 2026-08-09. [All news](index.md) + +### archied - feat(gateway): tool-approval gate, session tools for chat, and /delete command - fix(webui): close open-redirect in dashboard token-exchange handler diff --git a/docs/news/archied/1.7.0.md b/docs/news/1.7.0.md similarity index 96% rename from docs/news/archied/1.7.0.md rename to docs/news/1.7.0.md index da24c6856..7afd61520 100644 --- a/docs/news/archied/1.7.0.md +++ b/docs/news/1.7.0.md @@ -1,6 +1,8 @@ -# archied 1.7.0 +# 1.7.0 -Released 2026-08-10. [All news](../index.md) +Released 2026-08-10. [All news](index.md) + +### archied - fix(build): install ripgrep where grep.go actually needs it on PATH - fix(webui): Send button no longer passes its click event to sendMessage diff --git a/docs/news/archied/1.8.0.md b/docs/news/1.8.0.md similarity index 93% rename from docs/news/archied/1.8.0.md rename to docs/news/1.8.0.md index 3de6eb1fa..bc3188226 100644 --- a/docs/news/archied/1.8.0.md +++ b/docs/news/1.8.0.md @@ -1,6 +1,8 @@ -# archied 1.8.0 +# 1.8.0 -Released 2026-08-15. [All news](../index.md) +Released 2026-08-15. [All news](index.md) + +### archied - feat(archied): add -version so the installed build can be read from a shell - fix(webui): rebuild the Configuration page layout so values stop colliding diff --git a/docs/news/1.9.0.md b/docs/news/1.9.0.md new file mode 100644 index 000000000..b158dd210 --- /dev/null +++ b/docs/news/1.9.0.md @@ -0,0 +1,20 @@ +# 1.9.0 + +Released 2026-08-15. [All news](index.md) + +### archied + +- fix(webui): style tool-call failure from a structured field, not a string prefix +- fix(config,webui): make show_tool_calls one cross-channel setting +- fix(telegram): guarantee no message is stranded on gateway stop/restart +- fix(telegram): use NewRequestWithContext to satisfy noctx +- refactor(webui): decompose handleSSE to cut cognitive complexity + +### archie-agent + +- fix(agent): resolve git dubious-ownership in sandbox containers +- feat(agent): mark the mounted worktree as a git safe directory +- fix(agent): route git safe.directory setup through markWorktreeSafe +- feat(chat): show tool calls inline and stream replies into one message +- refactor(agent): move worker runtime into application layer +- fix(config,webui): make show_tool_calls one cross-channel setting diff --git a/docs/news/archied/1.9.1.md b/docs/news/1.9.1.md similarity index 59% rename from docs/news/archied/1.9.1.md rename to docs/news/1.9.1.md index d91e313e0..bf093a87a 100644 --- a/docs/news/archied/1.9.1.md +++ b/docs/news/1.9.1.md @@ -1,7 +1,13 @@ -# archied 1.9.1 +# 1.9.1 -Released 2026-08-15. [All news](../index.md) +Released 2026-08-15. [All news](index.md) + +### archied - fix(agentworker): forward workflow events across the NATS worker boundary - fix(webui): filter turn_completed noise from the Live Activity SSE feed - feat(releaseupdate): stamp install type at build time, fail closed on unknown + +### archie-agent + +- fix(agentworker): forward workflow events across the NATS worker boundary diff --git a/docs/news/archied/1.9.10.md b/docs/news/1.9.10.md similarity index 81% rename from docs/news/archied/1.9.10.md rename to docs/news/1.9.10.md index e95bad1c9..8d8caf76a 100644 --- a/docs/news/archied/1.9.10.md +++ b/docs/news/1.9.10.md @@ -1,5 +1,7 @@ -# archied 1.9.10 +# 1.9.10 -Released 2026-08-19. [All news](../index.md) +Released 2026-08-19. [All news](index.md) + +### archied - feat(update): `/update` now streams live progress while an update installs, reports a clear version summary (previous/installed, daemon/agent) once the build succeeds, and automatically rolls back and reports the outcome if the restarted daemon fails its post-update health check diff --git a/docs/news/1.9.11.md b/docs/news/1.9.11.md new file mode 100644 index 000000000..6dcbab5e8 --- /dev/null +++ b/docs/news/1.9.11.md @@ -0,0 +1,7 @@ +# 1.9.11 + +Released 2026-08-19. [All news](index.md) + +### archied + +- fix(mcp): persist npx package cache across daemon restarts diff --git a/docs/news/1.9.2.md b/docs/news/1.9.2.md new file mode 100644 index 000000000..499d83028 --- /dev/null +++ b/docs/news/1.9.2.md @@ -0,0 +1,11 @@ +# 1.9.2 + +Released 2026-08-15. [All news](index.md) + +### archied + +- fix(worktree): force checkout so retry recovers from a dirty worktree + +### archie-agent + +- fix(worktree): force checkout so retry recovers from a dirty worktree diff --git a/docs/news/1.9.3.md b/docs/news/1.9.3.md new file mode 100644 index 000000000..9fc3d3eea --- /dev/null +++ b/docs/news/1.9.3.md @@ -0,0 +1,15 @@ +# 1.9.3 + +Released 2026-08-15. [All news](index.md) + +### archied + +- fix(webui): scroll selected command into view on keyboard navigation +- fix(logging): resolve error attrs to their message string, not {} +- feat(agentexec,workflow): surface tool calls on the task timeline + +### archie-agent + +- fix(logging): resolve error attrs to their message string, not {} +- fix(agentworker): back off before refetching a nak'd stage message +- feat(agentexec,workflow): surface tool calls on the task timeline diff --git a/docs/news/1.9.4.md b/docs/news/1.9.4.md new file mode 100644 index 000000000..c329415e4 --- /dev/null +++ b/docs/news/1.9.4.md @@ -0,0 +1,12 @@ +# 1.9.4 + +Released 2026-08-15. [All news](index.md) + +### archied + +- feat(gateway): polish /status command response format +- fix(telegram): preserve URL boundaries in responses + +### archie-agent + +- chore: no user-facing changes diff --git a/docs/news/archied/1.9.5.md b/docs/news/1.9.5.md similarity index 65% rename from docs/news/archied/1.9.5.md rename to docs/news/1.9.5.md index 241b07fb7..57b07326d 100644 --- a/docs/news/archied/1.9.5.md +++ b/docs/news/1.9.5.md @@ -1,6 +1,8 @@ -# archied 1.9.5 +# 1.9.5 -Released 2026-08-16. [All news](../index.md) +Released 2026-08-16. [All news](index.md) + +### archied - refactor(archied): decompose the daemon bootstrap into phased wiring (no behaviour change; splits the ~950-line run() into focused setup phases so complexity linting passes) - refactor(archied): extract the config overlay boot helper and thread context through chat gateway setup @@ -10,3 +12,9 @@ Released 2026-08-16. [All news](../index.md) - fix(indexing): remove the unused code search test runner - fix(tests): use contexts and type assertions in overlay and gateway tests - docs(architecture): document the memory engine family + +### archie-agent + +- refactor: decompose the daemon bootstrap into phased wiring (no behaviour change; complexity-driven restructure) +- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity +- fix(tools): avoid predeclared `max` names diff --git a/docs/news/1.9.6.md b/docs/news/1.9.6.md new file mode 100644 index 000000000..e14cae95a --- /dev/null +++ b/docs/news/1.9.6.md @@ -0,0 +1,11 @@ +# 1.9.6 + +Released 2026-08-16. [All news](index.md) + +### archied + +- fix(update): stamp install type and bound retry backoff + +### archie-agent + +- chore: no user-facing changes diff --git a/docs/news/1.9.7.md b/docs/news/1.9.7.md new file mode 100644 index 000000000..cde52f69e --- /dev/null +++ b/docs/news/1.9.7.md @@ -0,0 +1,11 @@ +# 1.9.7 + +Released 2026-08-17. [All news](index.md) + +### archied + +- chore: no user-facing changes + +### archie-agent + +- chore: no user-facing changes diff --git a/docs/news/1.9.8.md b/docs/news/1.9.8.md new file mode 100644 index 000000000..4e91a519f --- /dev/null +++ b/docs/news/1.9.8.md @@ -0,0 +1,11 @@ +# 1.9.8 + +Released 2026-08-17. [All news](index.md) + +### archied + +- chore: no user-facing changes + +### archie-agent + +- chore: no user-facing changes diff --git a/docs/news/1.9.9.md b/docs/news/1.9.9.md new file mode 100644 index 000000000..515b8ff4c --- /dev/null +++ b/docs/news/1.9.9.md @@ -0,0 +1,11 @@ +# 1.9.9 + +Released 2026-08-18. [All news](index.md) + +### archied + +- fix(telegram): drain live renderer in concurrency test + +### archie-agent + +- chore: no user-facing changes diff --git a/docs/news/archie/1.0.0.md b/docs/news/archie/1.0.0.md deleted file mode 100644 index b8d43e2d1..000000000 --- a/docs/news/archie/1.0.0.md +++ /dev/null @@ -1,6 +0,0 @@ -# archie-agent 1.0.0 - -Released 2026-07-22. [All news](../index.md) - -- feat: ship the isolated agent runtime, NATS RPC boundary, workflow execution, skills, and plugin support -- feat: publish the `archie-agent` container image to the Gitea registry diff --git a/docs/news/archie/1.1.0.md b/docs/news/archie/1.1.0.md deleted file mode 100644 index cd2703499..000000000 --- a/docs/news/archie/1.1.0.md +++ /dev/null @@ -1,12 +0,0 @@ -# archie-agent 1.1.0 - -Released 2026-07-27. [All news](../index.md) - -- feat: add streamed agent execution with typed message events -- feat: add MCP client transports and managed tool-provider discovery -- feat: add memory context scrubbing and normalized memory tool schemas -- feat: add plugin metadata extraction from `metadata.archie.plugins` -- feat: add configurable container networking for daemon-launched runtimes -- fix: preserve valid UTF-8 when clipping runtime output -- fix: make MCP stdio lifecycle, retries, and timeout handling race-safe -- fix: enforce a zero-finding lint and vet baseline diff --git a/docs/news/archie/1.16.1.md b/docs/news/archie/1.16.1.md deleted file mode 100644 index ff06549f7..000000000 --- a/docs/news/archie/1.16.1.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.16.1 - -Released 2026-08-25. [All news](../index.md) - -- fix(agentworker): reconcile task clone ownership after commits diff --git a/docs/news/archie/1.18.0.md b/docs/news/archie/1.18.0.md deleted file mode 100644 index 331eb8467..000000000 --- a/docs/news/archie/1.18.0.md +++ /dev/null @@ -1,6 +0,0 @@ -# archie-agent 1.18.0 - -Released 2026-08-28. [All news](../index.md) - -- feat(logging): cursor pagination and filtering for task_logs -- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29 diff --git a/docs/news/archie/1.19.5.md b/docs/news/archie/1.19.5.md deleted file mode 100644 index dff6202da..000000000 --- a/docs/news/archie/1.19.5.md +++ /dev/null @@ -1,19 +0,0 @@ -# archie-agent 1.19.5 - -Released 2026-09-01. [All news](../index.md) - -- feat(tasks): allow rejecting a task from any non-terminal state -- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta -- fix: go.mod bumped to 1.27.0 and stupid tests removed -- refactor: go modernisation fixes -- refactor: remove unused Operator param. -- fix(plugin): add missing CLAUDE.md reference to plugin engine rule -- fix(app): repoint archied wiring contract test at internal/app/archied -- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet -- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui -- fix(app): repoint capability-host wiring contract test at internal/app/archied -- refactor(lint): extract more helpers to clear nestif/gocyclo findings -- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult -- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization -- fix(lint): noctx fixes and dead-code cleanup -- feat(workflow): adversarial self-review stage before PR open diff --git a/docs/news/archie/1.19.7.md b/docs/news/archie/1.19.7.md deleted file mode 100644 index d5613dca0..000000000 --- a/docs/news/archie/1.19.7.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.19.7 - -Released 2026-09-02. [All news](../index.md) - -- fix(logging): make Tail/Page allocation bound explicit for CodeQL diff --git a/docs/news/archie/1.19.9.md b/docs/news/archie/1.19.9.md deleted file mode 100644 index b7f0527d3..000000000 --- a/docs/news/archie/1.19.9.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.19.9 - -Released 2026-09-02. [All news](../index.md) - -- feat(config): config surface for memory engine selection diff --git a/docs/news/archie/1.2.0.md b/docs/news/archie/1.2.0.md deleted file mode 100644 index 8f97f1cc3..000000000 --- a/docs/news/archie/1.2.0.md +++ /dev/null @@ -1,25 +0,0 @@ -# archie-agent 1.2.0 - -Released 2026-07-31. [All news](../index.md) - -- feat: add MCP client capabilities to archied and archie-agent -- fix: Transition() ignores `from` status guard, allowing lost updates -- fix: skillscript.Run ignores context, cannot be canceled/timed out -- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup -- fix(indexing): surface index config properly and stop silent degradation -- refactor(worktree): replace git shell-out with go-git v6 -- fix(worktreerpc): bound handler contexts and drop the git binary from tests -- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries -- refactor: route tasks on a typed kind, not forge labels -- fix(natsrpc): make RegisterAll wait for the server to see subscriptions -- refactor(config): move loading into infrastructure/configuration -- refactor: add internal/eventbus as the broker-neutral messaging contract -- feat(tools): lift tau's file and shell tools into the tool registry -- feat: make /stop cancel the running chat turn -- fix: kill the whole process group when a shell command is cancelled -- feat: refuse unrecoverable shell commands -- feat: make /stop reach running agent tasks -- fix: use errors.Is/As for context errors and cleanup -- fix(grep): distinguish ripgrep exit 1 from a failed search -- fix(docker): slim both images and repair unreachable Go tooling -- fix(container): write the task boot brief under .git diff --git a/docs/news/archie/1.20.0.md b/docs/news/archie/1.20.0.md deleted file mode 100644 index 72c545f21..000000000 --- a/docs/news/archie/1.20.0.md +++ /dev/null @@ -1,13 +0,0 @@ -# archie-agent 1.20.0 - -Released 2026-09-03. [All news](../index.md) - -- fix: baseline gate repair (go test ./... -count=1) -- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler -- feat(image): define provider-neutral image capability contract and config -- fix(workflow): stop discarding baseline-fix commits as 'no changes' -- fix(workflow): net cache hits from token totals, trim gate-retry output -- feat(workflow): dynamic triage instead of defaulting every task to implement -- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated -- feat(store): encrypt playbook binding secrets at rest -- fix(store): satisfy makezero when building cipher payload diff --git a/docs/news/archie/1.21.0.md b/docs/news/archie/1.21.0.md deleted file mode 100644 index 5c1b387d9..000000000 --- a/docs/news/archie/1.21.0.md +++ /dev/null @@ -1,14 +0,0 @@ -# archie-agent 1.21.0 - -Released 2026-09-03. [All news](../index.md) - -- feat(workflow): make kind-to-workflow routing YAML-overridable -- feat(workflow): route arbitrary forge labels to workflows via playbook YAML -- feat(workflow): load kind/label bindings from multiple playbook directories -- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive -- feat(eda): Module position first slice -- registry + side-effect-free log kind -- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch -- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch -- fix(binding): split ValidateForUpdate so edits can preserve the secret -- refactor(eda): extract helpers to satisfy cyclop/gocognit gates -- fix(eda): make playbook key collision reporting deterministic diff --git a/docs/news/archie/1.23.0.md b/docs/news/archie/1.23.0.md deleted file mode 100644 index b57a2847a..000000000 --- a/docs/news/archie/1.23.0.md +++ /dev/null @@ -1,35 +0,0 @@ -# archie-agent 1.23.0 - -Released 2026-09-12. [All news](../index.md) - -The agent runtime now reaches task state through the State Store gRPC contract -(`STATE_STORE_URL`/`STATE_STORE_TOKEN`, injected by the daemon) instead of the -NATS `storerpc` transport, which is deleted. Credentials handed to a task -container are scoped to that task rather than being the daemon's own token. -Running a 1.23.0 daemon against an older agent image will not work; rebuild or -pull the `archie-agent` image with this release. - -- feat(state-store): generalize storerpc as the State Store gRPC contract (#770) -- feat(state-store): stand up archie-state-store binary and own archie.db (#771) -- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774) -- fix(state-store): task-scope container credentials, stream large capture lists, validate Update -- fix(staterpc): attach the bearer token to State Store streams -- feat(staterpc): carry the dashboard's configuration snapshot -- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754) -- refactor(store): move the producer-owned contracts to internal/contracts/store/v1 -- feat(contracts): add gateway service seams and protobuf toolchain -- fix(gateway): drop services.gateway.mode, remote is the only transport -- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview) -- feat(gateway): operator-triggered PR review with selectable reviewer model -- feat(workflow): surface adversarial review findings on the PR body -- feat(workflow): review calibration, checked properties and style nits out of contract -- fix(workflow): order findings before footer; test the report stash -- fix(archied): share one PR reviewer across channels; harden forge and worktree -- feat(worktree): Resume re-syncs a worktree onto its branch tip -- feat(telegram): support secret refs for bot tokens (#705) -- feat(gateway): wire progressive tool disclosure (bridge tools) -- feat(archied): serve the daemon's own health endpoint -- feat(archieui): standalone UI process over remote Gateway and State Store -- refactor(archied): move webhook capture intake to the process that owns work intake -- refactor(ui): sever the archie-ui binary from every daemon runtime package -- fix(archieui): resolve service tokens from env, without requiring a config file diff --git a/docs/news/archie/1.25.0.md b/docs/news/archie/1.25.0.md deleted file mode 100644 index ad93159d0..000000000 --- a/docs/news/archie/1.25.0.md +++ /dev/null @@ -1,6 +0,0 @@ -# archie-agent 1.25.0 - -Released 2026-09-15. [All news](../index.md) - -- chore: no user-facing changes; versioned so the 1.25.0 release tags both - components at the same commit diff --git a/docs/news/archie/1.26.0.md b/docs/news/archie/1.26.0.md deleted file mode 100644 index f276efde0..000000000 --- a/docs/news/archie/1.26.0.md +++ /dev/null @@ -1,47 +0,0 @@ -# archie-agent 1.26.0 - -Released 2026-09-17. [All news](../index.md) - -- feat(config): add [scheduling] config block -- fix(webui): count every chat front-end in the published projection -- fix(scheduling): respect configuration ownership -- feat(ratelimit): wire per-identity inbound rate limiting into the gateway -- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it -- fix(daemon): carry kind/label routing bindings to the process that routes -- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone -- fix(logging): keep the live descriptor open across a failed rotation -- fix(agentworker): wire configured tool-result policy into worker's LoopRunner -- refactor(staterpc): delete the superseded single-token auth interceptor -- refactor(tools): delete unreachable dispatch/gating engine -- feat(channels): wire chat.webhook route config through to the gateway -- refactor(tools): delete unreachable AST-based tool discovery -- refactor(tools): delete unused plugin-tool registration API from builtin.Registry -- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted) -- fix(staterpc): preserve marshal_error marker in eventDataJSON -- fix(gate): validate finding level and share the blocking threshold -- fix(tools/provider/mcp): preserve MCP binary tool results for delivery -- refactor(tools/mcp): delete unreachable MCP adaptation path -- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path -- refactor(skillbuild): delete dead AugmentRegistry path -- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout -- refactor(binding): delete dead Matcher.Overlaps method -- refactor(forge): delete dead CreateIssue surface -- fix(mcp): cancel in-flight SSE reconnect on Stop -- fix(container): enforce MaxUptime lifetime cap with a timer -- refactor(forge): delete the unwired RepliesAfter surface -- refactor(config): delete the two decoded-but-unread policy fields - -The runtime carries a smaller, more focused set of changes than the same -version's archied entry: agent-side tool-result policy is now wired into the -worker's loop, MCP binary tool results survive to delivery, the container -`MaxUptime` lifetime cap is enforced with a timer, and a scheduled run records -completion so it does not re-fire each tick. - -Note that several bullets above name config, webui and ratelimit packages. Those -are attributed here by the release tool's package-closure rule (`go list -deps` -over the agent binary), not because the agent owns them; the substantive -runtime changes are the worker, MCP, container and scheduling fixes. - -This entry also confirms the removal of the dead `IncrementRetryCount` State -Store RPC, which the agent reaches through `staterpc` rather than by calling it -directly. diff --git a/docs/news/archie/1.27.0.md b/docs/news/archie/1.27.0.md deleted file mode 100644 index 4db9cebd2..000000000 --- a/docs/news/archie/1.27.0.md +++ /dev/null @@ -1,7 +0,0 @@ -# archie-agent 1.27.0 - -Released 2026-09-17. [All news](../index.md) - -- The per-task runtime picks up the new State Store task-log read contract, so - the sandboxed agents share one log-reading path with the daemon and the - dashboard. diff --git a/docs/news/archie/1.28.0.md b/docs/news/archie/1.28.0.md deleted file mode 100644 index ef66c8118..000000000 --- a/docs/news/archie/1.28.0.md +++ /dev/null @@ -1,20 +0,0 @@ -# archie-agent 1.28.0 - -Released 2026-09-19. [All news](../index.md) - -- The sandboxed runtime picks up the attempt-attribution contract, so the events - and changes an agent produces are recorded against the attempt that produced - them. -- `grep` can use the workspace codesearch index. -- A worktree is handed back on every sandbox exit, and container teardown is - claimed once — a released container's reaper is cancelled rather than - re-firing during the grace period. -- Retries recover from worktree path-type conflicts instead of failing - opaquely. -- A parked workflow run records its park reason in its own log. -- Triage criteria distinguish the workflows, and a workflow is required when a - code change is needed. -- Namespaced forge labels match when routing by kind. -- The `ARCHIE_REACTIONS` fan-out stream is provisioned. -- Collection fields decoded over the State Store gRPC contract are never nil - slices, so an empty collection marshals as `[]` rather than `null`. diff --git a/docs/news/archie/1.29.0.md b/docs/news/archie/1.29.0.md deleted file mode 100644 index 9253f9602..000000000 --- a/docs/news/archie/1.29.0.md +++ /dev/null @@ -1,11 +0,0 @@ -# archie-agent 1.29.0 - -Released 2026-09-19. [All news](../index.md) - -- The sandboxed runtime picks up the review-reaction envelope and its - owned-PR authorization, so an agent can only react to reviews on pull - requests it opened itself. -- `google.golang.org/grpc` bumped past `v1.84.0` to patch - [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443) (shared dependency - with `archied`; the pre-release commit is pinned pending a stable - `v1.85.0`). diff --git a/docs/news/archie/1.30.0.md b/docs/news/archie/1.30.0.md deleted file mode 100644 index 4bbd6ca15..000000000 --- a/docs/news/archie/1.30.0.md +++ /dev/null @@ -1,20 +0,0 @@ -# archie-agent 1.30.0 - -Released 2026-09-20. [All news](../index.md) - -- The sandboxed runtime picks up line-anchored review comments: a finding is - posted against the line it is about, with a suggested fix where it has one, - and a suggestion is rejected unless it is single-line -- GitHub applies a - multi-line suggestion only up to its first line, silently corrupting the - file (#891). -- `diff_cap_lines` is an optional value in the shared config the runtime - reconstructs, so an explicit `0` means "no cap" rather than being rewritten - to the default. **Behaviour change** for a repo that set `0` expecting - unlimited and was silently getting 400 (#899). -- A diff-cap park names a remedy that exists: a parked task's actions are - retry, abandon and reject, so the reason no longer says "approve manually". -- A released container is not torn down twice -- the reaper no longer deletes - teardown bookkeeping before `Release` is finished with it (#893). -- Build toolchain: `gofumpt` and `golangci-lint` are pinned as one matched - pair, and `task fmt` uses the same engine the gate checks with, so the - runtime's own gate is satisfiable (#901). diff --git a/docs/news/archie/1.31.0.md b/docs/news/archie/1.31.0.md deleted file mode 100644 index 712b71f35..000000000 --- a/docs/news/archie/1.31.0.md +++ /dev/null @@ -1,29 +0,0 @@ -# archie-agent 1.31.0 - -Released 2026-09-22. [All news](../index.md) - -The sandboxed runtime links the same shared packages as archied, so this -release carries the control-plane and workflow changes alongside it: - -- Runtime administration over the State Store's gRPC server, resource history, - and control-plane apply status on the store contract. -- The shared step vocabulary, owned by a family manager registered at each - composition root, and `gate.diff-rules` in place of `.archie/gate.go` - (fails closed on a change it never read). -- The workflow pin crosses the wire. - -Runtime-specific changes: - -- `refactor(plugin)`: the unused `Registry` type is deleted. -- `yaegiutil` refuses incomplete Yaegi interface wrappers at load rather than - running them. -- The runtime config overlay is deleted. -- The state store dial installs client keepalive, and the server policy accepts - the dialer's pings. -- The MCP client supports per-server `parallel_tool_calls`. -- A late max-uptime callback no longer resurrects teardown state. -- A webhook route path no longer becomes a sender identity. - -Note: the `archie-agent` image is rebuilt by this tag through CI -(`.github/workflows/deploy.yml`); a gateway-only release would not have rebuilt -it. `docker compose pull agent` is required to pick it up. diff --git a/docs/news/archie/1.32.0.md b/docs/news/archie/1.32.0.md deleted file mode 100644 index e8db217aa..000000000 --- a/docs/news/archie/1.32.0.md +++ /dev/null @@ -1,13 +0,0 @@ -# archie-agent 1.32.0 - -Released 2026-09-22. [All news](../index.md) - -The sandboxed runtime links `storecontract` and `staterpc`, so it carries the dispatch-ledger -contract alongside archied: - -- The shared `store.ErrAlreadyDispatched` sentinel now describes both dedup ledgers -- - `binding_dispatches` per `(binding_id, capture_id)`, and `playbook_dispatches` per - `(playbook_id, playbook_version, event_id, action_id)`. Each is an at-most-once guarantee. -- `RecordPlaybookDispatch` is part of the store contract the runtime builds against. - -archied and archie-agent move together in this release. diff --git a/docs/news/archie/1.35.0.md b/docs/news/archie/1.35.0.md deleted file mode 100644 index b5b59bef6..000000000 --- a/docs/news/archie/1.35.0.md +++ /dev/null @@ -1,13 +0,0 @@ -# archie-agent 1.35.0 - -Released 2026-09-22. [All news](../index.md) - -The sandboxed runtime links the same shared packages as archied, so this release carries the -channel-lifecycle store contract and the stricter action-load errors with it: - -- The channel-status store contract (`PutChannelStatus`/`ListChannelStatus`) and its replace-the-set - semantics. -- Authoritative module ids and stricter action load errors: a misspelled result field, an unknown id, - or a dynamic `actions` read now fails the playbook load rather than the dispatch. - -archied and archie-agent move together in this release. diff --git a/docs/news/archie/1.9.0.md b/docs/news/archie/1.9.0.md deleted file mode 100644 index 4b09e7257..000000000 --- a/docs/news/archie/1.9.0.md +++ /dev/null @@ -1,10 +0,0 @@ -# archie-agent 1.9.0 - -Released 2026-08-15. [All news](../index.md) - -- fix(agent): resolve git dubious-ownership in sandbox containers -- feat(agent): mark the mounted worktree as a git safe directory -- fix(agent): route git safe.directory setup through markWorktreeSafe -- feat(chat): show tool calls inline and stream replies into one message -- refactor(agent): move worker runtime into application layer -- fix(config,webui): make show_tool_calls one cross-channel setting diff --git a/docs/news/archie/1.9.1.md b/docs/news/archie/1.9.1.md deleted file mode 100644 index 432cbbe79..000000000 --- a/docs/news/archie/1.9.1.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.9.1 - -Released 2026-08-15. [All news](../index.md) - -- fix(agentworker): forward workflow events across the NATS worker boundary diff --git a/docs/news/archie/1.9.2.md b/docs/news/archie/1.9.2.md deleted file mode 100644 index c9ae8a704..000000000 --- a/docs/news/archie/1.9.2.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.9.2 - -Released 2026-08-15. [All news](../index.md) - -- fix(worktree): force checkout so retry recovers from a dirty worktree diff --git a/docs/news/archie/1.9.3.md b/docs/news/archie/1.9.3.md deleted file mode 100644 index e53e10432..000000000 --- a/docs/news/archie/1.9.3.md +++ /dev/null @@ -1,7 +0,0 @@ -# archie-agent 1.9.3 - -Released 2026-08-15. [All news](../index.md) - -- fix(logging): resolve error attrs to their message string, not {} -- fix(agentworker): back off before refetching a nak'd stage message -- feat(agentexec,workflow): surface tool calls on the task timeline diff --git a/docs/news/archie/1.9.4.md b/docs/news/archie/1.9.4.md deleted file mode 100644 index 6dadd77c0..000000000 --- a/docs/news/archie/1.9.4.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.9.4 - -Released 2026-08-15. [All news](../index.md) - -- chore: no user-facing changes diff --git a/docs/news/archie/1.9.5.md b/docs/news/archie/1.9.5.md deleted file mode 100644 index 1d3bae2fb..000000000 --- a/docs/news/archie/1.9.5.md +++ /dev/null @@ -1,7 +0,0 @@ -# archie-agent 1.9.5 - -Released 2026-08-16. [All news](../index.md) - -- refactor: decompose the daemon bootstrap into phased wiring (no behaviour change; complexity-driven restructure) -- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity -- fix(tools): avoid predeclared `max` names diff --git a/docs/news/archie/1.9.6.md b/docs/news/archie/1.9.6.md deleted file mode 100644 index 9edc3b413..000000000 --- a/docs/news/archie/1.9.6.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.9.6 - -Released 2026-08-16. [All news](../index.md) - -- chore: no user-facing changes diff --git a/docs/news/archie/1.9.7.md b/docs/news/archie/1.9.7.md deleted file mode 100644 index edcf5cf91..000000000 --- a/docs/news/archie/1.9.7.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.9.7 - -Released 2026-08-17. [All news](../index.md) - -- chore: no user-facing changes diff --git a/docs/news/archie/1.9.8.md b/docs/news/archie/1.9.8.md deleted file mode 100644 index 0ff403ff3..000000000 --- a/docs/news/archie/1.9.8.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.9.8 - -Released 2026-08-17. [All news](../index.md) - -- chore: no user-facing changes diff --git a/docs/news/archie/1.9.9.md b/docs/news/archie/1.9.9.md deleted file mode 100644 index e2a7f6eb6..000000000 --- a/docs/news/archie/1.9.9.md +++ /dev/null @@ -1,5 +0,0 @@ -# archie-agent 1.9.9 - -Released 2026-08-18. [All news](../index.md) - -- chore: no user-facing changes diff --git a/docs/news/archied/1.13.0.md b/docs/news/archied/1.13.0.md deleted file mode 100644 index f210b0d6b..000000000 --- a/docs/news/archied/1.13.0.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.13.0 - -Released 2026-08-23. [All news](../index.md) - -- fix(telegram): render tool progress as bounded code blocks diff --git a/docs/news/archied/1.16.0.md b/docs/news/archied/1.16.0.md deleted file mode 100644 index cf79ff3be..000000000 --- a/docs/news/archied/1.16.0.md +++ /dev/null @@ -1,30 +0,0 @@ -# archied 1.16.0 - -Released 2026-08-25. [All news](../index.md) - -**The agent can hand you a file, and the dashboard works behind a reverse -proxy.** Media delivery was fetch-by-URL only, so a file the agent produced -locally — a transcript, a log dump, a screenshot — was passed to Telegram as -a URL it could not fetch: the send did nothing and reported success. The new -`send_file` tool plus upload-by-reader delivery closes that, and every layer -that cannot deliver now says so rather than staying silent. Dashboard -mutations behind a TLS-terminating proxy were refused as cross-origin; -forwarded headers are now honoured, but only under an explicit opt-in that is -off by default. - -- feat(telegram): deliver a local file as an uploaded attachment, choosing - upload-by-reader or fetch-by-URL per attachment; `send_file` resolves paths - under the same confinement policy the read tool applies, so sending cannot - reach what reading cannot -- feat(gateway): `task_action` chat tool for operator task management — - abandon, archive, retry, stop, cancel, approve and reject from chat, on the - same action path and state machine as the dashboard -- fix(webui): validate mutation `Origin` against the effective external - scheme and host. `X-Forwarded-Proto`/`-Host` are honoured only when - `web.trust_forwarded_headers` is set, which is off by default and safe only - behind a proxy that overwrites or strips untrusted forwarded headers -- fix(webui): report a local file the dashboard chat cannot upload as - undelivered instead of dropping the event, which had reproduced the exact - silent non-delivery `send_file` was built to end -- fix(daemon): detach terminal state transitions and cleanup from a cancelled - context, so a stopped task still records its outcome diff --git a/docs/news/archied/1.17.0.md b/docs/news/archied/1.17.0.md deleted file mode 100644 index b548ce893..000000000 --- a/docs/news/archied/1.17.0.md +++ /dev/null @@ -1,6 +0,0 @@ -# archied 1.17.0 - -Released 2026-08-25. [All news](../index.md) - -- fix(webui): add nil receiver guard to Server.trustForwardedHeaders -- fix(chat): restore transcript and update replay diff --git a/docs/news/archied/1.19.7.md b/docs/news/archied/1.19.7.md deleted file mode 100644 index de4ebcbcf..000000000 --- a/docs/news/archied/1.19.7.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.19.7 - -Released 2026-09-02. [All news](../index.md) - -- fix(logging): make Tail/Page allocation bound explicit for CodeQL diff --git a/docs/news/archied/1.3.0.md b/docs/news/archied/1.3.0.md deleted file mode 100644 index a9b2716ec..000000000 --- a/docs/news/archied/1.3.0.md +++ /dev/null @@ -1,6 +0,0 @@ -# archied 1.3.0 - -Released 2026-07-31. [All news](../index.md) - -- fix(memory): replace framework-specific names with generic equivalents -- feat: unify provider and model selection diff --git a/docs/news/archied/1.3.1.md b/docs/news/archied/1.3.1.md deleted file mode 100644 index 8d13b83ed..000000000 --- a/docs/news/archied/1.3.1.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.3.1 - -Released 2026-07-31. [All news](../index.md) - -- fix(telegram): omit empty model picker markup diff --git a/docs/news/archied/1.4.0.md b/docs/news/archied/1.4.0.md deleted file mode 100644 index bed679e3d..000000000 --- a/docs/news/archied/1.4.0.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.4.0 - -Released 2026-07-31. [All news](../index.md) - -- fix(secrets): wire provider credentials through engines diff --git a/docs/news/archied/1.4.1.md b/docs/news/archied/1.4.1.md deleted file mode 100644 index bb1b7ed4c..000000000 --- a/docs/news/archied/1.4.1.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.4.1 - -Released 2026-07-31. [All news](../index.md) - -- fix(catalog): match SDK provider fallback diff --git a/docs/news/archied/1.9.0.md b/docs/news/archied/1.9.0.md deleted file mode 100644 index 947060c6b..000000000 --- a/docs/news/archied/1.9.0.md +++ /dev/null @@ -1,9 +0,0 @@ -# archied 1.9.0 - -Released 2026-08-15. [All news](../index.md) - -- fix(webui): style tool-call failure from a structured field, not a string prefix -- fix(config,webui): make show_tool_calls one cross-channel setting -- fix(telegram): guarantee no message is stranded on gateway stop/restart -- fix(telegram): use NewRequestWithContext to satisfy noctx -- refactor(webui): decompose handleSSE to cut cognitive complexity diff --git a/docs/news/archied/1.9.11.md b/docs/news/archied/1.9.11.md deleted file mode 100644 index 8a23147ed..000000000 --- a/docs/news/archied/1.9.11.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.9.11 - -Released 2026-08-19. [All news](../index.md) - -- fix(mcp): persist npx package cache across daemon restarts diff --git a/docs/news/archied/1.9.2.md b/docs/news/archied/1.9.2.md deleted file mode 100644 index 3c6d28f30..000000000 --- a/docs/news/archied/1.9.2.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.9.2 - -Released 2026-08-15. [All news](../index.md) - -- fix(worktree): force checkout so retry recovers from a dirty worktree diff --git a/docs/news/archied/1.9.3.md b/docs/news/archied/1.9.3.md deleted file mode 100644 index ce27e2aa3..000000000 --- a/docs/news/archied/1.9.3.md +++ /dev/null @@ -1,7 +0,0 @@ -# archied 1.9.3 - -Released 2026-08-15. [All news](../index.md) - -- fix(webui): scroll selected command into view on keyboard navigation -- fix(logging): resolve error attrs to their message string, not {} -- feat(agentexec,workflow): surface tool calls on the task timeline diff --git a/docs/news/archied/1.9.4.md b/docs/news/archied/1.9.4.md deleted file mode 100644 index 63626b304..000000000 --- a/docs/news/archied/1.9.4.md +++ /dev/null @@ -1,6 +0,0 @@ -# archied 1.9.4 - -Released 2026-08-15. [All news](../index.md) - -- feat(gateway): polish /status command response format -- fix(telegram): preserve URL boundaries in responses diff --git a/docs/news/archied/1.9.6.md b/docs/news/archied/1.9.6.md deleted file mode 100644 index d61b4a228..000000000 --- a/docs/news/archied/1.9.6.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.9.6 - -Released 2026-08-16. [All news](../index.md) - -- fix(update): stamp install type and bound retry backoff diff --git a/docs/news/archied/1.9.7.md b/docs/news/archied/1.9.7.md deleted file mode 100644 index 697d87d7b..000000000 --- a/docs/news/archied/1.9.7.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.9.7 - -Released 2026-08-17. [All news](../index.md) - -- chore: no user-facing changes diff --git a/docs/news/archied/1.9.8.md b/docs/news/archied/1.9.8.md deleted file mode 100644 index 142be74ad..000000000 --- a/docs/news/archied/1.9.8.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.9.8 - -Released 2026-08-17. [All news](../index.md) - -- chore: no user-facing changes diff --git a/docs/news/archied/1.9.9.md b/docs/news/archied/1.9.9.md deleted file mode 100644 index db013049e..000000000 --- a/docs/news/archied/1.9.9.md +++ /dev/null @@ -1,5 +0,0 @@ -# archied 1.9.9 - -Released 2026-08-18. [All news](../index.md) - -- fix(telegram): drain live renderer in concurrency test diff --git a/docs/news/index.md b/docs/news/index.md index 4640ad5a6..3f7a2369d 100644 --- a/docs/news/index.md +++ b/docs/news/index.md @@ -1,179 +1,146 @@ # News -Release notes for archied and archie-agent, newest first. +Release notes, newest first. ## 2026-09-22 -- [archied 1.37.0](archied/1.37.0.md) -- [archied 1.36.0](archied/1.36.0.md) -- [archied 1.35.0](archied/1.35.0.md) -- [archied 1.34.0](archied/1.34.0.md) -- [archied 1.33.0](archied/1.33.0.md) -- [archied 1.32.1](archied/1.32.1.md) -- [archied 1.32.0](archied/1.32.0.md) -- [archied 1.31.0](archied/1.31.0.md) -- [archie-agent 1.35.0](archie/1.35.0.md) -- [archie-agent 1.32.0](archie/1.32.0.md) -- [archie-agent 1.31.0](archie/1.31.0.md) +- [1.37.0](1.37.0.md) +- [1.36.0](1.36.0.md) +- [1.35.0](1.35.0.md) +- [1.34.0](1.34.0.md) +- [1.33.0](1.33.0.md) +- [1.32.1](1.32.1.md) +- [1.32.0](1.32.0.md) +- [1.31.0](1.31.0.md) ## 2026-09-20 -- [archied 1.30.0](archied/1.30.0.md) -- [archie-agent 1.30.0](archie/1.30.0.md) +- [1.30.0](1.30.0.md) ## 2026-09-19 -- [archied 1.29.0](archied/1.29.0.md) -- [archied 1.28.0](archied/1.28.0.md) -- [archie-agent 1.29.0](archie/1.29.0.md) -- [archie-agent 1.28.0](archie/1.28.0.md) +- [1.29.0](1.29.0.md) +- [1.28.0](1.28.0.md) ## 2026-09-17 -- [archied 1.27.0](archied/1.27.0.md) -- [archied 1.26.0](archied/1.26.0.md) -- [archie-agent 1.27.0](archie/1.27.0.md) -- [archie-agent 1.26.0](archie/1.26.0.md) +- [1.27.0](1.27.0.md) +- [1.26.0](1.26.0.md) ## 2026-09-15 -- [archied 1.25.0](archied/1.25.0.md) -- [archie-agent 1.25.0](archie/1.25.0.md) +- [1.25.0](1.25.0.md) ## 2026-09-12 -- [archied 1.24.0](archied/1.24.0.md) -- [archied 1.23.0](archied/1.23.0.md) -- [archie-agent 1.23.0](archie/1.23.0.md) +- [1.24.0](1.24.0.md) +- [1.23.0](1.23.0.md) ## 2026-09-03 -- [archied 1.22.0](archied/1.22.0.md) -- [archied 1.21.0](archied/1.21.0.md) -- [archied 1.20.0](archied/1.20.0.md) -- [archie-agent 1.21.0](archie/1.21.0.md) -- [archie-agent 1.20.0](archie/1.20.0.md) +- [1.22.0](1.22.0.md) +- [1.21.0](1.21.0.md) +- [1.20.0](1.20.0.md) ## 2026-09-02 -- [archied 1.19.10](archied/1.19.10.md) -- [archied 1.19.9](archied/1.19.9.md) -- [archied 1.19.8](archied/1.19.8.md) -- [archied 1.19.7](archied/1.19.7.md) -- [archied 1.19.6](archied/1.19.6.md) -- [archie-agent 1.19.9](archie/1.19.9.md) -- [archie-agent 1.19.7](archie/1.19.7.md) +- [1.19.10](1.19.10.md) +- [1.19.9](1.19.9.md) +- [1.19.8](1.19.8.md) +- [1.19.7](1.19.7.md) +- [1.19.6](1.19.6.md) ## 2026-09-01 -- [archied 1.19.5](archied/1.19.5.md) -- [archie-agent 1.19.5](archie/1.19.5.md) +- [1.19.5](1.19.5.md) ## 2026-08-28 -- [archied 1.19.4](archied/1.19.4.md) -- [archied 1.19.3](archied/1.19.3.md) -- [archied 1.19.2](archied/1.19.2.md) -- [archied 1.19.0](archied/1.19.0.md) -- [archie-agent 1.18.0](archie/1.18.0.md) +- [1.19.4](1.19.4.md) +- [1.19.3](1.19.3.md) +- [1.19.2](1.19.2.md) +- [1.19.0](1.19.0.md) +- [1.18.0](1.18.0.md) ## 2026-08-27 -- [archied 1.19.1](archied/1.19.1.md) +- [1.19.1](1.19.1.md) ## 2026-08-25 -- [archied 1.18.0](archied/1.18.0.md) -- [archied 1.17.1](archied/1.17.1.md) -- [archied 1.17.0](archied/1.17.0.md) -- [archied 1.16.0](archied/1.16.0.md) -- [archie-agent 1.17.0](archie/1.17.0.md) -- [archie-agent 1.16.1](archie/1.16.1.md) -- [archie-agent 1.16.0](archie/1.16.0.md) +- [1.17.1](1.17.1.md) +- [1.17.0](1.17.0.md) +- [1.16.1](1.16.1.md) +- [1.16.0](1.16.0.md) ## 2026-08-24 -- [archied 1.15.0](archied/1.15.0.md) +- [1.15.0](1.15.0.md) ## 2026-08-23 -- [archied 1.14.0](archied/1.14.0.md) -- [archied 1.13.0](archied/1.13.0.md) -- [archied 1.12.0](archied/1.12.0.md) -- [archied 1.11.1](archied/1.11.1.md) -- [archied 1.11.0](archied/1.11.0.md) +- [1.14.0](1.14.0.md) +- [1.13.0](1.13.0.md) +- [1.12.0](1.12.0.md) +- [1.11.1](1.11.1.md) +- [1.11.0](1.11.0.md) ## 2026-08-22 -- [archied 1.10.0](archied/1.10.0.md) +- [1.10.0](1.10.0.md) ## 2026-08-19 -- [archied 1.9.11](archied/1.9.11.md) -- [archied 1.9.10](archied/1.9.10.md) +- [1.9.11](1.9.11.md) +- [1.9.10](1.9.10.md) ## 2026-08-18 -- [archied 1.9.9](archied/1.9.9.md) -- [archie-agent 1.9.9](archie/1.9.9.md) +- [1.9.9](1.9.9.md) ## 2026-08-17 -- [archied 1.9.8](archied/1.9.8.md) -- [archied 1.9.7](archied/1.9.7.md) -- [archie-agent 1.9.8](archie/1.9.8.md) -- [archie-agent 1.9.7](archie/1.9.7.md) +- [1.9.8](1.9.8.md) +- [1.9.7](1.9.7.md) ## 2026-08-16 -- [archied 1.9.6](archied/1.9.6.md) -- [archied 1.9.5](archied/1.9.5.md) -- [archie-agent 1.9.6](archie/1.9.6.md) -- [archie-agent 1.9.5](archie/1.9.5.md) +- [1.9.6](1.9.6.md) +- [1.9.5](1.9.5.md) ## 2026-08-15 -- [archied 1.9.4](archied/1.9.4.md) -- [archied 1.9.3](archied/1.9.3.md) -- [archied 1.9.2](archied/1.9.2.md) -- [archied 1.9.1](archied/1.9.1.md) -- [archied 1.9.0](archied/1.9.0.md) -- [archied 1.8.0](archied/1.8.0.md) -- [archie-agent 1.9.4](archie/1.9.4.md) -- [archie-agent 1.9.3](archie/1.9.3.md) -- [archie-agent 1.9.2](archie/1.9.2.md) -- [archie-agent 1.9.1](archie/1.9.1.md) -- [archie-agent 1.9.0](archie/1.9.0.md) +- [1.9.4](1.9.4.md) +- [1.9.3](1.9.3.md) +- [1.9.2](1.9.2.md) +- [1.9.1](1.9.1.md) +- [1.9.0](1.9.0.md) +- [1.8.0](1.8.0.md) ## 2026-08-10 -- [archied 1.7.0](archied/1.7.0.md) -- [archie-agent 1.4.0](archie/1.4.0.md) +- [1.7.0](1.7.0.md) +- [1.4.0](1.4.0.md) ## 2026-08-09 -- [archied 1.6.0](archied/1.6.0.md) +- [1.6.0](1.6.0.md) ## 2026-08-08 -- [archied 1.5.0](archied/1.5.0.md) -- [archie-agent 1.3.0](archie/1.3.0.md) +- [1.5.0](1.5.0.md) +- [1.3.0](1.3.0.md) ## 2026-07-31 -- [archied 1.4.1](archied/1.4.1.md) -- [archied 1.4.0](archied/1.4.0.md) -- [archied 1.3.1](archied/1.3.1.md) -- [archied 1.3.0](archied/1.3.0.md) -- [archied 1.2.0](archied/1.2.0.md) -- [archie-agent 1.2.0](archie/1.2.0.md) +- [1.4.1](1.4.1.md) +- [1.3.1](1.3.1.md) +- [1.2.0](1.2.0.md) ## 2026-07-27 -- [archied 1.1.0](archied/1.1.0.md) -- [archie-agent 1.1.0](archie/1.1.0.md) +- [1.1.0](1.1.0.md) ## 2026-07-22 -- [archied 1.0.0](archied/1.0.0.md) -- [archie-agent 1.0.0](archie/1.0.0.md) +- [1.0.0](1.0.0.md) diff --git a/docs/news/redirects.json b/docs/news/redirects.json new file mode 100644 index 000000000..c672fa8c5 --- /dev/null +++ b/docs/news/redirects.json @@ -0,0 +1,132 @@ +{ + "/news/archie/1.0.0/": "/news/1.0.0/", + "/news/archie/1.1.0/": "/news/1.1.0/", + "/news/archie/1.10.0/": "/news/1.10.0/", + "/news/archie/1.11.0/": "/news/1.11.0/", + "/news/archie/1.11.1/": "/news/1.11.1/", + "/news/archie/1.12.0/": "/news/1.12.0/", + "/news/archie/1.13.0/": "/news/1.13.0/", + "/news/archie/1.14.0/": "/news/1.14.0/", + "/news/archie/1.15.0/": "/news/1.15.0/", + "/news/archie/1.16.0/": "/news/1.16.0/", + "/news/archie/1.16.1/": "/news/1.16.1/", + "/news/archie/1.17.0/": "/news/1.17.0/", + "/news/archie/1.17.1/": "/news/1.17.1/", + "/news/archie/1.18.0/": "/news/1.18.0/", + "/news/archie/1.19.0/": "/news/1.19.0/", + "/news/archie/1.19.1/": "/news/1.19.1/", + "/news/archie/1.19.10/": "/news/1.19.10/", + "/news/archie/1.19.2/": "/news/1.19.2/", + "/news/archie/1.19.3/": "/news/1.19.3/", + "/news/archie/1.19.4/": "/news/1.19.4/", + "/news/archie/1.19.5/": "/news/1.19.5/", + "/news/archie/1.19.6/": "/news/1.19.6/", + "/news/archie/1.19.7/": "/news/1.19.7/", + "/news/archie/1.19.8/": "/news/1.19.8/", + "/news/archie/1.19.9/": "/news/1.19.9/", + "/news/archie/1.2.0/": "/news/1.2.0/", + "/news/archie/1.20.0/": "/news/1.20.0/", + "/news/archie/1.21.0/": "/news/1.21.0/", + "/news/archie/1.22.0/": "/news/1.22.0/", + "/news/archie/1.23.0/": "/news/1.23.0/", + "/news/archie/1.24.0/": "/news/1.24.0/", + "/news/archie/1.25.0/": "/news/1.25.0/", + "/news/archie/1.26.0/": "/news/1.26.0/", + "/news/archie/1.27.0/": "/news/1.27.0/", + "/news/archie/1.28.0/": "/news/1.28.0/", + "/news/archie/1.29.0/": "/news/1.29.0/", + "/news/archie/1.3.0/": "/news/1.3.0/", + "/news/archie/1.3.1/": "/news/1.3.1/", + "/news/archie/1.30.0/": "/news/1.30.0/", + "/news/archie/1.31.0/": "/news/1.31.0/", + "/news/archie/1.32.0/": "/news/1.32.0/", + "/news/archie/1.32.1/": "/news/1.32.1/", + "/news/archie/1.33.0/": "/news/1.33.0/", + "/news/archie/1.34.0/": "/news/1.34.0/", + "/news/archie/1.35.0/": "/news/1.35.0/", + "/news/archie/1.36.0/": "/news/1.36.0/", + "/news/archie/1.37.0/": "/news/1.37.0/", + "/news/archie/1.4.0/": "/news/1.4.0/", + "/news/archie/1.4.1/": "/news/1.4.1/", + "/news/archie/1.5.0/": "/news/1.5.0/", + "/news/archie/1.6.0/": "/news/1.6.0/", + "/news/archie/1.7.0/": "/news/1.7.0/", + "/news/archie/1.8.0/": "/news/1.8.0/", + "/news/archie/1.9.0/": "/news/1.9.0/", + "/news/archie/1.9.1/": "/news/1.9.1/", + "/news/archie/1.9.10/": "/news/1.9.10/", + "/news/archie/1.9.11/": "/news/1.9.11/", + "/news/archie/1.9.2/": "/news/1.9.2/", + "/news/archie/1.9.3/": "/news/1.9.3/", + "/news/archie/1.9.4/": "/news/1.9.4/", + "/news/archie/1.9.5/": "/news/1.9.5/", + "/news/archie/1.9.6/": "/news/1.9.6/", + "/news/archie/1.9.7/": "/news/1.9.7/", + "/news/archie/1.9.8/": "/news/1.9.8/", + "/news/archie/1.9.9/": "/news/1.9.9/", + "/news/archied/1.0.0/": "/news/1.0.0/", + "/news/archied/1.1.0/": "/news/1.1.0/", + "/news/archied/1.10.0/": "/news/1.10.0/", + "/news/archied/1.11.0/": "/news/1.11.0/", + "/news/archied/1.11.1/": "/news/1.11.1/", + "/news/archied/1.12.0/": "/news/1.12.0/", + "/news/archied/1.13.0/": "/news/1.13.0/", + "/news/archied/1.14.0/": "/news/1.14.0/", + "/news/archied/1.15.0/": "/news/1.15.0/", + "/news/archied/1.16.0/": "/news/1.16.0/", + "/news/archied/1.16.1/": "/news/1.16.1/", + "/news/archied/1.17.0/": "/news/1.17.0/", + "/news/archied/1.17.1/": "/news/1.17.1/", + "/news/archied/1.18.0/": "/news/1.18.0/", + "/news/archied/1.19.0/": "/news/1.19.0/", + "/news/archied/1.19.1/": "/news/1.19.1/", + "/news/archied/1.19.10/": "/news/1.19.10/", + "/news/archied/1.19.2/": "/news/1.19.2/", + "/news/archied/1.19.3/": "/news/1.19.3/", + "/news/archied/1.19.4/": "/news/1.19.4/", + "/news/archied/1.19.5/": "/news/1.19.5/", + "/news/archied/1.19.6/": "/news/1.19.6/", + "/news/archied/1.19.7/": "/news/1.19.7/", + "/news/archied/1.19.8/": "/news/1.19.8/", + "/news/archied/1.19.9/": "/news/1.19.9/", + "/news/archied/1.2.0/": "/news/1.2.0/", + "/news/archied/1.20.0/": "/news/1.20.0/", + "/news/archied/1.21.0/": "/news/1.21.0/", + "/news/archied/1.22.0/": "/news/1.22.0/", + "/news/archied/1.23.0/": "/news/1.23.0/", + "/news/archied/1.24.0/": "/news/1.24.0/", + "/news/archied/1.25.0/": "/news/1.25.0/", + "/news/archied/1.26.0/": "/news/1.26.0/", + "/news/archied/1.27.0/": "/news/1.27.0/", + "/news/archied/1.28.0/": "/news/1.28.0/", + "/news/archied/1.29.0/": "/news/1.29.0/", + "/news/archied/1.3.0/": "/news/1.3.0/", + "/news/archied/1.3.1/": "/news/1.3.1/", + "/news/archied/1.30.0/": "/news/1.30.0/", + "/news/archied/1.31.0/": "/news/1.31.0/", + "/news/archied/1.32.0/": "/news/1.32.0/", + "/news/archied/1.32.1/": "/news/1.32.1/", + "/news/archied/1.33.0/": "/news/1.33.0/", + "/news/archied/1.34.0/": "/news/1.34.0/", + "/news/archied/1.35.0/": "/news/1.35.0/", + "/news/archied/1.36.0/": "/news/1.36.0/", + "/news/archied/1.37.0/": "/news/1.37.0/", + "/news/archied/1.4.0/": "/news/1.4.0/", + "/news/archied/1.4.1/": "/news/1.4.1/", + "/news/archied/1.5.0/": "/news/1.5.0/", + "/news/archied/1.6.0/": "/news/1.6.0/", + "/news/archied/1.7.0/": "/news/1.7.0/", + "/news/archied/1.8.0/": "/news/1.8.0/", + "/news/archied/1.9.0/": "/news/1.9.0/", + "/news/archied/1.9.1/": "/news/1.9.1/", + "/news/archied/1.9.10/": "/news/1.9.10/", + "/news/archied/1.9.11/": "/news/1.9.11/", + "/news/archied/1.9.2/": "/news/1.9.2/", + "/news/archied/1.9.3/": "/news/1.9.3/", + "/news/archied/1.9.4/": "/news/1.9.4/", + "/news/archied/1.9.5/": "/news/1.9.5/", + "/news/archied/1.9.6/": "/news/1.9.6/", + "/news/archied/1.9.7/": "/news/1.9.7/", + "/news/archied/1.9.8/": "/news/1.9.8/", + "/news/archied/1.9.9/": "/news/1.9.9/" +} diff --git a/docs/news/releases.json b/docs/news/releases.json index e25bbd470..45ede23e4 100644 --- a/docs/news/releases.json +++ b/docs/news/releases.json @@ -1,688 +1,327 @@ [ { - "component": "archied", - "name": "archied", "version": "1.37.0", "date": "2026-09-22", - "body": "### A request is attributed to the identity that made it\n\n- **A browser can sign in, and an action taken through it records the person.** The dashboard validates a\n provider-issued token, resolves it to an identity, and attaches it to the request; the task-action record\n then names the actor. `Authenticate` and the sign-in callback share one resolver, so a browser sign-in\n cannot be accepted on terms a presented token would be refused on.\n- **archie issues no session.** The callback stores the provider's own token in an HttpOnly cookie and every\n later request re-verifies it, so nothing archie holds can outlive the provider's decision and there is no\n session table to expire, revoke or get wrong.\n- **The event kind describes the actor.** A person's approval records `human_approved` as that person; an\n agent's records `agent_approved`; an action with no authorising principal records `task_approved` with the\n attribution fields **empty**. Nothing is credited to an identity that did not act, and an unattributed\n action is recorded as unattributed rather than guessed.\n- The acting identity is derived from the presented credential and **never** from a request field: a body\n carrying `actor`, `actor_id`, `identity` and an `X-Archie-Actor` header still cannot choose it.\n\n### A host install now works, and an update refuses a host it cannot keep consistent\n\n- `install.sh` writes and enables **all five** host units; previously it seeded only `archied.service`, so a\n fresh host ran one service of five and an operator applied the rest by hand from a runbook. The runbook is\n a description again: it names the units and points at `systemctl --user cat`.\n- **Every host binary reports its version**, and the updater reads all of them **before it can report\n \"nothing to install\"**. A host whose binaries disagree is refused, naming each one: a newer messaging\n binary beside an older state store crash-loops against a service the older store does not serve, and that\n install previously looked healthy from the updater's point of view.\n- The packaged, installer and updater command lists are pinned by a test, so a service added to one and not\n the others fails the gate instead of shipping a partial install.\n\n### A release image can be traced to a commit\n\n- The publish step derives the commit by **dereferencing the ref** rather than reading `github.sha`, because\n every release tag in this repository is annotated and a tag's object id is not a commit. An immutable\n `sha-` tag is published alongside `:latest`, and a build with no release tag is stamped\n `dev+` rather than a bare `dev` that identified nothing.\n\n### Curator definitions are data, not a second registry\n\n- Curator definitions may come from configuration or code and run through **one** engine into the existing\n registry — no parallel authority and no second config reader. A definition declares its tools, and an\n unknown tool name fails rather than widening the set silently." + "body": "### archied — A request is attributed to the identity that made it\n\n- **A browser can sign in, and an action taken through it records the person.** The dashboard validates a\n provider-issued token, resolves it to an identity, and attaches it to the request; the task-action record\n then names the actor. `Authenticate` and the sign-in callback share one resolver, so a browser sign-in\n cannot be accepted on terms a presented token would be refused on.\n- **archie issues no session.** The callback stores the provider's own token in an HttpOnly cookie and every\n later request re-verifies it, so nothing archie holds can outlive the provider's decision and there is no\n session table to expire, revoke or get wrong.\n- **The event kind describes the actor.** A person's approval records `human_approved` as that person; an\n agent's records `agent_approved`; an action with no authorising principal records `task_approved` with the\n attribution fields **empty**. Nothing is credited to an identity that did not act, and an unattributed\n action is recorded as unattributed rather than guessed.\n- The acting identity is derived from the presented credential and **never** from a request field: a body\n carrying `actor`, `actor_id`, `identity` and an `X-Archie-Actor` header still cannot choose it.\n\n### archied — A host install now works, and an update refuses a host it cannot keep consistent\n\n- `install.sh` writes and enables **all five** host units; previously it seeded only `archied.service`, so a\n fresh host ran one service of five and an operator applied the rest by hand from a runbook. The runbook is\n a description again: it names the units and points at `systemctl --user cat`.\n- **Every host binary reports its version**, and the updater reads all of them **before it can report\n \"nothing to install\"**. A host whose binaries disagree is refused, naming each one: a newer messaging\n binary beside an older state store crash-loops against a service the older store does not serve, and that\n install previously looked healthy from the updater's point of view.\n- The packaged, installer and updater command lists are pinned by a test, so a service added to one and not\n the others fails the gate instead of shipping a partial install.\n\n### archied — A release image can be traced to a commit\n\n- The publish step derives the commit by **dereferencing the ref** rather than reading `github.sha`, because\n every release tag in this repository is annotated and a tag's object id is not a commit. An immutable\n `sha-` tag is published alongside `:latest`, and a build with no release tag is stamped\n `dev+` rather than a bare `dev` that identified nothing.\n\n### archied — Curator definitions are data, not a second registry\n\n- Curator definitions may come from configuration or code and run through **one** engine into the existing\n registry — no parallel authority and no second config reader. A definition declares its tools, and an\n unknown tool name fails rather than widening the set silently." }, { - "component": "archied", - "name": "archied", "version": "1.36.0", "date": "2026-09-22", - "body": "### The dashboard declares tools an in-browser agent can call\n\n- The dashboard registers **seven WebMCP tools**. Read-only: `list_tasks`, `get_task`,\n `recent_events`, `daemon_health`. Recovery: `retry_task`, `stop_task`, `cancel_task`. An agent\n operating the dashboard now reads structured state and recovers stuck work instead of scraping the\n UI.\n- Every tool wraps the same `ui/src/lib/api.ts` client the dashboard itself calls, so an agent and a\n person exercise one path rather than two.\n- `archie-ui` cannot be attributed to the agent that called it: a page can invoke its own tools, so an\n agent's call and a page script's call reach the server identically. Tools therefore record the\n signed-in identity and a source, and **never** that an agent acted.\n\n### Binaries built by the development build task can be updated\n\n- `task build` passed the `installtype` stamp for three of six commands, so `archie-messaging`,\n `archie-state-store` and `archie-ui` were built without it. An unstamped binary reports `unknown`\n and the self-update path **refuses rather than guesses**, which is how an operator ends up unable to\n update with `install type is unknown` and no way forward. All six are stamped now, and a test reads\n the build task and fails naming any command line that omits it." + "body": "### archied — The dashboard declares tools an in-browser agent can call\n\n- The dashboard registers **seven WebMCP tools**. Read-only: `list_tasks`, `get_task`,\n `recent_events`, `daemon_health`. Recovery: `retry_task`, `stop_task`, `cancel_task`. An agent\n operating the dashboard now reads structured state and recovers stuck work instead of scraping the\n UI.\n- Every tool wraps the same `ui/src/lib/api.ts` client the dashboard itself calls, so an agent and a\n person exercise one path rather than two.\n- `archie-ui` cannot be attributed to the agent that called it: a page can invoke its own tools, so an\n agent's call and a page script's call reach the server identically. Tools therefore record the\n signed-in identity and a source, and **never** that an agent acted.\n\n### archied — Binaries built by the development build task can be updated\n\n- `task build` passed the `installtype` stamp for three of six commands, so `archie-messaging`,\n `archie-state-store` and `archie-ui` were built without it. An unstamped binary reports `unknown`\n and the self-update path **refuses rather than guesses**, which is how an operator ends up unable to\n update with `install type is unknown` and no way forward. All six are stamped now, and a test reads\n the build task and fails naming any command line that omits it." }, { - "component": "archied", - "name": "archied", "version": "1.35.0", "date": "2026-09-22", - "body": "### The Messaging Service is severed from the store and workflow runtime\n\n- `cmd/archie-messaging` no longer links `modernc.org/sqlite`, `internal/store`,\n `internal/domain/workflow` or `internal/agentexec`. All four arrived through a single import of\n `internal/app/controlplane`; the client half now lives in\n `internal/infrastructure/controlplanerpc`, and the app package keeps the server, the registry, the\n seeds, the validators and the schema derivation.\n- The resource documents are type-aliased back into the app package, so there is one definition read\n under two names rather than a copy per side.\n\n### Channel lifecycle reaches the dashboard\n\n- The Messaging Service reports each channel's state, recorded **per channel**: one channel's failure\n marks only itself, a channel that cannot start is marked failed **with its reason** rather than only\n logged, and one that returns is marked stopped. `internal/channels/status.Manager` reports each channel's state.\n- `PutChannelStatus`/`ListChannelStatus` carry that to the dashboard, following the config-snapshot\n split. The store **replaces the reported set**, so a channel the reporter stops mentioning is\n deleted rather than left as a stale `running`; an empty report clears the table, because hosting no\n channels is a fact worth reporting; and an id-less row is refused, since it could never be replaced\n or removed by a later report.\n- `Service.ReloadChannel` routes to the channel's own seam and refuses a channel that cannot reload\n with a reason rather than accepting and ignoring it. `ReloadSupported` was previously declared **by\n name**, so a channel could advertise reload with nothing behind it; one function now decides both.\n\n### Action playbooks: a second playbook shape, with typed results\n\n- A playbook is now one of two shapes: a **workflow playbook** (exactly one `workflow` action,\n unchanged) or an **action playbook** (one or more `module` actions in order). A playbook does not\n mix them.\n- `args` and `when` share one compilation path and one evaluation context, and `actions.` is typed\n by the kind that action runs, so a misspelled result field, an unknown id, a map index, `in`, a\n comprehension, or a shape-foreign key (`kind` on a `workflow` action, `workflow` on a `module`\n action) is a **load failure** rather than a dispatch failure.\n- **Action playbooks load but do not run yet.** Routing arrives with the first side-effecting\n position; the daemon warns at load rather than accepting them silently.\n- The CEL environment is built per playbook, because result typing depends on the ids a playbook\n declares.\n- `ModuleRegistry.DecodeResult` turns a kind's flat map result into its typed `Result` before a later\n expression reads it. Without it a typed read evaluated against a shape the run never produces, and\n so silently read null." + "body": "### archied — The Messaging Service is severed from the store and workflow runtime\n\n- `cmd/archie-messaging` no longer links `modernc.org/sqlite`, `internal/store`,\n `internal/domain/workflow` or `internal/agentexec`. All four arrived through a single import of\n `internal/app/controlplane`; the client half now lives in\n `internal/infrastructure/controlplanerpc`, and the app package keeps the server, the registry, the\n seeds, the validators and the schema derivation.\n- The resource documents are type-aliased back into the app package, so there is one definition read\n under two names rather than a copy per side.\n\n### archied — Channel lifecycle reaches the dashboard\n\n- The Messaging Service reports each channel's state, recorded **per channel**: one channel's failure\n marks only itself, a channel that cannot start is marked failed **with its reason** rather than only\n logged, and one that returns is marked stopped. `internal/channels/status.Manager` reports each channel's state.\n- `PutChannelStatus`/`ListChannelStatus` carry that to the dashboard, following the config-snapshot\n split. The store **replaces the reported set**, so a channel the reporter stops mentioning is\n deleted rather than left as a stale `running`; an empty report clears the table, because hosting no\n channels is a fact worth reporting; and an id-less row is refused, since it could never be replaced\n or removed by a later report.\n- `Service.ReloadChannel` routes to the channel's own seam and refuses a channel that cannot reload\n with a reason rather than accepting and ignoring it. `ReloadSupported` was previously declared **by\n name**, so a channel could advertise reload with nothing behind it; one function now decides both.\n\n### archied — Action playbooks: a second playbook shape, with typed results\n\n- A playbook is now one of two shapes: a **workflow playbook** (exactly one `workflow` action,\n unchanged) or an **action playbook** (one or more `module` actions in order). A playbook does not\n mix them.\n- `args` and `when` share one compilation path and one evaluation context, and `actions.` is typed\n by the kind that action runs, so a misspelled result field, an unknown id, a map index, `in`, a\n comprehension, or a shape-foreign key (`kind` on a `workflow` action, `workflow` on a `module`\n action) is a **load failure** rather than a dispatch failure.\n- **Action playbooks load but do not run yet.** Routing arrives with the first side-effecting\n position; the daemon warns at load rather than accepting them silently.\n- The CEL environment is built per playbook, because result typing depends on the ids a playbook\n declares.\n- `ModuleRegistry.DecodeResult` turns a kind's flat map result into its typed `Result` before a later\n expression reads it. Without it a typed read evaluated against a shape the run never produces, and\n so silently read null.\n\n### archie-agent\n\nThe sandboxed runtime links the same shared packages as archied, so this release carries the\nchannel-lifecycle store contract and the stricter action-load errors with it:\n\n- The channel-status store contract (`PutChannelStatus`/`ListChannelStatus`) and its replace-the-set\n semantics.\n- Authoritative module ids and stricter action load errors: a misspelled result field, an unknown id,\n or a dynamic `actions` read now fails the playbook load rather than the dispatch.\n\narchied and archie-agent move together in this release." }, { - "component": "archied", - "name": "archied", "version": "1.34.0", "date": "2026-09-22", - "body": "### Dashboard: an actionable authentication failure state\n\n- An unauthenticated **document** request now receives a self-contained HTML page with a\n paste-the-token form, instead of plain text. Previously the whole dashboard -- `index.html`, the\n bundle and every asset -- sat behind the token check, so a bookmarked bare URL returned a\n `text/plain` \"unauthorised: open the dashboard URL archied logged at startup\", the SPA never ran,\n and none of the dashboard's existing failure surfaces were reachable at all.\n- The response is still **401**, with `Cache-Control: no-store` and a CSP. It is deliberately not a\n 200: a login page served as success would be cacheable, would read as healthy to anything that\n checks status alone, and a shared cache could hand it to the wrong person.\n- API and stream callers are unaffected. `application/json`, `*/*` and `text/event-stream` requests\n keep the plain-text 401, with a test pinning that split so an XHR or an `EventSource` reconnect can\n never start receiving a page.\n- The auth banner gains a **Retry** action that re-runs the dashboard's bootstrap reads, so a\n recovered session is actionable without a browser-level reload. It deliberately does not re-drive\n the SSE stream, which already reports its own reconnect state.\n- The page's guidance stays generic: it points at the dashboard URL the daemon logs rather than\n naming where the token is stored, so the HTTP layer is not coupled to the token file's location." + "body": "### archied — Dashboard: an actionable authentication failure state\n\n- An unauthenticated **document** request now receives a self-contained HTML page with a\n paste-the-token form, instead of plain text. Previously the whole dashboard -- `index.html`, the\n bundle and every asset -- sat behind the token check, so a bookmarked bare URL returned a\n `text/plain` \"unauthorised: open the dashboard URL archied logged at startup\", the SPA never ran,\n and none of the dashboard's existing failure surfaces were reachable at all.\n- The response is still **401**, with `Cache-Control: no-store` and a CSP. It is deliberately not a\n 200: a login page served as success would be cacheable, would read as healthy to anything that\n checks status alone, and a shared cache could hand it to the wrong person.\n- API and stream callers are unaffected. `application/json`, `*/*` and `text/event-stream` requests\n keep the plain-text 401, with a test pinning that split so an XHR or an `EventSource` reconnect can\n never start receiving a page.\n- The auth banner gains a **Retry** action that re-runs the dashboard's bootstrap reads, so a\n recovered session is actionable without a browser-level reload. It deliberately does not re-drive\n the SSE stream, which already reports its own reconnect state.\n- The page's guidance stays generic: it points at the dashboard URL the daemon logs rather than\n naming where the token is stored, so the HTTP layer is not coupled to the token file's location." }, { - "component": "archied", - "name": "archied", "version": "1.33.0", "date": "2026-09-22", - "body": "### EDA: playbook action arguments are compiled at load (J2)\n\n- A playbook action may now declare `args`, compiled as CEL expressions when the playbook loads.\n `args` and `when` share one compilation path and one evaluation context, so an expression written\n for one works in the other.\n- **Behaviour change:** an `args` expression that does not compile is a **load failure**, not a\n runtime miss — the same reject-at-load rule already applied to a binding collision and to an\n unknown `actions.`. In practice, a daemon loading a playbook with a malformed `args` block\n fails at startup rather than part-way through a dispatch.\n- Compiling several arguments now reports the **first** bad key deterministically (keys are sorted).\n Previously it ranged a map, so the reported bad key could differ between runs and the failure was\n not reproducible.\n- `args` is deliberately **inert** for now: parsed, compiled and stored, but no shipped position\n consumes it yet. A consumer arrives with the first side-effecting position.\n\n**Not yet decided:** how an `args` evaluation failure behaves at dispatch. The `when` predicate rule\n(error, skip, log) does not obviously transfer, because `args` is data rather than a predicate, and\nsilently skipping an action whose arguments failed to evaluate would be a silent failure of exactly\nthe kind this release train has been removing. It currently propagates the error to the caller, and\nthat asymmetry is documented at the code. Ratifying it against a real consumer is tracked separately." + "body": "### archied — EDA: playbook action arguments are compiled at load (J2)\n\n- A playbook action may now declare `args`, compiled as CEL expressions when the playbook loads.\n `args` and `when` share one compilation path and one evaluation context, so an expression written\n for one works in the other.\n- **Behaviour change:** an `args` expression that does not compile is a **load failure**, not a\n runtime miss — the same reject-at-load rule already applied to a binding collision and to an\n unknown `actions.`. In practice, a daemon loading a playbook with a malformed `args` block\n fails at startup rather than part-way through a dispatch.\n- Compiling several arguments now reports the **first** bad key deterministically (keys are sorted).\n Previously it ranged a map, so the reported bad key could differ between runs and the failure was\n not reproducible.\n- `args` is deliberately **inert** for now: parsed, compiled and stored, but no shipped position\n consumes it yet. A consumer arrives with the first side-effecting position.\n\n**Not yet decided:** how an `args` evaluation failure behaves at dispatch. The `when` predicate rule\n(error, skip, log) does not obviously transfer, because `args` is data rather than a predicate, and\nsilently skipping an action whose arguments failed to evaluate would be a silent failure of exactly\nthe kind this release train has been removing. It currently propagates the error to the caller, and\nthat asymmetry is documented at the code. Ratifying it against a real consumer is tracked separately." }, { - "component": "archied", - "name": "archied", "version": "1.32.1", "date": "2026-09-22", - "body": "### Host packaging: `archie-messaging` now ships and updates\n\n- `cmd/archie-messaging` is included in the distribution zip, and `scripts/archie-update-install`\n installs and restarts it.\n- **Why this mattered.** v1.30.0 moved Telegram, email and webhook out of `archied` and into\n `archie-messaging`, but nothing packaged the new binary. A host install that upgraded across\n v1.30.0 therefore ran on with **no messaging process at all**: `archied` logged that it stopped\n serving the telegram gateway, nothing replaced it, and Telegram stayed dead — with no error\n logged anywhere, because nothing was failing. The process simply did not exist.\n- The host component set was enumerated in four places — the zip's build loop, the zip's copy list,\n the installer's service list, and the installer's binary list — and `archie-messaging` was missing\n from all four. The duplication was the defect: a single test now derives the host-run commands\n from `cmd/` and asserts that all four lists agree with it, so adding or extracting a process fails\n until it is packaged.\n- `deployments/systemd-user-service.md` gains the messaging unit. That is load-bearing rather than\n cosmetic: the updater refuses an update when a service unit is missing and tells the operator to\n create one from that document, which previously had nothing to offer.\n\n**Upgrade note:** a host that reached v1.30.0 without a messaging unit has been running with no\nTelegram, email or webhook. Updating to this release installs and starts `archie-messaging`." + "body": "### archied — Host packaging: `archie-messaging` now ships and updates\n\n- `cmd/archie-messaging` is included in the distribution zip, and `scripts/archie-update-install`\n installs and restarts it.\n- **Why this mattered.** v1.30.0 moved Telegram, email and webhook out of `archied` and into\n `archie-messaging`, but nothing packaged the new binary. A host install that upgraded across\n v1.30.0 therefore ran on with **no messaging process at all**: `archied` logged that it stopped\n serving the telegram gateway, nothing replaced it, and Telegram stayed dead — with no error\n logged anywhere, because nothing was failing. The process simply did not exist.\n- The host component set was enumerated in four places — the zip's build loop, the zip's copy list,\n the installer's service list, and the installer's binary list — and `archie-messaging` was missing\n from all four. The duplication was the defect: a single test now derives the host-run commands\n from `cmd/` and asserts that all four lists agree with it, so adding or extracting a process fails\n until it is packaged.\n- `deployments/systemd-user-service.md` gains the messaging unit. That is load-bearing rather than\n cosmetic: the updater refuses an update when a service unit is missing and tells the operator to\n create one from that document, which previously had nothing to offer.\n\n**Upgrade note:** a host that reached v1.30.0 without a messaging unit has been running with no\nTelegram, email or webhook. Updating to this release installs and starts `archie-messaging`." }, { - "component": "archied", - "name": "archied", "version": "1.32.0", "date": "2026-09-22", - "body": "### EDA: playbook action ids, and a dispatch idempotency ledger\n\n- **Action ids (J1).** Every action a later action references must now carry an `id`. Ids are\n validated at load -- unique and stable-identifier-shaped -- and a `when`/`args` expression\n naming an unknown `actions.` is a **load failure**, not a runtime miss, the same\n reject-at-load rule already applied to a binding collision.\n- **Reference classification is strict at load.** A map-index reference (`actions[expr]`), a\n non-literal index, and a reference to an unknown prior id are all rejected when the playbook\n loads; references are classified by identifier versus static access, and the when-compilation\n helper is shared between the load-time and runtime paths.\n- **Dispatch idempotency ledger.** A `playbook_dispatches` row records a dispatch against\n `(playbook_id, playbook_version, event_id, action_id)`, written with `INSERT OR IGNORE` and\n surfaced through the shared `store.ErrAlreadyDispatched` sentinel. Module, channel and forge\n action positions are therefore at-most-once, which is what unblocks the side-effecting\n positions that were previously rejected at load.\n- **The ledger is wired into production.** `stateStoreDeps` constructs `Deps.PlaybookDispatcher`,\n so the ledger RPCs no longer answer `Unavailable` in a running daemon. This defect was found\n by the pre-release review of this change rather than by its tests.\n\n**Behaviour change:** a playbook whose actions reference `actions.` without declaring that\nid, declare a duplicate id, or index `actions` with a non-literal value now fails to load\ninstead of failing at dispatch time." + "body": "### archied — EDA: playbook action ids, and a dispatch idempotency ledger\n\n- **Action ids (J1).** Every action a later action references must now carry an `id`. Ids are\n validated at load -- unique and stable-identifier-shaped -- and a `when`/`args` expression\n naming an unknown `actions.` is a **load failure**, not a runtime miss, the same\n reject-at-load rule already applied to a binding collision.\n- **Reference classification is strict at load.** A map-index reference (`actions[expr]`), a\n non-literal index, and a reference to an unknown prior id are all rejected when the playbook\n loads; references are classified by identifier versus static access, and the when-compilation\n helper is shared between the load-time and runtime paths.\n- **Dispatch idempotency ledger.** A `playbook_dispatches` row records a dispatch against\n `(playbook_id, playbook_version, event_id, action_id)`, written with `INSERT OR IGNORE` and\n surfaced through the shared `store.ErrAlreadyDispatched` sentinel. Module, channel and forge\n action positions are therefore at-most-once, which is what unblocks the side-effecting\n positions that were previously rejected at load.\n- **The ledger is wired into production.** `stateStoreDeps` constructs `Deps.PlaybookDispatcher`,\n so the ledger RPCs no longer answer `Unavailable` in a running daemon. This defect was found\n by the pre-release review of this change rather than by its tests.\n\n**Behaviour change:** a playbook whose actions reference `actions.` without declaring that\nid, declare a duplicate id, or index `actions` with a non-literal value now fails to load\ninstead of failing at dispatch time.\n\n### archie-agent\n\nThe sandboxed runtime links `storecontract` and `staterpc`, so it carries the dispatch-ledger\ncontract alongside archied:\n\n- The shared `store.ErrAlreadyDispatched` sentinel now describes both dedup ledgers --\n `binding_dispatches` per `(binding_id, capture_id)`, and `playbook_dispatches` per\n `(playbook_id, playbook_version, event_id, action_id)`. Each is an at-most-once guarantee.\n- `RecordPlaybookDispatch` is part of the store contract the runtime builds against.\n\narchied and archie-agent move together in this release." }, { - "component": "archied", - "name": "archied", "version": "1.31.0", "date": "2026-09-22", - "body": "### Dashboard replaced: Preact -> Vue 3 + shadcn-vue\n\nThe dashboard is now a Vue 3 application built on shadcn-vue. This is the\nlarge piece of this release; it touches every page.\n\n- History routing, a grouped topbar built from components, the violet palette\n with self-hosted Geist, and a command palette with live tasks.\n- Chat is a FAB-opened panel that behaves like a chat window and scrolls its\n transcript with `MessageScroller`.\n- Task actions and dangerous approvals are deliberate; the task detail page is\n a single head strip with honest states; the run page settles its head around\n an attempts pager, which is hidden for zero or one attempt.\n- Appearance and System navigation were refined, with a four-column appearance\n grid on wide screens.\n- A copy pass removed redundant tails and restating descriptions, empty states\n derive their own titles, and a stuck log read surfaces as an error rather\n than eternal loading.\n- The capture pane is bound to the list it sits beside and reads beside it,\n not over it.\n\n### Events is one page with three tabs\n\n- Inspector, Bindings and Mappings are now tabs of a single **Events** page.\n- The nav entry is always live, the tabs prune by capability, and the three old\n paths survive as bookmarks that redirect to their tab.\n- Tab selection lives in one module (`ui/src/events/tab-selection.ts`) that the\n page uses, rather than a copy of it.\n- `feat(tools)`: a capture-intake sender exists for exercising the Events\n surfaces.\n\n### The channel travels with the message\n\n`SessionSource.Platform` -- the first component of the session natural key, and\nthe column `GetByChannel` filters on -- was a constant `\"web\"`, because one\nRouter serves every channel and named itself after its own. Two things followed:\nthe per-user identity policy was real code that no production call site reached\nwith a real channel name, and a curator pass's write to agent-user memory could\nnot be read back by the turn that wrote it, because that turn resolved no\n`UserID`.\n\n- The frontends now name the channel they carry (`telegram`, `email`,\n `webhook`, `web`), the channel rides the message, and the Gateway stamps the\n session from it -- falling back to its own name when a sender names none,\n which is what every existing row holds.\n- Identity resolution reads the platform off the inbound, so `carriesPersonIdentity`\n decides something in production: telegram and email resolve a person, the\n dashboard and a webhook resolve nothing, and an unknown platform fails closed.\n- **Behaviour change:** a chat whose active session came from `/new` or\n `/branch` re-resolves once, because session lookup now filters on the\n channel's real name. A chat without `/new` re-resolves onto the same\n deterministic id and heals silently.\n- Deliberately unchanged: `TurnRunnerConfig.Channel` still keys tool\n availability, so no channel gains or loses a tool in this release.\n\n### Control plane: runtime administration, history, and derived schemas\n\n- The State Store's gRPC server now carries runtime administration, and each\n process reports which settings version it is running; the dashboard shows it.\n- Resource history is exposed so edits can be reviewed and rolled back, and\n resource schemas are derived from the documents they describe -- the document\n editor reads the derived schema (labels from `title`, `format: duration` ->\n `1m0s`, hints from `doc`), and the abandoned schema-driven card is deleted.\n- A live settings replacement is checked before it is switched to, the daemon's\n state surfaces are folded into one boot step, and a SIGHUP reload re-applies\n database-owned settings.\n- Forge intake settings that nothing reads are now rejected at load.\n\n### Configuration: judged where it is owned\n\n- The runtime config overlay is deleted; database-owned settings are judged at\n the layer that owns them rather than on the file load path.\n- A file overlay no longer drops the fields it omits inside a map entry, and a\n kind with no stored value leaves the file's value in force.\n- The default config path is resolved in one place, and the channel document\n has its own shape.\n\n### State Store: offline backup, restore, validate and rollback\n\n- New offline backup / restore / validate / rollback path.\n- `validate` runs boot's own gate; it no longer replaces the database, reads a\n kind the store does not hold as its seed, or touches the daemon's log.\n- The recovery control-plane server is built on the shared step vocabulary.\n\n### Workflow: one step vocabulary and a `gate.diff-rules` replacement\n\n- The step vocabulary is owned by a family manager registered at each\n composition root, replacing `.archie/gate.go` with `gate.diff-rules`, which\n fails closed on a change it never read.\n- Workflow roots are pinned and the dead vocabulary is removed; the workflow pin\n crosses the wire.\n- The schedules resource skips the legacy cron jobs it cannot hold, and the\n scheduling policy carries the label its trigger pairs with.\n\n### EDA: the playbook coordinator reaches production selection\n\n- The playbook coordinator is wired into production workflow selection, so a\n matching playbook decides a real task's workflow at the daemon's definition\n pin, inheriting idempotency from `TaskEnvelope`.\n\n### Reliability and operations\n\n- `cronstore` writes a schedule interval as a duration, not nanoseconds -- a\n persisted `1m` no longer round-trips as `60000000000`.\n- Worktrees are cut from the mapped base branch, and the Gateway's worktree\n manager is built so it serves `review_pr`.\n- A late max-uptime callback no longer resurrects teardown state.\n- The state store dial installs client keepalive, and its server policy accepts\n the dialer's pings; control-plane watch streams re-establish themselves after\n they end.\n- `/status` serves only the health facts a reply can carry; the daemon reports\n systemd readiness and loop-driven watchdog heartbeats.\n- A webhook route path no longer becomes a sender identity.\n- A chat session compresses when a turn crosses its context budget.\n- The MCP client supports per-server `parallel_tool_calls`, carried through the\n tool-settings projection.\n- Resource request-ID idempotency keys are scoped to their kind.\n- The session curator addresses memory by the deployment's bot user." + "body": "### archied — Dashboard replaced: Preact -> Vue 3 + shadcn-vue\n\nThe dashboard is now a Vue 3 application built on shadcn-vue. This is the\nlarge piece of this release; it touches every page.\n\n- History routing, a grouped topbar built from components, the violet palette\n with self-hosted Geist, and a command palette with live tasks.\n- Chat is a FAB-opened panel that behaves like a chat window and scrolls its\n transcript with `MessageScroller`.\n- Task actions and dangerous approvals are deliberate; the task detail page is\n a single head strip with honest states; the run page settles its head around\n an attempts pager, which is hidden for zero or one attempt.\n- Appearance and System navigation were refined, with a four-column appearance\n grid on wide screens.\n- A copy pass removed redundant tails and restating descriptions, empty states\n derive their own titles, and a stuck log read surfaces as an error rather\n than eternal loading.\n- The capture pane is bound to the list it sits beside and reads beside it,\n not over it.\n\n### archied — Events is one page with three tabs\n\n- Inspector, Bindings and Mappings are now tabs of a single **Events** page.\n- The nav entry is always live, the tabs prune by capability, and the three old\n paths survive as bookmarks that redirect to their tab.\n- Tab selection lives in one module (`ui/src/events/tab-selection.ts`) that the\n page uses, rather than a copy of it.\n- `feat(tools)`: a capture-intake sender exists for exercising the Events\n surfaces.\n\n### archied — The channel travels with the message\n\n`SessionSource.Platform` -- the first component of the session natural key, and\nthe column `GetByChannel` filters on -- was a constant `\"web\"`, because one\nRouter serves every channel and named itself after its own. Two things followed:\nthe per-user identity policy was real code that no production call site reached\nwith a real channel name, and a curator pass's write to agent-user memory could\nnot be read back by the turn that wrote it, because that turn resolved no\n`UserID`.\n\n- The frontends now name the channel they carry (`telegram`, `email`,\n `webhook`, `web`), the channel rides the message, and the Gateway stamps the\n session from it -- falling back to its own name when a sender names none,\n which is what every existing row holds.\n- Identity resolution reads the platform off the inbound, so `carriesPersonIdentity`\n decides something in production: telegram and email resolve a person, the\n dashboard and a webhook resolve nothing, and an unknown platform fails closed.\n- **Behaviour change:** a chat whose active session came from `/new` or\n `/branch` re-resolves once, because session lookup now filters on the\n channel's real name. A chat without `/new` re-resolves onto the same\n deterministic id and heals silently.\n- Deliberately unchanged: `TurnRunnerConfig.Channel` still keys tool\n availability, so no channel gains or loses a tool in this release.\n\n### archied — Control plane: runtime administration, history, and derived schemas\n\n- The State Store's gRPC server now carries runtime administration, and each\n process reports which settings version it is running; the dashboard shows it.\n- Resource history is exposed so edits can be reviewed and rolled back, and\n resource schemas are derived from the documents they describe -- the document\n editor reads the derived schema (labels from `title`, `format: duration` ->\n `1m0s`, hints from `doc`), and the abandoned schema-driven card is deleted.\n- A live settings replacement is checked before it is switched to, the daemon's\n state surfaces are folded into one boot step, and a SIGHUP reload re-applies\n database-owned settings.\n- Forge intake settings that nothing reads are now rejected at load.\n\n### archied — Configuration: judged where it is owned\n\n- The runtime config overlay is deleted; database-owned settings are judged at\n the layer that owns them rather than on the file load path.\n- A file overlay no longer drops the fields it omits inside a map entry, and a\n kind with no stored value leaves the file's value in force.\n- The default config path is resolved in one place, and the channel document\n has its own shape.\n\n### archied — State Store: offline backup, restore, validate and rollback\n\n- New offline backup / restore / validate / rollback path.\n- `validate` runs boot's own gate; it no longer replaces the database, reads a\n kind the store does not hold as its seed, or touches the daemon's log.\n- The recovery control-plane server is built on the shared step vocabulary.\n\n### archied — Workflow: one step vocabulary and a `gate.diff-rules` replacement\n\n- The step vocabulary is owned by a family manager registered at each\n composition root, replacing `.archie/gate.go` with `gate.diff-rules`, which\n fails closed on a change it never read.\n- Workflow roots are pinned and the dead vocabulary is removed; the workflow pin\n crosses the wire.\n- The schedules resource skips the legacy cron jobs it cannot hold, and the\n scheduling policy carries the label its trigger pairs with.\n\n### archied — EDA: the playbook coordinator reaches production selection\n\n- The playbook coordinator is wired into production workflow selection, so a\n matching playbook decides a real task's workflow at the daemon's definition\n pin, inheriting idempotency from `TaskEnvelope`.\n\n### archied — Reliability and operations\n\n- `cronstore` writes a schedule interval as a duration, not nanoseconds -- a\n persisted `1m` no longer round-trips as `60000000000`.\n- Worktrees are cut from the mapped base branch, and the Gateway's worktree\n manager is built so it serves `review_pr`.\n- A late max-uptime callback no longer resurrects teardown state.\n- The state store dial installs client keepalive, and its server policy accepts\n the dialer's pings; control-plane watch streams re-establish themselves after\n they end.\n- `/status` serves only the health facts a reply can carry; the daemon reports\n systemd readiness and loop-driven watchdog heartbeats.\n- A webhook route path no longer becomes a sender identity.\n- A chat session compresses when a turn crosses its context budget.\n- The MCP client supports per-server `parallel_tool_calls`, carried through the\n tool-settings projection.\n- Resource request-ID idempotency keys are scoped to their kind.\n- The session curator addresses memory by the deployment's bot user.\n\n### archie-agent\n\nThe sandboxed runtime links the same shared packages as archied, so this\nrelease carries the control-plane and workflow changes alongside it:\n\n- Runtime administration over the State Store's gRPC server, resource history,\n and control-plane apply status on the store contract.\n- The shared step vocabulary, owned by a family manager registered at each\n composition root, and `gate.diff-rules` in place of `.archie/gate.go`\n (fails closed on a change it never read).\n- The workflow pin crosses the wire.\n\nRuntime-specific changes:\n\n- `refactor(plugin)`: the unused `Registry` type is deleted.\n- `yaegiutil` refuses incomplete Yaegi interface wrappers at load rather than\n running them.\n- The runtime config overlay is deleted.\n- The state store dial installs client keepalive, and the server policy accepts\n the dialer's pings.\n- The MCP client supports per-server `parallel_tool_calls`.\n- A late max-uptime callback no longer resurrects teardown state.\n- A webhook route path no longer becomes a sender identity.\n\nNote: the `archie-agent` image is rebuilt by this tag through CI\n(`.github/workflows/deploy.yml`); a gateway-only release would not have rebuilt\nit. `docker compose pull agent` is required to pick it up." }, { - "component": "archie", - "name": "archie-agent", - "version": "1.35.0", - "date": "2026-09-22", - "body": "The sandboxed runtime links the same shared packages as archied, so this release carries the\nchannel-lifecycle store contract and the stricter action-load errors with it:\n\n- The channel-status store contract (`PutChannelStatus`/`ListChannelStatus`) and its replace-the-set\n semantics.\n- Authoritative module ids and stricter action load errors: a misspelled result field, an unknown id,\n or a dynamic `actions` read now fails the playbook load rather than the dispatch.\n\narchied and archie-agent move together in this release." - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.32.0", - "date": "2026-09-22", - "body": "The sandboxed runtime links `storecontract` and `staterpc`, so it carries the dispatch-ledger\ncontract alongside archied:\n\n- The shared `store.ErrAlreadyDispatched` sentinel now describes both dedup ledgers --\n `binding_dispatches` per `(binding_id, capture_id)`, and `playbook_dispatches` per\n `(playbook_id, playbook_version, event_id, action_id)`. Each is an at-most-once guarantee.\n- `RecordPlaybookDispatch` is part of the store contract the runtime builds against.\n\narchied and archie-agent move together in this release." - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.31.0", - "date": "2026-09-22", - "body": "The sandboxed runtime links the same shared packages as archied, so this\nrelease carries the control-plane and workflow changes alongside it:\n\n- Runtime administration over the State Store's gRPC server, resource history,\n and control-plane apply status on the store contract.\n- The shared step vocabulary, owned by a family manager registered at each\n composition root, and `gate.diff-rules` in place of `.archie/gate.go`\n (fails closed on a change it never read).\n- The workflow pin crosses the wire.\n\nRuntime-specific changes:\n\n- `refactor(plugin)`: the unused `Registry` type is deleted.\n- `yaegiutil` refuses incomplete Yaegi interface wrappers at load rather than\n running them.\n- The runtime config overlay is deleted.\n- The state store dial installs client keepalive, and the server policy accepts\n the dialer's pings.\n- The MCP client supports per-server `parallel_tool_calls`.\n- A late max-uptime callback no longer resurrects teardown state.\n- A webhook route path no longer becomes a sender identity.\n\nNote: the `archie-agent` image is rebuilt by this tag through CI\n(`.github/workflows/deploy.yml`); a gateway-only release would not have rebuilt\nit. `docker compose pull agent` is required to pick it up." - }, - { - "component": "archied", - "name": "archied", "version": "1.30.0", "date": "2026-09-20", - "body": "### Messaging Service extraction completed\n\nTelegram, email and webhook no longer run inside the daemon. They run in\n`archie-messaging` and reach the daemon through the Gateway's `ChatContract`\nover gRPC; the daemon builds no channel and no `gateway.Router` (#899).\n\n- The operator surface is re-wired in the extracted service: `/update` (built\n from its own `[chat.telegram]` commands), the update-report relay, the\n `show_tool_calls` projection, and `/restart`'s config reload, which\n re-resolves the token and allowlist from this service's own file and refuses\n a reload that resolves to an empty token.\n- `/version` is sourced from the Gateway through a new `ChatSnapshot.Version`\n field. `cmd/archie-messaging` deliberately takes no version ldflags, so it\n cannot report a partial upgrade as a matched one.\n- Channel configuration is validated at composition, so a configured-but-\n invalid front-end fails the service instead of being silently dropped.\n- The inbound rate limiter moves to the Gateway, which now owns the only\n Router and is therefore the one place a per-sender budget can apply to every\n channel's turns.\n\n`RunningVersions` and `ReleaseAnnouncements` are deliberately left unwired:\nboth need a component's real running version, and the only versions this\nprocess can obtain are another binary's stamps. See\n`docs/architecture/migration-decisions.md`.\n\n### Configuration\n\n- `diff_cap_lines = 0` now switches the cap off, as the dashboard and the\n workflow step have always documented. It was a plain `int`, so the defaults\n pass could not tell an absent key from an explicit `0` and rewrote both to\n 400 -- the documented way to disable the cap was unreachable. **Behaviour\n change:** a config that set `0` was silently getting 400 and will now get no\n cap.\n- The same ambiguity was failing open per identity: `configForIdentity`\n assigned the identity's value unconditionally, so an identity that merely\n omitted `diff_cap_lines` overwrote the shared cap with the zero value and\n disabled the safety rail entirely. An identity now overrides only when it\n sets the key.\n- A diff-cap park no longer tells the operator to \"approve manually\". A parked\n task's actions are retry, abandon and reject, so there is no approve path out\n of diff-cap; it now names the two things that work.\n- `[health].dependency_timeout` makes the daemon's readiness probe timeout\n configurable, matching the extracted services.\n\n### Chat rendering\n\n- `/status` and `/tasks` are line-oriented reports but separated lines with a\n plain newline, which is CommonMark's soft wrap: the Telegram renderer joined\n them into one run-on paragraph. The renderer implements CommonMark's hard\n line break and the reports use it. Ordinary prose still soft-wraps.\n- A park reason is capped to its first line in the `/tasks` list. It carries\n whatever the failing stage reported, which for a lint gate is a whole tool\n log; unbounded, one parked task pushed every other task out of the reply. The\n full reason is unchanged on the task, in `task_list` and on the dashboard.\n\n### Review\n\n- Review findings are posted as line-anchored PR comments with suggested fixes,\n and a suggestion must be single-line -- GitHub applies a multi-line suggestion\n only up to its first line, silently corrupting the file (#891).\n- The remediate workflow handles PR review comments and requested changes.\n\n### /status health surface\n\n`/status` reports the live broker connection and the last-known outcome of this\nprocess's chat-model calls, alongside the queue depth and runtime block (#892).\n\n- A provider error is flattened and capped, so a multiline or oversized error\n cannot break the one-line-per-fact layout.\n- Concurrent model calls no longer reorder: the completion time is taken before\n the lock, so the newer outcome wins rather than whichever goroutine stored\n last.\n- Curator model calls are recorded too. They bypass the chat path, so a daemon\n whose only recent model traffic was curator work reported \"no calls attempted\n yet\" while the provider was demonstrably reachable.\n- Title generation does not record health. It runs detached under its own\n bound and its error is swallowed, so a cosmetic timeout was overwriting the\n line with \"failed\".\n\n**Known limitation:** the container, poll and channel sections cannot render.\nThose facts live in the daemon, but the only Router lives in the Gateway\nprocess, which has no container pool and no poll loop. The command description\nsays what actually appears; restoring the rest needs a cross-process health\ncontract.\n\n### Dashboard and containers\n\n- The served lifecycle vocabulary reaches an already-painted page, the page\n registry matches the routes, and the build verifies `ui/dist` is fresh\n instead of never looking at it (#890, #898).\n- The container reaper no longer deletes teardown bookkeeping early, so a\n released container is not torn down twice (#893).\n\n### Build\n\n- `task fmt` runs `golangci-lint fmt` -- the same engine and configuration the\n gate checks with. Standalone `gofumpt` cannot reproduce gci's import\n grouping, so formatting and linting could not converge and no command\n satisfied the gate (#901).\n- `goimports` is deliberately absent from the formatter set: it re-reads and\n re-parses the module index once per file, ~135s across this tree.\n\n### Fixed\n\n- `Config.Clone` left the new diff-cap pointers aliased, so a clone could write\n through to the published snapshot (#902).\n- A curator asking for a completion on a daemon with no configured provider\n panicked the process; it now returns an error." + "body": "### archied — Messaging Service extraction completed\n\nTelegram, email and webhook no longer run inside the daemon. They run in\n`archie-messaging` and reach the daemon through the Gateway's `ChatContract`\nover gRPC; the daemon builds no channel and no `gateway.Router` (#899).\n\n- The operator surface is re-wired in the extracted service: `/update` (built\n from its own `[chat.telegram]` commands), the update-report relay, the\n `show_tool_calls` projection, and `/restart`'s config reload, which\n re-resolves the token and allowlist from this service's own file and refuses\n a reload that resolves to an empty token.\n- `/version` is sourced from the Gateway through a new `ChatSnapshot.Version`\n field. `cmd/archie-messaging` deliberately takes no version ldflags, so it\n cannot report a partial upgrade as a matched one.\n- Channel configuration is validated at composition, so a configured-but-\n invalid front-end fails the service instead of being silently dropped.\n- The inbound rate limiter moves to the Gateway, which now owns the only\n Router and is therefore the one place a per-sender budget can apply to every\n channel's turns.\n\n`RunningVersions` and `ReleaseAnnouncements` are deliberately left unwired:\nboth need a component's real running version, and the only versions this\nprocess can obtain are another binary's stamps. See\n`docs/architecture/migration-decisions.md`.\n\n### archied — Configuration\n\n- `diff_cap_lines = 0` now switches the cap off, as the dashboard and the\n workflow step have always documented. It was a plain `int`, so the defaults\n pass could not tell an absent key from an explicit `0` and rewrote both to\n 400 -- the documented way to disable the cap was unreachable. **Behaviour\n change:** a config that set `0` was silently getting 400 and will now get no\n cap.\n- The same ambiguity was failing open per identity: `configForIdentity`\n assigned the identity's value unconditionally, so an identity that merely\n omitted `diff_cap_lines` overwrote the shared cap with the zero value and\n disabled the safety rail entirely. An identity now overrides only when it\n sets the key.\n- A diff-cap park no longer tells the operator to \"approve manually\". A parked\n task's actions are retry, abandon and reject, so there is no approve path out\n of diff-cap; it now names the two things that work.\n- `[health].dependency_timeout` makes the daemon's readiness probe timeout\n configurable, matching the extracted services.\n\n### archied — Chat rendering\n\n- `/status` and `/tasks` are line-oriented reports but separated lines with a\n plain newline, which is CommonMark's soft wrap: the Telegram renderer joined\n them into one run-on paragraph. The renderer implements CommonMark's hard\n line break and the reports use it. Ordinary prose still soft-wraps.\n- A park reason is capped to its first line in the `/tasks` list. It carries\n whatever the failing stage reported, which for a lint gate is a whole tool\n log; unbounded, one parked task pushed every other task out of the reply. The\n full reason is unchanged on the task, in `task_list` and on the dashboard.\n\n### archied — Review\n\n- Review findings are posted as line-anchored PR comments with suggested fixes,\n and a suggestion must be single-line -- GitHub applies a multi-line suggestion\n only up to its first line, silently corrupting the file (#891).\n- The remediate workflow handles PR review comments and requested changes.\n\n### archied — /status health surface\n\n`/status` reports the live broker connection and the last-known outcome of this\nprocess's chat-model calls, alongside the queue depth and runtime block (#892).\n\n- A provider error is flattened and capped, so a multiline or oversized error\n cannot break the one-line-per-fact layout.\n- Concurrent model calls no longer reorder: the completion time is taken before\n the lock, so the newer outcome wins rather than whichever goroutine stored\n last.\n- Curator model calls are recorded too. They bypass the chat path, so a daemon\n whose only recent model traffic was curator work reported \"no calls attempted\n yet\" while the provider was demonstrably reachable.\n- Title generation does not record health. It runs detached under its own\n bound and its error is swallowed, so a cosmetic timeout was overwriting the\n line with \"failed\".\n\n**Known limitation:** the container, poll and channel sections cannot render.\nThose facts live in the daemon, but the only Router lives in the Gateway\nprocess, which has no container pool and no poll loop. The command description\nsays what actually appears; restoring the rest needs a cross-process health\ncontract.\n\n### archied — Dashboard and containers\n\n- The served lifecycle vocabulary reaches an already-painted page, the page\n registry matches the routes, and the build verifies `ui/dist` is fresh\n instead of never looking at it (#890, #898).\n- The container reaper no longer deletes teardown bookkeeping early, so a\n released container is not torn down twice (#893).\n\n### archied — Build\n\n- `task fmt` runs `golangci-lint fmt` -- the same engine and configuration the\n gate checks with. Standalone `gofumpt` cannot reproduce gci's import\n grouping, so formatting and linting could not converge and no command\n satisfied the gate (#901).\n- `goimports` is deliberately absent from the formatter set: it re-reads and\n re-parses the module index once per file, ~135s across this tree.\n\n### archied — Fixed\n\n- `Config.Clone` left the new diff-cap pointers aliased, so a clone could write\n through to the published snapshot (#902).\n- A curator asking for a completion on a daemon with no configured provider\n panicked the process; it now returns an error.\n\n### archie-agent\n\n- The sandboxed runtime picks up line-anchored review comments: a finding is\n posted against the line it is about, with a suggested fix where it has one,\n and a suggestion is rejected unless it is single-line -- GitHub applies a\n multi-line suggestion only up to its first line, silently corrupting the\n file (#891).\n- `diff_cap_lines` is an optional value in the shared config the runtime\n reconstructs, so an explicit `0` means \"no cap\" rather than being rewritten\n to the default. **Behaviour change** for a repo that set `0` expecting\n unlimited and was silently getting 400 (#899).\n- A diff-cap park names a remedy that exists: a parked task's actions are\n retry, abandon and reject, so the reason no longer says \"approve manually\".\n- A released container is not torn down twice -- the reaper no longer deletes\n teardown bookkeeping before `Release` is finished with it (#893).\n- Build toolchain: `gofumpt` and `golangci-lint` are pinned as one matched\n pair, and `task fmt` uses the same engine the gate checks with, so the\n runtime's own gate is satisfiable (#901)." }, { - "component": "archie", - "name": "archie-agent", - "version": "1.30.0", - "date": "2026-09-20", - "body": "- The sandboxed runtime picks up line-anchored review comments: a finding is\n posted against the line it is about, with a suggested fix where it has one,\n and a suggestion is rejected unless it is single-line -- GitHub applies a\n multi-line suggestion only up to its first line, silently corrupting the\n file (#891).\n- `diff_cap_lines` is an optional value in the shared config the runtime\n reconstructs, so an explicit `0` means \"no cap\" rather than being rewritten\n to the default. **Behaviour change** for a repo that set `0` expecting\n unlimited and was silently getting 400 (#899).\n- A diff-cap park names a remedy that exists: a parked task's actions are\n retry, abandon and reject, so the reason no longer says \"approve manually\".\n- A released container is not torn down twice -- the reaper no longer deletes\n teardown bookkeeping before `Release` is finished with it (#893).\n- Build toolchain: `gofumpt` and `golangci-lint` are pinned as one matched\n pair, and `task fmt` uses the same engine the gate checks with, so the\n runtime's own gate is satisfiable (#901)." - }, - { - "component": "archied", - "name": "archied", "version": "1.29.0", "date": "2026-09-19", - "body": "### Security\n\n- `google.golang.org/grpc` bumped past `v1.84.0` to patch\n [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443), a server panic via a\n missing `:authority`/`Host` header reachable through `archied`'s gRPC\n gateway server. No stable release carries the fix yet, so this pins the\n pre-release commit that does (`v1.85.0-dev.0.20260825072537-93e31b48545e`)\n until `grpc-go` cuts `v1.85.0`.\n\n### Memory engine unification\n\nOne memory engine, addressed by four typed scopes (global, agent, user,\nagent-user), replaces the two disconnected stores that previously existed:\na chat-tool-written store nothing ever read back, and a curator-written store\nwith no scope model.\n\n- `internal/domain/memory` is a CRUD contract (`Create`/`Get`/`Query`/`List`/\n `Update`/`Forget`/`Revisions`) with retained revisions; updates supersede\n rather than overwrite, so a crash mid-write leaves a recoverable extra\n history entry, never a lost prior state (#886).\n- The chat turn reads its subject's scopes synchronously before the prompt is\n built, rendering recalled records into a `` block; a failing or\n panicking engine degrades to no memory block rather than failing the turn\n (#887).\n- The model writes memory through four id-addressed tools\n (`memory_create`/`update`/`delete`/`list`), scoped to the turn's own\n resolved identity -- the model chooses the scope kind, never the ids, so it\n has no path to write into another user's memory (#888).\n- The session curator now derives the agent-user scope from the session's own\n user-role messages, instead of keying facts by a session id that stops\n meaning anything once the session ends.\n- A channel with no resolvable user (dashboard, webhook) reads and writes only\n global and agent scope; a webhook's route path is never treated as a user\n identity.\n- Fixed a review finding on the read path: the per-scope record limit was\n being applied as one shared total across all scopes rather than per scope,\n and the rendered block's byte cap was checked before template escaping\n rather than after, letting the escaped block exceed it.\n\n### Work intake\n\n- feat(workintake): define review reaction envelope\n- feat(workintake): authorize review reactions by owned PR\n\n### Cleanup\n\n- Deleted the unwired plugin capability-host health surface\n (`Host.Health`/`Host.Manifests`/`ModuleStatus`) and the `Module.Health`\n chain it fed -- including the `mcp`/`builtin` tool-provider health\n implementations and their aggregation in `tools/provider.Registry` -- none\n of which had ever had a production caller (#882)." + "body": "### archied — Security\n\n- `google.golang.org/grpc` bumped past `v1.84.0` to patch\n [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443), a server panic via a\n missing `:authority`/`Host` header reachable through `archied`'s gRPC\n gateway server. No stable release carries the fix yet, so this pins the\n pre-release commit that does (`v1.85.0-dev.0.20260825072537-93e31b48545e`)\n until `grpc-go` cuts `v1.85.0`.\n\n### archied — Memory engine unification\n\nOne memory engine, addressed by four typed scopes (global, agent, user,\nagent-user), replaces the two disconnected stores that previously existed:\na chat-tool-written store nothing ever read back, and a curator-written store\nwith no scope model.\n\n- `internal/domain/memory` is a CRUD contract (`Create`/`Get`/`Query`/`List`/\n `Update`/`Forget`/`Revisions`) with retained revisions; updates supersede\n rather than overwrite, so a crash mid-write leaves a recoverable extra\n history entry, never a lost prior state (#886).\n- The chat turn reads its subject's scopes synchronously before the prompt is\n built, rendering recalled records into a `` block; a failing or\n panicking engine degrades to no memory block rather than failing the turn\n (#887).\n- The model writes memory through four id-addressed tools\n (`memory_create`/`update`/`delete`/`list`), scoped to the turn's own\n resolved identity -- the model chooses the scope kind, never the ids, so it\n has no path to write into another user's memory (#888).\n- The session curator now derives the agent-user scope from the session's own\n user-role messages, instead of keying facts by a session id that stops\n meaning anything once the session ends.\n- A channel with no resolvable user (dashboard, webhook) reads and writes only\n global and agent scope; a webhook's route path is never treated as a user\n identity.\n- Fixed a review finding on the read path: the per-scope record limit was\n being applied as one shared total across all scopes rather than per scope,\n and the rendered block's byte cap was checked before template escaping\n rather than after, letting the escaped block exceed it.\n\n### archied — Work intake\n\n- feat(workintake): define review reaction envelope\n- feat(workintake): authorize review reactions by owned PR\n\n### archied — Cleanup\n\n- Deleted the unwired plugin capability-host health surface\n (`Host.Health`/`Host.Manifests`/`ModuleStatus`) and the `Module.Health`\n chain it fed -- including the `mcp`/`builtin` tool-provider health\n implementations and their aggregation in `tools/provider.Registry` -- none\n of which had ever had a production caller (#882).\n\n### archie-agent\n\n- The sandboxed runtime picks up the review-reaction envelope and its\n owned-PR authorization, so an agent can only react to reviews on pull\n requests it opened itself.\n- `google.golang.org/grpc` bumped past `v1.84.0` to patch\n [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443) (shared dependency\n with `archied`; the pre-release commit is pinned pending a stable\n `v1.85.0`)." }, { - "component": "archied", - "name": "archied", "version": "1.28.0", "date": "2026-09-19", - "body": "### Task detail and attempt attribution\n\n- New per-run task detail page, showing each attempt's own events, changes and\n configuration rather than a single merged view.\n- Events, changes and config are attributed to the attempt that produced them;\n `Event` carries `attempt` and `ReadTaskLogRequest` carries `stage`.\n- The task detail page remounts when the task id changes, so switching tasks\n does not leave the previous one's data on screen.\n\n### Configuration\n\n- Services are keyed by name through a registry, so the State Store and Gateway\n listen addresses are configurable rather than fixed.\n- A partial overlay no longer clears the fields it omits — an overlay that set\n one key was wiping the rest.\n- The Services map is cloned on publish, so an overlay can no longer mutate the\n snapshot other readers are holding.\n- The service context is enforced at registration.\n\n### Logging and park reasons\n\n- A parked run's reason is recorded in its own attempt log, in both the daemon\n and the workflow, so \"why did this park?\" is answerable from the task itself.\n- `TaskRegistry.Write` takes the caller's context.\n\n### Worktrees and containers\n\n- Retries recover from path-type conflicts instead of failing opaquely, and the\n underlying cause is no longer masked.\n- The worktree is handed back on every sandbox exit.\n- A container's max-uptime reaper is cancelled on release, the cap stays active\n through the grace period, and teardown is claimed once rather than by\n cancelling a timer.\n\n### Daemon and startup\n\n- Every identity's forge and repos are swept at startup, including the root\n forge.\n- A cancelled startup is no longer reported as an exhausted sweep budget; an\n exhausted budget names itself as the cause.\n\n### Other\n\n- `grep` can use the workspace codesearch index.\n- Forge labels are matched when namespaced, so label-driven routing works for\n namespaced labels.\n- Triage is given criteria for choosing between workflows, and a workflow is\n required when a code change is needed.\n- The Telegram adapter restart callback is wired into the chat router.\n- The `ARCHIE_REACTIONS` fan-out stream is provisioned and bounded by age.\n- `archie-ui` exits cleanly when graceful shutdown overruns its deadline.\n- The dashboard's event pump retries priming until the State Store answers.\n- The update writer emits the agent version sidecar with a real newline.\n- The UI finishes its Preact port; the imperative DOM layer is deleted.\n- Collection fields decoded over the State Store gRPC contract are never nil\n slices, so an empty collection marshals as `[]` rather than `null`." + "body": "### archied — Task detail and attempt attribution\n\n- New per-run task detail page, showing each attempt's own events, changes and\n configuration rather than a single merged view.\n- Events, changes and config are attributed to the attempt that produced them;\n `Event` carries `attempt` and `ReadTaskLogRequest` carries `stage`.\n- The task detail page remounts when the task id changes, so switching tasks\n does not leave the previous one's data on screen.\n\n### archied — Configuration\n\n- Services are keyed by name through a registry, so the State Store and Gateway\n listen addresses are configurable rather than fixed.\n- A partial overlay no longer clears the fields it omits — an overlay that set\n one key was wiping the rest.\n- The Services map is cloned on publish, so an overlay can no longer mutate the\n snapshot other readers are holding.\n- The service context is enforced at registration.\n\n### archied — Logging and park reasons\n\n- A parked run's reason is recorded in its own attempt log, in both the daemon\n and the workflow, so \"why did this park?\" is answerable from the task itself.\n- `TaskRegistry.Write` takes the caller's context.\n\n### archied — Worktrees and containers\n\n- Retries recover from path-type conflicts instead of failing opaquely, and the\n underlying cause is no longer masked.\n- The worktree is handed back on every sandbox exit.\n- A container's max-uptime reaper is cancelled on release, the cap stays active\n through the grace period, and teardown is claimed once rather than by\n cancelling a timer.\n\n### archied — Daemon and startup\n\n- Every identity's forge and repos are swept at startup, including the root\n forge.\n- A cancelled startup is no longer reported as an exhausted sweep budget; an\n exhausted budget names itself as the cause.\n\n### archied — Other\n\n- `grep` can use the workspace codesearch index.\n- Forge labels are matched when namespaced, so label-driven routing works for\n namespaced labels.\n- Triage is given criteria for choosing between workflows, and a workflow is\n required when a code change is needed.\n- The Telegram adapter restart callback is wired into the chat router.\n- The `ARCHIE_REACTIONS` fan-out stream is provisioned and bounded by age.\n- `archie-ui` exits cleanly when graceful shutdown overruns its deadline.\n- The dashboard's event pump retries priming until the State Store answers.\n- The update writer emits the agent version sidecar with a real newline.\n- The UI finishes its Preact port; the imperative DOM layer is deleted.\n- Collection fields decoded over the State Store gRPC contract are never nil\n slices, so an empty collection marshals as `[]` rather than `null`.\n\n### archie-agent\n\n- The sandboxed runtime picks up the attempt-attribution contract, so the events\n and changes an agent produces are recorded against the attempt that produced\n them.\n- `grep` can use the workspace codesearch index.\n- A worktree is handed back on every sandbox exit, and container teardown is\n claimed once — a released container's reaper is cancelled rather than\n re-firing during the grace period.\n- Retries recover from worktree path-type conflicts instead of failing\n opaquely.\n- A parked workflow run records its park reason in its own log.\n- Triage criteria distinguish the workflows, and a workflow is required when a\n code change is needed.\n- Namespaced forge labels match when routing by kind.\n- The `ARCHIE_REACTIONS` fan-out stream is provisioned.\n- Collection fields decoded over the State Store gRPC contract are never nil\n slices, so an empty collection marshals as `[]` rather than `null`." }, { - "component": "archie", - "name": "archie-agent", - "version": "1.29.0", - "date": "2026-09-19", - "body": "- The sandboxed runtime picks up the review-reaction envelope and its\n owned-PR authorization, so an agent can only react to reviews on pull\n requests it opened itself.\n- `google.golang.org/grpc` bumped past `v1.84.0` to patch\n [GO-2026-6443](https://pkg.go.dev/vuln/GO-2026-6443) (shared dependency\n with `archied`; the pre-release commit is pinned pending a stable\n `v1.85.0`)." - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.28.0", - "date": "2026-09-19", - "body": "- The sandboxed runtime picks up the attempt-attribution contract, so the events\n and changes an agent produces are recorded against the attempt that produced\n them.\n- `grep` can use the workspace codesearch index.\n- A worktree is handed back on every sandbox exit, and container teardown is\n claimed once — a released container's reaper is cancelled rather than\n re-firing during the grace period.\n- Retries recover from worktree path-type conflicts instead of failing\n opaquely.\n- A parked workflow run records its park reason in its own log.\n- Triage criteria distinguish the workflows, and a workflow is required when a\n code change is needed.\n- Namespaced forge labels match when routing by kind.\n- The `ARCHIE_REACTIONS` fan-out stream is provisioned.\n- Collection fields decoded over the State Store gRPC contract are never nil\n slices, so an empty collection marshals as `[]` rather than `null`." - }, - { - "component": "archied", - "name": "archied", "version": "1.27.0", "date": "2026-09-17", - "body": "### Dashboard task logs\n\n- Task logs are readable from the dashboard again, through a new State Store\n read contract (`ReadTaskLog`, `StreamTaskLogContent`) rather than the UI\n process reaching into the daemon's log files. Wired server-side by the\n standalone state-store process.\n- Added `GET /api/tasks/{id}/logs/download`, serving an attempt's raw log as a\n `task--attempt-.log` attachment.\n- A process that cannot read logs and an attempt that recorded no log are now\n distinguishable (\"cannot read\" answers 503, \"no log\" answers 404) instead of\n both rendering as a claim about a configuration setting.\n\n### Telegram output\n\n- Tool results are summarised rather than quoted: a search reports how many\n matches came back, a truncated result reports the tool's own total. The\n renderer no longer states a count it computed from its own truncated sample.\n- Repeated successful tool calls collapse into one counted entry.\n- The tool-activity block is capped to a third of the live frame, keeps the\n newest lines, and marks what it dropped with a `+N earlier` indicator. Every\n line that fits is kept.\n- Every clamped answer marks its cut with an ellipsis, including the opening\n frame, which previously appeared to begin mid-sentence.\n- An error response from the log download no longer ships as a `.log` file.\n\n### Readiness and shutdown\n\n- The disk probe reports per-filesystem results and checks the root filesystem\n as well as the work directory, so a full root is no longer invisible.\n- A path shared by several disk targets keeps the strictest requirement any\n target places on it, so an optional target can no longer mask a required one.\n- The shutdown-watchdog test no longer races the Go scheduler, which was\n intermittently failing the quality gate and parking work unrelated to it.\n\n### Other\n\n- Messages persist the channel-native sender id.\n- go-telegram/bot bumped to v1.27.0, fixing a streaming bug where the multipart\n body could not be replayed and `sendMessage`/`editMessageText` failed until\n the connection dropped." + "body": "### archied — Dashboard task logs\n\n- Task logs are readable from the dashboard again, through a new State Store\n read contract (`ReadTaskLog`, `StreamTaskLogContent`) rather than the UI\n process reaching into the daemon's log files. Wired server-side by the\n standalone state-store process.\n- Added `GET /api/tasks/{id}/logs/download`, serving an attempt's raw log as a\n `task--attempt-.log` attachment.\n- A process that cannot read logs and an attempt that recorded no log are now\n distinguishable (\"cannot read\" answers 503, \"no log\" answers 404) instead of\n both rendering as a claim about a configuration setting.\n\n### archied — Telegram output\n\n- Tool results are summarised rather than quoted: a search reports how many\n matches came back, a truncated result reports the tool's own total. The\n renderer no longer states a count it computed from its own truncated sample.\n- Repeated successful tool calls collapse into one counted entry.\n- The tool-activity block is capped to a third of the live frame, keeps the\n newest lines, and marks what it dropped with a `+N earlier` indicator. Every\n line that fits is kept.\n- Every clamped answer marks its cut with an ellipsis, including the opening\n frame, which previously appeared to begin mid-sentence.\n- An error response from the log download no longer ships as a `.log` file.\n\n### archied — Readiness and shutdown\n\n- The disk probe reports per-filesystem results and checks the root filesystem\n as well as the work directory, so a full root is no longer invisible.\n- A path shared by several disk targets keeps the strictest requirement any\n target places on it, so an optional target can no longer mask a required one.\n- The shutdown-watchdog test no longer races the Go scheduler, which was\n intermittently failing the quality gate and parking work unrelated to it.\n\n### archied — Other\n\n- Messages persist the channel-native sender id.\n- go-telegram/bot bumped to v1.27.0, fixing a streaming bug where the multipart\n body could not be replayed and `sendMessage`/`editMessageText` failed until\n the connection dropped.\n\n### archie-agent\n\n- The per-task runtime picks up the new State Store task-log read contract, so\n the sandboxed agents share one log-reading path with the daemon and the\n dashboard." }, { - "component": "archied", - "name": "archied", "version": "1.26.0", "date": "2026-09-17", - "body": "- fix(webui): publish per-identity forges so multi-identity task rows keep their links\n- feat(config): add [scheduling] config block\n- feat(configuration): translate [scheduling] into scheduling.EngineConfig\n- feat(cronevents): adapt the events bus to scheduling.Sink\n- fix(webui): count every chat front-end in the published projection\n- fix(scheduling): respect configuration ownership\n- feat(ratelimit): wire per-identity inbound rate limiting into the gateway\n- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it\n- fix(store): keep an empty binding secret empty so a partial edit cannot erase it\n- fix(archied): stop advertising review_pr when no reviewer can run\n- fix(daemon): carry kind/label routing bindings to the process that routes\n- feat(configuration): add archied setup, the caller the first-run flow was built for\n- fix(configuration): stop letting a secret value be set from the command line\n- feat(configuration): let setup reference a secret without carrying its value\n- fix(archied): disable a provider whose credential is missing instead of refusing to boot\n- refactor(install): install.sh delegates config generation, and tests stop reading hand-written configs\n- fix(daemon): guard binding dispatch loop against nil dispatcher/creator\n- fix(webui): enforce CSRF/origin gate on binding and mapping mutations\n- fix(secret): recover a panicking secret engine instead of crashing\n- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone\n- fix(email): stop dropping the first paragraph of plain-text bodies\n- fix(logging): keep the live descriptor open across a failed rotation\n- feat(configuration): report config keys no decode target consumed\n- feat(archied): warn at boot when the config file has unrecognised keys\n- feat(archied): wire the scheduling ticker engine at boot\n- fix(agentworker): wire configured tool-result policy into worker's LoopRunner\n- refactor(staterpc): delete the superseded single-token auth interceptor\n- refactor(memory): delete the unreachable fence scrubber\n- fix(channels): delete unreachable Telegram webhook delivery mode\n- fix(gateway): delete unwired Router.Dangerous approval path\n- refactor(gateway): delete orphaned SessionState goal/steer/queue machinery\n- refactor(archied): delete the daemon's unused webui.Server and UI adapters\n- refactor(tools): delete unreachable dispatch/gating engine\n- feat(channels): wire chat.webhook route config through to the gateway\n- refactor(tools): delete unreachable AST-based tool discovery\n- refactor(tools): delete unused plugin-tool registration API from builtin.Registry\n- feat(channels): wire ConfigSchema/ValidateConfig into a startup validation loop\n- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted)\n- fix(curator): populate PassInput.Since with the prior pass time\n- fix(memory): install the threat scanner the composition root never wired\n- fix(staterpc): preserve marshal_error marker in eventDataJSON\n- fix(gate): validate finding level and share the blocking threshold\n- fix(scheduling): record a completed run so a recurring job stops re-firing every tick\n- fix(releaseupdate): don't treat empty available as deferred\n- fix(tools/provider/mcp): preserve MCP binary tool results for delivery\n- refactor(gateway): share sensitive-key markers with webhookguard\n- refactor(daemon): remove unreachable SQLite poll/drain path\n- refactor(tools/mcp): delete unreachable MCP adaptation path\n- fix(taskactions): resolve max_retries from the task's owning identity\n- fix(daemon): forward configured MCP servers to task agents\n- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path\n- refactor(skillbuild): delete dead AugmentRegistry path\n- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout\n- refactor(binding): delete dead Matcher.Overlaps method\n- refactor(forge): delete dead CreateIssue surface\n- fix(mcp): cancel in-flight SSE reconnect on Stop\n- fix(container): enforce MaxUptime lifetime cap with a timer\n- refactor(store): use taskstate status constants in SQL\n- fix(ui): unbreak binding approve and the two deletes, and centralise the client\n- fix(tools): stop testing on the text of other files, and ungate contractaudit\n- refactor(forge): delete the unwired RepliesAfter surface\n- refactor(config): delete the two decoded-but-unread policy fields\n\nThis release is dominated by dead-code removal and the completion of the\nscheduling capability. Roughly half the commits delete surfaces that no longer\nhad a caller: the unreachable SQLite poll/drain path, the unwired MCP\nadaptation path, the AST-based tool discovery, the superseded single-token auth\ninterceptor, and several dead forge and binding methods. The\n`IncrementRetryCount` State Store RPC is gone with them -- a breaking change to\nthe wire contract, accepted because nothing called it.\n\nThe cron/scheduling epic lands its remaining slices: the `[scheduling]` config\nblock, its translation into the engine's own settings, the events-bus sink\nadapter, and the boot wiring that starts the ticker. A recurring job now records\na completed run, so it stops re-firing on every tick.\n\nOperator-facing work: `archied setup` gives the first-run flow the caller it was\nbuilt for, configuration no longer accepts a secret value from the command line,\nand a provider whose credential is missing is disabled rather than refusing to\nboot. A secret engine that panics is now recovered instead of crashing the\ndaemon." + "body": "### archied\n\n- fix(webui): publish per-identity forges so multi-identity task rows keep their links\n- feat(config): add [scheduling] config block\n- feat(configuration): translate [scheduling] into scheduling.EngineConfig\n- feat(cronevents): adapt the events bus to scheduling.Sink\n- fix(webui): count every chat front-end in the published projection\n- fix(scheduling): respect configuration ownership\n- feat(ratelimit): wire per-identity inbound rate limiting into the gateway\n- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it\n- fix(store): keep an empty binding secret empty so a partial edit cannot erase it\n- fix(archied): stop advertising review_pr when no reviewer can run\n- fix(daemon): carry kind/label routing bindings to the process that routes\n- feat(configuration): add archied setup, the caller the first-run flow was built for\n- fix(configuration): stop letting a secret value be set from the command line\n- feat(configuration): let setup reference a secret without carrying its value\n- fix(archied): disable a provider whose credential is missing instead of refusing to boot\n- refactor(install): install.sh delegates config generation, and tests stop reading hand-written configs\n- fix(daemon): guard binding dispatch loop against nil dispatcher/creator\n- fix(webui): enforce CSRF/origin gate on binding and mapping mutations\n- fix(secret): recover a panicking secret engine instead of crashing\n- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone\n- fix(email): stop dropping the first paragraph of plain-text bodies\n- fix(logging): keep the live descriptor open across a failed rotation\n- feat(configuration): report config keys no decode target consumed\n- feat(archied): warn at boot when the config file has unrecognised keys\n- feat(archied): wire the scheduling ticker engine at boot\n- fix(agentworker): wire configured tool-result policy into worker's LoopRunner\n- refactor(staterpc): delete the superseded single-token auth interceptor\n- refactor(memory): delete the unreachable fence scrubber\n- fix(channels): delete unreachable Telegram webhook delivery mode\n- fix(gateway): delete unwired Router.Dangerous approval path\n- refactor(gateway): delete orphaned SessionState goal/steer/queue machinery\n- refactor(archied): delete the daemon's unused webui.Server and UI adapters\n- refactor(tools): delete unreachable dispatch/gating engine\n- feat(channels): wire chat.webhook route config through to the gateway\n- refactor(tools): delete unreachable AST-based tool discovery\n- refactor(tools): delete unused plugin-tool registration API from builtin.Registry\n- feat(channels): wire ConfigSchema/ValidateConfig into a startup validation loop\n- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted)\n- fix(curator): populate PassInput.Since with the prior pass time\n- fix(memory): install the threat scanner the composition root never wired\n- fix(staterpc): preserve marshal_error marker in eventDataJSON\n- fix(gate): validate finding level and share the blocking threshold\n- fix(scheduling): record a completed run so a recurring job stops re-firing every tick\n- fix(releaseupdate): don't treat empty available as deferred\n- fix(tools/provider/mcp): preserve MCP binary tool results for delivery\n- refactor(gateway): share sensitive-key markers with webhookguard\n- refactor(daemon): remove unreachable SQLite poll/drain path\n- refactor(tools/mcp): delete unreachable MCP adaptation path\n- fix(taskactions): resolve max_retries from the task's owning identity\n- fix(daemon): forward configured MCP servers to task agents\n- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path\n- refactor(skillbuild): delete dead AugmentRegistry path\n- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout\n- refactor(binding): delete dead Matcher.Overlaps method\n- refactor(forge): delete dead CreateIssue surface\n- fix(mcp): cancel in-flight SSE reconnect on Stop\n- fix(container): enforce MaxUptime lifetime cap with a timer\n- refactor(store): use taskstate status constants in SQL\n- fix(ui): unbreak binding approve and the two deletes, and centralise the client\n- fix(tools): stop testing on the text of other files, and ungate contractaudit\n- refactor(forge): delete the unwired RepliesAfter surface\n- refactor(config): delete the two decoded-but-unread policy fields\n\nThis release is dominated by dead-code removal and the completion of the\nscheduling capability. Roughly half the commits delete surfaces that no longer\nhad a caller: the unreachable SQLite poll/drain path, the unwired MCP\nadaptation path, the AST-based tool discovery, the superseded single-token auth\ninterceptor, and several dead forge and binding methods. The\n`IncrementRetryCount` State Store RPC is gone with them -- a breaking change to\nthe wire contract, accepted because nothing called it.\n\nThe cron/scheduling epic lands its remaining slices: the `[scheduling]` config\nblock, its translation into the engine's own settings, the events-bus sink\nadapter, and the boot wiring that starts the ticker. A recurring job now records\na completed run, so it stops re-firing on every tick.\n\nOperator-facing work: `archied setup` gives the first-run flow the caller it was\nbuilt for, configuration no longer accepts a secret value from the command line,\nand a provider whose credential is missing is disabled rather than refusing to\nboot. A secret engine that panics is now recovered instead of crashing the\ndaemon.\n\n### archie-agent\n\n- feat(config): add [scheduling] config block\n- fix(webui): count every chat front-end in the published projection\n- fix(scheduling): respect configuration ownership\n- feat(ratelimit): wire per-identity inbound rate limiting into the gateway\n- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it\n- fix(daemon): carry kind/label routing bindings to the process that routes\n- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone\n- fix(logging): keep the live descriptor open across a failed rotation\n- fix(agentworker): wire configured tool-result policy into worker's LoopRunner\n- refactor(staterpc): delete the superseded single-token auth interceptor\n- refactor(tools): delete unreachable dispatch/gating engine\n- feat(channels): wire chat.webhook route config through to the gateway\n- refactor(tools): delete unreachable AST-based tool discovery\n- refactor(tools): delete unused plugin-tool registration API from builtin.Registry\n- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted)\n- fix(staterpc): preserve marshal_error marker in eventDataJSON\n- fix(gate): validate finding level and share the blocking threshold\n- fix(tools/provider/mcp): preserve MCP binary tool results for delivery\n- refactor(tools/mcp): delete unreachable MCP adaptation path\n- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path\n- refactor(skillbuild): delete dead AugmentRegistry path\n- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout\n- refactor(binding): delete dead Matcher.Overlaps method\n- refactor(forge): delete dead CreateIssue surface\n- fix(mcp): cancel in-flight SSE reconnect on Stop\n- fix(container): enforce MaxUptime lifetime cap with a timer\n- refactor(forge): delete the unwired RepliesAfter surface\n- refactor(config): delete the two decoded-but-unread policy fields\n\nThe runtime carries a smaller, more focused set of changes than the same\nversion's archied entry: agent-side tool-result policy is now wired into the\nworker's loop, MCP binary tool results survive to delivery, the container\n`MaxUptime` lifetime cap is enforced with a timer, and a scheduled run records\ncompletion so it does not re-fire each tick.\n\nNote that several bullets above name config, webui and ratelimit packages. Those\nare attributed here by the release tool's package-closure rule (`go list -deps`\nover the agent binary), not because the agent owns them; the substantive\nruntime changes are the worker, MCP, container and scheduling fixes.\n\nThis entry also confirms the removal of the dead `IncrementRetryCount` State\nStore RPC, which the agent reaches through `staterpc` rather than by calling it\ndirectly." }, { - "component": "archie", - "name": "archie-agent", - "version": "1.27.0", - "date": "2026-09-17", - "body": "- The per-task runtime picks up the new State Store task-log read contract, so\n the sandboxed agents share one log-reading path with the daemon and the\n dashboard." - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.26.0", - "date": "2026-09-17", - "body": "- feat(config): add [scheduling] config block\n- fix(webui): count every chat front-end in the published projection\n- fix(scheduling): respect configuration ownership\n- feat(ratelimit): wire per-identity inbound rate limiting into the gateway\n- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it\n- fix(daemon): carry kind/label routing bindings to the process that routes\n- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone\n- fix(logging): keep the live descriptor open across a failed rotation\n- fix(agentworker): wire configured tool-result policy into worker's LoopRunner\n- refactor(staterpc): delete the superseded single-token auth interceptor\n- refactor(tools): delete unreachable dispatch/gating engine\n- feat(channels): wire chat.webhook route config through to the gateway\n- refactor(tools): delete unreachable AST-based tool discovery\n- refactor(tools): delete unused plugin-tool registration API from builtin.Registry\n- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted)\n- fix(staterpc): preserve marshal_error marker in eventDataJSON\n- fix(gate): validate finding level and share the blocking threshold\n- fix(tools/provider/mcp): preserve MCP binary tool results for delivery\n- refactor(tools/mcp): delete unreachable MCP adaptation path\n- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path\n- refactor(skillbuild): delete dead AugmentRegistry path\n- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout\n- refactor(binding): delete dead Matcher.Overlaps method\n- refactor(forge): delete dead CreateIssue surface\n- fix(mcp): cancel in-flight SSE reconnect on Stop\n- fix(container): enforce MaxUptime lifetime cap with a timer\n- refactor(forge): delete the unwired RepliesAfter surface\n- refactor(config): delete the two decoded-but-unread policy fields\n\nThe runtime carries a smaller, more focused set of changes than the same\nversion's archied entry: agent-side tool-result policy is now wired into the\nworker's loop, MCP binary tool results survive to delivery, the container\n`MaxUptime` lifetime cap is enforced with a timer, and a scheduled run records\ncompletion so it does not re-fire each tick.\n\nNote that several bullets above name config, webui and ratelimit packages. Those\nare attributed here by the release tool's package-closure rule (`go list -deps`\nover the agent binary), not because the agent owns them; the substantive\nruntime changes are the worker, MCP, container and scheduling fixes.\n\nThis entry also confirms the removal of the dead `IncrementRetryCount` State\nStore RPC, which the agent reaches through `staterpc` rather than by calling it\ndirectly." - }, - { - "component": "archied", - "name": "archied", "version": "1.25.0", "date": "2026-09-15", - "body": "- fix(update): resolve releases without a checkout, and fail loudly when it cannot\n- fix(update): back up the task store the daemon actually uses, or refuse\n- fix(update): build each component from its own approved release tag\n\nComponents are independently versioned, so the newest `archied/v*` and\n`archie/v*` tags usually sit on different commits. The installer required both\ntags to resolve to one commit whenever both components changed, which refused\nevery update once the two newest releases diverged -- a deployment stuck on\n1.22.0 could not take any update. Each component now builds from its own\napproved tag." + "body": "### archied\n\n- fix(update): resolve releases without a checkout, and fail loudly when it cannot\n- fix(update): back up the task store the daemon actually uses, or refuse\n- fix(update): build each component from its own approved release tag\n\nComponents are independently versioned, so the newest `archied/v*` and\n`archie/v*` tags usually sit on different commits. The installer required both\ntags to resolve to one commit whenever both components changed, which refused\nevery update once the two newest releases diverged -- a deployment stuck on\n1.22.0 could not take any update. Each component now builds from its own\napproved tag.\n\n### archie-agent\n\n- chore: no user-facing changes; versioned so the 1.25.0 release tags both\n components at the same commit" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.25.0", - "date": "2026-09-15", - "body": "- chore: no user-facing changes; versioned so the 1.25.0 release tags both\n components at the same commit" - }, - { - "component": "archied", - "name": "archied", "version": "1.24.0", "date": "2026-09-12", - "body": "Makes 1.23.0 deployable. That release split archied into separate processes,\nbut the self-updater still installed only the `archied` binary and restarted\nonly `archied.service`, so updating to it left the State Store, Gateway and UI\non the previous release. archied cannot boot without a reachable State Store,\nso the update failed its health check and rolled back. Update to this release\nrather than to 1.23.0.\n\nIf your host does not yet run the four units in\n`deployments/systemd-user-service.md`, create them first: the updater now\nrefuses, naming what is missing, instead of installing binaries onto a host it\nwould leave broken.\n\n- fix(update): install and cycle every process in the release\n- fix(telegram): stop the relay corrupting identifiers and code\n\nAlso in this release, though outside the version-stamped package closure:\n\n- ci(deploy): produce a complete distribution zip on every release. No zip was\n built for v1.23.0 at all, and the zip omitted `archie-ui`." + "body": "### archied\n\nMakes 1.23.0 deployable. That release split archied into separate processes,\nbut the self-updater still installed only the `archied` binary and restarted\nonly `archied.service`, so updating to it left the State Store, Gateway and UI\non the previous release. archied cannot boot without a reachable State Store,\nso the update failed its health check and rolled back. Update to this release\nrather than to 1.23.0.\n\nIf your host does not yet run the four units in\n`deployments/systemd-user-service.md`, create them first: the updater now\nrefuses, naming what is missing, instead of installing binaries onto a host it\nwould leave broken.\n\n- fix(update): install and cycle every process in the release\n- fix(telegram): stop the relay corrupting identifiers and code\n\nAlso in this release, though outside the version-stamped package closure:\n\n- ci(deploy): produce a complete distribution zip on every release. No zip was\n built for v1.23.0 at all, and the zip omitted `archie-ui`." }, { - "component": "archied", - "name": "archied", "version": "1.23.0", "date": "2026-09-12", - "body": "Archied is no longer a single process. The State Store (`archie-state-store`)\nnow owns `archie.db` outright, the Gateway serves its contract over\nauthenticated gRPC, and the dashboard ships as a standalone UI Service\n(`archie-ui`). Upgrading is not a binary swap: these processes must be running\nand addressable before `archied` will start clean. See `deployments/` for the\nsupported profiles.\n\n### Service decomposition\n\n- feat(contracts): add gateway service seams and protobuf toolchain\n- feat(gateway): extract ChatContract service\n- feat(gateway): delete in-process ChatContract path, make remote the only mode\n- feat(gateway): authenticate the gRPC contract and allow off-loopback listeners\n- fix(gateway): drop services.gateway.mode, remote is the only transport\n- feat(state-store): generalize storerpc as the State Store gRPC contract (#770)\n- feat(state-store): stand up archie-state-store binary and own archie.db (#771)\n- refactor(state-store): migrate capture/mapping/binding consumers to State Store (#772)\n- refactor(state-store): migrate workflow/intake/task lifecycle consumers to State Store (#773)\n- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774)\n- fix(state-store): task-scope container credentials, stream large capture lists, validate Update\n- feat(archieui): standalone UI process over remote Gateway and State Store\n- refactor(archied): cut the dashboard over to the archie-ui process\n- refactor(ui): sever the archie-ui binary from every daemon runtime package\n- refactor(archied): move the update relay to the process that owns updates\n- refactor(archied): move webhook capture intake to the process that owns work intake\n- feat(archieui): mount the capture intake receiver over the State Store\n- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754)\n- refactor(store): move the producer-owned contracts to internal/contracts/store/v1\n- feat(messaging): migrate gateway session persistence onto domain types\n- feat(gateway): flip channel boundary onto messaging.Message\n\n### Pull request review\n\n- feat(gateway): operator-triggered PR review with selectable reviewer model\n- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview)\n- feat(workflow): surface adversarial review findings on the PR body\n- feat(workflow): review calibration, checked properties and style nits out of contract\n- fix(archied): share one PR reviewer across channels; harden forge and worktree\n- fix(workflow): order findings before footer; test the report stash\n\n### Dashboard\n\n- feat(webui): render configuration from a published snapshot\n- feat(staterpc): carry the dashboard's configuration snapshot\n- refactor(webui): take configuration off the dashboard server\n- feat(webui): report which dashboard sections a process can serve\n- feat(webui): deliver live dashboard events by polling the State Store cursor\n- feat(webui): route dashboard task actions through the Gateway contract\n- feat(gateway): give the dashboard operator its own task-action contract\n- feat(webui): add /health and /health/detailed readiness endpoints (#717)\n- fix(webui): distinguish refused vs broken task actions, handle 401 (#753)\n\n### Daemon, gateway and workflow\n\n- feat(archied): add shutdown watchdog that force-exits a hung graceful shutdown (#716)\n- feat(archied): serve the daemon's own health endpoint\n- feat(drain): honour external drain marker with instantiation epoch (#718)\n- feat(gateway): wire progressive tool disclosure (bridge tools)\n- feat(gateway): render workspace, managed repos and operator into chat env\n- feat(gateway): add session_transcript tool for full JSON export\n- feat(gateway): consolidate task actions and repair daemon default path\n- feat(eda): thread Playbook ID/Version and DispatchInput task identity\n- feat(worktree): Resume re-syncs a worktree onto its branch tip\n- fix(staterpc): attach the bearer token to State Store streams\n- fix(archieui): resolve service tokens from env, without requiring a config file\n- fix(archied): initialize conversation persistence on daemon startup\n- fix(archied): preserve channel turn ledger with remote gateway\n- fix(gateway): share NATS and session ownership\n- fix(update): probe the dashboard's real address after a self-update\n- fix(store): migrate binding owner and repo columns" + "body": "### archied\n\nArchied is no longer a single process. The State Store (`archie-state-store`)\nnow owns `archie.db` outright, the Gateway serves its contract over\nauthenticated gRPC, and the dashboard ships as a standalone UI Service\n(`archie-ui`). Upgrading is not a binary swap: these processes must be running\nand addressable before `archied` will start clean. See `deployments/` for the\nsupported profiles.\n\n### archied — Service decomposition\n\n- feat(contracts): add gateway service seams and protobuf toolchain\n- feat(gateway): extract ChatContract service\n- feat(gateway): delete in-process ChatContract path, make remote the only mode\n- feat(gateway): authenticate the gRPC contract and allow off-loopback listeners\n- fix(gateway): drop services.gateway.mode, remote is the only transport\n- feat(state-store): generalize storerpc as the State Store gRPC contract (#770)\n- feat(state-store): stand up archie-state-store binary and own archie.db (#771)\n- refactor(state-store): migrate capture/mapping/binding consumers to State Store (#772)\n- refactor(state-store): migrate workflow/intake/task lifecycle consumers to State Store (#773)\n- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774)\n- fix(state-store): task-scope container credentials, stream large capture lists, validate Update\n- feat(archieui): standalone UI process over remote Gateway and State Store\n- refactor(archied): cut the dashboard over to the archie-ui process\n- refactor(ui): sever the archie-ui binary from every daemon runtime package\n- refactor(archied): move the update relay to the process that owns updates\n- refactor(archied): move webhook capture intake to the process that owns work intake\n- feat(archieui): mount the capture intake receiver over the State Store\n- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754)\n- refactor(store): move the producer-owned contracts to internal/contracts/store/v1\n- feat(messaging): migrate gateway session persistence onto domain types\n- feat(gateway): flip channel boundary onto messaging.Message\n\n### archied — Pull request review\n\n- feat(gateway): operator-triggered PR review with selectable reviewer model\n- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview)\n- feat(workflow): surface adversarial review findings on the PR body\n- feat(workflow): review calibration, checked properties and style nits out of contract\n- fix(archied): share one PR reviewer across channels; harden forge and worktree\n- fix(workflow): order findings before footer; test the report stash\n\n### archied — Dashboard\n\n- feat(webui): render configuration from a published snapshot\n- feat(staterpc): carry the dashboard's configuration snapshot\n- refactor(webui): take configuration off the dashboard server\n- feat(webui): report which dashboard sections a process can serve\n- feat(webui): deliver live dashboard events by polling the State Store cursor\n- feat(webui): route dashboard task actions through the Gateway contract\n- feat(gateway): give the dashboard operator its own task-action contract\n- feat(webui): add /health and /health/detailed readiness endpoints (#717)\n- fix(webui): distinguish refused vs broken task actions, handle 401 (#753)\n\n### archied — Daemon, gateway and workflow\n\n- feat(archied): add shutdown watchdog that force-exits a hung graceful shutdown (#716)\n- feat(archied): serve the daemon's own health endpoint\n- feat(drain): honour external drain marker with instantiation epoch (#718)\n- feat(gateway): wire progressive tool disclosure (bridge tools)\n- feat(gateway): render workspace, managed repos and operator into chat env\n- feat(gateway): add session_transcript tool for full JSON export\n- feat(gateway): consolidate task actions and repair daemon default path\n- feat(eda): thread Playbook ID/Version and DispatchInput task identity\n- feat(worktree): Resume re-syncs a worktree onto its branch tip\n- fix(staterpc): attach the bearer token to State Store streams\n- fix(archieui): resolve service tokens from env, without requiring a config file\n- fix(archied): initialize conversation persistence on daemon startup\n- fix(archied): preserve channel turn ledger with remote gateway\n- fix(gateway): share NATS and session ownership\n- fix(update): probe the dashboard's real address after a self-update\n- fix(store): migrate binding owner and repo columns\n\n### archie-agent\n\nThe agent runtime now reaches task state through the State Store gRPC contract\n(`STATE_STORE_URL`/`STATE_STORE_TOKEN`, injected by the daemon) instead of the\nNATS `storerpc` transport, which is deleted. Credentials handed to a task\ncontainer are scoped to that task rather than being the daemon's own token.\nRunning a 1.23.0 daemon against an older agent image will not work; rebuild or\npull the `archie-agent` image with this release.\n\n- feat(state-store): generalize storerpc as the State Store gRPC contract (#770)\n- feat(state-store): stand up archie-state-store binary and own archie.db (#771)\n- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774)\n- fix(state-store): task-scope container credentials, stream large capture lists, validate Update\n- fix(staterpc): attach the bearer token to State Store streams\n- feat(staterpc): carry the dashboard's configuration snapshot\n- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754)\n- refactor(store): move the producer-owned contracts to internal/contracts/store/v1\n- feat(contracts): add gateway service seams and protobuf toolchain\n- fix(gateway): drop services.gateway.mode, remote is the only transport\n- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview)\n- feat(gateway): operator-triggered PR review with selectable reviewer model\n- feat(workflow): surface adversarial review findings on the PR body\n- feat(workflow): review calibration, checked properties and style nits out of contract\n- fix(workflow): order findings before footer; test the report stash\n- fix(archied): share one PR reviewer across channels; harden forge and worktree\n- feat(worktree): Resume re-syncs a worktree onto its branch tip\n- feat(telegram): support secret refs for bot tokens (#705)\n- feat(gateway): wire progressive tool disclosure (bridge tools)\n- feat(archied): serve the daemon's own health endpoint\n- feat(archieui): standalone UI process over remote Gateway and State Store\n- refactor(archied): move webhook capture intake to the process that owns work intake\n- refactor(ui): sever the archie-ui binary from every daemon runtime package\n- fix(archieui): resolve service tokens from env, without requiring a config file" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.23.0", - "date": "2026-09-12", - "body": "The agent runtime now reaches task state through the State Store gRPC contract\n(`STATE_STORE_URL`/`STATE_STORE_TOKEN`, injected by the daemon) instead of the\nNATS `storerpc` transport, which is deleted. Credentials handed to a task\ncontainer are scoped to that task rather than being the daemon's own token.\nRunning a 1.23.0 daemon against an older agent image will not work; rebuild or\npull the `archie-agent` image with this release.\n\n- feat(state-store): generalize storerpc as the State Store gRPC contract (#770)\n- feat(state-store): stand up archie-state-store binary and own archie.db (#771)\n- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774)\n- fix(state-store): task-scope container credentials, stream large capture lists, validate Update\n- fix(staterpc): attach the bearer token to State Store streams\n- feat(staterpc): carry the dashboard's configuration snapshot\n- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754)\n- refactor(store): move the producer-owned contracts to internal/contracts/store/v1\n- feat(contracts): add gateway service seams and protobuf toolchain\n- fix(gateway): drop services.gateway.mode, remote is the only transport\n- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview)\n- feat(gateway): operator-triggered PR review with selectable reviewer model\n- feat(workflow): surface adversarial review findings on the PR body\n- feat(workflow): review calibration, checked properties and style nits out of contract\n- fix(workflow): order findings before footer; test the report stash\n- fix(archied): share one PR reviewer across channels; harden forge and worktree\n- feat(worktree): Resume re-syncs a worktree onto its branch tip\n- feat(telegram): support secret refs for bot tokens (#705)\n- feat(gateway): wire progressive tool disclosure (bridge tools)\n- feat(archied): serve the daemon's own health endpoint\n- feat(archieui): standalone UI process over remote Gateway and State Store\n- refactor(archied): move webhook capture intake to the process that owns work intake\n- refactor(ui): sever the archie-ui binary from every daemon runtime package\n- fix(archieui): resolve service tokens from env, without requiring a config file" - }, - { - "component": "archied", - "name": "archied", "version": "1.22.0", "date": "2026-09-03", - "body": "- feat(telegram): support secret refs for bot tokens (#705)\n- fix(update): make daemon rollback schema-safe (#704)\n- fix(archied): preserve ephemeral gateway ports (#707)\n- fix(webui): bound log limit parsing and add endpoint regression coverage (#706)\n- fix(deps): upgrade x/crypto to v0.56.0 for security fixes (#708)" + "body": "### archied\n\n- feat(telegram): support secret refs for bot tokens (#705)\n- fix(update): make daemon rollback schema-safe (#704)\n- fix(archied): preserve ephemeral gateway ports (#707)\n- fix(webui): bound log limit parsing and add endpoint regression coverage (#706)\n- fix(deps): upgrade x/crypto to v0.56.0 for security fixes (#708)" }, { - "component": "archied", - "name": "archied", "version": "1.21.0", "date": "2026-09-03", - "body": "- feat(workflow): make kind-to-workflow routing YAML-overridable\n- feat(workflow): route arbitrary forge labels to workflows via playbook YAML\n- feat(workflow): load kind/label bindings from multiple playbook directories\n- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive\n- feat(eda): Module position first slice -- registry + side-effect-free log kind\n- feat(eda): CEL expression environment (compile/validate at load, evaluate at dispatch)\n- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch\n- fix(skillcurator): document and scope the intentional nilerr in reviewOne\n- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch\n- feat(webui): bindings dashboard UI; fix app-wide Preact render regression\n- fix(binding): split ValidateForUpdate so edits can preserve the secret\n- refactor(ui): extract Pill to ui/src/base/, closing archie-core-mlro\n- refactor(eda): extract helpers to satisfy cyclop/gocognit gates\n- fix(webui): stretch HEALTH row cards to equal height\n- fix(eda): make playbook key collision reporting deterministic\n- fix(gateway): split /status (health) and /tasks (work) apart" + "body": "### archied\n\n- feat(workflow): make kind-to-workflow routing YAML-overridable\n- feat(workflow): route arbitrary forge labels to workflows via playbook YAML\n- feat(workflow): load kind/label bindings from multiple playbook directories\n- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive\n- feat(eda): Module position first slice -- registry + side-effect-free log kind\n- feat(eda): CEL expression environment (compile/validate at load, evaluate at dispatch)\n- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch\n- fix(skillcurator): document and scope the intentional nilerr in reviewOne\n- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch\n- feat(webui): bindings dashboard UI; fix app-wide Preact render regression\n- fix(binding): split ValidateForUpdate so edits can preserve the secret\n- refactor(ui): extract Pill to ui/src/base/, closing archie-core-mlro\n- refactor(eda): extract helpers to satisfy cyclop/gocognit gates\n- fix(webui): stretch HEALTH row cards to equal height\n- fix(eda): make playbook key collision reporting deterministic\n- fix(gateway): split /status (health) and /tasks (work) apart\n\n### archie-agent\n\n- feat(workflow): make kind-to-workflow routing YAML-overridable\n- feat(workflow): route arbitrary forge labels to workflows via playbook YAML\n- feat(workflow): load kind/label bindings from multiple playbook directories\n- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive\n- feat(eda): Module position first slice -- registry + side-effect-free log kind\n- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch\n- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch\n- fix(binding): split ValidateForUpdate so edits can preserve the secret\n- refactor(eda): extract helpers to satisfy cyclop/gocognit gates\n- fix(eda): make playbook key collision reporting deterministic" }, { - "component": "archied", - "name": "archied", "version": "1.20.0", "date": "2026-09-03", - "body": "- fix: baseline gate repair (go test ./... -count=1)\n- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler\n- feat(image): define provider-neutral image capability contract and config\n- fix(channels): call MarkRunning once a channel is actually up\n- fix(workflow): stop discarding baseline-fix commits as 'no changes'\n- fix(webui): wire the Logs page to per-task attempt-log detail\n- fix(workflow): net cache hits from token totals, trim gate-retry output\n- feat(workflow): dynamic triage instead of defaulting every task to implement\n- fix(gateway): stop SOUL from forging the prompt invariant tags\n- fix(curator): stop curator actions from serializing a zero timestamp\n- feat(webui): hand-author the configuration field descriptor catalog\n- feat(webui): attach the config field schema to GET /api/config\n- feat(webui): render scalar config sections generically from the schema\n- feat(webui): surface allow_concurrent/max_retries/review_enabled on the repositories card\n- feat(webui): inline editing for per-repo allow_concurrent/max_retries/review_enabled\n- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated\n- fix: resolve golangci-lint funlen, nilerr, and empty branch issues\n- feat(store): encrypt playbook binding secrets at rest\n- feat(webhook): harden captured payload redaction\n- fix(store): satisfy makezero when building cipher payload\n- feat(webui): refactor chat module to Preact component and add unit tests" + "body": "### archied\n\n- fix: baseline gate repair (go test ./... -count=1)\n- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler\n- feat(image): define provider-neutral image capability contract and config\n- fix(channels): call MarkRunning once a channel is actually up\n- fix(workflow): stop discarding baseline-fix commits as 'no changes'\n- fix(webui): wire the Logs page to per-task attempt-log detail\n- fix(workflow): net cache hits from token totals, trim gate-retry output\n- feat(workflow): dynamic triage instead of defaulting every task to implement\n- fix(gateway): stop SOUL from forging the prompt invariant tags\n- fix(curator): stop curator actions from serializing a zero timestamp\n- feat(webui): hand-author the configuration field descriptor catalog\n- feat(webui): attach the config field schema to GET /api/config\n- feat(webui): render scalar config sections generically from the schema\n- feat(webui): surface allow_concurrent/max_retries/review_enabled on the repositories card\n- feat(webui): inline editing for per-repo allow_concurrent/max_retries/review_enabled\n- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated\n- fix: resolve golangci-lint funlen, nilerr, and empty branch issues\n- feat(store): encrypt playbook binding secrets at rest\n- feat(webhook): harden captured payload redaction\n- fix(store): satisfy makezero when building cipher payload\n- feat(webui): refactor chat module to Preact component and add unit tests\n\n### archie-agent\n\n- fix: baseline gate repair (go test ./... -count=1)\n- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler\n- feat(image): define provider-neutral image capability contract and config\n- fix(workflow): stop discarding baseline-fix commits as 'no changes'\n- fix(workflow): net cache hits from token totals, trim gate-retry output\n- feat(workflow): dynamic triage instead of defaulting every task to implement\n- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated\n- feat(store): encrypt playbook binding secrets at rest\n- fix(store): satisfy makezero when building cipher payload" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.21.0", - "date": "2026-09-03", - "body": "- feat(workflow): make kind-to-workflow routing YAML-overridable\n- feat(workflow): route arbitrary forge labels to workflows via playbook YAML\n- feat(workflow): load kind/label bindings from multiple playbook directories\n- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive\n- feat(eda): Module position first slice -- registry + side-effect-free log kind\n- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch\n- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch\n- fix(binding): split ValidateForUpdate so edits can preserve the secret\n- refactor(eda): extract helpers to satisfy cyclop/gocognit gates\n- fix(eda): make playbook key collision reporting deterministic" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.20.0", - "date": "2026-09-03", - "body": "- fix: baseline gate repair (go test ./... -count=1)\n- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler\n- feat(image): define provider-neutral image capability contract and config\n- fix(workflow): stop discarding baseline-fix commits as 'no changes'\n- fix(workflow): net cache hits from token totals, trim gate-retry output\n- feat(workflow): dynamic triage instead of defaulting every task to implement\n- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated\n- feat(store): encrypt playbook binding secrets at rest\n- fix(store): satisfy makezero when building cipher payload" - }, - { - "component": "archied", - "name": "archied", "version": "1.19.10", "date": "2026-09-02", - "body": "- feat(curator): session-memory curator reference implementation" + "body": "### archied\n\n- feat(curator): session-memory curator reference implementation" }, { - "component": "archied", - "name": "archied", "version": "1.19.9", "date": "2026-09-02", - "body": "- feat(memory): typed memory engine contract, registry, and registrar\n- feat(memory): builtin engine implementing the domain/memory contract\n- feat(config): config surface for memory engine selection\n- feat(daemon): wire the domain/memory engine registry at boot\n- feat(curator): bind curators to memory engines\n- fix(config): reject memory.provider instead of silently ignoring it\n- feat(curator): skill curator reference implementation" + "body": "### archied\n\n- feat(memory): typed memory engine contract, registry, and registrar\n- feat(memory): builtin engine implementing the domain/memory contract\n- feat(config): config surface for memory engine selection\n- feat(daemon): wire the domain/memory engine registry at boot\n- feat(curator): bind curators to memory engines\n- fix(config): reject memory.provider instead of silently ignoring it\n- feat(curator): skill curator reference implementation\n\n### archie-agent\n\n- feat(config): config surface for memory engine selection" }, { - "component": "archied", - "name": "archied", "version": "1.19.8", "date": "2026-09-02", - "body": "- fix(update): drop dev-facing wording from the unconfirmed-update message\n- fix(telegram): stop adjacent rich blocks from rendering glued together\n- fix(telegram): send undelivered-media fallback after finalize as its own message" + "body": "### archied\n\n- fix(update): drop dev-facing wording from the unconfirmed-update message\n- fix(telegram): stop adjacent rich blocks from rendering glued together\n- fix(telegram): send undelivered-media fallback after finalize as its own message" }, { - "component": "archied", - "name": "archied", "version": "1.19.7", "date": "2026-09-02", - "body": "- fix(logging): make Tail/Page allocation bound explicit for CodeQL" + "body": "### archied\n\n- fix(logging): make Tail/Page allocation bound explicit for CodeQL\n\n### archie-agent\n\n- fix(logging): make Tail/Page allocation bound explicit for CodeQL" }, { - "component": "archied", - "name": "archied", "version": "1.19.6", "date": "2026-09-02", - "body": "- fix(build): stamp gatewayVersion/runtimeVersion in the right package" + "body": "### archied\n\n- fix(build): stamp gatewayVersion/runtimeVersion in the right package" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.19.9", - "date": "2026-09-02", - "body": "- feat(config): config surface for memory engine selection" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.19.7", - "date": "2026-09-02", - "body": "- fix(logging): make Tail/Page allocation bound explicit for CodeQL" - }, - { - "component": "archied", - "name": "archied", "version": "1.19.5", "date": "2026-09-01", - "body": "- feat(webui): dashboard-aware chat — Archie sees the page, points you there\n- fix(telegram): drop retry_after bandaid, bump go-telegram/bot to v1.24.0\n- feat(curator): track and expose recent activity per curator\n- fix: go.mod bumped to 1.27.0 and stupid tests removed\n- refactor: remove unnecessary AI-generated scaffolding\n- refactor: go modernisation fixes\n- refactor: remove unused Operator param.\n- fix(gateway): fix broken system prompt template and scrub real telegram ID from tests\n- fix(plugin): add missing CLAUDE.md reference to plugin engine rule\n- fix(app): repoint archied wiring contract test at internal/app/archied\n- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet\n- fix(config): standardize Provenance to pointer receivers (recvcheck)\n- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui\n- fix(app): repoint capability-host wiring contract test at internal/app/archied\n- refactor(lint): extract more helpers to clear nestif/gocyclo findings\n- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult\n- refactor(lint): split TurnRunner.Run and dispatchLocal further\n- refactor(lint): extract markdownBlockParser and list/quote helpers in richblocks.go\n- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization\n- fix(lint): noctx fixes and dead-code cleanup\n- feat(workflow): adversarial self-review stage before PR open" + "body": "### archied\n\n- feat(webui): dashboard-aware chat — Archie sees the page, points you there\n- fix(telegram): drop retry_after bandaid, bump go-telegram/bot to v1.24.0\n- feat(curator): track and expose recent activity per curator\n- fix: go.mod bumped to 1.27.0 and stupid tests removed\n- refactor: remove unnecessary AI-generated scaffolding\n- refactor: go modernisation fixes\n- refactor: remove unused Operator param.\n- fix(gateway): fix broken system prompt template and scrub real telegram ID from tests\n- fix(plugin): add missing CLAUDE.md reference to plugin engine rule\n- fix(app): repoint archied wiring contract test at internal/app/archied\n- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet\n- fix(config): standardize Provenance to pointer receivers (recvcheck)\n- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui\n- fix(app): repoint capability-host wiring contract test at internal/app/archied\n- refactor(lint): extract more helpers to clear nestif/gocyclo findings\n- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult\n- refactor(lint): split TurnRunner.Run and dispatchLocal further\n- refactor(lint): extract markdownBlockParser and list/quote helpers in richblocks.go\n- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization\n- fix(lint): noctx fixes and dead-code cleanup\n- feat(workflow): adversarial self-review stage before PR open\n\n### archie-agent\n\n- feat(tasks): allow rejecting a task from any non-terminal state\n- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta\n- fix: go.mod bumped to 1.27.0 and stupid tests removed\n- refactor: go modernisation fixes\n- refactor: remove unused Operator param.\n- fix(plugin): add missing CLAUDE.md reference to plugin engine rule\n- fix(app): repoint archied wiring contract test at internal/app/archied\n- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet\n- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui\n- fix(app): repoint capability-host wiring contract test at internal/app/archied\n- refactor(lint): extract more helpers to clear nestif/gocyclo findings\n- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult\n- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization\n- fix(lint): noctx fixes and dead-code cleanup\n- feat(workflow): adversarial self-review stage before PR open" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.19.5", - "date": "2026-09-01", - "body": "- feat(tasks): allow rejecting a task from any non-terminal state\n- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta\n- fix: go.mod bumped to 1.27.0 and stupid tests removed\n- refactor: go modernisation fixes\n- refactor: remove unused Operator param.\n- fix(plugin): add missing CLAUDE.md reference to plugin engine rule\n- fix(app): repoint archied wiring contract test at internal/app/archied\n- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet\n- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui\n- fix(app): repoint capability-host wiring contract test at internal/app/archied\n- refactor(lint): extract more helpers to clear nestif/gocyclo findings\n- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult\n- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization\n- fix(lint): noctx fixes and dead-code cleanup\n- feat(workflow): adversarial self-review stage before PR open" - }, - { - "component": "archied", - "name": "archied", "version": "1.19.4", "date": "2026-08-28", - "body": "- refactor(telegram): render replies as structured rich blocks" + "body": "### archied\n\n- refactor(telegram): render replies as structured rich blocks" }, { - "component": "archied", - "name": "archied", "version": "1.19.3", "date": "2026-08-28", - "body": "- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta\n- feat(dashboard): render task actions, statuses and filters from the server catalog" + "body": "### archied\n\n- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta\n- feat(dashboard): render task actions, statuses and filters from the server catalog" }, { - "component": "archied", - "name": "archied", "version": "1.19.2", "date": "2026-08-28", - "body": "- feat(tasks): allow rejecting a task from any non-terminal state" + "body": "### archied\n\n- feat(tasks): allow rejecting a task from any non-terminal state" }, { - "component": "archied", - "name": "archied", "version": "1.19.0", "date": "2026-08-28", - "body": "- feat(logging): cursor pagination and filtering for task_logs\n- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29" + "body": "### archied\n\n- feat(logging): cursor pagination and filtering for task_logs\n- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29" }, { - "component": "archie", - "name": "archie-agent", "version": "1.18.0", "date": "2026-08-28", - "body": "- feat(logging): cursor pagination and filtering for task_logs\n- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29" + "body": "### archied (released 2026-08-25)\n\n- Fix concurrent chat-turn claims so SQLite writer contention no longer leaks as `SQLITE_BUSY`.\n- Make task timelines operationally useful with stage outcomes, durations, retry context, and durable per-stage token economics.\n- Return canonical repository, issue, and pull-request URLs for each task's owning GitHub or Gitea identity.\n- Preserve per-identity commit attribution and real model context limits across daemon-to-worker dispatch.\n\n### archie-agent\n\n- feat(logging): cursor pagination and filtering for task_logs\n- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29" }, { - "component": "archied", - "name": "archied", "version": "1.19.1", "date": "2026-08-27", - "body": "- fix(telegram): keep Markdown headings/lists as blocks and strip Markdown on plain fallback" + "body": "### archied\n\n- fix(telegram): keep Markdown headings/lists as blocks and strip Markdown on plain fallback" }, { - "component": "archied", - "name": "archied", - "version": "1.18.0", - "date": "2026-08-25", - "body": "- Fix concurrent chat-turn claims so SQLite writer contention no longer leaks as `SQLITE_BUSY`.\n- Make task timelines operationally useful with stage outcomes, durations, retry context, and durable per-stage token economics.\n- Return canonical repository, issue, and pull-request URLs for each task's owning GitHub or Gitea identity.\n- Preserve per-identity commit attribution and real model context limits across daemon-to-worker dispatch." - }, - { - "component": "archied", - "name": "archied", "version": "1.17.1", "date": "2026-08-25", - "body": "- fix(update): remove source checkout dependency\n- fix(gateway): make UUIDv7 session references unambiguous" + "body": "### archied\n\n- fix(update): remove source checkout dependency\n- fix(gateway): make UUIDv7 session references unambiguous" }, { - "component": "archied", - "name": "archied", "version": "1.17.0", "date": "2026-08-25", - "body": "- fix(webui): add nil receiver guard to Server.trustForwardedHeaders\n- fix(chat): restore transcript and update replay" + "body": "### archied\n\n- fix(webui): add nil receiver guard to Server.trustForwardedHeaders\n- fix(chat): restore transcript and update replay\n\n### archie-agent\n\n- Compact task history against the selected model's real context capacity without imposing a token cap.\n- Preserve completed steps and billed usage when a later provider call fails; failed compaction now keeps the original history and continues.\n- Persist detailed agent-stage usage through the daemon-owned store before lossy live event fan-out.\n- Apply configured or forge-derived author and committer identity to sandboxed task commits." }, { - "component": "archied", - "name": "archied", - "version": "1.16.0", - "date": "2026-08-25", - "body": "**The agent can hand you a file, and the dashboard works behind a reverse\nproxy.** Media delivery was fetch-by-URL only, so a file the agent produced\nlocally — a transcript, a log dump, a screenshot — was passed to Telegram as\na URL it could not fetch: the send did nothing and reported success. The new\n`send_file` tool plus upload-by-reader delivery closes that, and every layer\nthat cannot deliver now says so rather than staying silent. Dashboard\nmutations behind a TLS-terminating proxy were refused as cross-origin;\nforwarded headers are now honoured, but only under an explicit opt-in that is\noff by default.\n\n- feat(telegram): deliver a local file as an uploaded attachment, choosing\n upload-by-reader or fetch-by-URL per attachment; `send_file` resolves paths\n under the same confinement policy the read tool applies, so sending cannot\n reach what reading cannot\n- feat(gateway): `task_action` chat tool for operator task management —\n abandon, archive, retry, stop, cancel, approve and reject from chat, on the\n same action path and state machine as the dashboard\n- fix(webui): validate mutation `Origin` against the effective external\n scheme and host. `X-Forwarded-Proto`/`-Host` are honoured only when\n `web.trust_forwarded_headers` is set, which is off by default and safe only\n behind a proxy that overwrites or strips untrusted forwarded headers\n- fix(webui): report a local file the dashboard chat cannot upload as\n undelivered instead of dropping the event, which had reproduced the exact\n silent non-delivery `send_file` was built to end\n- fix(daemon): detach terminal state transitions and cleanup from a cancelled\n context, so a stopped task still records its outcome" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.17.0", - "date": "2026-08-25", - "body": "- Compact task history against the selected model's real context capacity without imposing a token cap.\n- Preserve completed steps and billed usage when a later provider call fails; failed compaction now keeps the original history and continues.\n- Persist detailed agent-stage usage through the daemon-owned store before lossy live event fan-out.\n- Apply configured or forge-derived author and committer identity to sandboxed task commits." - }, - { - "component": "archie", - "name": "archie-agent", "version": "1.16.1", "date": "2026-08-25", - "body": "- fix(agentworker): reconcile task clone ownership after commits" + "body": "### archie-agent\n\n- fix(agentworker): reconcile task clone ownership after commits" }, { - "component": "archie", - "name": "archie-agent", "version": "1.16.0", "date": "2026-08-25", - "body": "**Version realigned with `archied`.** This release jumps from 1.9.9 to 1.16.0\nto put the two components on matching numbers; there are no 1.10-1.15 agent\nreleases. It clears the accumulated runtime backlog in one cut rather than\nbundling it as a rider on a later change, so the list below spans several\nweeks of work rather than one session's.\n\nHighlights:\n\n- feat(nats): run an embedded server when no external NATS is configured, and\n expose the embedded broker to managed task workers\n- feat(deployment): default to managed NATS workers; the daemon requires a\n full-task worker handoff and the legacy in-process, subprocess and\n single-stage execution paths are gone\n- feat(forge): GitHub webhook receiver for immediate issue dispatch, with\n dedup regression proof; unbound webhook events are stored retention-bounded\n- feat(webui): payload field mapping -- bind JSON paths to named fields and\n preview before saving\n- feat(scheduling): ticker engine with configurable interval and pools\n- feat(storage): persist agent project state\n- feat(agent): stamp archie-agent's build and report it back to the daemon\n- feat(tools): `generate_video` via MiniMax, gated behind config, and\n `MultimodalResult.URLs` for remote-hosted media\n- feat(workflow): define the adversarial-review findings contract\n\nFixes:\n\n- fix(worktree): bind publication to dispatch grants; reset retries to a\n pristine base; reject diffs without a merge base; clean untracked files when\n `.git` is a gitdir file; post-push metadata resilience, cancellation and\n branch naming\n- fix(container): persist the npm cache for per-task MCP servers\n- fix(agentexec): recover omitted finish calls\n- fix(agentworker): move JSONL decode into storage, unblocking CI\n- fix(telegram): compact tool output and drop turn caps\n- fix(webui): give dashboard-initiated updates a phase-2 report; restore the\n provider gate and dashboard token accounting\n- refactor: remove dead `BasePlatformAdapter` code and legacy execution paths\n\nShared with archied 1.16.0 (these packages are in both closures):\n\n- feat(telegram): send local files as uploads, not fetchable URLs\n- fix(webui,sendfile): close three holes the adversarial review found\n- fix(webui): validate mutation Origin against the effective external scheme" + "body": "### archied\n\n**The agent can hand you a file, and the dashboard works behind a reverse\nproxy.** Media delivery was fetch-by-URL only, so a file the agent produced\nlocally — a transcript, a log dump, a screenshot — was passed to Telegram as\na URL it could not fetch: the send did nothing and reported success. The new\n`send_file` tool plus upload-by-reader delivery closes that, and every layer\nthat cannot deliver now says so rather than staying silent. Dashboard\nmutations behind a TLS-terminating proxy were refused as cross-origin;\nforwarded headers are now honoured, but only under an explicit opt-in that is\noff by default.\n\n- feat(telegram): deliver a local file as an uploaded attachment, choosing\n upload-by-reader or fetch-by-URL per attachment; `send_file` resolves paths\n under the same confinement policy the read tool applies, so sending cannot\n reach what reading cannot\n- feat(gateway): `task_action` chat tool for operator task management —\n abandon, archive, retry, stop, cancel, approve and reject from chat, on the\n same action path and state machine as the dashboard\n- fix(webui): validate mutation `Origin` against the effective external\n scheme and host. `X-Forwarded-Proto`/`-Host` are honoured only when\n `web.trust_forwarded_headers` is set, which is off by default and safe only\n behind a proxy that overwrites or strips untrusted forwarded headers\n- fix(webui): report a local file the dashboard chat cannot upload as\n undelivered instead of dropping the event, which had reproduced the exact\n silent non-delivery `send_file` was built to end\n- fix(daemon): detach terminal state transitions and cleanup from a cancelled\n context, so a stopped task still records its outcome\n\n### archie-agent\n\n**Version realigned with `archied`.** This release jumps from 1.9.9 to 1.16.0\nto put the two components on matching numbers; there are no 1.10-1.15 agent\nreleases. It clears the accumulated runtime backlog in one cut rather than\nbundling it as a rider on a later change, so the list below spans several\nweeks of work rather than one session's.\n\nHighlights:\n\n- feat(nats): run an embedded server when no external NATS is configured, and\n expose the embedded broker to managed task workers\n- feat(deployment): default to managed NATS workers; the daemon requires a\n full-task worker handoff and the legacy in-process, subprocess and\n single-stage execution paths are gone\n- feat(forge): GitHub webhook receiver for immediate issue dispatch, with\n dedup regression proof; unbound webhook events are stored retention-bounded\n- feat(webui): payload field mapping -- bind JSON paths to named fields and\n preview before saving\n- feat(scheduling): ticker engine with configurable interval and pools\n- feat(storage): persist agent project state\n- feat(agent): stamp archie-agent's build and report it back to the daemon\n- feat(tools): `generate_video` via MiniMax, gated behind config, and\n `MultimodalResult.URLs` for remote-hosted media\n- feat(workflow): define the adversarial-review findings contract\n\nFixes:\n\n- fix(worktree): bind publication to dispatch grants; reset retries to a\n pristine base; reject diffs without a merge base; clean untracked files when\n `.git` is a gitdir file; post-push metadata resilience, cancellation and\n branch naming\n- fix(container): persist the npm cache for per-task MCP servers\n- fix(agentexec): recover omitted finish calls\n- fix(agentworker): move JSONL decode into storage, unblocking CI\n- fix(telegram): compact tool output and drop turn caps\n- fix(webui): give dashboard-initiated updates a phase-2 report; restore the\n provider gate and dashboard token accounting\n- refactor: remove dead `BasePlatformAdapter` code and legacy execution paths\n\nShared with archied 1.16.0 (these packages are in both closures):\n\n- feat(telegram): send local files as uploads, not fetchable URLs\n- fix(webui,sendfile): close three holes the adversarial review found\n- fix(webui): validate mutation Origin against the effective external scheme" }, { - "component": "archied", - "name": "archied", "version": "1.15.0", "date": "2026-08-24", - "body": "**Autonomous workflows now have exactly one production execution path.** Every\ntask is handed complete to a scoped `archie-agent` container over core NATS;\n`archied` no longer runs an agent loop in-process. Embedded NATS is the\ndefault and generates a per-start token, binding to the resolved Docker bridge\nso managed workers can reach it; external NATS changes only broker placement.\nThe legacy `[agent]` section and `containers.enabled` still decode for\nmigration but can no longer select an execution path, and a reloaded\n`nats.url` is logged as requiring a restart. Operators upgrading from a\n`agent.mode = inprocess` configuration get the managed-worker topology\nautomatically; see `deployments/` for the supported profiles.\n\n- feat(nats): expose the embedded broker to managed task containers behind a\n generated per-start credential\n- fix(daemon): park before worktree access when the container pool or task\n transport is unavailable, rather than silently executing locally\n- refactor(agentexec): remove the in-process, subprocess and single-stage\n execution paths\n- fix(worktree): report a successful push as successful even when writing\n local upstream tracking metadata afterwards fails, so a published branch no\n longer parks the task as failed\n- fix(worktree): honour context cancellation in `CommitAll`, so a cancelled\n task can no longer stage or commit\n- fix(daemon): remove the worktree when a task completes with no changes,\n which previously leaked a full clone per no-change task; parked worktrees\n are still retained for post-mortems\n- fix(worktree): derive the branch prefix from the issue title before falling\n back to labels, matching the documented contract\n- fix(worktree): clean untracked files when `.git` is a gitdir file\n- fix(agentexec): recover agents that end a turn without the required finish\n call\n- feat(scheduling): ticker engine with a configurable interval and pools\n- fix(telegram): keep tool-call context when compacting tool output (#609)\n- feat(workflow): add the adversarial-review findings contract, where only a\n confirmed finding blocks and \"review found nothing\" is distinct from\n \"review did not run\" (contract only; no review stage runs yet)" + "body": "### archied\n\n**Autonomous workflows now have exactly one production execution path.** Every\ntask is handed complete to a scoped `archie-agent` container over core NATS;\n`archied` no longer runs an agent loop in-process. Embedded NATS is the\ndefault and generates a per-start token, binding to the resolved Docker bridge\nso managed workers can reach it; external NATS changes only broker placement.\nThe legacy `[agent]` section and `containers.enabled` still decode for\nmigration but can no longer select an execution path, and a reloaded\n`nats.url` is logged as requiring a restart. Operators upgrading from a\n`agent.mode = inprocess` configuration get the managed-worker topology\nautomatically; see `deployments/` for the supported profiles.\n\n- feat(nats): expose the embedded broker to managed task containers behind a\n generated per-start credential\n- fix(daemon): park before worktree access when the container pool or task\n transport is unavailable, rather than silently executing locally\n- refactor(agentexec): remove the in-process, subprocess and single-stage\n execution paths\n- fix(worktree): report a successful push as successful even when writing\n local upstream tracking metadata afterwards fails, so a published branch no\n longer parks the task as failed\n- fix(worktree): honour context cancellation in `CommitAll`, so a cancelled\n task can no longer stage or commit\n- fix(daemon): remove the worktree when a task completes with no changes,\n which previously leaked a full clone per no-change task; parked worktrees\n are still retained for post-mortems\n- fix(worktree): derive the branch prefix from the issue title before falling\n back to labels, matching the documented contract\n- fix(worktree): clean untracked files when `.git` is a gitdir file\n- fix(agentexec): recover agents that end a turn without the required finish\n call\n- feat(scheduling): ticker engine with a configurable interval and pools\n- fix(telegram): keep tool-call context when compacting tool output (#609)\n- feat(workflow): add the adversarial-review findings contract, where only a\n confirmed finding blocks and \"review found nothing\" is distinct from\n \"review did not run\" (contract only; no review stage runs yet)" }, { - "component": "archied", - "name": "archied", "version": "1.14.0", "date": "2026-08-23", - "body": "- fix(telegram): compact tool output and drop turn caps\n- fix(update): install only approved components" + "body": "### archied\n\n- fix(telegram): compact tool output and drop turn caps\n- fix(update): install only approved components" }, { - "component": "archied", - "name": "archied", "version": "1.13.0", "date": "2026-08-23", - "body": "- fix(telegram): render tool progress as bounded code blocks" + "body": "### archied\n\n- fix(telegram): render tool progress as bounded code blocks" }, { - "component": "archied", - "name": "archied", "version": "1.12.0", "date": "2026-08-23", - "body": "- fix(webui): give dashboard-initiated updates a phase-2 report\n- feat(agent): stamp archie-agent's build and report it back to the daemon\n- feat(releaseupdate): enrich components with install type and reference\n- feat(webui): surface per-component update status on /api/version and Configuration" + "body": "### archied\n\n- fix(webui): give dashboard-initiated updates a phase-2 report\n- feat(agent): stamp archie-agent's build and report it back to the daemon\n- feat(releaseupdate): enrich components with install type and reference\n- feat(webui): surface per-component update status on /api/version and Configuration" }, { - "component": "archied", - "name": "archied", "version": "1.11.1", "date": "2026-08-23", - "body": "- fix(update): wire Telegram personas and survive callback cancellation\n- fix(webui): theme the Workflows 'Start work' form controls" + "body": "### archied\n\n- fix(update): wire Telegram personas and survive callback cancellation\n- fix(webui): theme the Workflows 'Start work' form controls" }, { - "component": "archied", - "name": "archied", "version": "1.11.0", "date": "2026-08-23", - "body": "- feat(forge): make webhook intake observable and deduplicate concurrent delivery\n- fix(telegram): preserve code fences across message splits\n- fix(gateway): replay completed-duplicate turns with their tool activity\n- feat(storage): persist agent project state across sessions\n- fix(container): persist npm cache for per-task MCP servers\n- fix(worktree): bind publication to dispatch grants, reset retries to a pristine base, and reject diffs without a merge base\n- feat(media): deliver generated media through Telegram with link fallback in the dashboard\n- feat(tools): generate videos through MiniMax, gated by provider configuration" + "body": "### archied\n\n- feat(forge): make webhook intake observable and deduplicate concurrent delivery\n- fix(telegram): preserve code fences across message splits\n- fix(gateway): replay completed-duplicate turns with their tool activity\n- feat(storage): persist agent project state across sessions\n- fix(container): persist npm cache for per-task MCP servers\n- fix(worktree): bind publication to dispatch grants, reset retries to a pristine base, and reject diffs without a merge base\n- feat(media): deliver generated media through Telegram with link fallback in the dashboard\n- feat(tools): generate videos through MiniMax, gated by provider configuration" }, { - "component": "archied", - "name": "archied", "version": "1.10.0", "date": "2026-08-22", - "body": "- feat(forge): GitHub webhook receiver for immediate issue dispatch\n- feat(webhookguard): shared HMAC, rate-limit, and redaction mechanics\n- feat(nats): run an embedded server when no external NATS is configured\n- feat(capture): store unbound webhook events, retention-bounded\n- feat(webui): event inspector -- see captured payloads in the dashboard\n- feat(webui): payload field mapping -- bind JSON paths to named fields, preview before saving\n- fix(webui): stop the capture live-event notification duplicating payloads into the unbounded events table\n- fix(update): verify an update took effect instead of trusting the report (#530)\n- fix(daemon): refuse to poll on an empty label-trigger match (#529)\n- fix(gateway): stop persona from asserting unverified claims as fact (#528)\n- fix(gateway): stop ClaimTurn's insert-race branch losing its own retry read\n- fix: restore provider gate and dashboard token accounting\n- fix: address simple findings from a repo-wide golangci-lint sweep" + "body": "### archied\n\n- feat(forge): GitHub webhook receiver for immediate issue dispatch\n- feat(webhookguard): shared HMAC, rate-limit, and redaction mechanics\n- feat(nats): run an embedded server when no external NATS is configured\n- feat(capture): store unbound webhook events, retention-bounded\n- feat(webui): event inspector -- see captured payloads in the dashboard\n- feat(webui): payload field mapping -- bind JSON paths to named fields, preview before saving\n- fix(webui): stop the capture live-event notification duplicating payloads into the unbounded events table\n- fix(update): verify an update took effect instead of trusting the report (#530)\n- fix(daemon): refuse to poll on an empty label-trigger match (#529)\n- fix(gateway): stop persona from asserting unverified claims as fact (#528)\n- fix(gateway): stop ClaimTurn's insert-race branch losing its own retry read\n- fix: restore provider gate and dashboard token accounting\n- fix: address simple findings from a repo-wide golangci-lint sweep" }, { - "component": "archied", - "name": "archied", "version": "1.9.11", "date": "2026-08-19", - "body": "- fix(mcp): persist npx package cache across daemon restarts" + "body": "### archied\n\n- fix(mcp): persist npx package cache across daemon restarts" }, { - "component": "archied", - "name": "archied", "version": "1.9.10", "date": "2026-08-19", - "body": "- feat(update): `/update` now streams live progress while an update installs, reports a clear version summary (previous/installed, daemon/agent) once the build succeeds, and automatically rolls back and reports the outcome if the restarted daemon fails its post-update health check" + "body": "### archied\n\n- feat(update): `/update` now streams live progress while an update installs, reports a clear version summary (previous/installed, daemon/agent) once the build succeeds, and automatically rolls back and reports the outcome if the restarted daemon fails its post-update health check" }, { - "component": "archied", - "name": "archied", "version": "1.9.9", "date": "2026-08-18", - "body": "- fix(telegram): drain live renderer in concurrency test" + "body": "### archied\n\n- fix(telegram): drain live renderer in concurrency test\n\n### archie-agent\n\n- chore: no user-facing changes" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.9.9", - "date": "2026-08-18", - "body": "- chore: no user-facing changes" - }, - { - "component": "archied", - "name": "archied", "version": "1.9.8", "date": "2026-08-17", - "body": "- chore: no user-facing changes" + "body": "### archied\n\n- chore: no user-facing changes\n\n### archie-agent\n\n- chore: no user-facing changes" }, { - "component": "archied", - "name": "archied", "version": "1.9.7", "date": "2026-08-17", - "body": "- chore: no user-facing changes" + "body": "### archied\n\n- chore: no user-facing changes\n\n### archie-agent\n\n- chore: no user-facing changes" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.9.8", - "date": "2026-08-17", - "body": "- chore: no user-facing changes" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.9.7", - "date": "2026-08-17", - "body": "- chore: no user-facing changes" - }, - { - "component": "archied", - "name": "archied", "version": "1.9.6", "date": "2026-08-16", - "body": "- fix(update): stamp install type and bound retry backoff" + "body": "### archied\n\n- fix(update): stamp install type and bound retry backoff\n\n### archie-agent\n\n- chore: no user-facing changes" }, { - "component": "archied", - "name": "archied", "version": "1.9.5", "date": "2026-08-16", - "body": "- refactor(archied): decompose the daemon bootstrap into phased wiring (no behaviour change; splits the ~950-line run() into focused setup phases so complexity linting passes)\n- refactor(archied): extract the config overlay boot helper and thread context through chat gateway setup\n- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity\n- fix(tools): avoid predeclared `max` names\n- fix(email): use context-aware test networking\n- fix(indexing): remove the unused code search test runner\n- fix(tests): use contexts and type assertions in overlay and gateway tests\n- docs(architecture): document the memory engine family" + "body": "### archied\n\n- refactor(archied): decompose the daemon bootstrap into phased wiring (no behaviour change; splits the ~950-line run() into focused setup phases so complexity linting passes)\n- refactor(archied): extract the config overlay boot helper and thread context through chat gateway setup\n- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity\n- fix(tools): avoid predeclared `max` names\n- fix(email): use context-aware test networking\n- fix(indexing): remove the unused code search test runner\n- fix(tests): use contexts and type assertions in overlay and gateway tests\n- docs(architecture): document the memory engine family\n\n### archie-agent\n\n- refactor: decompose the daemon bootstrap into phased wiring (no behaviour change; complexity-driven restructure)\n- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity\n- fix(tools): avoid predeclared `max` names" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.9.6", - "date": "2026-08-16", - "body": "- chore: no user-facing changes" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.9.5", - "date": "2026-08-16", - "body": "- refactor: decompose the daemon bootstrap into phased wiring (no behaviour change; complexity-driven restructure)\n- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity\n- fix(tools): avoid predeclared `max` names" - }, - { - "component": "archied", - "name": "archied", "version": "1.9.4", "date": "2026-08-15", - "body": "- feat(gateway): polish /status command response format\n- fix(telegram): preserve URL boundaries in responses" + "body": "### archied\n\n- feat(gateway): polish /status command response format\n- fix(telegram): preserve URL boundaries in responses\n\n### archie-agent\n\n- chore: no user-facing changes" }, { - "component": "archied", - "name": "archied", "version": "1.9.3", "date": "2026-08-15", - "body": "- fix(webui): scroll selected command into view on keyboard navigation\n- fix(logging): resolve error attrs to their message string, not {}\n- feat(agentexec,workflow): surface tool calls on the task timeline" + "body": "### archied\n\n- fix(webui): scroll selected command into view on keyboard navigation\n- fix(logging): resolve error attrs to their message string, not {}\n- feat(agentexec,workflow): surface tool calls on the task timeline\n\n### archie-agent\n\n- fix(logging): resolve error attrs to their message string, not {}\n- fix(agentworker): back off before refetching a nak'd stage message\n- feat(agentexec,workflow): surface tool calls on the task timeline" }, { - "component": "archied", - "name": "archied", "version": "1.9.2", "date": "2026-08-15", - "body": "- fix(worktree): force checkout so retry recovers from a dirty worktree" + "body": "### archied\n\n- fix(worktree): force checkout so retry recovers from a dirty worktree\n\n### archie-agent\n\n- fix(worktree): force checkout so retry recovers from a dirty worktree" }, { - "component": "archied", - "name": "archied", "version": "1.9.1", "date": "2026-08-15", - "body": "- fix(agentworker): forward workflow events across the NATS worker boundary\n- fix(webui): filter turn_completed noise from the Live Activity SSE feed\n- feat(releaseupdate): stamp install type at build time, fail closed on unknown" + "body": "### archied\n\n- fix(agentworker): forward workflow events across the NATS worker boundary\n- fix(webui): filter turn_completed noise from the Live Activity SSE feed\n- feat(releaseupdate): stamp install type at build time, fail closed on unknown\n\n### archie-agent\n\n- fix(agentworker): forward workflow events across the NATS worker boundary" }, { - "component": "archied", - "name": "archied", "version": "1.9.0", "date": "2026-08-15", - "body": "- fix(webui): style tool-call failure from a structured field, not a string prefix\n- fix(config,webui): make show_tool_calls one cross-channel setting\n- fix(telegram): guarantee no message is stranded on gateway stop/restart\n- fix(telegram): use NewRequestWithContext to satisfy noctx\n- refactor(webui): decompose handleSSE to cut cognitive complexity" + "body": "### archied\n\n- fix(webui): style tool-call failure from a structured field, not a string prefix\n- fix(config,webui): make show_tool_calls one cross-channel setting\n- fix(telegram): guarantee no message is stranded on gateway stop/restart\n- fix(telegram): use NewRequestWithContext to satisfy noctx\n- refactor(webui): decompose handleSSE to cut cognitive complexity\n\n### archie-agent\n\n- fix(agent): resolve git dubious-ownership in sandbox containers\n- feat(agent): mark the mounted worktree as a git safe directory\n- fix(agent): route git safe.directory setup through markWorktreeSafe\n- feat(chat): show tool calls inline and stream replies into one message\n- refactor(agent): move worker runtime into application layer\n- fix(config,webui): make show_tool_calls one cross-channel setting" }, { - "component": "archied", - "name": "archied", "version": "1.8.0", "date": "2026-08-15", - "body": "- feat(archied): add -version so the installed build can be read from a shell\n- fix(webui): rebuild the Configuration page layout so values stop colliding\n- fix(webui): size Configuration key/value lists to their own content\n- fix(webui): keep Configuration rows full width, hug only the label column\n- fix(webui): cap and centre the Configuration page instead of its lists\n- fix(webui): preserve encoded redirect path characters\n- feat(chat): show tool calls inline and stream replies into one message\n- fix(chat): harden inline tool call streaming\n- refactor(agent): move worker runtime into application layer\n- fix(telegram): harden live-reply delivery against /stop and multi-byte content\n- fix(telegram): keep tool activity visible and mark failed/empty turns\n- fix(config): de-duplicate disabled-forge predicate, export ForgeDisabled" + "body": "### archied\n\n- feat(archied): add -version so the installed build can be read from a shell\n- fix(webui): rebuild the Configuration page layout so values stop colliding\n- fix(webui): size Configuration key/value lists to their own content\n- fix(webui): keep Configuration rows full width, hug only the label column\n- fix(webui): cap and centre the Configuration page instead of its lists\n- fix(webui): preserve encoded redirect path characters\n- feat(chat): show tool calls inline and stream replies into one message\n- fix(chat): harden inline tool call streaming\n- refactor(agent): move worker runtime into application layer\n- fix(telegram): harden live-reply delivery against /stop and multi-byte content\n- fix(telegram): keep tool activity visible and mark failed/empty turns\n- fix(config): de-duplicate disabled-forge predicate, export ForgeDisabled" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.9.4", - "date": "2026-08-15", - "body": "- chore: no user-facing changes" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.9.3", - "date": "2026-08-15", - "body": "- fix(logging): resolve error attrs to their message string, not {}\n- fix(agentworker): back off before refetching a nak'd stage message\n- feat(agentexec,workflow): surface tool calls on the task timeline" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.9.2", - "date": "2026-08-15", - "body": "- fix(worktree): force checkout so retry recovers from a dirty worktree" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.9.1", - "date": "2026-08-15", - "body": "- fix(agentworker): forward workflow events across the NATS worker boundary" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.9.0", - "date": "2026-08-15", - "body": "- fix(agent): resolve git dubious-ownership in sandbox containers\n- feat(agent): mark the mounted worktree as a git safe directory\n- fix(agent): route git safe.directory setup through markWorktreeSafe\n- feat(chat): show tool calls inline and stream replies into one message\n- refactor(agent): move worker runtime into application layer\n- fix(config,webui): make show_tool_calls one cross-channel setting" - }, - { - "component": "archied", - "name": "archied", "version": "1.7.0", "date": "2026-08-10", - "body": "- fix(build): install ripgrep where grep.go actually needs it on PATH\n- fix(webui): Send button no longer passes its click event to sendMessage\n- feat(webui): Enter sends, Shift+Enter inserts a newline\n- fix(chat): stop showing raw 501 banner for unconfigured update-check\n- fix(chat): give chat page a real height budget instead of a floor\n- fix(workflow): carry gate output into the baseline park error\n- feat(logging): add a per-task log sink\n- feat(agentexec): publish agent-side logs to the task's system subject\n- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed\n- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool\n- refactor(gateway): persist conversations in sqlite\n- refactor(store): replace legacy persistence with SQLite\n- fix(webui): tighten configuration KV row spacing\n- fix(gateway): harden session recovery paths\n- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe\n- feat(config): SIGHUP-triggered reload with requires-restart warnings\n- fix(config): share one config Holder between daemon and dashboard; re-apply model catalog on reload\n- fix(config): complete the reloadable allowlist and pin it against ForTask\n- feat(config): runtime config overlay store, PATCH /api/config, and the `--no-config-overlay` recovery flag\n- feat(webui): inline config editing on the Configuration page\n- feat(config): surface overlay state, shadowed keys, and per-row reset\n- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state\n- fix(config): preserve nil slices in Clone to avoid spurious reload warnings" + "body": "### archied\n\n- fix(build): install ripgrep where grep.go actually needs it on PATH\n- fix(webui): Send button no longer passes its click event to sendMessage\n- feat(webui): Enter sends, Shift+Enter inserts a newline\n- fix(chat): stop showing raw 501 banner for unconfigured update-check\n- fix(chat): give chat page a real height budget instead of a floor\n- fix(workflow): carry gate output into the baseline park error\n- feat(logging): add a per-task log sink\n- feat(agentexec): publish agent-side logs to the task's system subject\n- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed\n- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool\n- refactor(gateway): persist conversations in sqlite\n- refactor(store): replace legacy persistence with SQLite\n- fix(webui): tighten configuration KV row spacing\n- fix(gateway): harden session recovery paths\n- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe\n- feat(config): SIGHUP-triggered reload with requires-restart warnings\n- fix(config): share one config Holder between daemon and dashboard; re-apply model catalog on reload\n- fix(config): complete the reloadable allowlist and pin it against ForTask\n- feat(config): runtime config overlay store, PATCH /api/config, and the `--no-config-overlay` recovery flag\n- feat(webui): inline config editing on the Configuration page\n- feat(config): surface overlay state, shadowed keys, and per-row reset\n- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state\n- fix(config): preserve nil slices in Clone to avoid spurious reload warnings" }, { - "component": "archie", - "name": "archie-agent", "version": "1.4.0", "date": "2026-08-10", - "body": "- feat(gateway): tool-approval gate, session tools for chat, and /delete command\n- feat(gateway): make chat turns durable and idempotent\n- feat(webui): lifecycle-safe task controls with atomic retry and archive\n- feat(logging,workflow): daemon log feed and executable workflow registry\n- fix(store,gateway): taskstate constants and mobile jump-to search\n- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams\n- fix(build): install ripgrep where grep.go actually needs it on PATH\n- fix(workflow): carry gate output into the baseline park error\n- feat(logging): add a per-task log sink\n- feat(agentexec): publish agent-side logs to the task's system subject\n- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed\n- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool\n- refactor(store): replace legacy persistence with SQLite\n- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe\n- feat(config): SIGHUP-triggered reload with requires-restart warnings\n- feat(config): surface overlay state, shadowed keys, and per-row reset\n- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state\n- fix(config): preserve nil slices in Clone to avoid spurious reload warnings" + "body": "### archied (released 2026-07-31)\n\n- fix(secrets): wire provider credentials through engines\n\n### archie-agent\n\n- feat(gateway): tool-approval gate, session tools for chat, and /delete command\n- feat(gateway): make chat turns durable and idempotent\n- feat(webui): lifecycle-safe task controls with atomic retry and archive\n- feat(logging,workflow): daemon log feed and executable workflow registry\n- fix(store,gateway): taskstate constants and mobile jump-to search\n- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams\n- fix(build): install ripgrep where grep.go actually needs it on PATH\n- fix(workflow): carry gate output into the baseline park error\n- feat(logging): add a per-task log sink\n- feat(agentexec): publish agent-side logs to the task's system subject\n- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed\n- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool\n- refactor(store): replace legacy persistence with SQLite\n- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe\n- feat(config): SIGHUP-triggered reload with requires-restart warnings\n- feat(config): surface overlay state, shadowed keys, and per-row reset\n- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state\n- fix(config): preserve nil slices in Clone to avoid spurious reload warnings" }, { - "component": "archied", - "name": "archied", "version": "1.6.0", "date": "2026-08-09", - "body": "- feat(gateway): tool-approval gate, session tools for chat, and /delete command\n- fix(webui): close open-redirect in dashboard token-exchange handler\n- feat(gateway): make chat turns durable and idempotent\n- feat(webui): lifecycle-safe task controls with atomic retry and archive\n- feat(config,channels): format-neutral config resolution and truthful channel state\n- feat(logging,workflow): daemon log feed and executable workflow registry\n- fix(store,gateway): taskstate constants and mobile jump-to search\n- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams\n- fix(ui): hide inactive chat command menu" + "body": "### archied\n\n- feat(gateway): tool-approval gate, session tools for chat, and /delete command\n- fix(webui): close open-redirect in dashboard token-exchange handler\n- feat(gateway): make chat turns durable and idempotent\n- feat(webui): lifecycle-safe task controls with atomic retry and archive\n- feat(config,channels): format-neutral config resolution and truthful channel state\n- feat(logging,workflow): daemon log feed and executable workflow registry\n- fix(store,gateway): taskstate constants and mobile jump-to search\n- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams\n- fix(ui): hide inactive chat command menu" }, { - "component": "archied", - "name": "archied", "version": "1.5.0", "date": "2026-08-08", - "body": "- feat(curator): engine family contract, registry, and runtime\n- feat(curator): trigger accounting — primary-input wake path\n- feat(setup): interactive setup steps with a TTY-gated prompter\n- feat(webui): rebuild the dashboard and add chat\n- feat(daemon): identity-scoped isolation plus gateway session titles and /delete\n- feat(logging): optional rotating log file\n- feat(configuration): export Validate for the setup flow\n- fix(gateway): durable message identity with a SQLite store\n- fix(gateway): consistent message ordering and paged search\n- fix(gateway): stop /compress destroying history it should have kept\n- fix(gateway): do not answer a redelivered message twice\n- fix(gateway): claim the session slot before writing it, not after\n- fix(gateway): keep /topic off from poisoning the session cache\n- fix(gateway): resolve the most recently active session, not an arbitrary one\n- fix(gateway): give branch-inherited messages their own identity\n- fix(gateway): make both backends agree on newest-first\n- fix(store): honour the transition guard in production persistence\n- fix(store): move ID counters away from the reserved metadata namespace\n- fix(store): surface task timestamps and tag the summary structs\n- fix(telegram): pause the update loop when rate limited\n- fix(memory): fail startup on an unusable memory directory\n- fix(tools): let an optional provider fail without taking the daemon down\n- fix(tools): report a cancelled find walk as an error, not empty results\n- fix(worktree): name the missing forge credential when a push fails\n- fix(tomlwrite): recognise table headers carrying a trailing comment\n- fix: close the duplicate-work loop and the dead paths around it\n- perf(tools): drop the embedded ripgrep binaries\n- refactor: one definition of what approving or declining a task means\n- refactor: move workflow into its own domain" + "body": "### archied\n\n- feat(curator): engine family contract, registry, and runtime\n- feat(curator): trigger accounting — primary-input wake path\n- feat(setup): interactive setup steps with a TTY-gated prompter\n- feat(webui): rebuild the dashboard and add chat\n- feat(daemon): identity-scoped isolation plus gateway session titles and /delete\n- feat(logging): optional rotating log file\n- feat(configuration): export Validate for the setup flow\n- fix(gateway): durable message identity with a SQLite store\n- fix(gateway): consistent message ordering and paged search\n- fix(gateway): stop /compress destroying history it should have kept\n- fix(gateway): do not answer a redelivered message twice\n- fix(gateway): claim the session slot before writing it, not after\n- fix(gateway): keep /topic off from poisoning the session cache\n- fix(gateway): resolve the most recently active session, not an arbitrary one\n- fix(gateway): give branch-inherited messages their own identity\n- fix(gateway): make both backends agree on newest-first\n- fix(store): honour the transition guard in production persistence\n- fix(store): move ID counters away from the reserved metadata namespace\n- fix(store): surface task timestamps and tag the summary structs\n- fix(telegram): pause the update loop when rate limited\n- fix(memory): fail startup on an unusable memory directory\n- fix(tools): let an optional provider fail without taking the daemon down\n- fix(tools): report a cancelled find walk as an error, not empty results\n- fix(worktree): name the missing forge credential when a push fails\n- fix(tomlwrite): recognise table headers carrying a trailing comment\n- fix: close the duplicate-work loop and the dead paths around it\n- perf(tools): drop the embedded ripgrep binaries\n- refactor: one definition of what approving or declining a task means\n- refactor: move workflow into its own domain" }, { - "component": "archie", - "name": "archie-agent", "version": "1.3.0", "date": "2026-08-08", - "body": "- feat(curator): engine family contract, registry, and runtime\n- feat(curator): trigger accounting — primary-input wake path\n- feat(logging): optional rotating log file\n- feat(daemon): identity-scoped isolation\n- fix(secrets): wire provider credentials through engines\n- fix(store): surface task timestamps and tag the summary structs\n- fix(tools): let an optional provider fail without taking the daemon down\n- fix(tools): report a cancelled find walk as an error, not empty results\n- fix(worktree): name the missing forge credential when a push fails\n- fix: close the duplicate-work loop and the dead paths around it\n- perf(tools): drop the embedded ripgrep binaries\n- refactor: one definition of what approving or declining a task means\n- refactor: move workflow into its own domain" + "body": "### archied (released 2026-07-31)\n\n- fix(memory): replace framework-specific names with generic equivalents\n- feat: unify provider and model selection\n\n### archie-agent\n\n- feat(curator): engine family contract, registry, and runtime\n- feat(curator): trigger accounting — primary-input wake path\n- feat(logging): optional rotating log file\n- feat(daemon): identity-scoped isolation\n- fix(secrets): wire provider credentials through engines\n- fix(store): surface task timestamps and tag the summary structs\n- fix(tools): let an optional provider fail without taking the daemon down\n- fix(tools): report a cancelled find walk as an error, not empty results\n- fix(worktree): name the missing forge credential when a push fails\n- fix: close the duplicate-work loop and the dead paths around it\n- perf(tools): drop the embedded ripgrep binaries\n- refactor: one definition of what approving or declining a task means\n- refactor: move workflow into its own domain" }, { - "component": "archied", - "name": "archied", "version": "1.4.1", "date": "2026-07-31", - "body": "- fix(catalog): match SDK provider fallback" + "body": "### archied\n\n- fix(catalog): match SDK provider fallback" }, { - "component": "archied", - "name": "archied", - "version": "1.4.0", - "date": "2026-07-31", - "body": "- fix(secrets): wire provider credentials through engines" - }, - { - "component": "archied", - "name": "archied", "version": "1.3.1", "date": "2026-07-31", - "body": "- fix(telegram): omit empty model picker markup" + "body": "### archied\n\n- fix(telegram): omit empty model picker markup" }, { - "component": "archied", - "name": "archied", - "version": "1.3.0", - "date": "2026-07-31", - "body": "- fix(memory): replace framework-specific names with generic equivalents\n- feat: unify provider and model selection" - }, - { - "component": "archied", - "name": "archied", "version": "1.2.0", "date": "2026-07-31", - "body": "- feat: add MCP client capabilities to archied and archie-agent\n- fix: handleSummary ignores errors from WorkflowStats/StageStats/TokensByDay\n- feat: establish Archie identity and use stable callback tokens\n- refactor(telegram): keep one model selector command\n- fix: handleSSE silently swallows EventsSince backlog fetch errors\n- fix: Transition() ignores `from` status guard, allowing lost updates\n- fix: skillscript.Run ignores context, cannot be canceled/timed out\n- feat(telegram): report installed component versions\n- feat(telegram): add approved component updates\n- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup\n- feat(chat): real system prompt for Archie — identity, tools, env\n- feat(indexing): port tau's codesearch workspace index\n- fix(indexing): surface index config properly and stop silent degradation\n- refactor(worktree): replace git shell-out with go-git v6\n- fix(worktreerpc): bound handler contexts and drop the git binary from tests\n- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries\n- refactor: route tasks on a typed kind, not forge labels\n- fix(natsrpc): make RegisterAll wait for the server to see subscriptions\n- refactor(config): move loading into infrastructure/configuration\n- fix(telegram): publish all executable session commands in menu and help\n- fix(telegram): publish the restored gateway commands\n- refactor: add internal/eventbus as the broker-neutral messaging contract\n- fix(chat): operator name from config, session wiring, prompt rules\n- feat(tools): lift tau's file and shell tools into the tool registry\n- feat: make /stop cancel the running chat turn\n- fix: kill the whole process group when a shell command is cancelled\n- feat: refuse unrecoverable shell commands\n- feat: make /stop reach running agent tasks\n- fix(chat): temper prompt brevity rules with warmth\n- fix: use errors.Is/As for context errors and cleanup\n- fix(grep): distinguish ripgrep exit 1 from a failed search\n- fix(archied): disable the forge on a missing credential, not the daemon\n- fix: restore /model parsing and close the 6d4e0be autofix audit\n- feat: embed config.example.toml and add comment-preserving TOML writer\n- fix(docker): install unzip and Node 24 so MCP servers can start\n- fix(docker): slim both images and repair unreachable Go tooling\n- fix(container): write the task boot brief under .git\n- fix(telegram): drop pending updates before long polling" + "body": "### archied\n\n- feat: add MCP client capabilities to archied and archie-agent\n- fix: handleSummary ignores errors from WorkflowStats/StageStats/TokensByDay\n- feat: establish Archie identity and use stable callback tokens\n- refactor(telegram): keep one model selector command\n- fix: handleSSE silently swallows EventsSince backlog fetch errors\n- fix: Transition() ignores `from` status guard, allowing lost updates\n- fix: skillscript.Run ignores context, cannot be canceled/timed out\n- feat(telegram): report installed component versions\n- feat(telegram): add approved component updates\n- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup\n- feat(chat): real system prompt for Archie — identity, tools, env\n- feat(indexing): port tau's codesearch workspace index\n- fix(indexing): surface index config properly and stop silent degradation\n- refactor(worktree): replace git shell-out with go-git v6\n- fix(worktreerpc): bound handler contexts and drop the git binary from tests\n- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries\n- refactor: route tasks on a typed kind, not forge labels\n- fix(natsrpc): make RegisterAll wait for the server to see subscriptions\n- refactor(config): move loading into infrastructure/configuration\n- fix(telegram): publish all executable session commands in menu and help\n- fix(telegram): publish the restored gateway commands\n- refactor: add internal/eventbus as the broker-neutral messaging contract\n- fix(chat): operator name from config, session wiring, prompt rules\n- feat(tools): lift tau's file and shell tools into the tool registry\n- feat: make /stop cancel the running chat turn\n- fix: kill the whole process group when a shell command is cancelled\n- feat: refuse unrecoverable shell commands\n- feat: make /stop reach running agent tasks\n- fix(chat): temper prompt brevity rules with warmth\n- fix: use errors.Is/As for context errors and cleanup\n- fix(grep): distinguish ripgrep exit 1 from a failed search\n- fix(archied): disable the forge on a missing credential, not the daemon\n- fix: restore /model parsing and close the 6d4e0be autofix audit\n- feat: embed config.example.toml and add comment-preserving TOML writer\n- fix(docker): install unzip and Node 24 so MCP servers can start\n- fix(docker): slim both images and repair unreachable Go tooling\n- fix(container): write the task boot brief under .git\n- fix(telegram): drop pending updates before long polling\n\n### archie-agent\n\n- feat: add MCP client capabilities to archied and archie-agent\n- fix: Transition() ignores `from` status guard, allowing lost updates\n- fix: skillscript.Run ignores context, cannot be canceled/timed out\n- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup\n- fix(indexing): surface index config properly and stop silent degradation\n- refactor(worktree): replace git shell-out with go-git v6\n- fix(worktreerpc): bound handler contexts and drop the git binary from tests\n- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries\n- refactor: route tasks on a typed kind, not forge labels\n- fix(natsrpc): make RegisterAll wait for the server to see subscriptions\n- refactor(config): move loading into infrastructure/configuration\n- refactor: add internal/eventbus as the broker-neutral messaging contract\n- feat(tools): lift tau's file and shell tools into the tool registry\n- feat: make /stop cancel the running chat turn\n- fix: kill the whole process group when a shell command is cancelled\n- feat: refuse unrecoverable shell commands\n- feat: make /stop reach running agent tasks\n- fix: use errors.Is/As for context errors and cleanup\n- fix(grep): distinguish ripgrep exit 1 from a failed search\n- fix(docker): slim both images and repair unreachable Go tooling\n- fix(container): write the task boot brief under .git" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.2.0", - "date": "2026-07-31", - "body": "- feat: add MCP client capabilities to archied and archie-agent\n- fix: Transition() ignores `from` status guard, allowing lost updates\n- fix: skillscript.Run ignores context, cannot be canceled/timed out\n- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup\n- fix(indexing): surface index config properly and stop silent degradation\n- refactor(worktree): replace git shell-out with go-git v6\n- fix(worktreerpc): bound handler contexts and drop the git binary from tests\n- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries\n- refactor: route tasks on a typed kind, not forge labels\n- fix(natsrpc): make RegisterAll wait for the server to see subscriptions\n- refactor(config): move loading into infrastructure/configuration\n- refactor: add internal/eventbus as the broker-neutral messaging contract\n- feat(tools): lift tau's file and shell tools into the tool registry\n- feat: make /stop cancel the running chat turn\n- fix: kill the whole process group when a shell command is cancelled\n- feat: refuse unrecoverable shell commands\n- feat: make /stop reach running agent tasks\n- fix: use errors.Is/As for context errors and cleanup\n- fix(grep): distinguish ripgrep exit 1 from a failed search\n- fix(docker): slim both images and repair unreachable Go tooling\n- fix(container): write the task boot brief under .git" - }, - { - "component": "archied", - "name": "archied", "version": "1.1.0", "date": "2026-07-27", - "body": "- feat: add the Telegram gateway with persistent sessions, topic-thread support, streamed rich replies, typing indicators, and Markdown rendering\n- feat: add `/spawn`, `/approve`, and `/cancel` for chat-driven task control\n- feat: provide a comprehensive `/help` guide whose command list stays aligned with Telegram's published menu and Archie's executable command surface\n- feat: add `/provider` and provider-filtered `/model` selectors that switch the provider and model used by subsequent live chat turns\n- feat: include the active provider and full model reference in `/status`\n- feat: notify authorized Telegram users once when a newly tagged component release is installed\n- feat: add `/restart` to reload and relaunch the Telegram gateway without interrupting in-flight daemon tasks\n- feat: add deny-by-default Telegram sender authorization and native command-menu publication\n- feat: connect Desktop Commander through Archie's managed MCP client so chat can use workspace file and process tools\n- feat: add multi-identity daemon configuration, persona routing, an email channel, and webhook platform support\n- feat: add durable task, session, message, and memory persistence\n- feat: add memory synchronization, prefetch, context scrubbing, threat scanning, and built-in memory tools\n- feat: add tool guardrails, classification, budgets, availability filtering, and disclosure controls\n- feat: add feature-based YAML configuration with `conf.d` overlay loading\n- feat: add typed secret-engine registration and Yaegi extension support\n- fix: reject unknown slash commands locally instead of allowing the LLM to fabricate command behavior\n- fix: publish Telegram commands to default, private-chat, and group-chat scopes so stale commands inherited with the bot token cannot shadow Archie's menu\n- fix: drain the SDK's full event stream so streamed Telegram replies cannot deadlock\n- fix: use standard newline-delimited JSON framing for MCP stdio clients\n- fix: make MCP stdio shutdown and timeout handling race-safe\n- fix: restore legacy `[forge].token_env` compatibility and required container environment passthrough\n- fix: make the agent-container Docker network explicitly configurable" + "body": "### archied\n\n- feat: add the Telegram gateway with persistent sessions, topic-thread support, streamed rich replies, typing indicators, and Markdown rendering\n- feat: add `/spawn`, `/approve`, and `/cancel` for chat-driven task control\n- feat: provide a comprehensive `/help` guide whose command list stays aligned with Telegram's published menu and Archie's executable command surface\n- feat: add `/provider` and provider-filtered `/model` selectors that switch the provider and model used by subsequent live chat turns\n- feat: include the active provider and full model reference in `/status`\n- feat: notify authorized Telegram users once when a newly tagged component release is installed\n- feat: add `/restart` to reload and relaunch the Telegram gateway without interrupting in-flight daemon tasks\n- feat: add deny-by-default Telegram sender authorization and native command-menu publication\n- feat: connect Desktop Commander through Archie's managed MCP client so chat can use workspace file and process tools\n- feat: add multi-identity daemon configuration, persona routing, an email channel, and webhook platform support\n- feat: add durable task, session, message, and memory persistence\n- feat: add memory synchronization, prefetch, context scrubbing, threat scanning, and built-in memory tools\n- feat: add tool guardrails, classification, budgets, availability filtering, and disclosure controls\n- feat: add feature-based YAML configuration with `conf.d` overlay loading\n- feat: add typed secret-engine registration and Yaegi extension support\n- fix: reject unknown slash commands locally instead of allowing the LLM to fabricate command behavior\n- fix: publish Telegram commands to default, private-chat, and group-chat scopes so stale commands inherited with the bot token cannot shadow Archie's menu\n- fix: drain the SDK's full event stream so streamed Telegram replies cannot deadlock\n- fix: use standard newline-delimited JSON framing for MCP stdio clients\n- fix: make MCP stdio shutdown and timeout handling race-safe\n- fix: restore legacy `[forge].token_env` compatibility and required container environment passthrough\n- fix: make the agent-container Docker network explicitly configurable\n\n### archie-agent\n\n- feat: add streamed agent execution with typed message events\n- feat: add MCP client transports and managed tool-provider discovery\n- feat: add memory context scrubbing and normalized memory tool schemas\n- feat: add plugin metadata extraction from `metadata.archie.plugins`\n- feat: add configurable container networking for daemon-launched runtimes\n- fix: preserve valid UTF-8 when clipping runtime output\n- fix: make MCP stdio lifecycle, retries, and timeout handling race-safe\n- fix: enforce a zero-finding lint and vet baseline" }, { - "component": "archie", - "name": "archie-agent", - "version": "1.1.0", - "date": "2026-07-27", - "body": "- feat: add streamed agent execution with typed message events\n- feat: add MCP client transports and managed tool-provider discovery\n- feat: add memory context scrubbing and normalized memory tool schemas\n- feat: add plugin metadata extraction from `metadata.archie.plugins`\n- feat: add configurable container networking for daemon-launched runtimes\n- fix: preserve valid UTF-8 when clipping runtime output\n- fix: make MCP stdio lifecycle, retries, and timeout handling race-safe\n- fix: enforce a zero-finding lint and vet baseline" - }, - { - "component": "archied", - "name": "archied", "version": "1.0.0", "date": "2026-07-22", - "body": "- feat: ship the resident forge-polling daemon, deterministic workflow engine, isolated worktrees, quality gates, Gitea integration, Docker/NATS worker split, plugin loading, and skills support\n- feat: publish `archied` and `archie-agent` container images to the Gitea registry" - }, - { - "component": "archie", - "name": "archie-agent", - "version": "1.0.0", - "date": "2026-07-22", - "body": "- feat: ship the isolated agent runtime, NATS RPC boundary, workflow execution, skills, and plugin support\n- feat: publish the `archie-agent` container image to the Gitea registry" + "body": "### archied\n\n- feat: ship the resident forge-polling daemon, deterministic workflow engine, isolated worktrees, quality gates, Gitea integration, Docker/NATS worker split, plugin loading, and skills support\n- feat: publish `archied` and `archie-agent` container images to the Gitea registry\n\n### archie-agent\n\n- feat: ship the isolated agent runtime, NATS RPC boundary, workflow execution, skills, and plugin support\n- feat: publish the `archie-agent` container image to the Gitea registry" } ] diff --git a/docs/prds/release-stream-and-commit-rules.md b/docs/prds/release-stream-and-commit-rules.md index 07ec3b3d6..5aad78e83 100644 --- a/docs/prds/release-stream-and-commit-rules.md +++ b/docs/prds/release-stream-and-commit-rules.md @@ -31,6 +31,13 @@ because a version's date is when the last part of it shipped. Where a component' date differs from it, that component's section label carries its own date, so the per-component fact survives the merge rather than being collapsed into the heading. +The merged history holds 65 versions: 33 that both components released, 31 only +`archied`, and one only `archie`, from 64 and 34 sections respectively, so 98 +published pages become 65. `## [Unreleased]` is not a release -- it carries no +version and gets no page -- but it stays at the top of the file, because it is +the one place unfinished work is recorded. Counting `##` headings rather than +releases overcounts by one. + This ambiguity is historical only. One version stream with one tag gives a version exactly one date, so the rule represents the merged past rather than a design that has to hold. diff --git a/internal/releaseannounce/announcer_test.go b/internal/releaseannounce/announcer_test.go index 9dacd3a99..a47a82c85 100644 --- a/internal/releaseannounce/announcer_test.go +++ b/internal/releaseannounce/announcer_test.go @@ -71,19 +71,17 @@ func TestAnnouncerBaselinesFirstReleaseWithoutSending(t *testing.T) { func TestAnnouncerSeparatesChangedAndUnchangedComponents(t *testing.T) { dir := t.TempDir() - gatewayChangelog := filepath.Join(dir, "CHANGELOG.archied.md") - runtimeChangelog := filepath.Join(dir, "CHANGELOG.archie.md") - if err := os.WriteFile(gatewayChangelog, []byte(testChangelog), 0o600); err != nil { - t.Fatal(err) - } - if err := os.WriteFile(runtimeChangelog, []byte(testChangelog), 0o600); err != nil { + // One changelog holds every release now; both components read the section + // for their version from it. + changelog := filepath.Join(dir, "CHANGELOG.md") + if err := os.WriteFile(changelog, []byte(testChangelog), 0o600); err != nil { t.Fatal(err) } announcer := Announcer{ StatePath: filepath.Join(dir, "announced.json"), Components: []Component{ - {ID: "gateway", Label: "THE GATEWAY", Version: "v0.1.0", ChangelogPath: gatewayChangelog}, - {ID: "runtime", Label: "THE RUNTIME", Version: "v0.1.0", ChangelogPath: runtimeChangelog}, + {ID: "gateway", Label: "THE GATEWAY", Version: "v0.1.0", ChangelogPath: changelog}, + {ID: "runtime", Label: "THE RUNTIME", Version: "v0.1.0", ChangelogPath: changelog}, }, } if err := announcer.Announce(context.Background(), []int64{7}, func(context.Context, int64, string) error { diff --git a/mkdocs.yml b/mkdocs.yml index 37aa5fa04..352feb68a 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -15,8 +15,7 @@ copyright: Vectis Labs # that grows with every release would push the architecture tree off the screen. # This is not exclude_docs -- the pages are wanted, just not as nav entries. not_in_nav: | - news/archied/* - news/archie/* + news/[0-9]* theme: name: material diff --git a/scripts/archie-update-check b/scripts/archie-update-check index edba2e0d9..b8ea82943 100755 --- a/scripts/archie-update-check +++ b/scripts/archie-update-check @@ -171,7 +171,7 @@ cat <] - `", c.changelog, section.heading) + return nil, fmt.Errorf("%s: %q is not a release heading; write `## [] - `", changelogPath, section.heading) } version, date := match[1], match[2] if version == "Unreleased" { continue } if date == "" { - return nil, fmt.Errorf("%s: release %s has no date; write `## [] - `", c.changelog, version) + return nil, fmt.Errorf("%s: release %s has no date; write `## [] - `", changelogPath, version) } if section.body == "" { - return nil, fmt.Errorf("%s: release %s has no notes", c.changelog, version) + return nil, fmt.Errorf("%s: release %s has no notes", changelogPath, version) } if target, ok := relativeLink(section.body); ok { - return nil, fmt.Errorf("%s: release %s has a relative link %q; release-notes links must be absolute", c.changelog, version, target) + return nil, fmt.Errorf("%s: release %s has a relative link %q; release-notes links must be absolute", changelogPath, version, target) } releases = append(releases, release{ - Component: c.key, - Name: c.name, - Version: version, - Date: date, - Body: section.body, + Version: version, + Date: date, + Body: section.body, }) } return releases, nil @@ -145,31 +132,19 @@ func relativeLink(body string) (string, bool) { return "", false } -// sortReleases orders releases newest first, then by component, then by -// descending version. Every host renders this order, so the canonical artifact -// is also the ordering contract. +// sortReleases orders releases newest first, then by descending version. Every +// host renders this order, so the canonical artifact is also the ordering +// contract. func sortReleases(releases []release) { sort.SliceStable(releases, func(i, j int) bool { a, b := releases[i], releases[j] if a.Date != b.Date { return a.Date > b.Date } - if ai, bi := componentIndex(a.Component), componentIndex(b.Component); ai != bi { - return ai < bi - } return compareVersions(a.Version, b.Version) > 0 }) } -func componentIndex(key string) int { - for i, c := range components { - if c.key == key { - return i - } - } - return len(components) -} - // compareVersions orders dotted versions by their numeric parts, so 1.9.10 is // newer than 1.9.9. A version carrying a prerelease is older than the same // version without one. diff --git a/tools/newsgen/changelog_test.go b/tools/newsgen/changelog_test.go index 67cbb3560..b431aa334 100644 --- a/tools/newsgen/changelog_test.go +++ b/tools/newsgen/changelog_test.go @@ -5,11 +5,11 @@ import ( "testing" ) -const sampleChangelog = `# archied changelog +const sampleChangelog = `# Changelog ## [1.31.0] - 2026-09-22 -### A heading +### archied — A heading - one bullet @@ -27,7 +27,7 @@ Not a release section. ` func TestParseChangelogReadsReleaseSections(t *testing.T) { - got, err := parseChangelog(components[0], sampleChangelog) + got, err := parseChangelog(sampleChangelog) if err != nil { t.Fatalf("parseChangelog error = %v", err) } @@ -35,13 +35,10 @@ func TestParseChangelogReadsReleaseSections(t *testing.T) { t.Fatalf("got %d releases, want 2: %+v", len(got), got) } first := got[0] - if first.Component != "archied" || first.Name != "archied" { - t.Fatalf("first release component/name = %q/%q, want archied/archied", first.Component, first.Name) - } if first.Version != "1.31.0" || first.Date != "2026-09-22" { t.Fatalf("first release version/date = %q/%q", first.Version, first.Date) } - if first.Body != "### A heading\n\n- one bullet" { + if first.Body != "### archied — A heading\n\n- one bullet" { t.Fatalf("first release body = %q", first.Body) } if got[1].Version != "1.30.0" || got[1].Body != "Just prose." { @@ -50,7 +47,7 @@ func TestParseChangelogReadsReleaseSections(t *testing.T) { } func TestParseChangelogSkipsUnreleased(t *testing.T) { - got, err := parseChangelog(components[0], sampleChangelog) + got, err := parseChangelog(sampleChangelog) if err != nil { t.Fatalf("parseChangelog error = %v", err) } @@ -95,7 +92,7 @@ func TestParseChangelogRejectsMalformedInput(t *testing.T) { } for _, tt := range tests { t.Run(tt.name, func(t *testing.T) { - _, err := parseChangelog(components[0], tt.source) + _, err := parseChangelog(tt.source) if err == nil { t.Fatal("expected an error") } @@ -112,14 +109,14 @@ func TestParseChangelogAllowsAbsoluteLinks(t *testing.T) { - [vulnerability](https://pkg.go.dev/vuln/GO-2026-6443), [anchor](#section), [root](/absolute), [angle](), [mail](mailto:a@b.c). ` - if _, err := parseChangelog(components[0], source); err != nil { + if _, err := parseChangelog(source); err != nil { t.Fatalf("parseChangelog error = %v", err) } } func TestParseChangelogKeepsFencedHeadingsInTheBody(t *testing.T) { source := "## [1.2.0] - 2026-01-01\n\n```sh\n## not a heading\n```\n\n- after the fence\n" - got, err := parseChangelog(components[0], source) + got, err := parseChangelog(source) if err != nil { t.Fatalf("parseChangelog error = %v", err) } @@ -151,20 +148,18 @@ func TestCompareVersions(t *testing.T) { } } -func TestSortReleasesNewestFirstThenComponentThenVersion(t *testing.T) { +func TestSortReleasesNewestFirstThenVersion(t *testing.T) { releases := []release{ - {Component: "archie", Name: "archie-agent", Version: "1.31.0", Date: "2026-09-22"}, - {Component: "archied", Name: "archied", Version: "1.9.9", Date: "2026-09-22"}, - {Component: "archied", Name: "archied", Version: "1.30.0", Date: "2026-09-20"}, - {Component: "archied", Name: "archied", Version: "1.9.10", Date: "2026-09-22"}, - {Component: "archied", Name: "archied", Version: "1.31.0", Date: "2026-09-22"}, + {Version: "1.9.9", Date: "2026-09-22"}, + {Version: "1.30.0", Date: "2026-09-20"}, + {Version: "1.9.10", Date: "2026-09-22"}, + {Version: "1.31.0", Date: "2026-09-22"}, } sortReleases(releases) - want := []string{"archied/1.31.0", "archied/1.9.10", "archied/1.9.9", "archie/1.31.0", "archied/1.30.0"} + want := []string{"1.31.0", "1.9.10", "1.9.9", "1.30.0"} for i, w := range want { - got := releases[i].Component + "/" + releases[i].Version - if got != w { - t.Fatalf("position %d = %s, want %s (all: %+v)", i, got, w, releases) + if releases[i].Version != w { + t.Fatalf("position %d = %s, want %s (all: %+v)", i, releases[i].Version, w, releases) } } } diff --git a/tools/newsgen/main.go b/tools/newsgen/main.go index 3db0508fc..9d7e122b3 100644 --- a/tools/newsgen/main.go +++ b/tools/newsgen/main.go @@ -1,17 +1,16 @@ -// Command newsgen derives every published release fact from the component -// changelogs. +// Command newsgen derives every published release fact from CHANGELOG.md. // -// CHANGELOG.archied.md and CHANGELOG.archie.md are the release process's frozen -// notes: tools/release.sh --prepare writes a section, the maintainer edits it, -// and --tag refuses to tag a version without its section. Tags are deliberately -// not a source, because CI and deployment check out shallow and a site build has -// no tags to read. +// CHANGELOG.md is the release process's frozen notes: tools/release.sh +// --prepare writes a section, the maintainer edits it, and --tag refuses to tag +// a version without its section. Tags are deliberately not a source, because CI +// and deployment check out shallow and a site build has no tags to read. // // Output is generated and committed: // -// docs/data/generated/releases.json the canonical, host-neutral fact set -// docs/news/index.md the news page -// docs/news//.md one page per release +// docs/news/releases.json the canonical, host-neutral fact set +// docs/news/redirects.json the retired per-component URLs, mapped to pages +// docs/news/index.md the news page +// docs/news/.md one page per release // // `newsgen check` reproduces the output in memory and fails when the committed // files differ, which keeps a changelog edit from landing without its pages. @@ -29,6 +28,7 @@ import ( "log" "os" "path/filepath" + "regexp" "sort" "strings" ) @@ -83,19 +83,15 @@ func parseOptions(args []string) (options, error) { return options{mode: selected, repoRoot: *repoRoot}, nil } -// load parses every component changelog and returns the releases newest first. +// load parses the changelog and returns the releases newest first. func load(repoRoot string) ([]release, error) { - releases := []release{} - for _, c := range components { - source, err := os.ReadFile(filepath.Join(repoRoot, c.changelog)) - if err != nil { - return nil, fmt.Errorf("read %s: %w", c.changelog, err) - } - parsed, err := parseChangelog(c, string(source)) - if err != nil { - return nil, err - } - releases = append(releases, parsed...) + source, err := os.ReadFile(filepath.Join(repoRoot, changelogPath)) + if err != nil { + return nil, fmt.Errorf("read %s: %w", changelogPath, err) + } + releases, err := parseChangelog(string(source)) + if err != nil { + return nil, err } sortReleases(releases) return releases, nil @@ -156,7 +152,7 @@ func check(repoRoot string) error { return fmt.Errorf("read %s: %w", path, err) } if !bytes.Equal(current, expected) { - problems = append(problems, path+" does not match the changelogs") + problems = append(problems, path+" does not match the changelog") } } for _, path := range unownedPages(repoRoot, files) { @@ -167,37 +163,48 @@ func check(repoRoot string) error { return fmt.Errorf("release notes are stale:\n %s\n fix with `task news`, then commit the result", strings.Join(problems, "\n ")) } - fmt.Printf("newsgen: %d release notes match the changelogs\n", len(releases)) + fmt.Printf("newsgen: %d release notes match the changelog\n", len(releases)) return nil } -// unownedPages lists files inside a generated component directory that this -// tool does not produce. The news directory's own root is not a generated -// directory, so a hand-written announcement there is left alone. +// releasePageName matches the basename of a generated version page, so a page +// left behind for a release the changelog no longer carries is reported. +var releasePageName = regexp.MustCompile(`^[0-9]+\.[0-9]+`) + +// unownedPages lists files under docs/news that this tool does not produce. A +// page from the retired per-component layout (a file in a subdirectory) and a +// stale version page are both unowned; anything else is a hand-written news +// item, and the news directory's root is where those live. func unownedPages(repoRoot string, files map[string][]byte) []string { var unowned []string - for _, c := range components { - dir := filepath.Join(repoRoot, newsDir, c.key) - err := filepath.WalkDir(dir, func(path string, entry fs.DirEntry, err error) error { - if err != nil { - return err - } - if entry.IsDir() { - return nil - } - relative, err := filepath.Rel(repoRoot, path) - if err != nil { - return err - } - slash := filepath.ToSlash(relative) - if _, generated := files[slash]; !generated { - unowned = append(unowned, slash) - } - return nil - }) - if err != nil && !errors.Is(err, fs.ErrNotExist) { - unowned = append(unowned, fmt.Sprintf("%s is unreadable: %v", c.key, err)) + root := filepath.Join(repoRoot, newsDir) + err := filepath.WalkDir(root, func(path string, entry fs.DirEntry, err error) error { + if err != nil { + return err } + if entry.IsDir() { + return nil + } + relative, err := filepath.Rel(repoRoot, path) + if err != nil { + return err + } + slash := filepath.ToSlash(relative) + if _, generated := files[slash]; generated { + return nil + } + if strings.Contains(slash[len(newsDir)+1:], "/") || looksLikeReleasePage(filepath.Base(path)) { + unowned = append(unowned, slash) + } + return nil + }) + if err != nil && !errors.Is(err, fs.ErrNotExist) { + unowned = append(unowned, fmt.Sprintf("%s is unreadable: %v", newsDir, err)) } return unowned } + +func looksLikeReleasePage(name string) bool { + base, ok := strings.CutSuffix(name, ".md") + return ok && releasePageName.MatchString(base) +} diff --git a/tools/newsgen/main_test.go b/tools/newsgen/main_test.go index 9c02787b6..bec4d18c9 100644 --- a/tools/newsgen/main_test.go +++ b/tools/newsgen/main_test.go @@ -7,29 +7,19 @@ import ( "testing" ) -const archiedFixture = `# archied changelog +const changelogFixture = `# Changelog ## [1.31.0] - 2026-09-22 +### archied — Gateway + - gateway bullet ` -const archieFixture = `# archie-agent changelog - -## [1.31.0] - 2026-09-22 - -- runtime bullet -` - -func writeChangelogs(t *testing.T, root, archied, archie string) { +func writeChangelog(t *testing.T, root, body string) { t.Helper() - for name, body := range map[string]string{ - "CHANGELOG.archied.md": archied, - "CHANGELOG.archie.md": archie, - } { - if err := os.WriteFile(filepath.Join(root, name), []byte(body), 0o644); err != nil { - t.Fatalf("write %s: %v", name, err) - } + if err := os.WriteFile(filepath.Join(root, changelogPath), []byte(body), 0o644); err != nil { + t.Fatalf("write %s: %v", changelogPath, err) } } @@ -44,7 +34,7 @@ func readFile(t *testing.T, root, name string) []byte { func TestWriteThenCheckIsClean(t *testing.T) { root := t.TempDir() - writeChangelogs(t, root, archiedFixture, archieFixture) + writeChangelog(t, root, changelogFixture) if err := write(root); err != nil { t.Fatalf("write error = %v", err) @@ -56,7 +46,7 @@ func TestWriteThenCheckIsClean(t *testing.T) { func TestWriteIsIdempotent(t *testing.T) { root := t.TempDir() - writeChangelogs(t, root, archiedFixture, archieFixture) + writeChangelog(t, root, changelogFixture) if err := write(root); err != nil { t.Fatalf("first write error = %v", err) @@ -72,48 +62,72 @@ func TestWriteIsIdempotent(t *testing.T) { func TestCheckReportsAStaleChangelog(t *testing.T) { root := t.TempDir() - writeChangelogs(t, root, archiedFixture, archieFixture) + writeChangelog(t, root, changelogFixture) if err := write(root); err != nil { t.Fatalf("write error = %v", err) } - writeChangelogs(t, root, archiedFixture+"\n## [1.32.0] - 2026-09-23\n\n- newer bullet\n", archieFixture) + writeChangelog(t, root, changelogFixture+"\n## [1.32.0] - 2026-09-23\n\n- newer bullet\n") err := check(root) if err == nil { t.Fatal("check accepted a committed tree that lags the changelog") } - for _, want := range []string{"task news", "docs/news/archied/1.32.0.md"} { + for _, want := range []string{"task news", "docs/news/1.32.0.md"} { if !strings.Contains(err.Error(), want) { t.Fatalf("error = %q, want it to mention %q", err, want) } } } -func TestCheckReportsFilesItDoesNotOwn(t *testing.T) { +func TestCheckReportsAStaleVersionPage(t *testing.T) { root := t.TempDir() - writeChangelogs(t, root, archiedFixture, archieFixture) + writeChangelog(t, root, changelogFixture) if err := write(root); err != nil { t.Fatalf("write error = %v", err) } - handwritten := filepath.Join(root, "docs", "news", "archied", "handwritten.md") - if err := os.WriteFile(handwritten, []byte("mine\n"), 0o644); err != nil { - t.Fatalf("write handwritten page: %v", err) + stale := filepath.Join(root, "docs", "news", "9.9.9.md") + if err := os.WriteFile(stale, []byte("gone from the changelog\n"), 0o644); err != nil { + t.Fatalf("write stale page: %v", err) } err := check(root) if err == nil { - t.Fatal("check ignored a file in a generated directory") + t.Fatal("check ignored a page for a version the changelog does not carry") } - if !strings.Contains(err.Error(), "handwritten.md") || !strings.Contains(err.Error(), "not generated") { - t.Fatalf("error = %q, want it to name the unmanaged page", err) + if !strings.Contains(err.Error(), "9.9.9.md") || !strings.Contains(err.Error(), "not generated") { + t.Fatalf("error = %q, want it to name the stale page", err) + } +} + +func TestCheckReportsTheRetiredComponentLayout(t *testing.T) { + root := t.TempDir() + writeChangelog(t, root, changelogFixture) + if err := write(root); err != nil { + t.Fatalf("write error = %v", err) + } + + retired := filepath.Join(root, "docs", "news", "archied", "1.31.0.md") + if err := os.MkdirAll(filepath.Dir(retired), 0o755); err != nil { + t.Fatalf("create retired directory: %v", err) + } + if err := os.WriteFile(retired, []byte("old layout\n"), 0o644); err != nil { + t.Fatalf("write retired page: %v", err) + } + + err := check(root) + if err == nil { + t.Fatal("check ignored a page left in the retired per-component layout") + } + if !strings.Contains(err.Error(), "archied/1.31.0.md") { + t.Fatalf("error = %q, want it to name the retired page", err) } } func TestWriteLeavesOtherNewsFilesAlone(t *testing.T) { root := t.TempDir() - writeChangelogs(t, root, archiedFixture, archieFixture) + writeChangelog(t, root, changelogFixture) if err := write(root); err != nil { t.Fatalf("write error = %v", err) } @@ -133,21 +147,22 @@ func TestWriteLeavesOtherNewsFilesAlone(t *testing.T) { } } -func TestRealChangelogsParse(t *testing.T) { +func TestRealChangelogParses(t *testing.T) { releases, err := load(filepath.Join("..", "..")) if err != nil { - t.Fatalf("load real changelogs: %v", err) + t.Fatalf("load the real changelog: %v", err) } - seen := map[string]int{} + if len(releases) == 0 { + t.Fatal("the real changelog produced no releases") + } + seen := map[string]bool{} for _, r := range releases { - seen[r.Component]++ if r.Version == "" || r.Date == "" || r.Body == "" { t.Fatalf("incomplete release: %+v", r) } - } - for _, c := range components { - if seen[c.key] == 0 { - t.Fatalf("%s produced no releases", c.changelog) + if seen[r.Version] { + t.Fatalf("version %s appears twice in the merged history", r.Version) } + seen[r.Version] = true } } diff --git a/tools/newsgen/render.go b/tools/newsgen/render.go index 7f4606b81..b722aa638 100644 --- a/tools/newsgen/render.go +++ b/tools/newsgen/render.go @@ -12,9 +12,21 @@ import ( // owns end-to-end, so it cannot collide with another generator's output. const releasesJSONPath = "docs/news/releases.json" +// redirectsJSONPath is the redirect table. The per-component pages were retired, +// so every `/news///` URL published before the merge is +// mapped to the unified page for that version. It is generated beside the pages +// for the same reason they are: a hand-kept list would drift from them. +const redirectsJSONPath = "docs/news/redirects.json" + // newsDir is where the MkDocs adapter writes the news index and its pages. const newsDir = "docs/news" +// legacyComponentDirs are the URL namespaces the per-component pages used. Both +// are mapped for every version rather than only the component that released it, +// so a published URL resolves whether or not that component ever carried that +// version, and the table is derived from the version set instead of a list. +var legacyComponentDirs = []string{"archied", "archie"} + // render returns every generated file keyed by repo-relative path. It is pure: // the same releases always produce the same bytes, so the write path can skip a // file that is already current. @@ -26,12 +38,17 @@ func render(releases []release) (map[string][]byte, error) { if err != nil { return nil, err } + redirects, err := encodeRedirects(releases) + if err != nil { + return nil, err + } files := map[string][]byte{ releasesJSONPath: canonical, + redirectsJSONPath: redirects, newsDir + "/index.md": renderIndex(releases), } for _, r := range releases { - files[fmt.Sprintf("%s/%s/%s.md", newsDir, r.Component, r.Version)] = renderRelease(r) + files[fmt.Sprintf("%s/%s.md", newsDir, r.Version)] = renderRelease(r) } return files, nil } @@ -40,12 +57,28 @@ func render(releases []release) (map[string][]byte, error) { // the artifact stays readable to a reviewer and to a non-Go consumer: the // changelogs write `->` and ``, not `\u003e` and `\u003cmemory\u003e`. func encodeCanonical(releases []release) ([]byte, error) { + return encodeJSON(releasesJSONPath, releases) +} + +// encodeRedirects writes the old-URL to new-URL table. encoding/json orders map +// keys, so the artifact is deterministic. +func encodeRedirects(releases []release) ([]byte, error) { + table := map[string]string{} + for _, r := range releases { + for _, component := range legacyComponentDirs { + table[fmt.Sprintf("/news/%s/%s/", component, r.Version)] = fmt.Sprintf("/news/%s/", r.Version) + } + } + return encodeJSON(redirectsJSONPath, table) +} + +func encodeJSON(path string, value any) ([]byte, error) { var buf bytes.Buffer encoder := json.NewEncoder(&buf) encoder.SetEscapeHTML(false) encoder.SetIndent("", " ") - if err := encoder.Encode(releases); err != nil { - return nil, fmt.Errorf("encode %s: %w", releasesJSONPath, err) + if err := encoder.Encode(value); err != nil { + return nil, fmt.Errorf("encode %s: %w", path, err) } return buf.Bytes(), nil } @@ -54,24 +87,24 @@ func encodeCanonical(releases []release) ([]byte, error) { func renderIndex(releases []release) []byte { var b strings.Builder b.WriteString("# News\n\n") - b.WriteString("Release notes for archied and archie-agent, newest first.\n") + b.WriteString("Release notes, newest first.\n") lastDate := "" for _, r := range releases { if r.Date != lastDate { fmt.Fprintf(&b, "\n## %s\n\n", r.Date) lastDate = r.Date } - fmt.Fprintf(&b, "- [%s %s](%s/%s.md)\n", r.Name, r.Version, r.Component, r.Version) + fmt.Fprintf(&b, "- [%s](%s.md)\n", r.Version, r.Version) } return []byte(b.String()) } // renderRelease is one version's page: the facts, and the changelog body -// verbatim. +// verbatim, which carries that release's per-component sections. func renderRelease(r release) []byte { var b strings.Builder - fmt.Fprintf(&b, "# %s %s\n\n", r.Name, r.Version) - fmt.Fprintf(&b, "Released %s. [All news](../index.md)\n\n", r.Date) + fmt.Fprintf(&b, "# %s\n\n", r.Version) + fmt.Fprintf(&b, "Released %s. [All news](index.md)\n\n", r.Date) b.WriteString(r.Body) b.WriteString("\n") return []byte(b.String()) diff --git a/tools/newsgen/render_test.go b/tools/newsgen/render_test.go index ac72ce0d6..db6e3668e 100644 --- a/tools/newsgen/render_test.go +++ b/tools/newsgen/render_test.go @@ -9,9 +9,8 @@ import ( func sampleReleases() []release { return []release{ - {Component: "archied", Name: "archied", Version: "1.31.0", Date: "2026-09-22", Body: "### Gateway\n\n- a bullet"}, - {Component: "archie", Name: "archie-agent", Version: "1.31.0", Date: "2026-09-22", Body: "- a runtime bullet"}, - {Component: "archied", Name: "archied", Version: "1.30.0", Date: "2026-09-20", Body: "Prose."}, + {Version: "1.31.0", Date: "2026-09-22", Body: "### archied — Gateway\n\n- a bullet\n\n### archie-agent\n\n- a runtime bullet"}, + {Version: "1.30.0", Date: "2026-09-20", Body: "Prose."}, } } @@ -35,7 +34,7 @@ func TestRenderEmitsTheCanonicalJSON(t *testing.T) { func TestRenderJSONKeepsHTMLCharactersReadable(t *testing.T) { releases := []release{{ - Component: "archied", Name: "archied", Version: "1.0.0", Date: "2026-01-01", + Version: "1.0.0", Date: "2026-01-01", Body: "a -> b and ", }} files, err := render(releases) @@ -50,16 +49,17 @@ func TestRenderJSONKeepsHTMLCharactersReadable(t *testing.T) { } } -func TestRenderWritesOnePagePerComponentVersion(t *testing.T) { +func TestRenderWritesOnePagePerVersion(t *testing.T) { files, err := render(sampleReleases()) if err != nil { t.Fatalf("render error = %v", err) } for _, path := range []string{ "docs/news/index.md", - "docs/news/archied/1.31.0.md", - "docs/news/archie/1.31.0.md", - "docs/news/archied/1.30.0.md", + "docs/news/1.31.0.md", + "docs/news/1.30.0.md", + "docs/news/releases.json", + "docs/news/redirects.json", } { if _, ok := files[path]; !ok { t.Fatalf("render did not produce %s (files: %v)", path, keys(files)) @@ -70,6 +70,26 @@ func TestRenderWritesOnePagePerComponentVersion(t *testing.T) { } } +func TestRenderRedirectsEveryRetiredComponentURL(t *testing.T) { + files, err := render(sampleReleases()) + if err != nil { + t.Fatalf("render error = %v", err) + } + var table map[string]string + if err := json.Unmarshal(files[redirectsJSONPath], &table); err != nil { + t.Fatalf("redirect table does not decode: %v", err) + } + want := map[string]string{ + "/news/archied/1.31.0/": "/news/1.31.0/", + "/news/archie/1.31.0/": "/news/1.31.0/", + "/news/archied/1.30.0/": "/news/1.30.0/", + "/news/archie/1.30.0/": "/news/1.30.0/", + } + if !reflect.DeepEqual(table, want) { + t.Fatalf("redirect table = %v, want %v", table, want) + } +} + func TestRenderIndexGroupsByDate(t *testing.T) { files, err := render(sampleReleases()) if err != nil { @@ -77,16 +97,15 @@ func TestRenderIndexGroupsByDate(t *testing.T) { } want := `# News -Release notes for archied and archie-agent, newest first. +Release notes, newest first. ## 2026-09-22 -- [archied 1.31.0](archied/1.31.0.md) -- [archie-agent 1.31.0](archie/1.31.0.md) +- [1.31.0](1.31.0.md) ## 2026-09-20 -- [archied 1.30.0](archied/1.30.0.md) +- [1.30.0](1.30.0.md) ` if got := string(files["docs/news/index.md"]); got != want { t.Fatalf("index markdown =\n%s\nwant\n%s", got, want) @@ -98,13 +117,19 @@ func TestRenderReleasePageKeepsTheBodyVerbatim(t *testing.T) { if err != nil { t.Fatalf("render error = %v", err) } - want := `# archie-agent 1.31.0 + want := `# 1.31.0 -Released 2026-09-22. [All news](../index.md) +Released 2026-09-22. [All news](index.md) + +### archied — Gateway + +- a bullet + +### archie-agent - a runtime bullet ` - if got := string(files["docs/news/archie/1.31.0.md"]); got != want { + if got := string(files["docs/news/1.31.0.md"]); got != want { t.Fatalf("release page =\n%s\nwant\n%s", got, want) } } @@ -131,7 +156,10 @@ func TestRenderHandlesNoReleases(t *testing.T) { if got := string(files[releasesJSONPath]); got != "[]\n" { t.Fatalf("empty canonical JSON = %q, want %q", got, "[]\n") } - if got := string(files["docs/news/index.md"]); got != "# News\n\nRelease notes for archied and archie-agent, newest first.\n" { + if got := string(files[redirectsJSONPath]); got != "{}\n" { + t.Fatalf("empty redirect table = %q, want %q", got, "{}\n") + } + if got := string(files["docs/news/index.md"]); got != "# News\n\nRelease notes, newest first.\n" { t.Fatalf("empty index = %q", got) } } diff --git a/tools/release.sh b/tools/release.sh index c0d524866..07010293b 100755 --- a/tools/release.sh +++ b/tools/release.sh @@ -3,26 +3,25 @@ # they are frozen into a tag -- the same review window release-please gives # you with its release PR. # -# tools/release.sh --gateway 1.2.0 --runtime 1.2.0 --dry-run # preview -# tools/release.sh --gateway 1.2.0 --runtime 1.2.0 --prepare # write, then edit -# tools/release.sh --gateway 1.2.0 --runtime 1.2.0 --tag # commit + tag +# tools/release.sh --version 1.2.0 --dry-run # preview +# tools/release.sh --version 1.2.0 --prepare # write, then edit +# tools/release.sh --version 1.2.0 --tag # commit + tag # -# archied and archie-agent are independently versioned (see CHANGELOG.md), -# so each gets its own version, tag and changelog. Pass "skip" for a -# component that is not moving this release. +# There is one release stream: CHANGELOG.md carries every release section, +# one generated page per version, and one tag names the release. A release is +# one version covering whatever changed; per-component detail is a labelled +# section inside it, not a separate number. # -# Which commits land in which changelog is decided by the binary's actual -# package closure (go list -deps), not by guessing from the commit subject: -# a change to a package archied does not import cannot appear in archied's -# changelog. Commits touching neither closure (docs, CI, deployment) are -# left out of both. +# Exit codes: 0 released (or previewed/prepared); 1 failure; 3 nothing to +# release -- a commit set that justifies no version is a result, not an error, +# so a pipeline can finish green without tagging. set -euo pipefail cd "$(dirname "$0")/.." +NOTHING_TO_RELEASE=3 MODE="" -GATEWAY_VERSION="" -RUNTIME_VERSION="" +VERSION="" die() { echo "release: $*" >&2 @@ -31,8 +30,7 @@ die() { while [ $# -gt 0 ]; do case "$1" in - --gateway) GATEWAY_VERSION="${2:-}"; shift 2 ;; - --runtime) RUNTIME_VERSION="${2:-}"; shift 2 ;; + --version) VERSION="${2:-}"; shift 2 ;; --dry-run) MODE="dry-run"; shift ;; --prepare) MODE="prepare"; shift ;; --tag) MODE="tag"; shift ;; @@ -40,8 +38,7 @@ while [ $# -gt 0 ]; do esac done -[ -n "$GATEWAY_VERSION" ] || die "--gateway is required" -[ -n "$RUNTIME_VERSION" ] || die "--runtime is required" +[ -n "$VERSION" ] || die "--version is required" [ -n "$MODE" ] || die "one of --dry-run, --prepare or --tag is required" if [ "$MODE" != "dry-run" ]; then @@ -60,36 +57,6 @@ component_dirs() { sed "s|^$PWD/||" } -# section ... -- changelog body for the -# commits since 's last tag that touched this component. -section() { - local prefix="$1" cmd="$2" - shift 2 - local last range dirs - last="$(git tag --list "$prefix/v*" | sort -V | tail -1)" - range="HEAD" - if [ -n "$last" ]; then - range="$last..HEAD" - fi - - dirs="$(component_dirs "$cmd")"$'\n'"$(printf '%s\n' "$@")" - - local sha subject files - while read -r sha; do - [ -n "$sha" ] || continue - subject="$(git log -1 --pretty=%s "$sha")" - # Conventional commits only; release commits are not news. - case "$subject" in - feat:* | feat\(*|fix:* | fix\(*|perf:* | perf\(*|refactor:* | refactor\(*) ;; - *) continue ;; - esac - files="$(git show --pretty=format: --name-only "$sha")" - if matches "$files" "$dirs"; then - echo "- $subject" - fi - done < <(git log --no-merges --pretty=%H --reverse "$range") -} - # matches -- true when any changed file lives in one # of the component's directories. matches() { @@ -107,71 +74,95 @@ matches() { return 1 } -# prepend -- insert a dated section directly -# under the file's title. +# The host bundle IS the archied artifact: the distribution zip is named and +# versioned by the release, and every process it ships carries that version. +# The paths below are named rather than whole directories, so a packaging-only +# change is attributed to archied deliberately and not every CI or script edit. +archied_dirs() { + component_dirs ./cmd/archied + printf '%s\n' "cmd/archied" "Dockerfile.archied" "cmd/archie-ui" "internal/app/archieui" \ + "Taskfile.yml" ".github/workflows/deploy.yml" "install.sh" \ + "scripts/archie-update-install" "scripts/archie-update-check" \ + "scripts/archie-update-watchdog" "deployments/INSTRUCTIONS.md" +} + +# The UI Service ships with the archied release on purpose (archie-ui shares +# internal/webui with archied), hence archied_dirs' extra paths above. +runtime_dirs() { + component_dirs ./cmd/archie-agent + printf '%s\n' "cmd/archie-agent" "Dockerfile" +} + +# changelog_body -- labelled per-component sections for every releasable commit +# since the last release. Empty output means nothing to release: a commit set +# that justifies no version produces no body, and the caller reports that +# rather than inventing one. +changelog_body() { + local last range archied runtime + last="$(git describe --tags --abbrev=0 2>/dev/null || true)" + range="HEAD" + if [ -n "$last" ]; then + range="$last..HEAD" + fi + archied="$(archied_dirs)" + runtime="$(runtime_dirs)" + + local sha subject files in_archied="" in_runtime="" + while read -r sha; do + [ -n "$sha" ] || continue + subject="$(git log -1 --pretty=%s "$sha")" + # Conventional commits only; release commits are not news. + case "$subject" in + feat:* | feat\(*|fix:* | fix\(*|perf:* | perf\(*|refactor:* | refactor\(*) ;; + *) continue ;; + esac + files="$(git show --pretty=format: --name-only "$sha")" + if matches "$files" "$archied"; then + in_archied="$in_archied- $subject"$'\n' + fi + if matches "$files" "$runtime"; then + in_runtime="$in_runtime- $subject"$'\n' + fi + done < <(git log --no-merges --pretty=%H --reverse "$range") + + if [ -n "$in_archied" ]; then + printf '### archied\n\n%s\n' "$in_archied" + fi + if [ -n "$in_runtime" ]; then + printf '### archie-agent\n\n%s\n' "$in_runtime" + fi +} + +# prepend -- insert the new section after the title and +# any [Unreleased] block, which stays at the top, and above every release. prepend() { - local file="$1" version="$2" body="$3" tmp + local version="$1" bodyfile="$2" tmp line + line="$(grep -n '^## \[' CHANGELOG.md | grep -v '## \[Unreleased\]' | head -1 | cut -d: -f1)" + if [ -z "$line" ]; then + line="$(($(wc -l "$tmp" - # Collapse the blank-line run left where the old body started. - awk 'BEGIN{blank=0} /^$/{blank++; if(blank>1) next} !/^$/{blank=0} {print}' "$tmp" >"$file" - rm -f "$tmp" + mv "$tmp" CHANGELOG.md } -release_component() { - local name="$1" version="$2" prefix="$3" changelog="$4" cmd="$5" - shift 5 - if [ "$version" = "skip" ]; then - echo "==> $name: skipped" - return - fi - local body - body="$(section "$prefix" "$cmd" "$@")" - if [ -z "$body" ]; then - body="- chore: no user-facing changes" - fi - echo "==> $name $version ($prefix/v$version)" - echo "$body" | sed 's/^/ /' - if [ "$MODE" = "prepare" ]; then - prepend "$changelog" "$version" "$body" - fi -} +body="$(changelog_body)" -# The host bundle IS the archied artifact: the distribution zip is named and -# versioned by the archied tag, and every process it ships carries that same -# version. So the inputs that decide what a host install contains belong in -# archied's closure -- the build task, the packaging workflow, the installer, -# the updater scripts it ships, and the instructions packed into the zip. -# Without them a change to packaging or the installer closes over no -# component at all, so the standing rule says "skip both" and the fix cannot -# be released by the mechanism it repairs (archie-core-12rp). Each path is -# named rather than its whole directory, so a packaging-only change is -# attributed to archied deliberately and not every CI or script edit is. -release_component "archied" "$GATEWAY_VERSION" "archied" \ - "CHANGELOG.archied.md" "./cmd/archied" "cmd/archied" "Dockerfile.archied" \ - "cmd/archie-ui" "internal/app/archieui" \ - "Taskfile.yml" ".github/workflows/deploy.yml" "install.sh" \ - "scripts/archie-update-install" "scripts/archie-update-check" \ - "scripts/archie-update-watchdog" "deployments/INSTRUCTIONS.md" +if [ -z "$body" ]; then + last="$(git describe --tags --abbrev=0 2>/dev/null || echo 'the beginning')" + echo "nothing to release: no releasable commits since $last" >&2 + exit "$NOTHING_TO_RELEASE" +fi -# The UI Service ships with the archied release on purpose: archie-ui shares -# internal/webui (the dashboard HTTP layer and the embedded SPA assets) with -# archied, so the two are versioned together -- an archied/vX.Y.Z tag carries -# the dashboard and the daemon that publishes its configuration snapshot. -# The two lines above extend archied's component closure with archie-ui's -# own packages, so a commit touching only archieui cannot fall between -# changelogs; it would otherwise land in neither (go list -deps from -# ./cmd/archied does not include internal/app/archieui). - -release_component "archie-agent" "$RUNTIME_VERSION" "archie" \ - "CHANGELOG.archie.md" "./cmd/archie-agent" "cmd/archie-agent" "Dockerfile" +echo "==> release $VERSION" +echo "$body" | sed 's/^/ /' if [ "$MODE" = "dry-run" ]; then echo @@ -179,50 +170,37 @@ if [ "$MODE" = "dry-run" ]; then exit 0 fi +bodyfile="$(mktemp)" +printf '%s\n' "$body" >"$bodyfile" + if [ "$MODE" = "prepare" ]; then + prepend "$VERSION" "$bodyfile" + rm -f "$bodyfile" echo - echo "changelogs updated and left uncommitted. Edit them -- generated notes" - echo "are a starting point, not the release -- then freeze them with:" + echo "CHANGELOG.md updated and left uncommitted. Edit it -- generated notes" + echo "are a starting point, not the release -- then freeze it with:" echo - echo " tools/release.sh --gateway $GATEWAY_VERSION --runtime $RUNTIME_VERSION --tag" + echo " tools/release.sh --version $VERSION --tag" exit 0 fi # --tag: the changelog must already describe this release. -[ "$GATEWAY_VERSION" = "skip" ] || grep -q "^## \\[$GATEWAY_VERSION\\]" CHANGELOG.archied.md || - die "CHANGELOG.archied.md has no [$GATEWAY_VERSION] section; run --prepare first" -[ "$RUNTIME_VERSION" = "skip" ] || grep -q "^## \\[$RUNTIME_VERSION\\]" CHANGELOG.archie.md || - die "CHANGELOG.archie.md has no [$RUNTIME_VERSION] section; run --prepare first" +grep -q "^## \\[$VERSION\\]" CHANGELOG.md || + die "CHANGELOG.md has no [$VERSION] section; run --prepare first" -# The published release notes are derived from the changelogs, so regenerate +# The published release notes are derived from the changelog, so regenerate # them after the maintainer's edit and ship them in the same commit as the -# sections they describe. newsgen skips a file whose bytes already match, so a +# section they describe. newsgen skips a file whose bytes already match, so a # re-run leaves the tree clean. go -C tools run -mod=readonly ./newsgen --repo-root .. -# Plain `[ cond ] && cmd` would abort the script under set -e whenever cond -# is false, i.e. whenever a component is skipped. -msg="chore(release):" -if [ "$GATEWAY_VERSION" != "skip" ]; then - msg="$msg archied v$GATEWAY_VERSION" -fi -if [ "$RUNTIME_VERSION" != "skip" ]; then - msg="$msg archie v$RUNTIME_VERSION" -fi - -git add CHANGELOG.archied.md CHANGELOG.archie.md docs/news -git commit -m "$msg" - -if [ "$GATEWAY_VERSION" != "skip" ]; then - git tag -a "archied/v$GATEWAY_VERSION" -m "archied v$GATEWAY_VERSION" -fi -if [ "$RUNTIME_VERSION" != "skip" ]; then - git tag -a "archie/v$RUNTIME_VERSION" -m "archie-agent v$RUNTIME_VERSION" -fi +git add CHANGELOG.md docs/news +git commit -m "chore(release): v$VERSION" +git tag -a "v$VERSION" -m "v$VERSION" echo echo "tagged. push with:" echo " git push origin main --follow-tags" echo echo "The deploy workflow reads the tags pointing at HEAD, so pushing the" -echo "commit without its tags builds images stamped 'dev'." +echo "commit without its tag builds images stamped 'dev'."