Feat/pro feature registry

[dishit-wednesday]

What this does

Introduces the Pro feature layer for Off Grid and moves the email/calendar tools out of the open core into the private pro submodule, behind the Pro entitlement.

The branch history was rebuilt into 7 focused commits so that no commit in the open repo ever contains the email/calendar handler implementation or any RevenueCat API keys.

Change set

Pro feature registry + license seam (d300dbb0)

• Adds the @offgrid/pro submodule and the registry seam (screenRegistry, sectionRegistry, loadProFeatures) so pro features register themselves at boot through an activate(registry) bag, with a no-op stub when the submodule is absent.

Tool extension seam + MCP wiring (26db7c0d)

• Adds ToolExtension (with optional getToolDefinitions()) and wires extension-provided tools into the generation tool loop, the chat input popovers, and the chat screen.

RevenueCat pro license service + unlock modal (3d5613bf)

• Web-billing flow: email is both the payment identity and the unlock key. proLicenseService configures RevenueCat with Trusted Entitlements (INFORMATIONAL verification, FAILED signatures blocked), caches the license in the keychain, and revalidates online at launch so access can be revoked from the RC dashboard.
• ProUnlockModal collects the email, opens the RC web checkout, and verifies the purchase. Replaces the auto-restart library with a manual "close and reopen" prompt.

RevenueCat config placeholders (66ff0c44)

• Public placeholder config so the app compiles. Real iOS/Android keys stay in gitignored revenueCatKeys.local.ts and are never committed.

In-app debug log viewer (99718d62)

• DebugLogsScreen + debugLogsStore for on-device log inspection.

Pro-gated email/calendar tools (fcbc9c99)

• send_email, create_calendar_event, read_calendar_events now live in the pro submodule as a ToolExtension. The core picker renders core tools plus extension-provided ones, deduped. handlers.ts/registry.ts match main exactly — the handler code exists only in the pro package.

tsconfig path mapping (18ee7f1d)

