You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8c2cd59
Browse filesBrowse the repository at this point in the historyBrowse files
🔀 Overlay the embedded adapters on ACPX's registry instead of replacing it
The workflow profile installed a registry closed to codex and claude, so a run
that named any other agent was refused. Carrying a patched Codex adapter is not
a reason to withdraw Gemini, and the closure also restated every non-embedded
agent's retained identity — a compatibility break in return for nothing.
The registry is now an overlay. codex and claude resolve to their exact
embedded snapshots and never fall through: a snapshot that cannot verify,
materialize or launch refuses the agent rather than becoming the published
adapter that names no turn. Every other agent resolves through the same ACPX
registry, to the same command, as before.
Preparation is conditional on the same predicate, so a non-embedded selection
reaches no capture, verification, materialization or fallback path. The retained
compatibility identity follows it: the stable provider/package/version/snapshot
identity for an embedded provider, and the resolved command — unchanged from the
base branch — for everything else.
Evidence is Gemini, an ACPX built-in this build carries nothing for. WAL13 runs
it to completion, retains its ordinary Prompt events, retains zero checkpoints
and proves the embedded machinery was never asked about it. WAL14 replays it
whole and resumes it interrupted, restoring the stored Prompt without asking
again. WAL15 pins its retained identity to `gemini --acp`. WAL16 refuses a
broken codex snapshot before any Prompt and leaves Gemini working under the same
broken snapshots. AM3/AM3b are the registry itself.
Spec §8.6 now describes a qualified Codex/Claude override rather than a closed
registry, and says that a missing checkpoint changes nothing about a successful
Prompt.
0 commit comments