b2fcf25c0b6dd352251bb9620acc54bb13ae9d9d
`git merge-base --is-ancestor` answers a topology question, so it reports a landed repair as never-landed for every squash merge and for any rebase merge that had to replay commits. This repository squash-merged its last fifteen pull requests (everything merged up to 2026-09-18 used merge commits), so the check documented in the failure-archaeology skill is a false negative for all of them. Add scripts/on-main.sh: `--is-ancestor` stays the offline fast path, and a non-ancestor falls back to the GitHub API, where merge state is recorded independently of the commit graph. It separates landed (0) from not-landed (1) from undetermined (2) instead of folding an unanswered question into a negative -- `if on-main.sh <ref>; then` is the mistake it exists to prevent. Verified against live data: ancestor -> 0, squash-merged PR #899 -> 0, closed unmerged PR #896 -> 1, commit in no pull request -> 1, local-only commit GitHub has never seen -> 2, bad ref / bad base / no args / bad option -> 2.
fix(ui,gateway): load the served lifecycle vocabulary, and make the page registry match the routes (#890)
fix(ui,gateway): load the served lifecycle vocabulary, and make the page registry match the routes (#890)
feat(messaging): Messaging Service operator surface, chat report rendering, and the diff-cap config fix (#899)
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
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%