Add sample channel dataset and Stripe + Firebase billing integration stubs

[Copilot]

Adds foundation for tiered channel access with Stripe subscriptions and Firebase backend. Draft PR pending credentials and deployment permissions.

Dataset

• src/data/channels.full.json: 210 channels (IDs 25-234). Gold-tier: 26, 33, 36, 40
• src/utils/loadChannels.js: Loader with require() + fs.readFileSync fallback

Client-side Gating Stub

• src/components/ChannelLock.stubs.jsx: Mock entitlement check demo
  • useUserEntitlements() returns { tier: 'silver' }
  • Renders lock overlay + "Upgrade to Gold" CTA for gold channels
  • Replace mock with Firestore queries

const { tier } = useUserEntitlements(); // TODO: Fetch from Firestore
if (channel.tier === 'gold' && tier !== 'gold') {
  return <LockOverlay>Upgrade to Gold</LockOverlay>;
}

Stripe Webhook Skeleton

• functions/stripe-webhooks/index.js: Express app for Cloud Functions
  • Reads STRIPE_WEBHOOK_SECRET, STRIPE_SECRET_KEY from env
  • TODO: stripe.webhooks.constructEvent() signature verification
  • TODO: Update Firestore on invoice/subscription events (map via metadata.firebaseUid)

Documentation

• functions/README.md: Deploy sequence, config commands
• docs/STRIPE_FIREBASE_INTEGRATION.md: Schema (/users/{uid}, /entitlements/{uid}), flow, security
• README/DEVNOTES.md: CI credential requirements (Stripe keys, Firebase service account, Android keystore)

---

Checklist for Maintainers

• Confirm gold-tier channel IDs (26, 33, 36, 40) or provide additional IDs
• Provide Stripe test keys or invite Stripe user for product/price setup
• Grant Firebase deployer permissions for functions and Firestore
• Provide CI signing access or keystore for APK generation

No secrets committed. All TODOs marked for manual wiring post-access.

Original prompt

Create a draft pull request that adds a large sample channel dataset and starter Stripe + Firebase billing integration stubs. Do NOT include any real secrets. Keep the PR as a draft for review.

Files to add (exact paths and high-level contents):

1. src/data/channels.full.json

• Combined dataset with 210 channels (IDs 25-220). This includes the original 60 channels plus 150 auto-generated synthetic channels. Several channels are marked with a tier property; gold-tier channel ids are 26, 33, 36, 40. Streams and logos use placeholder domains and placeholder image URLs. Example object shape for each channel: { id, name, country, language, category, logo, stream, epg, type, tier }.

2. src/utils/loadChannels.js

• Export a function loadChannels() that loads and returns src/data/channels.full.json. Use require('../data/channels.full.json') with a fallback to fs.readFileSync for environments where JSON require may fail. Return [] on error and log errors to console.

3. src/components/ChannelLock.stubs.jsx

• A React component demonstrating client-side gating. Include a mock hook useUserEntitlements() returning a sample entitlement (tier: 'silver'). If channel.tier === 'gold' and user.tier !== 'gold', render a lock overlay with an "Upgrade to Gold" CTA. Include comments explaining to replace the mock with Firestore-backed entitlement checks.

4. functions/stripe-webhooks/index.js

• An Express app skeleton intended for Firebase Cloud Functions to receive Stripe webhooks. Use bodyParser.raw({ type: 'application/json' }) and show TODOs for verifying signatures with stripe.webhooks.constructEvent. Read STRIPE_WEBHOOK_SECRET and STRIPE_SECRET_KEY from env. Parse req.body safely after verification. Route invoice.payment_succeeded, invoice.payment_failed, customer.subscription.* to TODO handlers that update Firestore (explain mapping via metadata: firebaseUid). Do not include any real secrets.

5. functions/README.md

• Explain how to deploy the webhook functions, how to set Firebase functions config (stripe.secret_key, stripe.webhook_secret), a reminder to verify signatures, and a short deploy sequence: firebase functions:config:set ... && firebase deploy --only functions.

6. docs/STRIPE_FIREBASE_INTEGRATION.md

• Integration overview: suggested Firestore schema (/users/{uid}, /users/{uid}/subscriptions/{subId}, /entitlements/{uid}), mapping stripe customers via metadata, recommended flow (client -> function creates Checkout Session -> Stripe Checkout -> webhook updates Firestore -> client reads entitlements), and security notes.

7. README/DEVNOTES.md

• Checklist for maintainers listing required credentials and env var names for CI: STRIPE_TEST_SECRET, STRIPE_TEST_PUBLISHABLE, STRIPE_LIVE_SECRET, STRIPE_LIVE_PUBLISHABLE, STRIPE_WEBHOOK_SECRET, FIREBASE_SERVICE_ACCOUNT (base64), FIREBASE_PROJECT_ID, ANDROID_KEYSTORE (base64) or KEY_ALIAS/KEYSTORE_PASSWORD/KEY_PASSWORD. Include steps to open the draft PR, staging verification, and production promotion steps.

Constraints & requirements:

• Open the PR as a draft so keys can be applied later and further wiring can be done after access is granted.
• Do NOT commit any secrets or service account JSON; code must read secrets from process.env and include clear README instructions.
• Keep changes minimal and well-documented with TODOs where manual configuration is required (Stripe product creation, webhook secret insertion, Firebase deploy with proper permissions, replacing placeholder streams with licensed feeds).

PR body (include this description verbatim in the pull request):