• Maps @offgrid/core/* → src/* for tsc, mirroring the existing jest moduleNameMapper, so tsc resolves the pro extension's core type imports.

Verification

• tsc --noEmit clean.
• EmailCalendarExtension unit tests pass (16/16).
• No email/calendar handler code (handleSendEmail, handleCreateCalendarEvent, ensureCalendarPermission, RNCalendarEvents) in any source file across the branch history.
• No RevenueCat API keys in history.
• handlers.ts / registry.ts are byte-identical to main.

Notes

• Branch coverage is ~79.7% (gate 80%); coverage top-up is a tracked follow-up.
• The pro submodule changes ship via offgrid-pro#2; the gitlink points at ed9b93b.

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[gemini-code-assist]

Code Review

This pull request introduces a Pro feature integration system using a git submodule, runtime registries for screens and settings sections, and a Metro configuration fallback. It also adds new built-in tools for sending emails and managing calendar events, alongside integrating tool extensions (such as MCP tools) into the generation loop. Feedback on these changes highlights a duplicate rendering bug of Pro settings sections in SettingsScreen.tsx, potential runtime crashes due to missing date validation in the calendar tool handlers, potential duplicate registrations in the screen and settings registries, and a lack of error handling when opening the mail client via Linking.openURL.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The getSettingsSections() map is duplicated in two different places on the SettingsScreen (once before the 'Community' section and once before the 'Reset Onboarding' section). This will cause all registered Pro settings sections to render twice on the screen. Remove this duplicate entry.

[gemini-code-assist]

If the model provides an invalid date string, calling new Date(startDate).toISOString() or new Date(endDate).toISOString() will throw a RangeError: Invalid time value and crash the execution. Validate the parsed dates before calling .toISOString().

  const start = new Date(startDate);
  const end = new Date(endDate);
  if (isNaN(start.getTime()) || isNaN(end.getTime())) {
    throw new Error('Invalid date format. Please provide valid ISO 8601 dates.');
  }
  const result = await RNAddCalendarEvent.presentEventCreatingDialog({
    title,
    startDate: start.toISOString(),
    endDate: end.toISOString(),
    ...(location ? { location } : {}),
    ...(notes ? { notes } : {}),
  });

[gemini-code-assist]

If startDateStr or endDateStr are invalid date strings, calling .toISOString() on the resulting Date objects will throw a RangeError. Validate the dates defensively before converting them to ISO strings.

  const startDt = startDateStr ? new Date(startDateStr) : new Date();
  if (isNaN(startDt.getTime())) {
    throw new Error('Invalid start date format.');
  }
  const endDt = endDateStr ? new Date(endDateStr) : new Date(startDt.getTime() + 7 * 24 * 60 * 60 * 1000);
  if (isNaN(endDt.getTime())) {
    throw new Error('Invalid end date format.');
  }
  const events = await RNCalendarEvents.fetchAllEvents(startDt.toISOString(), endDt.toISOString());

[gemini-code-assist]

Since loadProFeatures registers screens on status changes, calling registerScreen multiple times will append duplicate screens to the registry. Add a check to prevent duplicate screen registrations.

export function registerScreen(screen: RegisteredScreen): void {
  if (!screens.some(s => s.name === screen.name)) {
    screens.push(screen);
  }
}

[gemini-code-assist]

Since loadProFeatures registers settings sections on status changes, calling registerSettingsSection multiple times will append duplicate sections to the registry. Add a check to prevent duplicate section registrations.

export function registerSettingsSection(component: ComponentType<any>): void {
  if (!sections.includes(component)) {
    sections.push(component);
  }
}

[gemini-code-assist]

Linking.openURL can throw an error if no mail client is installed or configured on the device (especially on simulators or devices without email apps). Wrap the call in a try-catch block to handle this gracefully, log the error to prevent silent failures, and return a meaningful error message.

  try {
    await Linking.openURL(url);
  } catch (err) {
    console.error('Failed to open mail client:', err);
    throw new Error('Could not open the mail app. Please ensure a mail client is configured on your device.');
  }

References

1. When catching errors, log them instead of swallowing them to ensure failures are visible and to aid in debugging.

[codecov]

Codecov Report

❌ Patch coverage is 73.39901% with 54 lines in your changes missing coverage. Please review.
✅ Project coverage is 81.78%. Comparing base (7ac1d68) to head (b0d85e0).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/screens/ChatScreen/useChatGenerationActions.ts	41.37%	14 Missing and 3 partials ⚠️
src/components/ChatInput/Popovers.tsx	10.00%	4 Missing and 5 partials ⚠️
src/services/generationToolLoop.ts	81.81%	4 Missing and 2 partials ⚠️
src/screens/ChatScreen/ChatMessageArea.tsx	37.50%	4 Missing and 1 partial ⚠️
src/utils/logger.ts	20.00%	3 Missing and 1 partial ⚠️
src/screens/SettingsScreen.tsx	25.00%	3 Missing ⚠️
src/services/tools/handlers.ts	94.23%	0 Missing and 3 partials ⚠️
src/stores/debugLogsStore.ts	40.00%	3 Missing ⚠️
src/services/proLicenseService.ts	94.73%	0 Missing and 2 partials ⚠️
src/components/CustomAlert.tsx	50.00%	0 Missing and 1 partial ⚠️
... and 1 more

❌ Your patch check has failed because the patch coverage (73.39%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #386      +/-   ##
==========================================
- Coverage   81.82%   81.78%   -0.04%     
==========================================
  Files         241      245       +4     
  Lines       12835    12954     +119     
  Branches     3535     3574      +39     
==========================================
+ Hits        10502    10595      +93     
- Misses       1403     1416      +13     
- Partials      930      943      +13     

Files with missing lines	Coverage Δ
src/bootstrap/loadProFeatures.ts	100.00% <100.00%> (ø)
src/components/ChatInput/index.tsx	84.14% <100.00%> (+0.19%)	⬆️
src/components/DebugLogsScreen/index.tsx	34.61% <100.00%> (+34.61%)	⬆️
src/components/ToolPickerSheet.tsx	86.66% <ø> (ø)
src/screens/ChatScreen/index.tsx	65.59% <ø> (ø)
src/services/tools/extensions.ts	100.00% <100.00%> (ø)
src/services/tools/registry.ts	100.00% <ø> (ø)
src/components/CustomAlert.tsx	92.30% <50.00%> (-3.70%)	⬇️
src/components/settings/sectionRegistry.ts	80.00% <80.00%> (ø)
src/services/proLicenseService.ts	94.73% <94.73%> (ø)
... and 8 more

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sonarqubecloud]

Quality Gate passed

Issues
9 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
2.7% Duplication on New Code

See analysis details on SonarQube Cloud