Resolve #1661: Reduce runtime peer internals#1664
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.
Summary
Closes #1661.
@fluojs/runtimedirect coupling to peer package internal subpaths by isolating the remaining@fluojs/core/internaland@fluojs/http/internalusage behind runtime-owned seams.Changes
internal-peer-dependencies.test.tsto ensure only the runtime seam files import peer internal subpaths.@fluojs/runtimebecause the public package artifact changes while behavior remains preserved.Testing
pnpm install --frozen-lockfilepnpm buildpnpm --dir packages/runtime typecheckpnpm --dir packages/runtime buildpnpm --dir packages/runtime testpnpm lint(completed; existing Biome warnings remain in unrelatedpackages/config/packages/corefiles whileverify:public-export-tsdocpassed)Public export documentation
@param/@returnstags where applicable.@exampleblocks and README scenario examples still play complementary roles.No public runtime API or export-map surface changed; new exported symbols are runtime-internal source seams and are not re-exported from package entrypoints.
Behavioral contract
This is a contract-preserving refactor. Runtime README behavior and documented runtime invariants are unchanged.
Platform consistency governance (SSOT)
createPlatformConformanceHarness(...)tests.No platform contract docs or package README conformance claims changed.