Files
archie/docs/news/archied/1.29.0.md
T
sam 83e9c33282 feat(docs): publish generated news and per-version release notes
Derive a public news page and one release-notes page per component version
from CHANGELOG.archied.md and CHANGELOG.archie.md, the notes the release
process already freezes.

- tools/newsgen writes docs/news/releases.json, the canonical artifact a host
  renders from, plus the MkDocs pages. Check mode fails when the committed
  files lag a changelog edit, and runs in task check; tools/release.sh --tag
  regenerates and stages them in the release commit, skipping files already
  current.
- mkdocs.yml keeps the version pages out of the derived navigation without
  excluding them from the site.
2026-09-22 05:03:29 +10:00

2.6 KiB

archied 1.29.0

Released 2026-09-19. All news

Security

  • google.golang.org/grpc bumped past v1.84.0 to patch 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 <memory> 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).