feat(mobile): Task 9 — core infrastructure (config, logger, supabase, query client, auth store)

[toruiwasa]

Task 9 of REQ-17 — the shared non-UI layer every screen from Task 10 onward depends on. Nothing here renders.

Closes #12

What landed

File	Role
app.config.js	new — lifts EXPO_PUBLIC_* into expo.extra. Task 7 shipped a static app.json, so nothing did this before
src/lib/config.ts	Reads those values and throws at import naming any that are missing
src/lib/logger.ts	MobileLogger — the only permitted console caller; no-console is now an error everywhere else
src/lib/supabase.ts	expo-secure-store adapter, detectSessionInUrl: false
src/lib/queryClient.ts	MMKV-persisted query cache + AppState focus / NetInfo online listeners
src/store/authStore.ts	Zustand session store — session, setSession, clearSession, nothing else
src/constants/{colors,thresholds}.ts	Design tokens; STALE_WARNING_MS / STALE_DISCONNECTED_MS

config.ts is what turns #95 (EAS cloud builds have no source for three EXPO_PUBLIC_* variables) from a silent undefined endpoint into a launch-time error naming the variable. #95 still has to supply the values; this makes its absence loud.

Deviations from REQ-17 — all four recorded in the plan with reasons

1. react-native-mmkv v4 renamed the v3 API the spec used. new MMKV({id}) → createMMKV({id}), delete(key) → remove(key). The v3 calls do not exist on a v4 instance, so the spec's adapter would have thrown on the first cache eviction, not at construction. A test asserts remove() specifically.
2. createSyncStoragePersister carries an @deprecated tag in @tanstack/query-sync-storage-persister@5.102, pointing at createAsyncStoragePersister. Switched. MMKV's synchronous methods satisfy the async persister's AsyncStorage interface unchanged (every field is MaybePromise), and PersistQueryClientProvider restores asynchronously either way — the hydration behaviour REQ-17 describes is unaffected.
3. EXPO_PUBLIC_APP_ENV, not APP_ENV — eas.json and .env.example, both merged in Task 7, already settled on that name.
4. An absent or unrecognised appEnv falls back to production, not development. CLAUDE.md > Logging Strategy fixes the undefined environment at the quietest level; defaulting the other way means a build that simply forgot the variable ships with debug logging on.

Issue #12's body also said gcTime: 300_000 and src/lib/query-client.ts / src/store/auth.ts. The plan is followed instead: gcTime is 24h (a query evicted after 5 minutes is never written to MMKV, which would put the skeleton state on every launch, not just the first), and the filenames are queryClient.ts / authStore.ts per the folder structure in REQ-17.

Two further changes made while implementing:

• react-native-nitro-modules added as a direct dependency. It is a required peer of react-native-mmkv@4 and was not resolvable from apps/mobile under pnpm's isolated layout. Same rule as Hoisted pnpm store mixes jest 29.x and 30.x — name-resolved config can bind the wrong major #97: every consumer declares what it resolves by name.
• userInterfaceStyle pinned to "light". colors.ts ships a light palette only — REQ-17 Phase 1 specifies no dark palette, and a second one would be invented rather than designed — so "automatic" would pair dark system chrome with light screens.

Test boundary

__tests__/{config,logger,supabase,queryClient,authStore,constants}.test.ts — 43 tests, 100% on all seven new files.

Mocked: expo-constants, expo-secure-store, @supabase/supabase-js, react-native-mmkv, @react-native-community/netinfo. Per CLAUDE.md, each mock is asserted to have actually intercepted (createClient call count, captured MMKV/NetInfo/AppState handlers) rather than only that behaviour looked right. sanitize() runs for real — the redaction assertions would pass against a no-op mock.

What the tests pin down, beyond the happy path:

• config.ts treats an empty string as missing (an unset EAS variable arrives that way) and names only the variables actually absent
• logger.ts redacts at warn and error too — the levels production still emits
• queryClient.ts gcTime >= persister.maxAge; no refetchInterval in the defaults; isConnected: null (NetInfo before its first probe) is not read as online; the focus listener's cleanup actually unsubscribes

Verification

pnpm --filter @pulseticker/mobile lint       clean
pnpm --filter @pulseticker/mobile typecheck  clean
pnpm --filter @pulseticker/mobile test:cov   43 passed, 100% on new files
pnpm build                                   6/6
pnpm test                                    6/6 tasks

