[Programcode]

Round 2 of the DebateOwl iOS and iPadOS parity plan. The Library and debates now do what the website does, with native menus, swipes and haptics on top. It runs in Expo Go and needs no backend change. There are no migrations, no Edge Function deploys and no config or secret changes.

What each item does

1. Library file import (PDF, DOCX, TXT, MD, CSV, JSON): done.

• The website's reader moved to packages/core/src/source-file-import.ts. The website and the app run the same code, with the same 8 MB and 120,000-character limits, the 80-page PDF cap and the same messages.
• Errors and warnings now carry codes. The website still shows its English text; the app shows it in en, hu and es.
• The app picks the file with expo-document-picker and checks size and type before reading anything, using the file's own size when the picker gives none. An Expo DOM component (components/source-file-reader.tsx) runs pdf.js and mammoth and pulls the file in 768 KB slices, one at a time, into one buffer.
• A read always ends. A two-minute timeout covers a webview that never loads (it shows the website's "Could not read this file."), a new file cancels the read before it, and closing the sheet stops the reader.
• The DOM component uses @expo/dom-webview, Expo's default for DOM components, which Expo Go includes. react-native-webview turned out not to be needed.
• pdf.js and mammoth are imported statically. Expo's export cannot split a DOM component into chunks. The webview only loads while a file is being read.
• The duplicate check matches a file by name within the debate, as the website does.
• Parsing stays on the device; import-source is unchanged.

2. Folders and sorting: done.

• Folder chips and New folder. The chosen folder gets a bar with a switch for the whole folder, Rename (which merges into an existing folder after asking) and Delete (which moves its sources to General).
• The website's eight sort orders, its search and its folder list now live in packages/core/src/library.ts, and LibraryPage uses them. One website fix came with it: the Library now filters by the trimmed folder name its chips show, so a legacy folder saved with spaces matches its chip.
• The type filter from the mock moved into the More menu.

3. The Active switch and the grounding banner: done.

• A switch on every row, swipe right to turn a source on or off, the same in the long-press menu and in the source view, plus the folder switch.
• A source that is off is dimmed and labelled "Off for AI". The switch sits beside the row's link, not inside it, so tapping it never opens the source.
• The website's grounding banner sits above the list.
• Changes run in order through one queue, and the newest tap decides. A failed write rolls a source back only if no newer tap replaced it, and then to the last value the server accepted, with the website's message. Offline, nothing is attempted.
• A mixed folder's switch shows on, so one tap turns it all off. The folder menu has the website's Activate and Deactivate, for General too. The app's request context already sends only active sources, so the switch really changes what grounds the AI.

4. Edit, Copy, quality, Undo, Clear all: done.

• The source view shows the website's assessment card ("Used in this case" / usage explanation), the switch, the folder, Copy, Share and Delete.
• Edit opens title, type, origin and content, and Save writes only the fields that changed.
• Delete acts at once and offers Undo, which puts the row back with its id and date, as on the website.
• Clear all asks first.
• Paste a link and Write a note now pick a folder too.

5. Debates: done.

• Start new debate and Edit settings share the website's DebateForm, with motion, format, your role and instructions and its limits and counters.
• Judge is an app addition. The website stores settings.judge and its prompts read it as "Judge expectations", but its form has no field. Both forms now keep settings they don't show: the website's DebateForm used to drop the judge on save, and a new test (src/test/debate/debate-form.test.tsx) covers it.
• The Debate tab shows format, role, judge and instructions under the motion, with Edit settings.
• Swipe left on a debate in the switcher to delete it, after the website's warning. The current debate can't be deleted, as on the website. The database already cascades the debate's work.
• After five idle days the website's "Still preparing this debate?" check opens with Continue, Switch or Start new. Closing it counts as Continue, as Escape does on the website.

6. Context menus and haptics: partial.

• A long press with a preview (Link.Preview and Link.Menu) works on:
  • Library source rows: Open, Turn on/off, Move to folder, Copy, Share, Delete;
  • the iPad dashboard's recent sources: Copy, Share;
  • saved work on the Debate tab, Prepare, Practice and History, including History's chats: Discuss and Share for cases, attacks, brainstorms and factoids, and Delete for cases and Sparring rounds with the History confirmation.
• Crossfire and chat rows on the Debate tab and Prepare open the Practice tab again (they have no preview, so they are plain rows).
• Follow-ups after round 1 (iOS parity round 1: prepare tools match the web #254) merges: Pin in the menus, and menus on Ask's own chat list. Discuss on a source is skipped because the website has none.
• Haptics come from one helper, lib/haptics.ts:
  • toggles, chips, segmented controls and pickers tap through the shared controls;
  • a finished result taps success (keepOpenResult);
  • a failed request warns (ToolError);
  • Crossfire taps when the turn comes back; Sparring already did.
  • Saves and deletes in the new flows tap too.

Shared-file edits that might overlap with round 1 are a few lines each, in tool-form.tsx, open-results.ts, crossfire.tsx, chip.tsx, segmented-control.tsx, form-rows.tsx, _layout.tsx.

Verification

• npm run verify passed locally at e6591ca5, after merging feat/native-ios with round 1 (iOS parity round 1: prepare tools match the web #254). This is a local pass, not CI; GitHub Actions is billing-blocked. It ran docs:check with knip, lint, typecheck, 807 unit tests, 30 collaboration tests, 543 edge tests, the build, the service worker test and 47 Playwright smoke tests.
• The new DebateForm test fails without its fix and passes with it.
• npm run -w @debatelab/mobile typecheck passes.
• A new core test, packages/core/src/source-file-import.test.ts, covers the limits, surrogate-safe truncation, the JSON fallback, the PDF page cap and naming the reader that failed.
• At e6591ca5, npx expo export --platform ios builds, including the 3 MB DOM bundle, and npx expo config --json is byte-identical to before, so the Expo Go config is unchanged.
• The screenshot harness drives the real flows in the web preview against staging (the seeded Pro account). Library rows and all writes are answered locally, so the account's data was not touched.
  • File import picks the fixture PDF, DOCX and PNG through the page's file chooser and checks the extracted text. That is the same reader code the DOM component runs.
  • The duplicate check fired once on a fixture that shared a file name.
• The shots were refreshed at e6591ca5: 455 are in ~/.t3/scratch/ios-parity/r2-shots/, for iPhone, iPad Air and iPad Air landscape, light and dark, English and Hungarian, plus Spanish on iPhone. They cover the Debate tab, switcher, new and edit debate, the five-day check, Library, More menu, folder bar, add link, note and file (PDF, DOCX, error), source view and edit, toasts, Prepare, Practice and History. The run had no page errors and no clipped text. I looked at every screen in every combination and fixed what they showed. Linked rows lost their layout on the web, Hungarian text was cut beside an open source on iPad, and the long-form shots didn't reach the end of the sheet. A New folder step proves a new folder stays chosen.

Not verified:

• Nothing ran on a device or simulator. This VPS has no iOS simulator, and Expo Go needs a phone.
• The native context menus, previews, swipes, haptics and the DOM webview on iOS are only proven by the iOS export building. The web preview has none of them.
• Rename, merge, the folder switch, Undo and debate delete ran against locally answered requests only, not real staging writes.
• Worth trying first on a device: the Import file sheet opening right after the Files picker closes (iOS can refuse a presentation while the picker is still animating), the slice messages across the DOM bridge, and a long-press preview on a row inside its swipeable container.

Merge with round 1

feat/native-ios (with #254) is merged in normally at e6591ca5, with no rebase. The locale files merged cleanly. The conflicts kept both rounds:

• apps/mobile/package.json: both new dependencies, @expo/dom-webview and @formatjs/intl-listformat.
• package-lock.json: round 1's lockfile, then npm install added round 2's packages.
• components/icon-paths.ts: both icon sets (no name clashes).
• components/chip.tsx: round 1's accessibility label and radio state, with round 2's haptics (radio chips tick like a picker).
• apps/mobile/AGENTS.md: round 2's Library, file import, toast and haptics, debate and row-menu bullets, plus round 1's newer Ask and Generate bullets. The routes line lists both rounds' sheets.
• scripts/screenshots.ts: only the header's screen list conflicted; it lists both rounds' groups.

Notes for review

• The web preview renders the DOM component inline, so its bundle grew by pdf.js and mammoth. That bundle only serves the screenshots.
• knip ignores @expo/dom-webview, which Expo loads by name.
• Undo restores a row with its old id, as the website does.
• A rapid double toggle that fails rolls back to the value before the last tap, which is simpler than the website's per-source settle logic.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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

• Source mode: Auto
• Repository: Programcode/DebateLab
• Branch: native-ios/parity-r2-library
• File: .coderabbit.yaml
• Commit: e6591ca
• Layers: Repository YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Free
• Run ID: 5ebfb4c1-21c6-4da9-8c62-5b63c8f2650c

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

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing.

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

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.