• Adds src/data/channels.full.json with 210 channels (IDs 25-220). Gold-tier channel ids: 26, 33, 36, 40.
• Adds src/utils/loadChannels.js to load the channels JSON.
• Adds src/components/ChannelLock.stubs.jsx gating stub demonstrating entitlement checks and Upgrade CTA.
• Adds functions/stripe-webhooks/index.js webhook skeleton (reads env vars, TODOs for signature verification and Firestore updates).
• Adds functions/README.md with deploy instructions and environment variable guidance.
• Adds docs/STRIPE_FIREBASE_INTEGRATION.md with integration plan, schema and notes.
• Adds README/DEVNOTES.md listing credentials required and next steps.

Checklist for maintainers (include in PR body):

• Confirm gold-tier channel ids (26, 33, 36, 40) or provide additional IDs to mark gold.
• Provide Stripe test keys or invite a Stripe user so products/prices can be created.
• Provide Firebase service account or grant deployer permissions for functions and Firestore so webhook functions can be deployed.
• Provide CI signing access or keystore for APK generation if you want a signed build.

If anything is unclear, ask for clarification. Otherwise create the draft PR on the default branch of STACEY77/RAG7 and return the PR URL and a short summary of what was added. Thank you.

This pull request was created as a result of the following prompt from Copilot chat.

Create a draft pull request that adds a large sample channel dataset and starter Stripe + Firebase billing integration stubs. Do NOT include any real secrets. Keep the PR as a draft for review.

Files to add (exact paths and high-level contents):

1. src/data/channels.full.json

• Combined dataset with 210 channels (IDs 25-220). This includes the original 60 channels plus 150 auto-generated synthetic channels. Several channels are marked with a tier property; gold-tier channel ids are 26, 33, 36, 40. Streams and logos use placeholder domains and placeholder image URLs. Example object shape for each channel: { id, name, country, language, category, logo, stream, epg, type, tier }.

2. src/utils/loadChannels.js

• Export a function loadChannels() that loads and returns src/data/channels.full.json. Use require('../data/channels.full.json') with a fallback to fs.readFileSync for environments where JSON require may fail. Return [] on error and log errors to console.

3. src/components/ChannelLock.stubs.jsx

• A React component demonstrating client-side gating. Include a mock hook useUserEntitlements() returning a sample entitlement (tier: 'silver'). If channel.tier === 'gold' and user.tier !== 'gold', render a lock overlay with an "Upgrade to Gold" CTA. Include comments explaining to replace the mock with Firestore-backed entitlement checks.

4. functions/stripe-webhooks/index.js

• An Express app skeleton intended for Firebase Cloud Functions to receive Stripe webhooks. Use bodyParser.raw({ type: 'application/json' }) and show TODOs for verifying signatures with stripe.webhooks.constructEvent. Read STRIPE_WEBHOOK_SECRET and STRIPE_SECRET_KEY from env. Parse req.body safely after verification. Route invoice.payment_succeeded, invoice.payment_failed, customer.subscription.* to TODO handlers that update Firestore (explain mapping via metadata: firebaseUid). Do not include any real secrets.

5. functions/README.md

• Explain how to deploy the webhook functions, how to set Firebase functions config (stripe.secret_key, stripe.webhook_secret), a reminder to verify signatures, and a short deploy sequence: firebase functions:config:set ... && firebase deploy --only functions.

6. docs/STRIPE_FIREBASE_INTEGRATION.md

• Integration overview: suggested Firestore schema (/users/{uid}, /users/{uid}/subscriptions/{subId}, /entitlements/{uid}), mapping stripe customers via metadata, recommended flow (client -> function creates Checkout Session -> Stripe Checkout -> webhook updates Firestore -> client reads entitlements), and security notes.

7. README/DEVNOTES.md

• Checklist for maintainers listing required credentials and env var names for CI: STRIPE_TEST_SECRET, STRIPE_TEST_PUBLISHABLE, STRIPE_LIVE_SECRET, STRIPE_LIVE_PUBLISHABLE, STRIPE_WEBHOOK_SECRET, FIREBASE_SERVICE_ACCOUNT (base64), FIREBASE_PROJECT_ID, ANDROID_KEYSTORE (base64) or KEY_ALIAS/KEYSTORE_PASSWORD/KEY_PASSWORD. Include steps to open the draft PR, staging verification, and production promotion steps.

Constraints & requirements:

• Open the PR as a draft so keys can be applied later and further wiring can be done after access is granted.
• Do NOT commit any secrets or service account JSON; code must read secrets from process.env and include clear README instructions.
• Keep changes minimal and well-documented with TODOs where manual configuration is required (Stripe product creation, webhook secret insertion, Firebase deploy with proper permissions, replacing placeholder streams with licensed feeds).

PR body (include this description verbatim in the pull request):

• Adds src/data/channels.full.json with 210 channels (IDs 25-220). Gold-tier channel ids: 26, 33, 36, 40.
• Adds src/utils/loadChannels.js to load the channels JSON.
• Adds src/components/ChannelLock.stubs.jsx gating stub demonstrating entitlement checks and Upgrade CTA.
• Adds functions/stripe-webhooks/index.js webhook skeleton (reads env vars, TODOs for signature verification and Firestore updates).
• Adds functions/README.md with deploy instructions and environment variable guidance.
• Adds docs/STRIPE_FIREBASE_INTEGRATION.md with integration plan, schema and notes.
• Adds README/DEVNOTES.md listing credentials required and next steps.

Checklist for maintainers (include in PR body):

• Confirm gold-tier channel ids (26, 33, 36, 40) or provide additional IDs to mark gold.
• Provide Stripe test keys or invite a Stripe user so products/prices can be created.
• Provide Firebase service account or grant deployer permissions for functions and Firestore so webhook functions can be deployed.
• Provide CI signing access or keystore for APK generation if you want a signed build.

If anything is unclear, ask for clarification. Otherwise create the draft PR on the default branch of STACEY77/RAG7 and return the PR URL and a short summary of what was added. Thank you.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.