expo config --type public was run with and without the variables set, confirming app.json is merged and extra is populated — the change is not inferred from the config file alone.

Not verified: nothing here has run on a device. The MMKV native module and the secure-store adapter need an EAS development build, which needs #95 first.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
pulseticker	Ready	Preview	Sep 3, 2026 2:08am UTC

[toruiwasa]

Review round — 9 findings, 6 fixed here, 3 filed

Reviewed the diff for correctness and quality. Five further candidates were raised and refuted on verification, recorded at the bottom so they do not get re-litigated.

Fixed in b1b8c25

#	Finding	Fix
1	sanitize() redacted top-level keys only, so { context: { access_token } } logged the token verbatim at warn — a level production emits. The new tests asserted redaction for flat objects only, so CI stayed green.	Recursion through plain objects and arrays in packages/logging, cycles guarded with a WeakSet. Applies to apps/web and apps/api too. Class instances still pass through — recorded as a limitation, since that is the LogData type's job.
2	warnWithCause / errorWithCause missing, which CLAUDE.md §6 requires for Supabase-auth and JWT errors. LogData rejects a raw Error, so Task 10 would have had no compliant way to log a cause.	Added, mirroring apps/web and apps/api: errorName always, errorMessage only in development, stack only for errorWithCause in development.
3	autoRefreshToken: true with no AppState wiring. auth-js drives the refresh from a 30s setInterval and RN suspends JS timers while backgrounded, so an app resumed after token expiry issues its next request with a stale JWT.	startAutoRefresh / stopAutoRefresh driven from AppState, registered at module scope so a screen cannot forget it.
4	Secure-store adapter passed rejections straight through: a refused write meant no persisted session and a silent sign-out on the next cold launch, with nothing logged.	All three methods wrapped in a guard() that logs through errorWithCause and rethrows (CLAUDE.md §3).
5	Level gate hand-rolled per method in two styles, instead of the LEVELS table @pulseticker/logging exports and apps/web already uses. As written, isProd gated debug and info identically.	One appEnv → LogLevel map compared through LEVELS.
6	clearSession() byte-for-byte setSession(null), with both documented as live paths — later sign-out cleanup would have run for one caller only.	clearSession is the single teardown path; setSession(null) delegates to it.

Also: the Config fixture duplicated across four suites moved to __tests__/helpers/mockConfig.ts, and the userInterfaceStyle note in colors.ts was corrected — the pin applies on iOS only, since Expo's config reference requires expo-system-ui for it to work on Android and that package is not installed. Nothing reads useColorScheme yet, so no screen is affected.

Filed rather than fixed

• Single-source the design palette between apps/web and apps/mobile #112 — single-source the web/mobile palette. colors.ts is hand-copied from --pt-* and matches byte-for-byte today, but nothing links them. The fix needs a generation step (web consumes CSS custom properties and carries a dark variant mobile omits), so it is a design task, not a drop-in import.
• Add expo-system-ui so userInterfaceStyle actually applies on Android #113 — add expo-system-ui. Needs a device build to verify, which is blocked on EAS cloud builds have no source for three EXPO_PUBLIC_* variables #95. Moot if Mobile app is pinned to light mode — no dark palette exists #111 lands a dark palette first.
• packages/logging has no test project, so sanitize() has no measured coverage #114 — packages/logging has no test project, so sanitize() has no measured coverage. It is genuinely exercised (mobile maps the package to src/), just not measured. Predates this PR; surfaced by making the deepest redaction path load-bearing.

Refuted on verification

Recorded so they are not raised again: the app.config.js extra spread (app.json has no extra to clobber); the re-declared AppEnv type in a test (the CLAUDE.md rule quoted against it is scoped to Zod-inferred types); the no-console exemption living in eslint.config.js (a rename produces a loud lint error, not a silent unpairing); the import-time throw in config.ts (REQ-17:537 argues for exactly that, and config is reached transitively regardless); and gcTime: 24h (load-bearing, pinned by a test, and negligible at MVP cardinality).

Verification

pnpm --filter @pulseticker/mobile lint       clean
pnpm --filter @pulseticker/mobile typecheck  clean
pnpm --filter @pulseticker/mobile test:cov   59 passed, 100% on all seven src files
pnpm build                                   6/6
pnpm test                                    6/6 (web 164, api, mobile 59)

Still not verified on a device — unchanged from the original PR, and #95 still gates that. The AppState wiring and the secure-store failure paths are asserted against mocks only.