Guides — start here

How-to pages: coding standards, the gates, the build and device loops, environments, deployment and the assessments that decided how this repo is run.

Read before changing a gate, a hook, a workflow or the operating manual

1. Quality gates — one section per check: / test: / deploy: script, with what each cannot see · 2. Claude Code operations — driving the apps, ports, the stale-bundle proof, the Windows shell traps · 3. Claude context architecture — where new knowledge goes (the placement policy) · 4. Coding standards. Gates: check:context · check:claims · test:hooks. Every new gate is mutation-tested in both directions and at least two tests spawn its CLI (a test that imports the function cannot see a driver that never runs).

Pages

• Adding a Feature
• Adding an Edge Function
• Android + iOS build & test — the release front door
• Apple Developer Program enrolment — the revert checklist
• AWS compute for our GitHub Actions runners
• Claude context architecture — the operating manual and the always-loaded context
• Coding Standards
• Deployment & Promotion
• Dev test-user reset
• Device test suite — consumer auth, onboarding and the app lock
• Environment Strategy
• GitHub Actions usage forensics
• Google OAuth + Sign in with Apple — Supabase social-auth setup
• iOS build & device testing — step by step
• macOS · iOS build environment
• Database Migrations
• Parity verification
• Production credentials & environment setup
• quality-gates
• Testing Strategy
• UI quality assurance — catching layout regressions before merge
• Windows Build Environment & Repo Relocation