66b07a4b46617166b0ffc2bceef051024d204f19
The build task's only sources were **/*.go, go.mod and go.sum, while ui/embed.go embeds the committed bundle with //go:embed all:dist. Task's up-to-date check is a content checksum over files, so a change to ui/dist -- including the one `task ui` writes in place -- left the task "up to date" and the previously embedded dashboard in every binary. Measured on this worktree, appending a byte to ui/dist/index.html: git status M ui/dist/index.html task build task: Task "build" is up to date grep <marker> bin/archied 0 <- stale asset shipped With ui/dist/** listed, the same probe rebuilds all six binaries and the marker is present; a nested asset (ui/dist/assets/index.css) does too. Reverting the probe rebuilds again, and a second build with nothing changed still reports "up to date", so the content cache is intact. touch-only changes do not retrigger, confirming the check is on content rather than mtime. deployment_contract_test.go gains a bounded test over the build task's sources block, the shape the neighbouring fmt assertion already uses. The version stamps in the same task stay out of reach of a file checksum: git describe moves with HEAD while no file content does, and the git metadata is not addressable from a worktree, where .git is a file. That needs a status/stamp design decision, so it is split to archie-core-pdq2.
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
132 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%