2001105254-netizen/RacePulsePH / .agents/skills/racepulse-release-engineering
racepulse-release-engineering
VerifiedManage RacePulsePH build pipelines, generated Firestore rules, rollout flags, staged deployments, rollbacks, versioning and dependency lockfiles. Use when preparing releases, editing firebase.json, running deploy scripts or updating dependencies.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
| references/checklist.md | markdown | 3.1 KB |
references/checklist.md
View on GitHub# Release engineering, flags and rollback checklist
Harvested from the backend concepts list (items 6, 51 to 55, 102 to 108: CI/CD, Feature Flags, Blue-Green Deployment, Canary Releases, Rolling Deployments, Rollbacks, API Versioning, Semantic Versioning, Infrastructure as Code, Build Caching, Dependency Hell) and mapped to RacePulsePH.
## 1. Deterministic verification pipeline (item 6)
Before any production deploy, run the repository verification pipeline in order:
1. `npm run generate:access` (`node scripts/build-access-rules.cjs`) to regenerate `firestore.rules` and policy modules.
2. `npm run lint` (`tsc --noEmit`) for static type checking.
3. `npm run build` (`vite build` + `esbuild server.ts --outfile=dist/server.cjs`) to verify both the browser SPA and the bundled LAN server compile cleanly.
4. `node --test tests/timing-sequence.test.cjs` and `npm run verify:rbac` (`node scripts/verify-rbac.cjs`, which writes `output/rbac-verification.json` with a cryptographic source hash from `scripts/verification-hash.cjs`).
## 2. Feature flags and staged rollout (items 51 to 55)
- **Access rollout flag (`accessSystem/rollout.enforcementReady`):**
- Keep `enforcementReady` false or absent until emulator tests, request-level tests, rule deploys and data backfill succeed (`racepulse-access`, `racepulse-access-validation`).
- `scripts/migrate-access.cjs --apply --activate` refuses to activate unless `output/rbac-verification.json` matches the current source hash.
- **Per-race operational flags:**
- `race.registrationOpen`, `race.onlinePaymentEnabled`, `race.registrationCloseDate` and `race.paymentFeeMode` (`functions/index.js` lines 154 to 222) let organizers enable or pause paid checkout per event without redeploying code.
- **Isolated Functions codebases (`firebase.json` lines 2 to 14):**
- `default` (`functions/`) and `rbac` (`functions/rbac/`) are separate codebases in `firebase.json`, allowing targeted deployments and isolated rollbacks.
## 3. API and storage schema versioning (items 102 and 103)
- **Local storage key versioning:** when changing the shape of persisted browser queues, bump the key suffix (`racepulse_pending_chip_reads_v1` to `racepulse_pending_chip_reads_v2:${uid}:${raceId}` in `src/lib/offlineScanQueue.ts`) and migrate the current user's items cleanly.
- **Bridge and timing compatibility (`docs/finish-precision.md`):** `server.ts` and `src/lib/preciseTime.ts` accept both legacy bridge payloads (`HH:MM:SS.fffffff`) and current compact timestamps (`HH:MM:SSfffff`) so an updated web app continues working with an older `Timing Station.exe` binary.
## 4. Build artifacts and dependency hygiene (items 104, 107, 108)
- **Multi-target builds:**
- Web + LAN server: `npm run build` outputs `dist/` and `dist/server.cjs`.
- Android: `npm run android:sync` builds `dist/` and syncs Capacitor into `android/`.
- Windows Timing Station: `rfid-station/package-station.ps1` packages the desktop wrapper around `dist/server.cjs`.
- **Never patch compiled files:** per `R-33` and `AGENTS.md`, always edit source files under `src/`, `functions/`, `server.ts` or `scripts/firestore-base.rules` and run the build/generator scripts.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |