The native Open Farming app server currently warns that its generated function barrel failed to load because usePaymentStore is not defined. This was observed before the STX 0.2.687 integration, during the marketing/docs audit, with the existing Stacks 0.74 dependency graph.
The owning framework source already imports the payment store explicitly and initializes it inside useBillable. Consume and qualify the maintained framework release containing that source fix. Do not edit storage/framework/defaults, generated auto-import barrels, installed package files or shared caches, and do not add a dependency patch.
Acceptance:
- Upgrade through native Stacks dependency tooling to a source release containing the explicit-import/lazy store initialization fix.
- Regenerate auto-imports with the native lifecycle and verify a cold app server imports the entire function barrel without the payment-store warning.
- Exercise actual app functions and marketing routes, full lint/types/tests, docs generation/search and mobile/browser behavior on the upgraded framework.
- Keep generated machine-specific paths out of source control and preserve the existing absence of dependency patches.
This follow-up is separate from the source-released documentation search and fragment-title fixes in PR #36. It is not a claim that all framework functionality has been qualified merely because static marketing pages render.
Source resolution inspection
On published app 488c0c9, the generated barrel explicitly imports ../defaults/functions/billing/payments. That committed vendored module still eagerly calls an undefined usePaymentStore. The installed @stacksjs/defaults module already contains the explicit payment-store import and lazy initialization inside useBillable; it is not the file selected by this barrel.
A read-only tree comparison found 803 changed shared files, 770 installed-only files and 168 vendored-only files. Native framework/defaults synchronization is therefore an application migration, not a safe one-file dependency edit. Qualify the native upgrade/publish or unpublish lifecycle, cold barrel loading and the resulting app behavior before publication. Do not edit the generated barrel, hand-patch the vendored module, or claim that static marketing success proves the warning resolved.
Native lifecycle checkpoint
A real cold native injection reproduces the original usePaymentStore warning and leaves both increment and useBillable unavailable. Native framework synchronization fixes barrel loading; a new fresh-process regression also executes the application's counter operations and verifies 2, 1 and 0. These candidate checks pass, with no dependency patches.
The synchronization exposed a separate native installer bug: requesting 0.74.66 installed 0.74.70 through the caret and falsely reported 0.74.66. Stacks PR #2980 fixes it at source. All seven source test shards and applicable quality/build jobs pass on 19864cc; main publication used a normal fast-forward as Chris without coauthors. Actual bun run release:patch completed and published main/tag v0.75.299 at 4fd78e75318346f466bdb877c353096b7f75155c. Its exact release-commit CI and package publication remain pending; no npm availability is claimed yet.
The unpublished Farming branch also used native buddy unpublish:defaults without force. It verified the synchronized copy, replaced it with the gitignored installed-package link and repointed app imports through the maintained package. The cold function regression still passes. Application-specific views and the canonical AGENTS.md are preserved.
Final released graph adoption, frozen lock/Bun coherence, full lint/types/tests, actual marketing/auth/docs browser qualification and final exact app CI/main publication remain open. The current intermediate 0.74.70 candidate is not being presented as the final qualified migration.
Released migration ready for final app CI
PR #39, commit 4c155b7cf365f02211adfc60e6160c7e7bd5b446, consumes the actual released Stacks 0.75.299 through the native upgrade and defaults lifecycle. The exact framework release-commit CI and releaser now pass, including published-package installation. The public v0.75.299 release exists. All installed files from six consumed archives match released bytes; installed native CLI rerun and forced frozen install leave the application graph byte-stable. Bun 1.4.4 actually preserves this application's format-1 lockfile, and CI/containers/runtime requirements are aligned.
The cold-process regression passes against final 299, including shared native listener boot ownership and real counter operations. Three explicit lock guard tests, native lint and app/test types pass. The 55-page docs audit verifies 507 search destinations, 4,901 local links and 93 assets with no failures. Actual native app desktop/mobile direct rendering and docs keyboard/pointer search checks pass. Auth-link activation stalls observed separately are tracked in #38; no authentication provider or delivery behavior is claimed. Both independent review axes are clean.
Full local suite was denied at a fresh 3.58 GB available, below the 4 GB admission floor. Final app CI, normal main publication and production verification remain required. The original cold failure and intermediate installer/guard failures remain retained separately from final passing evidence.