Repository navigation
feat: dispatch gates, wrapper background wait, grok 1.0.77 (0.0.71) - #85
Merged
Merged
Conversation
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.
closes #74
closes #75
closes #83
summary
timeout, and fusion read the wrapper's first stop as a failed delivery. from 10-28, 76% of wrappers moved, 49% ended asdelivery, wrappers went from 5 to 8 calls, and the parent's terminal collection blocks rose from 20 to 80 a day. a wrapper now stays in flight until it relays the real output, and the waiting notification is not a result.lifecycle/subagents.mjsandlifecycle/notifications.mjscarry the logic.Exploreon sonnet when no model is named, denies agpt-6-astrawrite brief of 3000 bytes or more, and denies an engine for 30 minutes after an infrastructure failure in the session, unless the latest user message names the model or engine./fusion:statsgains a verification evidence block, and the guard now records verification in every posture.observedAt, a wind down records usage when its rollout proves continuity, the job monitor keeps summaries instead of parsed records (165 to 94 mib of rss), and grokindependencedefaults to medium (9 of 23 runs finished at high).[1.0.14, 1.0.78), with a new lane snapshot: grok burst passed 9 of 9 on T05, T06, and T09. the T01 bench task has one defect again, and five process timing tests stop depending on host load.bench/results/lanes-2026-11-07/andrules-manifest.jsonare generated or recorded output.test plan
already verified
npm test: 1900 pass, 0 fail, 3 skipped on the tree before the grok move. after it, heavy host load (average above 100) left 4 timing failures; the failing files pass at--test-concurrency=2(373 of 374, then the last version pin fixed: 84 of 84)claude plugin validatepasses for codex, grok, cursor, devin, fusion, and the marketplace root--plugin-dir: a codex wrapper's bash moved at 180 seconds, it printedwaiting on <id>, woke on the notification, read the output, and relayed. recorddone,failureKindnull,retryCount0, no parent stop blockfusion-staged-tokenand ran the task directly; with a haiku main session,Exploreran onclaude-sonnet-5-5state: donebash bench/tasks/T01-seeded-bug/selftest.sh: PASS; inserting a, b, c, d withmaxSize: 2leavesc,dreviewer should verify
/fusion:smokepasses and/fusion:statsshowsdeliveryfailures near zero for wrappers past 180 secondsnotes
single-flight-fit reasonis replaced by the enforced 3000 byte gate andgpt-6.1-solat xhigh, because the warning had not moved a 58% timeout rate at 3 to 6 kb.may pin the Explore agent to haikubecomes a sonnet default that still allows haiku. the10 minute Bash capwording becomes the 570 second flight, because the 180 second move made it false. a repeated scoring sentence is dropped. the lane default line movesindependenceto medium. no invariant inCONTRIBUTING.mdchanges.~/.grok/hooksinside managed runs, and no per run switch exists;/grok:setupnames them, and suppress grok plugin hooks in managed runs #84 tracks a privateGROK_HOME.cancel_requestedin stats after this ships.