Read-only conductor session, 2026-08-20, yonatangross/orchestkit
This is a read-only conductor session run on 2026-08-20 against yonatangross/orchestkit. Nothing here
is a plan or a proposal: every figure was verified during the session itself. Three views follow. The
first covers Claude Code version adoption, which had been frozen for three weeks by a single
JSON.parse call and was released across six versions in one watcher run.
The second covers five pull requests, all with zero real red, and a worktree map that fell from 13
directories to 8 while three phantom registrations refused to prune. The third is about method: four
confident claims that were overturned, four instruments that returned confident wrong answers, and two
gates that printed OK while measuring nothing.
Session 2026-08-20 · yonatangross/orchestkit
One JSON.parse call held Claude Code version adoption still for three weeks. The
snapshot ceiling sat at 2.1.231 while the machine was already running
2.1.237. Fixing the parse released six versions in a single watcher run, and
back-filled six waves of features that had been sitting behind an empty array.
Before
2.1.231
snapshot ceiling
After
2.1.237
ceiling meets running
Gap closed
six new snapshots, floor stays 2.1.220
Floor 2.1.220 is the supported minimum. Everything from 2.1.232 up was invisible to the board until the parse was fixed. Hover or focus a tick for its state.
Select a version tick for detail.
Every version read 0 before. That is the whole point: a wave showing
features: [] was not an empty release, it was a release nobody had triaged. Once
triage actually ran, six of the eight filled in. Read this chart as proof of
untriaged, not proof of empty.
Hover or focus a bar group for detail.
Genuinely zero
These two stay at 0 after triage, for two different and real reasons. 2.1.219 is below the support floor, so it is out of scope, not overlooked.
Zero only because triage never ran
Six waves. 54 features recovered from an array that a reader would have called empty.
Claim: cc-adoption-gaps.json waves are untriaged. Verdict: WRONG.
features: [] is a placeholder written by cc-release-watch.mjs:309 with the comment "filled in by triage". Proven by the watcher run back-filling 12/12/11/7/6/6 features once triage finally ran.
conductor-verified root cause, session 2026-08-20
scripts/cc-triage.mjs:318calledJSON.parseon model stdout. The model wrapped its array in a json code fence,JSON.parsethrew on the backtick, and the retry re-rolled a BYTE-IDENTICAL prompt so it reproduced the same wrapper forever. Three retry layers, none of which touched the parse.
A retry that does not change its input is not a retry, it is the same failure on a timer.
32350918138fix/cc-watch-fence-parse2026-08-20T08:51:46Z
The ref is the load-bearing detail. Dispatching main instead of
fix/cc-watch-fence-parse would have re-run the broken parser: same fence, same throw,
same three no-op retries, and the model quota spent on a run that could not have succeeded. The
fix has to be on the ref you dispatch, not merely written.
Related: PR #3580 on that branch shows head movement because the watcher
committed snapshot 58519b412 back to the branch.
Five PRs, zero real red. The only NOT-PASS anywhere in the set is
Enable auto-merge for Dependabot = skipped, which is the correct outcome on a
non-Dependabot PR. Separately, 13 worktree directories were reduced to 8, three phantom
registrations resisted pruning with EPERM, and one worktree must never be reaped.
Session 2026-08-20 on yonatangross/orchestkit. main at start 4fb82d5a3, origin/main now 5092fff91.
| PR | Branch | Before | After | Checks | realRed | Evidence |
|---|
Counts are check-runs on the head commit, not distinct workflows.
Enable auto-merge for Dependabot reports skipped. Skipped is
the correct result on a non-Dependabot PR: the step is conditioned on the Dependabot
author and none of these five PRs has it. No other check is anything but a pass across
all 168 recorded check-runs in the after column.
Directories fell while registrations rose. Those move independently: deleting an orphan directory does not remove its registration, and new work registered more worktrees than the cleanup removed.
Each had no .git file. See the instrument note below on why that matters.
git worktree prune fails with EPERM on all three stale registrations, from a
subagent and from the main session with the sandbox disabled. Synthetic stale
registrations in the same directory prune cleanly in the same invocation.
Worse: it exits rc=0 while deleting nothing. A caller checking only the exit code records a successful prune.
.worktrees/3322-sandbox-block
It holds a gitignored settings.local.json (1886 B) that
git status reports as clean. A reaper that gates deletion on
clean status would destroy it and report success. Clean status is not the same question as
"nothing here matters".
git -C inside a non-worktree walks UP.git, so git -C reported the PARENT repo state as theirs: branch main, 467 ignored paths. All of it was the main tree.git ls-remote writes "failed to store" to stderr. Folding it in with 2>&1 made all 11 branches look present on origin when only 4 were.NODE_USE_ENV_PROXY=1 node works. gh auth status calling the token invalid is downstream of the same break.ork:debug-investigator cannot use pipesRequired on every non-exempt PR. Two steps, and one trap that is the single most reusable operational fact of the session.
docs/<head_ref with / as -->
to exist with at least one .html file, in the merge ref.
ci.yml:292
playground.
ci.yml:318
ci.yml declares on: pull_request with no types:, so it
defaults to opened, synchronize, reopened. Editing the
body is none of those. The gate keeps reporting its last result on the old body, so the PR
stays red after you fixed it.
Always follow a body edit with an explicit re-run. Clearing this gate by editing a body without one leaves the failure in place while looking like you addressed it.
dependabot/, release-please, renovate/, chore/cc-snapshot-, ci/This is why "PRs would be fine to open normally" was WRONG: PR Playground is a required body grep, and three fresh PRs would have landed instantly red.
Four confident claims were overturned, four instruments returned confident wrong answers, and two gates printed OK while measuring nothing. This panel is about method. The single recurring failure is trusting an instrument's zero without asking what that instrument can structurally observe.
Not softened. The value is that each one was caught by evidence, not avoided by caution.
features: [] is a placeholder written by cc-release-watch.mjs:309 with the
comment "filled in by triage". Proven by the watcher run back-filling 12/12/11/7/6/6 features once
triage finally ran.
Evidence: cc-release-watch.mjs:309, watcher run 32350918138
ci.yml:77 DOES diff docs/site/lib/generated/. Nothing in
npm run build regenerated cc-adoption-data.ts, so the gate was blind, not absent.
Evidence: ci.yml:77
.mcp.json is gitignored and untracked. The tracked template declares
context7 as type: http with a url.
Evidence: tracked .mcp.json template, context7 entry
PR Playground is a REQUIRED body grep. Three fresh PRs would have landed instantly red.
Evidence: ci.yml:292 (docs dir with >=1 .html in merge ref), ci.yml:318 (case-insensitive body grep for "playground")
Trap: ci.yml declares on: pull_request with no
types:, so it defaults to opened/synchronize/reopened. A body edit does not re-trigger CI.
Clearing this gate by editing a body always needs an explicit re-run afterwards.
Exempt: bot authors, branch prefixes dependabot/ release-please renovate/ chore/cc-snapshot- ci/, fork PRs, or an all-inert diff per ci.yml:262
A local MITM proxy intercepts everything (curl reports remote_ip 127.0.0.1).
gh is Go, honours the proxy, then must verify its cert via macOS trustd, which is
blocked. Node ships its own CA bundle, so NODE_USE_ENV_PROXY=1 node works.
gh auth status calling the token invalid is downstream of the same break.
Three symptoms that look unrelated, one cause. The table makes the shared root visible.
| Client | Proxy aware | CA store | Symptom |
|---|---|---|---|
curl |
yes | system (macOS) | reports remote_ip 127.0.0.1, which is what exposed the MITM proxy |
gh (Go) |
yes | system, verified via trustd (blocked) |
appears dead; gh auth status reports the token invalid, which is downstream, not the cause |
node |
opt-in via NODE_USE_ENV_PROXY=1 |
own bundled CA | works; the usable path while gh is broken |
git ls-remote writes "failed to store" to stderr. Folding it in with 2>&1
made all 11 branches look present on origin when only 4 were.
4 of 11 actually on origin
git -C inside a non-worktree walks UP5 directories had no .git, so git -C reported the PARENT repo state as theirs:
branch main, 467 ignored paths. All of it was the main tree.
5 directories, 467 ignored paths, all belonging to the parent
ork:debug-investigator cannot use pipesRefused on its first command: compound commands not permitted for read-only agents. It produced nothing and cost a whole recon lane.
0 output, 1 recon lane lost
mutation-gate.sh issue #3583Same command. Same tree. The only difference is the sandbox. Both exit 0. Both print OK.
exit 0 OK
exit 0 OK
Identical exit code. Identical verdict string. One of these measured nothing.
Cause. mktemp -d -t at mutation-gate.sh:116 is denied,
RESULT_DIR becomes empty, workers write to /test-*.sh, and reduce reads nothing.
And it emits advice
Lower MUTATION_BASELINE to 0 to lock the gain in.
Following that would zero a security ratchet on a measurement that never happened.
git worktree pruneFails with EPERM on all 3 stale registrations, from a subagent AND from the main session with the sandbox disabled. Synthetic stale registrations in the same directory prune cleanly in the same invocation.
Exits rc=0 while deleting nothing. A caller checking only the exit code
records a successful prune.
Shared lesson: a green exit code is not evidence that a check ran. Ask what an instrument can structurally observe before trusting its zero.
A prior triage doc claimed 3 of 5 done. That counted documentation prose as adoption.
Measured on feat/3309-adopt-cc-settings (PR #3582): EPIC D measured 0 of 5 adopted; two had been closed on markdown alone.