- read CLAUDE.md
- check relevant
.claude/rules/ - inspect current implementation
- identify the smallest coherent slice
- define how success will be verified
- keep domain logic independent of UI
- prefer small components and pure functions
- preserve accessibility
- avoid speculative abstractions
- do not introduce dependencies without a concrete reason
- review the diff
- run lint
- run type checking
- run tests if present
- run a production build when appropriate
- run
/eiga-ship-checkfor meaningful milestones
Use focused commits. Prefer commit messages such as:
feat: add local letterboxd importfeat: render director relationshipsfix: preserve graph focus during searchrefactor: isolate graph constructiondocs: define visual direction
Never commit secrets, .env files, generated build output, or personal imported media exports.
The frontend remains a Next.js static export into out/. The separate
eiga-persistent repository owns
Pages Functions, Google OAuth, D1 migrations, and the combined deployment workflow.
It builds a pinned frontend commit and deploys the exported files and Functions
on the same origin, keeping API calls and session cookies same-origin.
Feature branches run checks through pull requests targeting staging or main.
Only pushes to frontend staging dispatch backend deploy.yml on backend staging.
The frontend needs EIGA_DEPLOY_DISPATCH_TOKEN with Actions Write access to the
backend repository. Backend staging pushes deploy the current frontend staging
commit. Feature pushes do not deploy. Legacy STAGING_FRONTEND_REF and
STAGING_BACKEND_REF variables are no longer used.
Create a persistent staging branch from main in each repository when activating
this workflow. Merge feature PRs into staging, verify the shared staging site,
then promote tested work to main. Install the backend workflow on backend
staging before the first frontend staging push. Manual deployment must run on
backend staging; an optional frontend commit must already belong to frontend
staging. Missing staging branches fail explicitly rather than falling back to main.
Staging is https://eiga-staging.pages.dev; production is https://eiga.pages.dev.
They share eiga-db but use fixed separate tables and migration ledgers. Table
prefixes do not prevent one deployment accessing the other environment's tables.
The release order is: merge features into staging, test the pair, merge frontend staging into main, pin its merged commit in the backend release manifest on staging, test that pair, then merge backend staging into main. Frontend main does not deploy production. The backend manifest keeps production disabled until release. Turn off the existing production Pages automatic Git build when adopting this workflow, so frontend merges cannot bypass release orchestration.
For full local development, build this repo and copy out/ into the backend's
ignored public/, configure its ignored .dev.vars, and run npm run dev there.
Use http://localhost:8788 for the app and API together. next dev alone still
supports anonymous import/exploration but has no authentication API.
Do not put Google secrets in this repo or NEXT_PUBLIC_ variables. Runtime
configuration and Wrangler belong to the backend. Neither repo tracks generated
build output. Pages Web Analytics stays off.
The Cloudflare build image's default Node is older than this project's floor
(engines.node is >=22.18, which is where native TypeScript type stripping —
what npm test runs on — became available without a flag). Without the pin the
build fails on a version error that names no file, so the pin is the whole fix.
It has to be a bare version string; nvm reads nothing else, which is why this
explanation lives here rather than in the file.
ORIGIN in src/app/site.ts must match the production origin Cloudflare actually
serves: <project-name>.pages.dev, or a custom domain once one is attached. The
Pages project name is the subdomain, so renaming the project in the dashboard
changes the URL and this line has to follow.
A static export has no request to learn its own host from, so this is baked in at build time: if it is wrong, every shared link's preview card asks the reader's browser for an image on a host you do not own. That failure is invisible locally, because whatever is baked in resolves fine on the machine that baked it.