Files
archie/docs/news/archied/1.28.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.28.0

Released 2026-09-19. All news

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.