Skip to content

fix(extensions): clear stale release-check mirror allowlists + drop gutted pi-agent-core from matrix#2384

Merged
alexey-pelykh merged 1 commit intomainfrom
fix/release-check-extension-mirror-drift
Apr 17, 2026
Merged

fix(extensions): clear stale release-check mirror allowlists + drop gutted pi-agent-core from matrix#2384
alexey-pelykh merged 1 commit intomainfrom
fix/release-check-extension-mirror-drift

Conversation

@alexey-pelykh
Copy link
Copy Markdown

Closes #2383.

Summary

Fixes the publish-next CI job failure on main after the v2026.3.11 sync (run 24567594577). The scripts/release-check.ts bundled-extension dependency-mirror validator reported drift on 6 extensions; root cause split into two classes:

  1. Stale allowlist (5 extensions)googlechat, msteams, nostr, tlon, zalouser had entries in rootDependencyMirrorAllowlist that were subsequently added to the root package.json. Allowlist must match "missing in root" exactly; emptied each.
  2. Gutted-package leak (matrix)@mariozechner/pi-agent-core reappeared in extensions/matrix/package.json after the v2026.3.11 sync lifted upstream's extension manifest verbatim. pi-agent-core is gutted in the fork (Middleware Boundary Principle). Zero source-level consumers in extensions/matrix/. Removed from dependencies and emptied allowlist. Same class of fix as e07d5d3 (post-v2026.3.7 cleanup).

Verification

  • pnpm install --lockfile-only removed the pi-agent-core transitive closure: pnpm-lock.yaml drops 1,125 lines
  • pnpm check (format + tsgo + lint) passes cleanly
  • Direct invocation of collectBundledExtensionRootDependencyGapErrors returns 0 errors
  • grep -rn "pi-agent-core" extensions/matrix/ returns only package.json (zero source references)
  • All 10 previously-mirrored extension deps confirmed present in root package.json

Test plan

  • CI publish-next job passes (was the failing job on main)
  • CI build, test, lint, rebrand-gate, stub-debt-gate, obsolescence-audit-gate, zombie-import-gate all pass
  • docs workflow passes
  • Post-merge main CI stays green (end-to-end goal of this fix)

Systemic follow-up (not in scope)

Each upstream sync re-introduces pi-agent-core in matrix's package.json (v2026.3.7, v2026.3.11). Consider classifying extensions/matrix/package.json as EXTRACT in the disposition registry so future syncs hunk-review the dep list instead of wholesale-applying upstream's manifest. Tracked separately.

🤖 Generated with Claude Code

…utted pi-agent-core from matrix

Closes #2383.

Fixes the publish-next CI job failure on main after the v2026.3.11 sync
(run 24567594577). The `scripts/release-check.ts` bundled-extension
dependency-mirror validator reported drift on 6 extensions.

Two distinct classes of drift:

1. Stale allowlist entries (5 extensions):
   googlechat, msteams, nostr, tlon, zalouser each listed deps in
   `rootDependencyMirrorAllowlist` that were subsequently added to the
   root package.json. The allowlist's invariant is "exactly the extension
   deps missing from root" — once mirrored, they must leave the allowlist.
   Emptied each allowlist.

2. Gutted-package leak (matrix):
   `@mariozechner/pi-agent-core` reappeared in `extensions/matrix/package.json`
   as a direct dependency after the v2026.3.11 sync lifted upstream's
   extension `package.json` verbatim. pi-agent-core is gutted in the
   RemoteClaw fork (Middleware Boundary Principle). Verified zero
   source-level consumers in extensions/matrix/. Same class of fix as
   e07d5d3 (post-v2026.3.7 cleanup). Removed from dependencies and
   emptied the allowlist.

Verification:
- `pnpm install --lockfile-only` removed pi-agent-core transitive closure
  (1,125 lines deleted from pnpm-lock.yaml)
- `pnpm check` (format + tsgo + lint) passes
- Direct invocation of `collectBundledExtensionRootDependencyGapErrors`
  returns 0 errors
- `grep -rn "pi-agent-core" extensions/matrix/` returns only package.json
  (zero source references)

Systemic follow-up (out of scope): each sync re-introduces pi-agent-core
in matrix's package.json (v2026.3.7, v2026.3.11). Consider classifying
`extensions/matrix/package.json` as EXTRACT in the disposition registry
so future syncs hunk-review the dep list. Tracked separately.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

release-check: extension root dependency mirror drift after v2026.3.11 sync

1 participant