Skip to content

Foundation 3 library reuse hardening and TalkingBytes 2.2 integration - #18

Open
abmmhasan wants to merge 126 commits into
mainfrom
foundation-3/library-reuse-hardening
Open

abmmhasan wants to merge 126 commits into
mainfrom
foundation-3/library-reuse-hardening

Conversation

@abmmhasan

Copy link
Copy Markdown
Member

Summary

This PR carries the Foundation 3 library-reuse/integration hardening work tracked in docs/plans/foundation-library-reuse-and-integration-plan.md.

Key areas:

  • reuse Webrick/CacheLayer native counter and cache mechanics;
  • enforce atomic auth-counter selection;
  • remove duplicate OAuth authorization evaluation;
  • reuse Pathwise download preparation while retaining stream freshness checks;
  • consolidate active refresh-token ownership around Epicrypt;
  • canonicalize named/default CacheLayer store identity;
  • route application-owned named cache consumers through CacheManager;
  • reuse generation-owned native lock providers without memoizing lock handles;
  • preserve DBLayer transaction/infrastructure-PDO lifecycle boundaries;
  • raise TalkingBytes to ^2.2 and use its released typed HTTP resolved-composition API;
  • certify TalkingBytes 2.2 email/webhook/gRPC/runtime-isolation integration surfaces;
  • keep CSRF semantics and the Foundation 3.x HTTP facade compatibility decisions explicit.

Validation

The tracker intentionally keeps final execution gates open until PR CI and consumer verification complete. Do not infer release readiness from unchecked plan items.

This PR should remain open while the final PHPForge/CI, Redis/Valkey, benchmark, dependency-matrix, production-database, clean-install, and Infbyte consumer gates are being resolved.

Merge

Do not merge automatically. Final merge remains maintainer-controlled.

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