fix(plugins): restore registry hash read and drift invalidation evidence #5330

Activity

1. Yeachan-Heo commented on Sep 6, 2026

   

   Yeachan-Heo

   on Sep 6, 2026

   OwnerAuthor

   More actions

   Taking sole ownership of #5330 in the existing dedicated worktree on new branch fix/issue-5330-plugin-registry-read-count, created from freshly fetched dev at c10db31866eb84efc7b420cf2f45d319195d52f4.

   No overlapping open PR or issue producer was found. Scope is limited to distinguishing plugin-registry read instrumentation drift from actual cache invalidation behavior, preserving hash reuse and quarantine guarantees, and producing one dev-target PR after exact parent/head reproduction and focused validation.

   —
   [repo owner's gaebal-gajae (clawdbot) 🦞]
2. Yeachan-Heo commented on Sep 6, 2026

   

   Yeachan-Heo

   on Sep 6, 2026

   OwnerAuthor

   More actions

   Exact reproduction and base/head evidence:

   • Failing dev head: c10db31866eb84efc7b420cf2f45d319195d52f4 — focused test result: 8 pass / 2 fail, both failures report plugin read count Expected: > 0, Received: 0.
   • Prior parent: ed67422699299b0257dd45ec1d37167b474b4918 — the same focused test also returns 8 pass / 2 fail with the same assertions.
   • The parent→head diff contains only seven unrelated fixture-test changes and does not touch plugin runtime adapters or this test.
   • Complete hosted job evidence was retrieved from actions/jobs/101411818139/logs; it identifies gjc-plugin-runtime-adapters.test.ts as the sole failing fresh-process file with the same lines 160 and 186 read-count failures.
   • Product safety behavior remains healthy during both failures: installed-file drift still quarantines with runtime_mismatch, same-size tamper with restored mtime still fails closed, and registry enablement invalidation still passes.

   Classification: test instrumentation drift, not product cache invalidation. The implementation now performs authenticated stable reads through fs.open()/FileHandle.read(); the stale assertions spy only on fs.readFile(), so they observe zero despite real hashing and quarantine behavior. The fix will update only the read instrumentation seam and preserve all caching/quarantine assertions.

   —
   [repo owner's gaebal-gajae (clawdbot) 🦞]
3. Yeachan-Heo commented on Sep 6, 2026

   

   Yeachan-Heo

   on Sep 6, 2026

   OwnerAuthor

   More actions

   Resolved by merged PR #5333.

   • Merge commit on dev: f6b14f1fc1c87e5d4156c549749e8c3129c4ef80
   • Final implementation head: 2da02522584702bdc783aa17a4277197e38cbbfa
   • Exact-head focused test and TypeScript build jobs passed in Dev CI run 34008106346.
   • Independent review verdict: MERGE_READY.
   • Final exact-head contract check passed; earlier cancelled contexts were not treated as authorization.

   —
   [repo owner's gaebal-gajae (clawdbot) 🦞]
4. Yeachan-Heo

   closed this as completedon Sep 6, 2026
5. Yeachan-Heo commented on Sep 6, 2026

   

   Yeachan-Heo

   on Sep 6, 2026

   OwnerAuthor

   More actions

   Terminal/post-merge evidence for #5330:

   • PR test(plugins): observe stable hash reads #5333 merged to dev as f6b14f1fc1c87e5d4156c549749e8c3129c4ef80; issue fix(plugins): restore registry hash read and drift invalidation evidence #5330 is closed.
   • Final PR head 2da02522584702bdc783aa17a4277197e38cbbfa passed exact-head Dev CI 34008106346, including the affected adapter test job and coding-agent TypeScript build, plus current signed contract and independent MERGE_READY review.
   • Direct validation on the actual merge commit f6b14f1fc1c87e5d4156c549749e8c3129c4ef80 passed:
     • plugin runtime adapters: 10 pass / 0 fail
     • coding-agent Biome + TypeScript check: pass
     • coding-agent binary build: pass
   • The merge-triggered Dev CI 34008721351 was invalidated/cancelled by successor pushes. Before cancellation it recorded unrelated failures only:
     • shard 1: resume-session-reentrancy.redteam.test.ts, matching open issue test(coding-agent): restore presentation reset in resume reentrancy red-team fixture #5328 (resetAssistantTextPresentation missing from its fixture)
     • shard 6: MCP initial-connect disconnect timeout, subsequently addressed by merged PR fix(mcp): settle disconnect during initial connect #5334
     • neither failing shard includes gjc-plugin-runtime-adapters.test.ts, and no fix(plugins): restore registry hash read and drift invalidation evidence #5330 runtime or test regression was observed.
   • Current dev is descendant 3bb72969910de49ac50b2b697e550c7f732b1d1b; its post-merge run 34010572862 is pending behind repository-wide CI. This is an external repository gate, not approval evidence, and is not being represented as green.
   • Recovery state is clean: branch fix/issue-5330-plugin-registry-read-count is published, merged, and an ancestor of current dev; there are no unique unpublished commits or working-tree changes.

   Signed-off-by: gaebal-gajae (clawdbot) 🦞

   —
   [repo owner's gaebal-gajae (clawdbot) 🦞]