feat(react): add Modal primitive, network switcher, env validation and strict tooling

[akargi]

Summary Four frontend/tooling foundations for the dApp. - Modal dialog primitive (#1149) ΓÇö portal-rendered ole="dialog" with �ria-modal, focus trapping across Tab / Shift+Tab, Escape and backdrop dismissal, blurred backdrop, refcounted body scroll lock, focus restoration to the trigger on close, and topmost-by-DOM-order arbitration so stacked dialogs do not fight. SSR-safe. - Multi-network switcher (#1148) ΓÇö useNetwork() returns { network, networkId, networks, rpcUrl, networkPassphrase, setNetwork, isSwitching, error } across Stellar Testnet, Futurenet and a local standalone node. Switching rebuilds �cForgeClient (and VaultClient) so every hook keyed on the client refetches, and pushes the new passphrase into the context that WalletProvider validates against. Unknown ids surface as error, not an exception. - Environment validation (#1146) ΓÇö eact/demo/src/config.ts validates VITE_RPC_URL, VITE_NETWORK_PASSPHRASE and VITE_CONTRACT_ID with zod on boot and returns a discriminated result instead of throwing. Unset variables keep the existing testnet defaults, so a fresh clone still runs; a variable that is set but malformed is reported with the received value, what is expected, and a remediation hint on a dedicated configuration error screen. - Strict TypeScript and ESLint (#1145) ΓÇö enables oUncheckedIndexedAccess, oImplicitOverride, oFallthroughCasesInSwitch, oUnusedLocals, oUnusedParameters and isolatedModules; promotes the eact-hooks rules and o-unused-vars to errors and adds o-console. Every resulting error is fixed by narrowing ΓÇö no �ny was introduced and no type was loosened. ## Notes for the reviewer - Backwards compatibility is structural, not incidental: when no network is selected, effectiveConfig returns the caller's config by identity, so client keeps a stable reference and existing consumers behave exactly as before. context.test.tsx and ConnectWallet.test.tsx are unaffected, and a new context.network.test.tsx covers the regression where an adapter on testnet must report wrong-network after switching to futurenet. - Two flags were deliberately left off: - exactOptionalPropertyTypes ΓÇö breaks existing call sites that pass explicit undefined, for zero runtime benefit. - �erbatimModuleSyntax ΓÇö eact/jest.config.js merges eact/tsconfig.json with an inline { module: 'commonjs' }, which would emit TS1286 on every ESM file and fail the whole test suite. - oImplicitReturns is also off: Dropdown's handleKeyDown intentionally falls through its switch. - A new pm run typecheck script runs sc --noEmit. - contractIds on BcForgeProvider is additive scope beyond the issue text ΓÇö a switcher that keeps one contract id across three chains is not useful in practice. ## Verification Nothing here has been machine-verified ΓÇö sc, eslint, jest and the demo build were not run, as requested. ΓÜá∩╕Å ** pm install is required before CI will pass.** zod@^4.4.3 was added to eact/demo/package.json but package-lock.json was intentionally left untouched, so pm ci fails on the out-of-sync lockfile. ΓÜá∩╕Å ** pm run test:visual:update --workspace @bc-forge/react** on the arm64 Playwright image ΓÇö the four new Primitives/Modal stories have no committed baselines. Closes #1145 Closes #1146 Closes #1148 Closes #1149

[drips-wave]

@akargi Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits