Sprint 0: Foundation scaffolding rebased onto latest main

[Copilot]

Rebases PR #353 (gamma/sprint0-foundation-dc01) cleanly onto main post-PRs #362–#369. No conflicts. Scope is identical to the original draft — pure scaffolding, zero behavior change.

What's added

• docs/DATA_MODEL.md — Firestore collection audit (shapes, access patterns, composite indexes + stubs for 6 new collections)
• docs/AGENT_STATUS.md — Gamma/Charlie sprint sync artifact
• src/lib/sharedTypes.ts — Append-only shared contract: DailyStreak, Mission, BattlePassState, Crew, RankedSeason, RankedEntry, ShareLink, XP constants
• src/lib/featureFlags.ts — Central flag registry; all 6 flags default false, toggleable via VITE_FF_*
• server/{battlePass,ranked,crews,dailyRewards}.js — No-op handler stubs, all return 501
• firestore.rules — Read-only stub rules for 6 new collections; all writes false

What this PR is NOT

• No UI changes
• No live endpoints (stubs return 501, nothing calls them)
• No Firestore writes enabled
• No Stripe / tier / payment touches
• No flags flipped to true

Engagement-loop consumers

PRs #354–#358 build on this scaffolding and will land incrementally on their own merits, not as a batch sprint push.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/graphql
  • Triggering command: /usr/bin/gh gh auth status --shared-client-connection (http block)
  • Triggering command: /usr/bin/gh gh pr ready 353 _mod�� get --global rgo/bin/git ame (http block)
  • Triggering command: `/usr/bin/gh gh pr edit 353 --body ## Summary

Sprint 0 foundation scaffolding, rebased cleanly onto the latest main (post PRs #362���#369). Zero behavior change ��� this PR is pure scaffolding.

> Rebase note: Branch rebased onto main as of commit 6504e4e (post-PR #369). No --global ndor/bin/git user.name` (http block)

• https://api.github.com/repos/driver727-pixel/Punch-Skater/pulls/353
  • Triggering command: /usr/bin/gh gh api repos/driver727-pixel/Punch-Skater/pulls/353 --jq .draft, .title (http block)
  • Triggering command: /usr/bin/gh gh api repos/driver727-pixel/Punch-Skater/pulls/353 --jq .draft, .title --disable-features=AcceptCHFrame,AvoidUnnecessaryBeforeUnloadCheckSync,DestroyProfileOnBrowserClose,DialMediaRouteProvider,GlobalMediaControls,HttpsUpgrades,LensOverlay,MediaRo--database=/root/.config/google-chrome/Crash Reports (http block)
  • Triggering command: /usr/bin/curl curl -s -H Authorization: ****** REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Background

PR #353 ("Sprint 0: Foundation scaffolding — data model, shared types, feature flags, server stubs, Firestore rules") is currently a draft branched from an older main. The repo owner wants to land this foundation so future engagement-loop work can build on it incrementally, without rushing.

PR: #353
Branch: gamma/sprint0-foundation-dc01

Task

1. Rebase gamma/sprint0-foundation-dc01 onto the latest main.

   • Resolve any conflicts conservatively. The repo has had heavy churn in the last 24 hours around board art, card layout, and weather routes (PRs Feature/forged card model #362–Bump board asset version to bust battery image cache #369 merged).
   • Likely conflict zones: server/index.js (route wiring), firestore.rules, possibly src/index.css. Preserve both sides — keep the new stub registrations from Sprint 0: Foundation scaffolding — data model, shared types, feature flags, server stubs, Firestore rules #353 alongside any newer changes from main.

2. Verify the foundation remains scope-pure. PR Sprint 0: Foundation scaffolding — data model, shared types, feature flags, server stubs, Firestore rules #353 should still only add:

   • docs/DATA_MODEL.md, docs/AGENT_STATUS.md
   • src/lib/sharedTypes.ts (append-only contract)
   • src/lib/featureFlags.ts (all flags default false)
   • Server stubs: server/battlePass.js, server/ranked.js, server/crews.js, server/dailyRewards.js (no-op handlers only)
   • Read-only Firestore rules for the 6 new collections (all writes false)

   If during the rebase you find any commits that snuck in actual feature behavior, drop them. The point of this PR is zero behavior change.

3. Run validation locally:

   • npm install
   • npm run lint — must be clean
   • npx tsc --noEmit — must be clean
   • npm run test:server — should pass at the same level as main (note: there is one known pre-existing failure being addressed in a separate PR; do not let that block you, but do not make it worse)

4. Mark the PR ready for review (un-draft it).

5. Update the PR description with:

   • A note that the rebase preserved scope (no behavior changes, all flags default false).
   • A short "what NOT to expect from this PR" section listing: no new UI, no new endpoints called, no Firestore writes enabled, no Stripe / tier / payment changes.
   • A pointer to the engagement-loop PRs (feat: Charge Up system — 8-hour free forge timer with capped rarity #354–feat: Battle Pass seasonal progression system #358) as the consumers of this scaffolding, with a note that they will be landed incrementally and on their own merits, not as a single sprint push.

Out of scope (very important)

• Do not touch Stripe, payment, tier, or checkout code in any way. The repo owner handles those via Cursor.
• Do not flip any feature flag from false to true.
• Do not add, modify, or merge code from PRs feat: Charge Up system — 8-hour free forge timer with capped rarity #354, Add authoritative Ozzies wallet, mission reward API, and Card Forge spend path #355, feat: Daily Missions system — 3 rotating missions per day with XP + Ozzies #356, feat: Weekly Heat card + weather quest rotation #357, or feat: Battle Pass seasonal progression system #358 into this branch. Each will be reviewed and landed on its own.
• Do not add new files beyond what Sprint 0: Foundation scaffolding — data model, shared types, feature flags, server stubs, Firestore rules #353 already introduces (other than minor conflict-resolution additions if a new file from main needs to coexist).
• Do not rebase or modify any other open PR.

Deliverable

A clean, conflict-free, ready-for-review (non-draft) PR #353 that the owner can merge with confidence as a pure-scaffolding change.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Take a look at the total repo, and help me figure out what to do next?

Assistant: # What to do next — a triage + roadmap

Here's my read on the current state of the repo and a concrete action plan, ordered by impact and urgency.

Snapshot

Signal	Reading
Repo age	~21 days old, very actively pushed (last commit hours ago)
Visibility	Public, live at punchskater.com, 1 star, single-owner
Open PRs	9 — mostly drafts
Recent merge cadence	High — ~10 PRs merged in the last 24 hours, all small board/card polish via Copilot/Cursor agents
Big in-flight work	A 6-PR "Sprint 0" engagement-loop initiative (PRs #353–#358) sitting in draft
Launch checklist	Has unchecked items in README.md

The picture

You're in a rapid-iteration polish phase on the existing forge (board art, card layout, weather rate limits) while a coordinated "engagement loop" expansion (streaks, missions, weekly heat, battle pass, charge-up) is staged but not landed. That tension is the thing to resolve next.

---

Recommended order of work

1. Triage open PRs first (do this today)

You have 9 open PRs. Decide each:

data:
- url: "https://github.com/driver727-pixel/Punch-Skater/pull/306"
  repository: "driver727-pixel/Punch-Skater"
  state: "open"
  draft: false
  title: "fix: image generation 503 when Firebase Admin is not configured"
  number: 306
  created_at: "2026-04-21T00:00:00Z"
  closed_at: ""
  merged_at: ""
  labels: []
  author: "Copilot"
  comments: 0
- url: "https://github.com/driver727-pixel/Punch-Skater/pull/341"
  repository: "driver727-pixel/Punch-Skater"
  state: "open"
  draft: false
  title: "fix: suppress redundant STRIPE_WEBHOOK_SECRET warning when Stripe is unconfigured"
  number: 341
  created_at: "2026-04-22T00:00:00Z"
  ...

</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

*This pull request was created from Copilot chat.*
>