chore(release): archied v1.36.0

This commit is contained in:
sam committed 2026-09-22 14:22:21 +10:00
1 parent dd7cb8b16f
commit c25f8d3956
4 files changed
+99

No files matched your search

+45
View File
@@ -1,5 +1,50 @@
# archied changelog
## [1.36.0] - 2026-09-22
### The dashboard declares tools an in-browser agent can call
- The dashboard registers **seven WebMCP tools**. Read-only: `list_tasks`, `get_task`,
`recent_events`, `daemon_health`. Recovery: `retry_task`, `stop_task`, `cancel_task`. An agent
operating the dashboard now reads structured state and recovers stuck work instead of scraping the
UI.
- Every tool wraps the same `ui/src/lib/api.ts` client the dashboard itself calls, so an agent and a
person exercise one path rather than two.
- `archie-ui` cannot be attributed to the agent that called it: a page can invoke its own tools, so an
agent's call and a page script's call reach the server identically. Tools therefore record the
signed-in identity and a source, and **never** that an agent acted.
### The four judgement verbs are deliberately absent
- `approve`, `reject`, `abandon` and `archive` are **not** exposed. `internal/domain/taskactions`
records only a source string and stamps `KindHumanApproved`, so an agent's approval would be written
down as a person's. An agent that can approve can approve its own work, and the one control this
design exists to keep is a human accepting it. Those verbs land once task actions carry both the
acting identity and the authorising principal.
### `consequentialHint` does not gate anything, and the release says so
- Chrome 152 accepts `consequentialHint` at registration and **omits it from `getTools()`**, so no
client sees it and the browser cannot enforce what it does not surface. The three recovery tools
instead require an explicit `confirm: true`, which is a **deliberate-action signal rather than a
security control** an agent can trivially satisfy. The boundary that holds is the session: the tools
cannot exceed what the signed-in operator can already do.
### Two ways this fails silently, now recorded next to the code
- **A secure context is required.** On a plain-HTTP origin `document.modelContext` is absent *even
with the flag*, and nothing reports why. `mkcert` covers local development.
- **`archie-ui` embeds `ui/dist` into its binary**, so rebuilding the distribution is not deploying it;
a running process can serve a bundle with no tools while the built one has them.
### Binaries built by the development build task can be updated
- `task build` passed the `installtype` stamp for three of six commands, so `archie-messaging`,
`archie-state-store` and `archie-ui` were built without it. An unstamped binary reports `unknown`
and the self-update path **refuses rather than guesses**, which is how an operator ends up unable to
update with `install type is unknown` and no way forward. All six are stamped now, and a test reads
the build task and fails naming any command line that omits it.
## [1.35.0] - 2026-09-22
### The Messaging Service is severed from the store and workflow runtime
+46
View File
@@ -0,0 +1,46 @@
# archied 1.36.0
Released 2026-09-22. [All news](../index.md)
### The dashboard declares tools an in-browser agent can call
- The dashboard registers **seven WebMCP tools**. Read-only: `list_tasks`, `get_task`,
`recent_events`, `daemon_health`. Recovery: `retry_task`, `stop_task`, `cancel_task`. An agent
operating the dashboard now reads structured state and recovers stuck work instead of scraping the
UI.
- Every tool wraps the same `ui/src/lib/api.ts` client the dashboard itself calls, so an agent and a
person exercise one path rather than two.
- `archie-ui` cannot be attributed to the agent that called it: a page can invoke its own tools, so an
agent's call and a page script's call reach the server identically. Tools therefore record the
signed-in identity and a source, and **never** that an agent acted.
### The four judgement verbs are deliberately absent
- `approve`, `reject`, `abandon` and `archive` are **not** exposed. `internal/domain/taskactions`
records only a source string and stamps `KindHumanApproved`, so an agent's approval would be written
down as a person's. An agent that can approve can approve its own work, and the one control this
design exists to keep is a human accepting it. Those verbs land once task actions carry both the
acting identity and the authorising principal.
### `consequentialHint` does not gate anything, and the release says so
- Chrome 152 accepts `consequentialHint` at registration and **omits it from `getTools()`**, so no
client sees it and the browser cannot enforce what it does not surface. The three recovery tools
instead require an explicit `confirm: true`, which is a **deliberate-action signal rather than a
security control** an agent can trivially satisfy. The boundary that holds is the session: the tools
cannot exceed what the signed-in operator can already do.
### Two ways this fails silently, now recorded next to the code
- **A secure context is required.** On a plain-HTTP origin `document.modelContext` is absent *even
with the flag*, and nothing reports why. `mkcert` covers local development.
- **`archie-ui` embeds `ui/dist` into its binary**, so rebuilding the distribution is not deploying it;
a running process can serve a bundle with no tools while the built one has them.
### Binaries built by the development build task can be updated
- `task build` passed the `installtype` stamp for three of six commands, so `archie-messaging`,
`archie-state-store` and `archie-ui` were built without it. An unstamped binary reports `unknown`
and the self-update path **refuses rather than guesses**, which is how an operator ends up unable to
update with `install type is unknown` and no way forward. All six are stamped now, and a test reads
the build task and fails naming any command line that omits it.
+1
View File
@@ -4,6 +4,7 @@ Release notes for archied and archie-agent, newest first.
## 2026-09-22
- [archied 1.36.0](archied/1.36.0.md)
- [archied 1.35.0](archied/1.35.0.md)
- [archied 1.34.0](archied/1.34.0.md)
- [archied 1.33.0](archied/1.33.0.md)
+7
View File
@@ -1,4 +1,11 @@
[
{
"component": "archied",
"name": "archied",
"version": "1.36.0",
"date": "2026-09-22",
"body": "### The dashboard declares tools an in-browser agent can call\n\n- The dashboard registers **seven WebMCP tools**. Read-only: `list_tasks`, `get_task`,\n `recent_events`, `daemon_health`. Recovery: `retry_task`, `stop_task`, `cancel_task`. An agent\n operating the dashboard now reads structured state and recovers stuck work instead of scraping the\n UI.\n- Every tool wraps the same `ui/src/lib/api.ts` client the dashboard itself calls, so an agent and a\n person exercise one path rather than two.\n- `archie-ui` cannot be attributed to the agent that called it: a page can invoke its own tools, so an\n agent's call and a page script's call reach the server identically. Tools therefore record the\n signed-in identity and a source, and **never** that an agent acted.\n\n### The four judgement verbs are deliberately absent\n\n- `approve`, `reject`, `abandon` and `archive` are **not** exposed. `internal/domain/taskactions`\n records only a source string and stamps `KindHumanApproved`, so an agent's approval would be written\n down as a person's. An agent that can approve can approve its own work, and the one control this\n design exists to keep is a human accepting it. Those verbs land once task actions carry both the\n acting identity and the authorising principal.\n\n### `consequentialHint` does not gate anything, and the release says so\n\n- Chrome 152 accepts `consequentialHint` at registration and **omits it from `getTools()`**, so no\n client sees it and the browser cannot enforce what it does not surface. The three recovery tools\n instead require an explicit `confirm: true`, which is a **deliberate-action signal rather than a\n security control** an agent can trivially satisfy. The boundary that holds is the session: the tools\n cannot exceed what the signed-in operator can already do.\n\n### Two ways this fails silently, now recorded next to the code\n\n- **A secure context is required.** On a plain-HTTP origin `document.modelContext` is absent *even\n with the flag*, and nothing reports why. `mkcert` covers local development.\n- **`archie-ui` embeds `ui/dist` into its binary**, so rebuilding the distribution is not deploying it;\n a running process can serve a bundle with no tools while the built one has them.\n\n### Binaries built by the development build task can be updated\n\n- `task build` passed the `installtype` stamp for three of six commands, so `archie-messaging`,\n `archie-state-store` and `archie-ui` were built without it. An unstamped binary reports `unknown`\n and the self-update path **refuses rather than guesses**, which is how an operator ends up unable to\n update with `install type is unknown` and no way forward. All six are stamped now, and a test reads\n the build task and fails naming any command line that omits it."
},
{
"component": "archied",
"name": "archied",