docs: rename default branch to main

web/README.md

@@ -34,5 +34,5 @@ npm run build         # default — root basePath, for Cloudflare Pages
 npm run build:gh      # /loto basePath, for tiennm99.github.io/loto manual export
 ```
 
-Static export to `build/`. Deployed to Cloudflare Pages from `master`
+Static export to `build/`. Deployed to Cloudflare Pages from `main`
 (set up via the CF dashboard — see `docs/deployment-guide.md`).

web/docs/deployment-guide.md

@@ -16,7 +16,7 @@ either profile without code changes.
 ## Production Deployment — Cloudflare Pages
 
 Primary deploy. Set up via the Cloudflare dashboard once; subsequent
-pushes to `master` trigger automatic builds + deploys.
+pushes to `main` trigger automatic builds + deploys.
 
 1. dash.cloudflare.com → Workers & Pages → Create → Pages → Connect to Git
    → pick the repo
@@ -24,7 +24,7 @@ pushes to `master` trigger automatic builds + deploys.
    - Framework preset: SvelteKit
    - Build command: `npm run build`
    - Build output directory: `build`
-   - Production branch: `master`
+   - Production branch: `main`
 3. After first deploy, add the custom domain:
    Project → Custom domains → `loto.miti99.com`. Cloudflare gives DNS
    records to add at your registrar (or auto-configures if `miti99.com` is

web/docs/project-overview-pdr.md

@@ -31,7 +31,7 @@ State is entirely client-side. Each page/card instance uses a unique localStorag
 
 ## Deployment
 
-- **Production**: GitHub Pages auto-deploys from `master` branch via `.github/workflows/deploy.yml`. App is served at `/loto` basePath.
+- **Production**: Cloudflare Pages auto-deploys from `main` branch (configured via the CF dashboard, no GitHub Actions). Custom domain `loto.miti99.com`. `npm run build:gh` is a manual fallback for GitHub Pages at the `/loto` basePath.
 - **Development**: `npm run dev` (local), `npm run dev:codeserver` (code-server via proxy).
 - **Build**: `npm run build` generates static export to `build/` directory.