Stome

Stome stores local study rooms and notes in SQLite. Create, open, rename, and confirm deletion of rooms. Each room shows ordered note chunks with subject tags, optional source links, and highlight annotations. The existing Markdown import and original notes/companion screens remain available from the room list. There are no accounts or sync.

npm install
npx expo start

• npm run web starts the Expo web dev server. metro.config.js adds the COOP and COEP headers on bundled requests. In this SDK the HTML document from expo start --web does not include those headers.
• npm run web:sqlite serves that same dev server through http://127.0.0.1:8081 and adds Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: credentialless to the document. Browser SQLite needs those document headers. Expo itself listens on port 8082 in this mode.
• npm run web:lan is the same proxy for other devices on your network, such as an iPad. Browsers only give browser SQLite its storage on https or on localhost, so http://<lan-ip>:8081 fails with "navigator.storage not available". This mode serves https://<lan-ip>:8081 with a self-signed certificate written to .expo/web-cert/cert.pem, and sends Cross-Origin-Embedder-Policy: require-corp because Safari does not support credentialless. Trust the certificate on the device: AirDrop it, install the profile, then turn it on under Settings > General > About > Certificate Trust Settings. Set EXPO_INTERNAL_PORT if port 8082 is already taken. The iPad cannot run Node or npm run companion. Run the companion on the laptop, open the web:lan https address in Safari, and leave the companion address as that same https origin. The page forwards /v1/status and /v1/tool to the laptop companion at 127.0.0.1:8787 and still requires the pairing token. http://127.0.0.1:8787 on the iPad is the iPad itself.
• npm run companion starts the laptop-local mock AI companion. See HARNESS.md for the ask, confirm, and reload path. The companion does not call a live model unless you start it with a live provider.
• npm run ios and npm run android open a simulator or Expo Go when that tooling is installed.

Standard expo-sqlite is included in Expo Go. This project does not commit ios/ or android/ directories.

Use Node 22.23.4 (.nvmrc). That release is inside Expo SDK 58's Node ^22.13.0 range, and it still accepts the SQLite and type-stripping flags in the schema script.

npm ci
npm run check

npm run check runs:

• npm run typecheck — tsc --noEmit
• npm run lint — expo lint
• npm run check:schema — note schema and migrations through Node's built-in node:sqlite
• npm run check:harness — harness sessions, mock provider, confirmation, and companion origin/token checks, also through node:sqlite

GitHub Actions runs npm run check on pull requests and on pushes to main. The harness checks were added to that existing script, not as a second workflow. A following build job runs npx expo export --platform web and uploads dist for 7 days. That export is Metro's production bundle for the laptop browser, including the SQLite WebAssembly asset. It is not an iOS or Android native compile, and the job does not sign, deploy, or call EAS. The schema and harness scripts can print Node's experimental SQLite warning; a command passes when its assertions pass.

render-web serves that dist export with Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: credentialless, then opens Chrome. It fails if a route throws, the database error boundary appears, the page is not cross-origin isolated, or the expected text is missing. Covered routes are /, /today (Nothing due today), /notes, /recent, and /import (bring your notes). Web opens a 1280px window, where home reads “Your rooms”. The Android emulator is phone-width, where an empty home reads “No rooms yet”. Room and review routes need a saved room id and are not opened. Screenshots and report.json are kept for 7 days.

render-android boots a GitHub-hosted Android emulator, installs the debug app with npx expo run:android, and checks the same five screens through the stome:// scheme. It fails when the screen text is missing or Metro/logcat reports a TypeError, ReferenceError, SyntaxError, or Invariant Violation. That is the Android runtime, not a phone-sized browser and not the web export. iOS is not covered: the iOS Simulator does not run on ubuntu-latest, and this workflow does not add a macOS job, so there is no iOS result to count as a pass or a skip.

npm run check:schema and npm run check:harness use Node's built-in SQLite. They are not the Expo SQLite driver on iOS, Android, or web. check:harness does not replace opening the Expo web app. The workflow boots an Android emulator only in render-android. It does not sign a build or call a live model API. Design-theme tests stay out of this check until that package is in the tree with its own lockfile-backed command.