Repository navigation
Commit e85479c
committed
🔬 Certify the supervised workflow from outside, on both entrypoints
Tier CF runs the shipped workflow the way a person runs it: real `xmd`
subprocesses, a private run store, a disposable bare repository, a loopback
forge named by the two variables a deployment names one with, and a real ACP
agent this suite starts and answers over a controller of its own. Three leaves
are substituted — the agent process, the forge origin, and a `git` that bridges
the one locator the Git-host adapters admit to the bare repository beside the
test. Everything between them ships.
CF1 completes the whole supervised workflow through the Deno source entrypoint
and through the compiled binary, from discovery to acceptance, with a real
suspension answered between them; and it asserts the Agent ceiling from the
agent's own side, because the agent reports what it was handed — an empty
provider-owned directory it can list, no additional directory, no MCP server, an
empty requested tool set, and the deny-all instruction layer. CF2 kills that run
mid-effect and resumes it from the exact committed journal and Workspace
frontier, performing the suffix once and then reaching nothing at all on a
completed replay. CF3 suspends the composed consumer at a real checkpoint, lets
delivery retain the answer without executing, and continues it through #300's
scheduler over the host the entrypoint builds. CF4 keeps two named Repositories
and Worktrees dirty and unpushed across a restart and publishes only what the
document authored. CF5 stops a malformed proposal and a denied native tool
before any later effect. CF6 finds no hidden decision state in a completed run's
retained history, forks it compatibly, refuses an incompatible fork, and refuses
a secret in an answer.
Every red I reported while building this was mine, not the product's. The
scripted agent asserted one identity when a session was created and a different
one when it was loaded, so every reattachment was refused and every continuation
looked like a shipped divergence; and the in-process executor CF3 schedules
through omitted the identity components the entrypoint declares, so `<Session>`
expanded and the turns beneath it never replayed. Both are fixed here, and the
corrections are recorded on #299.
Two paths beyond the certification file, both registration. The suite drives
`dist/xmd`, which no shard builds, so it joins the binary suite already excluded
from every runtime's discovery — and the manifest says #299's own commands own
it, building the binary and then naming the file outright. SCH9's reviewed-blob
pins move to what R3 left, with its `525efaa7` over `170a021d` provenance
untouched: two blobs changed under an approved repair, and pinning what they
hold now is what keeps that case about this slice rather than about nobody.
Claude-Session: https://claude.ai/code/session_01MNztk1fikXUnD2FW4yS6Kr1 parent 6b3653c commit e85479c
4 files changed
Lines changed: 1819 additions & 6 deletions
File tree
- packages/cli/tests
- scripts
- tests
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1006 | 1006 | | |
1007 | 1007 | | |
1008 | 1008 | | |
1009 | | - | |
| 1009 | + | |
1010 | 1010 | | |
1011 | 1011 | | |
1012 | 1012 | | |
1013 | 1013 | | |
1014 | 1014 | | |
| 1015 | + | |
| 1016 | + | |
| 1017 | + | |
| 1018 | + | |
| 1019 | + | |
| 1020 | + | |
| 1021 | + | |
| 1022 | + | |
| 1023 | + | |
1015 | 1024 | | |
1016 | 1025 | | |
1017 | 1026 | | |
1018 | 1027 | | |
1019 | | - | |
| 1028 | + | |
1020 | 1029 | | |
1021 | 1030 | | |
1022 | 1031 | | |
1023 | 1032 | | |
1024 | | - | |
| 1033 | + | |
1025 | 1034 | | |
1026 | 1035 | | |
1027 | 1036 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
512 | 512 | | |
513 | 513 | | |
514 | 514 | | |
| 515 | + | |
| 516 | + | |
| 517 | + | |
| 518 | + | |
| 519 | + | |
| 520 | + | |
515 | 521 | | |
516 | 522 | | |
517 | 523 | | |
| |||
0 commit comments