chore(release): archied v1.35.0 archie v1.35.0
This commit is contained in:
6 files changed
+138
No files matched your search
@@ -1,5 +1,17 @@
|
||||
# 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
|
||||
|
||||
@@ -1,5 +1,53 @@
|
||||
# archied changelog
|
||||
|
||||
## [1.35.0] - 2026-09-22
|
||||
|
||||
### The Messaging Service is severed from the store and workflow runtime
|
||||
|
||||
- `cmd/archie-messaging` no longer links `modernc.org/sqlite`, `internal/store`,
|
||||
`internal/domain/workflow` or `internal/agentexec`. All four arrived through a single import of
|
||||
`internal/app/controlplane`; the client half now lives in
|
||||
`internal/infrastructure/controlplanerpc`, and the app package keeps the server, the registry, the
|
||||
seeds, the validators and the schema derivation.
|
||||
- **The PRD's guard now exists, and passes:** `cmd/archie-messaging/architecture_test.go` measures the
|
||||
linked binary against the banned list, with `internal/domain/workflow/task` as an exception checked
|
||||
in both directions. Before this the guard had never been written -- because it failed. A messaging
|
||||
process linking a SQLite driver and the workflow engine is a severance hole, not a design choice.
|
||||
- The resource documents are type-aliased back into the app package, so there is one definition read
|
||||
under two names rather than a copy per side.
|
||||
|
||||
### Channel lifecycle reaches the dashboard
|
||||
|
||||
- The Messaging Service reports each channel's state, recorded **per channel**: one channel's failure
|
||||
marks only itself, a channel that cannot start is marked failed **with its reason** rather than only
|
||||
logged, and one that returns is marked stopped. `internal/channels/status.Manager` finally has a
|
||||
production writer.
|
||||
- `PutChannelStatus`/`ListChannelStatus` carry that to the dashboard, following the config-snapshot
|
||||
split. The store **replaces the reported set**, so a channel the reporter stops mentioning is
|
||||
deleted rather than left as a stale `running`; an empty report clears the table, because hosting no
|
||||
channels is a fact worth reporting; and an id-less row is refused, since it could never be replaced
|
||||
or removed by a later report.
|
||||
- `Service.ReloadChannel` routes to the channel's own seam and refuses a channel that cannot reload
|
||||
with a reason rather than accepting and ignoring it. `ReloadSupported` was previously declared **by
|
||||
name**, so a channel could advertise reload with nothing behind it; one function now decides both.
|
||||
|
||||
### Action playbooks: a second playbook shape, with typed results
|
||||
|
||||
- A playbook is now one of two shapes: a **workflow playbook** (exactly one `workflow` action,
|
||||
unchanged) or an **action playbook** (one or more `module` actions in order). A playbook does not
|
||||
mix them.
|
||||
- `args` and `when` share one compilation path and one evaluation context, and `actions.<id>` is typed
|
||||
by the kind that action runs, so a misspelled result field, an unknown id, a map index, `in`, a
|
||||
comprehension, or a shape-foreign key (`kind` on a `workflow` action, `workflow` on a `module`
|
||||
action) is a **load failure** rather than a dispatch failure.
|
||||
- **Action playbooks load but do not run yet.** Routing arrives with the first side-effecting
|
||||
position; the daemon warns at load rather than accepting them silently.
|
||||
- The CEL environment is built per playbook, because result typing depends on the ids a playbook
|
||||
declares.
|
||||
- `ModuleRegistry.DecodeResult` turns a kind's flat map result into its typed `Result` before a later
|
||||
expression reads it. Without it a typed read evaluated against a shape the run never produces, and
|
||||
so silently read null.
|
||||
|
||||
## [1.34.0] - 2026-09-22
|
||||
|
||||
### Dashboard: an actionable authentication failure state
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
# 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.
|
||||
@@ -0,0 +1,49 @@
|
||||
# archied 1.35.0
|
||||
|
||||
Released 2026-09-22. [All news](../index.md)
|
||||
|
||||
### The Messaging Service is severed from the store and workflow runtime
|
||||
|
||||
- `cmd/archie-messaging` no longer links `modernc.org/sqlite`, `internal/store`,
|
||||
`internal/domain/workflow` or `internal/agentexec`. All four arrived through a single import of
|
||||
`internal/app/controlplane`; the client half now lives in
|
||||
`internal/infrastructure/controlplanerpc`, and the app package keeps the server, the registry, the
|
||||
seeds, the validators and the schema derivation.
|
||||
- **The PRD's guard now exists, and passes:** `cmd/archie-messaging/architecture_test.go` measures the
|
||||
linked binary against the banned list, with `internal/domain/workflow/task` as an exception checked
|
||||
in both directions. Before this the guard had never been written -- because it failed. A messaging
|
||||
process linking a SQLite driver and the workflow engine is a severance hole, not a design choice.
|
||||
- The resource documents are type-aliased back into the app package, so there is one definition read
|
||||
under two names rather than a copy per side.
|
||||
|
||||
### Channel lifecycle reaches the dashboard
|
||||
|
||||
- The Messaging Service reports each channel's state, recorded **per channel**: one channel's failure
|
||||
marks only itself, a channel that cannot start is marked failed **with its reason** rather than only
|
||||
logged, and one that returns is marked stopped. `internal/channels/status.Manager` finally has a
|
||||
production writer.
|
||||
- `PutChannelStatus`/`ListChannelStatus` carry that to the dashboard, following the config-snapshot
|
||||
split. The store **replaces the reported set**, so a channel the reporter stops mentioning is
|
||||
deleted rather than left as a stale `running`; an empty report clears the table, because hosting no
|
||||
channels is a fact worth reporting; and an id-less row is refused, since it could never be replaced
|
||||
or removed by a later report.
|
||||
- `Service.ReloadChannel` routes to the channel's own seam and refuses a channel that cannot reload
|
||||
with a reason rather than accepting and ignoring it. `ReloadSupported` was previously declared **by
|
||||
name**, so a channel could advertise reload with nothing behind it; one function now decides both.
|
||||
|
||||
### Action playbooks: a second playbook shape, with typed results
|
||||
|
||||
- A playbook is now one of two shapes: a **workflow playbook** (exactly one `workflow` action,
|
||||
unchanged) or an **action playbook** (one or more `module` actions in order). A playbook does not
|
||||
mix them.
|
||||
- `args` and `when` share one compilation path and one evaluation context, and `actions.<id>` is typed
|
||||
by the kind that action runs, so a misspelled result field, an unknown id, a map index, `in`, a
|
||||
comprehension, or a shape-foreign key (`kind` on a `workflow` action, `workflow` on a `module`
|
||||
action) is a **load failure** rather than a dispatch failure.
|
||||
- **Action playbooks load but do not run yet.** Routing arrives with the first side-effecting
|
||||
position; the daemon warns at load rather than accepting them silently.
|
||||
- The CEL environment is built per playbook, because result typing depends on the ids a playbook
|
||||
declares.
|
||||
- `ModuleRegistry.DecodeResult` turns a kind's flat map result into its typed `Result` before a later
|
||||
expression reads it. Without it a typed read evaluated against a shape the run never produces, and
|
||||
so silently read null.
|
||||
@@ -4,11 +4,13 @@ Release notes for archied and archie-agent, newest first.
|
||||
|
||||
## 2026-09-22
|
||||
|
||||
- [archied 1.35.0](archied/1.35.0.md)
|
||||
- [archied 1.34.0](archied/1.34.0.md)
|
||||
- [archied 1.33.0](archied/1.33.0.md)
|
||||
- [archied 1.32.1](archied/1.32.1.md)
|
||||
- [archied 1.32.0](archied/1.32.0.md)
|
||||
- [archied 1.31.0](archied/1.31.0.md)
|
||||
- [archie-agent 1.35.0](archie/1.35.0.md)
|
||||
- [archie-agent 1.32.0](archie/1.32.0.md)
|
||||
- [archie-agent 1.31.0](archie/1.31.0.md)
|
||||
|
||||
|
||||
@@ -1,4 +1,11 @@
|
||||
[
|
||||
{
|
||||
"component": "archied",
|
||||
"name": "archied",
|
||||
"version": "1.35.0",
|
||||
"date": "2026-09-22",
|
||||
"body": "### The Messaging Service is severed from the store and workflow runtime\n\n- `cmd/archie-messaging` no longer links `modernc.org/sqlite`, `internal/store`,\n `internal/domain/workflow` or `internal/agentexec`. All four arrived through a single import of\n `internal/app/controlplane`; the client half now lives in\n `internal/infrastructure/controlplanerpc`, and the app package keeps the server, the registry, the\n seeds, the validators and the schema derivation.\n- **The PRD's guard now exists, and passes:** `cmd/archie-messaging/architecture_test.go` measures the\n linked binary against the banned list, with `internal/domain/workflow/task` as an exception checked\n in both directions. Before this the guard had never been written -- because it failed. A messaging\n process linking a SQLite driver and the workflow engine is a severance hole, not a design choice.\n- The resource documents are type-aliased back into the app package, so there is one definition read\n under two names rather than a copy per side.\n\n### Channel lifecycle reaches the dashboard\n\n- The Messaging Service reports each channel's state, recorded **per channel**: one channel's failure\n marks only itself, a channel that cannot start is marked failed **with its reason** rather than only\n logged, and one that returns is marked stopped. `internal/channels/status.Manager` finally has a\n production writer.\n- `PutChannelStatus`/`ListChannelStatus` carry that to the dashboard, following the config-snapshot\n split. The store **replaces the reported set**, so a channel the reporter stops mentioning is\n deleted rather than left as a stale `running`; an empty report clears the table, because hosting no\n channels is a fact worth reporting; and an id-less row is refused, since it could never be replaced\n or removed by a later report.\n- `Service.ReloadChannel` routes to the channel's own seam and refuses a channel that cannot reload\n with a reason rather than accepting and ignoring it. `ReloadSupported` was previously declared **by\n name**, so a channel could advertise reload with nothing behind it; one function now decides both.\n\n### Action playbooks: a second playbook shape, with typed results\n\n- A playbook is now one of two shapes: a **workflow playbook** (exactly one `workflow` action,\n unchanged) or an **action playbook** (one or more `module` actions in order). A playbook does not\n mix them.\n- `args` and `when` share one compilation path and one evaluation context, and `actions.<id>` is typed\n by the kind that action runs, so a misspelled result field, an unknown id, a map index, `in`, a\n comprehension, or a shape-foreign key (`kind` on a `workflow` action, `workflow` on a `module`\n action) is a **load failure** rather than a dispatch failure.\n- **Action playbooks load but do not run yet.** Routing arrives with the first side-effecting\n position; the daemon warns at load rather than accepting them silently.\n- The CEL environment is built per playbook, because result typing depends on the ids a playbook\n declares.\n- `ModuleRegistry.DecodeResult` turns a kind's flat map result into its typed `Result` before a later\n expression reads it. Without it a typed read evaluated against a shape the run never produces, and\n so silently read null."
|
||||
},
|
||||
{
|
||||
"component": "archied",
|
||||
"name": "archied",
|
||||
@@ -34,6 +41,13 @@
|
||||
"date": "2026-09-22",
|
||||
"body": "### Dashboard replaced: Preact -> Vue 3 + shadcn-vue\n\nThe dashboard is now a Vue 3 application built on shadcn-vue. This is the\nlarge piece of this release; it touches every page.\n\n- History routing, a grouped topbar built from components, the violet palette\n with self-hosted Geist, and a command palette with live tasks.\n- Chat is a FAB-opened panel that behaves like a chat window and scrolls its\n transcript with `MessageScroller`.\n- Task actions and dangerous approvals are deliberate; the task detail page is\n a single head strip with honest states; the run page settles its head around\n an attempts pager, which is hidden for zero or one attempt.\n- Appearance and System navigation were refined, with a four-column appearance\n grid on wide screens.\n- A copy pass removed redundant tails and restating descriptions, empty states\n derive their own titles, and a stuck log read surfaces as an error rather\n than eternal loading.\n- The capture pane is bound to the list it sits beside and reads beside it,\n not over it.\n\n### Events is one page with three tabs\n\n- Inspector, Bindings and Mappings are now tabs of a single **Events** page.\n- The nav entry is always live, the tabs prune by capability, and the three old\n paths survive as bookmarks that redirect to their tab.\n- Tab selection lives in one module (`ui/src/events/tab-selection.ts`) that the\n page uses, rather than a copy of it.\n- `feat(tools)`: a capture-intake sender exists for exercising the Events\n surfaces.\n\n### The channel travels with the message\n\n`SessionSource.Platform` -- the first component of the session natural key, and\nthe column `GetByChannel` filters on -- was a constant `\"web\"`, because one\nRouter serves every channel and named itself after its own. Two things followed:\nthe per-user identity policy was real code that no production call site reached\nwith a real channel name, and a curator pass's write to agent-user memory could\nnot be read back by the turn that wrote it, because that turn resolved no\n`UserID`.\n\n- The frontends now name the channel they carry (`telegram`, `email`,\n `webhook`, `web`), the channel rides the message, and the Gateway stamps the\n session from it -- falling back to its own name when a sender names none,\n which is what every existing row holds.\n- Identity resolution reads the platform off the inbound, so `carriesPersonIdentity`\n decides something in production: telegram and email resolve a person, the\n dashboard and a webhook resolve nothing, and an unknown platform fails closed.\n- **Behaviour change:** a chat whose active session came from `/new` or\n `/branch` re-resolves once, because session lookup now filters on the\n channel's real name. A chat without `/new` re-resolves onto the same\n deterministic id and heals silently.\n- Deliberately unchanged: `TurnRunnerConfig.Channel` still keys tool\n availability, so no channel gains or loses a tool in this release.\n\n### Control plane: runtime administration, history, and derived schemas\n\n- The State Store's gRPC server now carries runtime administration, and each\n process reports which settings version it is running; the dashboard shows it.\n- Resource history is exposed so edits can be reviewed and rolled back, and\n resource schemas are derived from the documents they describe -- the document\n editor reads the derived schema (labels from `title`, `format: duration` ->\n `1m0s`, hints from `doc`), and the abandoned schema-driven card is deleted.\n- A live settings replacement is checked before it is switched to, the daemon's\n state surfaces are folded into one boot step, and a SIGHUP reload re-applies\n database-owned settings.\n- Forge intake settings that nothing reads are now rejected at load.\n\n### Configuration: judged where it is owned\n\n- The runtime config overlay is deleted; database-owned settings are judged at\n the layer that owns them rather than on the file load path.\n- A file overlay no longer drops the fields it omits inside a map entry, and a\n kind with no stored value leaves the file's value in force.\n- The default config path is resolved in one place, and the channel document\n has its own shape.\n\n### State Store: offline backup, restore, validate and rollback\n\n- New offline backup / restore / validate / rollback path.\n- `validate` runs boot's own gate; it no longer replaces the database, reads a\n kind the store does not hold as its seed, or touches the daemon's log.\n- The recovery control-plane server is built on the shared step vocabulary.\n\n### Workflow: one step vocabulary and a `gate.diff-rules` replacement\n\n- The step vocabulary is owned by a family manager registered at each\n composition root, replacing `.archie/gate.go` with `gate.diff-rules`, which\n fails closed on a change it never read.\n- Workflow roots are pinned and the dead vocabulary is removed; the workflow pin\n crosses the wire.\n- The schedules resource skips the leLine truncated
|
||||
},
|
||||
{
|
||||
"component": "archie",
|
||||
"name": "archie-agent",
|
||||
"version": "1.35.0",
|
||||
"date": "2026-09-22",
|
||||
"body": "The sandboxed runtime links the same shared packages as archied, so this release carries the\nchannel-lifecycle store contract and the stricter action-load errors with it:\n\n- The channel-status store contract (`PutChannelStatus`/`ListChannelStatus`) and its replace-the-set\n semantics.\n- Authoritative module ids and stricter action load errors: a misspelled result field, an unknown id,\n or a dynamic `actions` read now fails the playbook load rather than the dispatch.\n\narchied and archie-agent move together in this release."
|
||||
},
|
||||
{
|
||||
"component": "archie",
|
||||
"name": "archie-agent",
|
||||
|
||||
Reference in new issue
Block a user