chore(scripts): move federation e2e scripts to deferred/ — complete b293040#200
Merged
Merged
Conversation
…lative paths Five e2e scripts (e2e-federation, e2e-pom, e2e-revocation, e2e-autosync, e2e-federation-network) imported `../dist/services/federation.js`, which is build-deferred per `mcp-server/tsconfig.json` (`"exclude": ["src/deferred/**"]`). Running any of them today crashes with `ERR_MODULE_NOT_FOUND` for federation.js. Commit b293040 ("chore: refocus mycelium on the brain core, decouple openClaw") moved e2e-push-pom.mjs to mcp-server/scripts/deferred/ to mirror the source placement, but left the rest behind. Complete the move so the directory structure tells the truth: federation-dependent e2e scripts live next to the deferred services they exercise, and stay inert until the deferred build is unparked (CLAUDE.md roadmap step 5). Side effect: e2e-push-pom.mjs's `../dist/...` paths were broken after its move (resolves to mcp-server/scripts/dist instead of mcp-server/dist). Bump every script in this directory to `../../dist/...` so the imports resolve correctly once the federation build is re-emitted. Verified locally: e2e-pom now errors on `dist/services/federation.js` (the deferred-build cause) instead of the path mismatch — IdentityService and GuardService imports resolve cleanly. Build green (`npm run build`). No active script or package.json target references these files; they are manually-invoked diagnostic tools. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 3, 2026
Dewinator
added a commit
that referenced
this pull request
May 3, 2026
…split) The Native-App Track section claimed "Alle 9 PRs sind green und MERGEABLE" and "9-PR-Queue", but the actual open-PR count has been 14 since PR #201 landed (151st tick). The 9-only framing under-stated the drain workload Reed is sitting on and obscured the orthogonal cohorts — 3 W4.1 anti-echo PRs (#197, #198, #201) and 2 W2 federation PRs (#199, #200) merge fully independent of the native-app stack (143rd-tick file- overlap audit, 148th-tick 3-order commute proof on 13 PRs; #201 is additive on top with no shared files). Now CLAUDE.md states the 14-PR total with the cohort split and the empirical commute evidence, so the next agent tick reads the correct drain workload and the next "queue full → analyse, don't add" decision is grounded in current state, not in the 2026-05-02 9-PR snapshot. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Dewinator
added a commit
that referenced
this pull request
May 3, 2026
…rain) Reed merged 10 PRs today: all 3 W4.1 anti-echo (#197/#198/#201), both W2 federation (#199/#200), 5 native-app (#190/#191/#192/#193/#194). Only the linear 4-PR #178-stack remains open (#185 independent + #187 → #188 → #189 strictly stacked). Three-cohort split collapsed to one cohort — old order- independence proofs (143rd/148th tick) now obsolete. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
mcp-server/scripts/into the existingmcp-server/scripts/deferred/directory, completing the structural intent of commit b293040 which moved onlye2e-push-pom.mjs.../dist/...imports →../../dist/...in all 6 scripts now living at depth 2.Why
These five scripts depend on
dist/services/federation.js:e2e-federation.mjse2e-pom.mjse2e-revocation.mjse2e-autosync.mjse2e-federation-network.mjsmcp-server/tsconfig.jsonexcludessrc/deferred/**, sofederation.tsis not compiled anddist/services/federation.jsdoes not exist on the active build. Running any of these scripts today crashes immediately:Commit b293040 already moved
e2e-push-pom.mjsintoscripts/deferred/for exactly this reason but left its siblings behind — they exercise the same deferred service. Putting them next to the deferred source they use (and to the lone deferred sibling) keeps the convention honest: if it lives inscripts/deferred/, it's gated on the federation build.This is also the same root cause CLAUDE.md flags around the dashboard: "Schwarm + Vererbung + Föderation" is roadmap step 5 (deferred). Wave 2's HTTP path works in the active build; the mTLS path is parked, and these e2e scripts exercise the parked side.
Path correction (collateral fix)
e2e-push-pom.mjs(already indeferred/) had../dist/...paths, which resolve tomcp-server/scripts/dist/...— that directory has never existed. The first import error today is a path mismatch onidentity.js, not a deferred-build error onfederation.js. After this PR, all six files use../../dist/...and only fail on the actual deferred-build cause.Verified locally:
IdentityServiceandGuardService(both compiled from active code) import-resolve cleanly; onlyFederationServiceerrors — i.e. exactly the gate Reed wants visible when the deferred build is re-emitted.Out of scope
src/deferred/**intsconfig.json. That's the roadmap-step-5 unpark decision, not this PR's concern.e2e-pki.mjs,e2e-breeding-sim.mjs,e2e-experience-coupling.mjs,e2e-motivation-coupling.mjs,e2e-neurochemistry.mjs,smoke-cross-spread.mjs,smoke-salience-reactor.mjs,backfill-pki.mjs). They don't import federation and stay where they are.ERR_MODULE_NOT_FOUNDare the documentation.Test plan
cd mcp-server && npm run build— green.package.jsonscript or other source/doc references the moved files (grep confirms only self-mentions inside the scripts themselves).node scripts/deferred/e2e-pom.mjsconfirms first failing import is nowdist/services/federation.js, not a path mismatch.🤖 Generated with Claude Code