Repository navigation
Temporarily disable Excavator pending native Argon support - #173
Merged
Merged
Conversation
sleegme
added a commit
that referenced
this pull request
Oct 25, 2026
Excavator: TEMPORARY headless Argon path via agy CLI (follow-up to #173)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TEMPORARY measure: disable Excavator until agy native subagents can select
Gemini 4 Argon. This replaces the originally requested runner-dispatched role;
no Excavator runner policy, transport or ledger schema is introduced.
The established AGY 1.3.6 probe showed that native
proandflashboth rangemini-3.8-flash-tiered, while exact Argon frontmatter failed registration.Flash does not fit this difficult diagnosis/repair role. Prior model evidence
remains in
.omo/evidence/74-argon-routing.md.Design and temporary workaround
agents/excavator.md, its full repair contract, tool list and shellguard. Set
subagent: false;mainAgent: falseremains unchanged.acceptance and native-delegation telemetry attribution. A packet claiming an
Excavator delegation fails closed before review.
bounded repairs stay with Bobcat and its existing Strix advisor gate.
evidenced
BLOCKEDresult and supervisor-owned ledger path. An unsettledarchitectural question uses existing
NEEDS_DEEP. Neither path promotes themilestone or starts Zen review. This avoids a new status, retry loop or
dispatch protocol.
internals and the canonical contract. Historical live evidence is labeled
historical, not evidence for current enabled routing.
Re-enable
This is not a permanent removal. When a bounded native-child probe proves
Argon selection in actual executed-model metadata, select that verified native
tier, change
subagentback totrue, restore the documented Bulldozer/spinerouting and tests, and remove temporary notices together. The preserved agent
file documents these steps. No exact-model runner workaround is shipped.
Verification
node --test --test-reporter=tap tests/*.mjs: exit 0; 290 tests,269 passed, 0 failed, 21 skipped, 107463.033592 ms.
Skips are 20 existing Windows-specific tests and one existing persistent
watch-mode test. Bare
node --testdiscovers zero tests in this repository,so the explicit filename glob was used.
python3 -m unittest discover -s tests -p "test_*shell_guard.py":15 passed, exit 0.
declared-delegation rejection for DONE/BLOCKED/NEEDS_DEEP, and durable blocker
and escalation evidence with no worker dispatch, promotion or Zen review.
hashes; existing equality and appended-guidance assertions remain intact.
git diff --checkpassed. Grepping the completecommitted diff from
8f0e258for/home/returned no matches.scripts/runner.mjsandscripts/ledger.mjsare unchanged from the base.agy plugin validate .passed on installed AGY 1.4.7 with the pre-existingwarning that root
AGENTS.mdis not loaded as a plugin rule.agy agentslistingexited 0 without altering the shared installation.
Not live-verified and remaining risks
gate follow-up below. Future native Argon selection, real repair quality
and future AGY versions remain unverified.
existing blocker/escalation path until native Argon is verified and the role
is deliberately re-enabled.
typescript-language-serveris notinstalled. Syntax checks and the full test suite were used instead.
below supplies that evidence; independent re-approval is not claimed.
The main checkout was not modified. Do not merge this PR.
Gate C1 follow-up: live native rejection and enabled control
Evidence:
.omo/evidence/173-native-excavator-probe.md, with the exact prompt,redacted 33-event native stream and redacted Bobcat transcript alongside it.
Tested production head:
e3a7c5ccea3b8d6a5568ceb4b57acda05372619a;this follow-up adds evidence only.
On AGY 1.4.7, installed that PR head into a fresh private HOME and empty
workspace. Worker files were byte-identical to PR head. Only the private
Bulldozer parent's
mainAgentflag was changed to true so it could be selectednatively; its role body and both worker definitions were unchanged.
One bounded
gemini-3.8-flash-highnative Bulldozer conversation(
7cad473a-ebc9-4bbf-bf1e-de6606a369bd) requested both workers sequentially:invoke_subagentstep 2 enteredERROR. Its stored
error_detailsand payload reportsubagent "excavator" not found or not allowed to be invoked.No child ID was created.
b0b9b93f-cdee-4586-8d72-b071a42ef5d7; its stored completed response wasNTG173_BOBCAT_CONTROL_READY.The fresh conversation store contained only the parent and Bobcat database,
with no Excavator child. This is native runtime evidence, not the spine
callback or a model's unsupported claim.
150-second AGY timeout and 170-second outer bound. No shared installation
changed. No disable-mechanism fix was needed.
Exact completed full-suite summary
node --test --test-reporter=tap tests/*.mjs, exit 0, on the unchangedproduction tree:
Retained shell guards, exit 0: