fix(main): cherry-pick #12936 — export Filesystem/Share from build:web native stubs (unbreaks prod Pages deploys)

[NubsCarson]

What

Cherry-pick of a06ad22 (#12936, already merged to develop) onto main.

Why main needs it now

• Promote Promote develop to main — 2026-07-04 overnight work (~380 commits) #12848 (merged 2026-07-04 04:46Z) carried test(app): add iOS native attachment smoke for #10936 #12065's packages/app/src/ios-attachment-smoke.ts onto main. That file top-level imports { Filesystem } from @capacitor/filesystem and { Share } from @capacitor/share.
• build:web routes all @capacitor/* (except core) through vite/native-module-stub-plugin.ts, whose generic stub did not emit those named exports, so rollup fails:
  "Filesystem" is not exported by "^@native-stub:@capacitor/filesystem", imported by "src/ios-attachment-smoke.ts".
• Observed live: develop→staging Cloud CF Deploy run 28695298240 failed both Pages jobs (console + app) at their build steps with exactly this error at head d567622 (pre-fix). The fix fix(app): export Filesystem/Share from build:web native stubs #12936 landed on develop at 05:26Z, but main does not have it — so every prod Pages deploy from current main (db2b2a0) will fail the same way (prod run 28695321227's App build is exposed to it).

Scope

• Single file, +18 lines, identical to the develop commit (cherry-picked with -x).
• Stubs are fail-loud (every method throws "mobile-only"), no fabricated success — consistent with the fallback-slop policy.
• Migrations + API Worker jobs are unaffected (they already pass); this only unbreaks the two Pages builds.

The next develop→main promote would carry this anyway; this PR just closes the window where prod front-end deploys from main are build-broken.

[cloud-security]

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c09d4f3e-2158-48a5-9166-816d024ee0ab

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/main-capacitor-stub-exports

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[lalalune]

Local validation for the main hotfix cherry-pick:

• PASS: git diff --check origin/main...HEAD
• PASS: bunx @biomejs/biome check packages/app/vite/native-module-stub-plugin.ts
• PASS: git diff --no-ext-diff --exit-code a06ad2211b3cc89ff09d2b5b6faba6cfb9cc13e7 HEAD -- packages/app/vite/native-module-stub-plugin.ts
  • Confirms the touched stub file is identical to the already-merged develop fix from #12936.
• PASS: direct Vite plugin check for @capacitor/filesystem and @capacitor/share
  • Both imports resolve to \0native-stub:* when isCapacitorMobileBuild: false.
  • Generated modules include the required named exports (Filesystem, Share) and mobile-only throwing behavior.

Attempted but blocked locally:

• bun run --cwd packages/app build:web did not reach app bundling in this sparse worktree because Vite config loading failed before the PR code path: the available installed dependency trees are missing @tailwindcss/vite. A local bun install --frozen-lockfile --ignore-scripts is also blocked by the sparse checkout omitting unrelated root workspaces.

Given this is a one-file cherry-pick of the develop fix and the generated stub output verifies the missing Rollup named exports directly, the risk is limited to the intended deployment unblock.

[lalalune]

Validated as a main hotfix cherry-pick of the already-merged #12936 native-stub fix.

Local checks:

• git diff --check origin/main...HEAD && git diff --check
• bunx @biomejs/biome check packages/app/vite/native-module-stub-plugin.ts
• direct smoke confirmed @capacitor/filesystem exports Filesystem/default and @capacitor/share exports Share/default from the stub source
• bunx vitest run packages/app/test/native-module-stub-plugin.test.ts passed

App visual audit is N/A for this PR: Vite build-time native module stubs only; no app UI/rendering path changed.

[lalalune]

Validated the main-branch cherry-pick locally against fresh main (github-main-fresh).

What I checked:

• Confirmed the commit is the same native-stub export change already present on fresh develop via a06ad2211b3cc89ff09d2b5b6faba6cfb9cc13e7.
• git diff --check github-main-fresh...HEAD -- packages/app/vite/native-module-stub-plugin.ts passed.
• bunx @biomejs/biome check packages/app/vite/native-module-stub-plugin.ts passed.
• bun run --cwd packages/app build:web passed and reached a normal completed Vite build:
  • no missing Filesystem / Share export failure
  • [renderer-build-manifest] wrote eliza-renderer-build.json buildId=bf439cdc3db4 (424 assets)
  • [verify-chunk-safety] OK: bn.js/crypto graph is confined to lazy vendor chunks (392 current chunks scanned).

I did not run audit:app because this is a Vite build-time native-module stub change only; it does not alter rendered app UI. Local worktree stayed clean after validation. GitHub checks are still queued and mergeStateStatus is currently UNKNOWN, so I’m leaving this for CI/mergeability to settle before merge.