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/<version>.md`, the index, the
  canonical `releases.json`, and `docs/news/redirects.json`. The redirect table
  is what keeps the retired `/news/<component>/<version>/` 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.
This commit is contained in:
sam committed 2026-09-22 17:18:06 +10:00
1 parent 80775676eb
commit 0b408017e0
134 files changed
+3189 -3241

No files matched your search

@@ -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
`## [<version>]`, and `.github/workflows/deploy.yml` gates each release tag with
`grep -q "^## \[$ver\]" CHANGELOG.<component>.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
+19 -18
View File
@@ -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
-431
View File
@@ -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
-1276
View File
File diff suppressed because it is too large. Load diff
+1812 -7
View File
File diff suppressed because it is too large. Load diff
+17 -14
View File
@@ -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/<component>/<version>/ 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/<component>/ 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/<component>/ 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]
+1 -1
View File
@@ -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. |
+2 -2
View File
@@ -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 chaLine truncated
"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 chaLine truncated
},
{
"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 rightLine truncated
"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 frLine truncated
},
{
"url": "/dev/prds/review-calibration/",
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
+7
View File
@@ -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
@@ -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
@@ -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;
@@ -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
+7
View File
@@ -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
@@ -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.
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
+11
View File
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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)
@@ -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
@@ -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
@@ -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
@@ -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.
@@ -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.
@@ -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`.
@@ -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`).
@@ -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
+7
View File
@@ -0,0 +1,7 @@
# 1.3.1
Released 2026-07-31. [All news](index.md)
### archied
- fix(telegram): omit empty model picker markup
@@ -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).
@@ -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.
@@ -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.<id>` 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,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.
@@ -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
@@ -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
@@ -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.
@@ -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`
@@ -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-<commit>` tag is published alongside `:latest`, and a build with no release tag is stamped
`dev+<short sha>` 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
@@ -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
+7
View File
@@ -0,0 +1,7 @@
# 1.4.1
Released 2026-07-31. [All news](index.md)
### archied
- fix(catalog): match SDK provider fallback
@@ -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
@@ -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
@@ -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
@@ -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
+20
View File
@@ -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
@@ -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
@@ -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
+7
View File
@@ -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
+11
View File
@@ -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
+15
View File
@@ -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
+12
View File
@@ -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
@@ -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
+11
View File
@@ -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
+11
View File
@@ -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
+11
View File
@@ -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
+11
View File
@@ -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
-6
View File
@@ -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
-12
View File
@@ -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
-5
View File
@@ -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
-6
View File
@@ -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
-19
View File
@@ -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
-5
View File
@@ -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
-5
View File
@@ -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
-25
View File
@@ -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
-13
View File
@@ -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
-14
View File
@@ -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
-35
View File
@@ -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
-6
View File
@@ -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
-47
View File
@@ -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.
-7
View File
@@ -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.
-20
View File
@@ -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`.
-11
View File
@@ -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`).
-20
View File
@@ -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).
-29
View File
@@ -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.
-13
View File
@@ -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.
-13
View File
@@ -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.
-10
View File
@@ -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
-5
View File
@@ -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
-5
View File
@@ -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
-7
View File
@@ -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
-5
View File
@@ -1,5 +0,0 @@
# archie-agent 1.9.4
Released 2026-08-15. [All news](../index.md)
- chore: no user-facing changes
-7
View File
@@ -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
-5
View File
@@ -1,5 +0,0 @@
# archie-agent 1.9.6
Released 2026-08-16. [All news](../index.md)
- chore: no user-facing changes
Loaded 100 of 134 files, more files were not shown because too many files have changed in this diff. Show more