Add channel dataset and Stripe + Firebase billing integration stubs

[Copilot]

Adds 210-channel dataset with tier-based gating and serverless billing webhook scaffolding. Draft PR for credential injection and deployment review.

Files Added

Dataset & Loader

• src/data/channels.full.json - 210 channels (IDs 25-220). Gold tier: 26, 33, 36, 40
• src/utils/loadChannels.js - JSON loader with fs fallback, error handling

Client-Side Gating

• src/components/ChannelLock.stubs.jsx - React component demonstrating tier-based access control with mock entitlements hook. Placeholder for Firestore-backed checks.

Webhook Infrastructure

• functions/stripe-webhooks/index.js - Express app for Firebase Functions. Handles invoice., customer.subscription. events. TODOs: signature verification, Firestore updates via metadata mapping
• functions/README.md - Deploy sequence, functions:config:set for stripe.secret_key and stripe.webhook_secret

Documentation

• docs/STRIPE_FIREBASE_INTEGRATION.md - Firestore schema (/users/{uid}, /subscriptions/{subId}, /entitlements/{uid}), Checkout Session flow, security notes
• README/DEVNOTES.md - CI credential checklist (STRIPE_, FIREBASE_, ANDROID_KEYSTORE vars)

Example Usage

// Load channels with automatic fallback
const channels = loadChannels();
const goldChannels = channels.filter(ch => ch.tier === 'gold');

// Gate premium content
<ChannelLock channel={channel}>
  <VideoPlayer stream={channel.stream} />
</ChannelLock>

Maintainer Checklist

• 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

No secrets committed. All configuration reads from process.env.

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.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.