Release InfByte on Foundation 3.0.1 native runtime lifecycle - #9
Merged
Merged
Conversation
abmmhasan
marked this pull request as ready for review
September 24, 2026 17:59
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
Finalize InfByte on the published Foundation 3.0.1 runtime lifecycle.
The implementation/handoff plan is fully complete and has been removed from the branch. This PR is now self-contained release evidence.
Published Foundation baseline
infocyph/foundation:^3.0.13.0.1fc9b3258646ac744e61fd02e18d9b98e5afff2e8Foundation 3.0.1 directly requires:
^5.2^3.4^10.1.1^5.4Native runtime ownership
Webrick
All matcher strategies use Webrick's native cache lifecycle:
fused→ native fused matcher cachegenerated→ native generated matcher cachesharded→ native__current+ immutablegeneration-*shardsFoundation owns the immutable release boundary/cache location only; it does not add a parallel route-cache format or pre-scan shards.
ArrayKit
Both development/build config-cache layouts are ArrayKit-native:
single→Config::exportCache()/loadCache()sharded→LazyFileConfig::warmNamespaceCache()+ native__flat.phpThere is no fake
fusedconfiguration mode. Foundation owns policy/identity/publication, not a second config serializer.InterMix + CacheLayer
Generated InterMix PHP
ProductionContainerartifacts remain the native compiled DI cache.CacheLayer remains Foundation core application infrastructure and is not automatically wrapped around compiled InterMix containers. Foundation validates Foundation-owned release metadata; InterMix validates its own native artifact/sidecar.
Stable package qualification
Functional release qualification on head
c07b62d6fe6fa7e9a27972350a732725fff128bc:36037084068) — successThe completed
plan.mdhas now been removed, and CI also asserts that it is not shipped in the create-project skeleton.Final plan-free release head
fb5a4c159a1a9586696ef0f47faa4ec321c9f1dbis qualified by Security & Standards run #147 (36037816498) — success.Guardrails
fusedconfig modeMerge ownership
Do not merge automatically. Final merge/release remains owner-controlled.