Skip to content

Release InfByte on Foundation 3.0.1 native runtime lifecycle - #9

Merged
abmmhasan merged 130 commits into
mainfrom
foundation-3/runtime-lifecycle
Sep 24, 2026
Merged

abmmhasan merged 130 commits into
mainfrom
foundation-3/runtime-lifecycle

Conversation

@abmmhasan

@abmmhasan abmmhasan commented Sep 5, 2026 •

Copy link
Copy Markdown
Member

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.1
  • Foundation tag: 3.0.1
  • Published merge/source commit: fc9b3258646ac744e61fd02e18d9b98e5afff2e8
  • normal Composer resolution only
  • no Foundation VCS/path repository override
  • no development branch alias
  • no candidate SHA pin

Foundation 3.0.1 directly requires:

  • ArrayKit ^5.2
  • CacheLayer ^3.4
  • InterMix ^10.1.1
  • Webrick ^5.4

Native runtime ownership

Webrick

All matcher strategies use Webrick's native cache lifecycle:

  • fused → native fused matcher cache
  • generated → native generated matcher cache
  • sharded → native __current + immutable generation-* shards

Foundation 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.php

There is no fake fused configuration mode. Foundation owns policy/identity/publication, not a second config serializer.

InterMix + CacheLayer

Generated InterMix PHP ProductionContainer artifacts 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:

  • Security & Standards run #144 (36037084068) — success
  • native Webrick + ArrayKit cache certification — success
  • production auth/session — success
  • generation lifecycle — success
  • module lifecycle — success
  • create-project — success
  • InfByte 2.1 → Foundation 3 migration — success
  • released PHP 8.4 and PHP 8.5 consumers — success
  • PHP 8.4/8.5 lowest/stable QA — success
  • PHP 8.4/8.5 analysis — success
  • PHP 8.4/8.5 benchmarks — success
  • clean production install — success

The completed plan.md has now been removed, and CI also asserts that it is not shipped in the create-project skeleton.

Final plan-free release head fb5a4c159a1a9586696ef0f47faa4ec321c9f1db is qualified by Security & Standards run #147 (36037816498) — success.

Guardrails

  • no PHPForge/PHPProbe bypass
  • no threshold weakening or complexity suppression
  • no Foundation 2 route/container cache switches
  • no application-owned route/container/config compiler
  • no automatic CacheLayer wrapping of compiled InterMix containers
  • no fake fused config mode
  • no Foundation VCS/path dependency workaround
  • no automatic merge

Merge ownership

Do not merge automatically. Final merge/release remains owner-controlled.

@abmmhasan abmmhasan changed the title Migrate skeleton to Foundation 3 runtime lifecycle Migrate skeleton to finalized Foundation 3 runtime lifecycle Sep 23, 2026
@abmmhasan abmmhasan changed the title Migrate skeleton to finalized Foundation 3 runtime lifecycle Finalize InfByte on Foundation 3 native runtime lifecycle Sep 24, 2026
@abmmhasan abmmhasan changed the title Finalize InfByte on Foundation 3 native runtime lifecycle Release InfByte on Foundation 3.0.1 native runtime lifecycle Sep 24, 2026
@abmmhasan
abmmhasan marked this pull request as ready for review September 24, 2026 17:59
@abmmhasan
abmmhasan merged commit 1a968ad into main Sep 24, 2026
21 checks passed
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.

1 participant