chore(release): archied v1.27.0 archie v1.27.0
This commit is contained in:
1 parent
6c6f6bf30b
commit
f7420f7576
2 files changed
+51
No files matched your search
@@ -1,5 +1,13 @@
|
||||
# archie-agent changelog
|
||||
|
||||
## [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.
|
||||
- The gateway version stamp now covers the binaries installed alongside the
|
||||
daemon, so their versions can be reported and compared.
|
||||
|
||||
## [1.26.0] - 2026-09-17
|
||||
|
||||
- feat(config): add [scheduling] config block
|
||||
|
||||
@@ -1,5 +1,48 @@
|
||||
# archied changelog
|
||||
|
||||
## [1.27.0] - 2026-09-17
|
||||
|
||||
### Dashboard task logs
|
||||
|
||||
- Task logs are readable from the dashboard again, through a new State Store
|
||||
read contract (`ReadTaskLog`, `StreamTaskLogContent`) rather than the UI
|
||||
process reaching into the daemon's log files. Wired server-side by the
|
||||
standalone state-store process.
|
||||
- Added `GET /api/tasks/{id}/logs/download`, serving an attempt's raw log as a
|
||||
`task-<id>-attempt-<n>.log` attachment.
|
||||
- A process that cannot read logs and an attempt that recorded no log are now
|
||||
distinguishable ("cannot read" answers 503, "no log" answers 404) instead of
|
||||
both rendering as a claim about a configuration setting.
|
||||
|
||||
### 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
|
||||
renderer no longer states a count it computed from its own truncated sample.
|
||||
- Repeated successful tool calls collapse into one counted entry.
|
||||
- The tool-activity block is capped to a third of the live frame, keeps the
|
||||
newest lines, and marks what it dropped with a `+N earlier` indicator. Every
|
||||
line that fits is kept.
|
||||
- Every clamped answer marks its cut with an ellipsis, including the opening
|
||||
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
|
||||
|
||||
- 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.
|
||||
- A path shared by several disk targets keeps the strictest requirement any
|
||||
target places on it, so an optional target can no longer mask a required one.
|
||||
- The shutdown-watchdog test no longer races the Go scheduler, which was
|
||||
intermittently failing the quality gate and parking work unrelated to it.
|
||||
|
||||
### 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.
|
||||
|
||||
## [1.26.0] - 2026-09-17
|
||||
|
||||
- fix(webui): publish per-identity forges so multi-identity task rows keep their links
|
||||
|
||||
Reference in new issue
Block a user