What to do next on this site

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site whensthegame.com.

WHY IT MATTERS
Confirm the certificate is valid and HTTPS is forced, the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, CSP), and the Agents-First endpoints expose only public, non-sensitive information — trustworthy to humans and safe for the agents reading it.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Build the definitive Streaming & TV cornerstone guide — on the site whensthegame.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Streaming & TV anywhere — the resource the whole site points to. Deep, current, expertly structured, and link-worthy. This anchors the site's authority and is the page most likely to earn rankings and citations.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Streaming & TV — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Streaming & TV resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Lock down sensitive data — nothing private is publicly reachable — on the site whensthegame.com.

WHY IT MATTERS
Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site whensthegame.com.

WHY IT MATTERS
Assume a determined automated, AI-driven attacker. Enforce HTTPS, add a sensible Content-Security-Policy plus the standard security headers, eliminate open redirects and reflected user input, validate and rate-limit any form, and ensure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data — never internal or personal information.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Add an interactive tool and an email capture for Streaming & TV — on the site whensthegame.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Streaming & TV (a calculator, checklist, finder, or quiz) plus a tasteful email capture. Tools earn repeat visits, backlinks, and a first-party audience the site actually owns.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Streaming & TV — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Streaming & TV resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site whensthegame.com.

WHY IT MATTERS
Give the homepage a clear point of view, a memorable hero, and real utility above the fold. A distinctive, intentional design lifts trust, time-on-page, and the Agents-First score out of generic-template territory.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Streaming & TV — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Streaming & TV resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Per-matchup answer pages, generated daily — on the site whensthegame.com.

WHY IT MATTERS
The domain is a question — answer it at scale. Generate a page per upcoming game ('When do the Cowboys play next?') with kickoff time, channel, and streaming home, built from the gamesked.com feed.json infrastructure already running. Thousands of long-tail queries, one template. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Publish: The 2026 live-TV price hikes and the cheapest path to the games — on the site whensthegame.com.

WHY IT MATTERS
Trending angle in Streaming & TV. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Streaming & TV reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Publish: Cord-cutting math for a typical household this year — on the site whensthegame.com.

WHY IT MATTERS
Trending angle in Streaming & TV. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Streaming & TV reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Team-by-team next-game landing pages — on the site whensthegame.com.

WHY IT MATTERS
A permanent page per major team — /cowboys/, /longhorns/ — always showing the next game first, then the remaining schedule. Permanent URLs accumulate rank while the gamesked feed keeps content perpetually current: evergreen shells, live filling. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Publish: Which service locked up the sports rights you care about — on the site whensthegame.com.

WHY IT MATTERS
Trending angle in Streaming & TV. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Streaming & TV reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
What-channel cheatsheets per league season — on the site whensthegame.com.

WHY IT MATTERS
Season-start pages mapping each league's broadcast rights — which NFL windows sit on which networks, where MLS streams — updated when rights shift. Rights confusion regenerates every season; a clean cheatsheet earns links from fan forums each August and hub status year-round. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
AdSense on game-day spike pages — on the site whensthegame.com.

WHY IT MATTERS
Enable pub-7759195213529699 across matchup and team pages, whose traffic spikes reliably every game day with brand-safe intent. Junk categories are blocked account-wide; schedule pages are the cleanest high-frequency ad inventory the sports cluster generates. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
TicketNetwork blocks on every matchup page — on the site whensthegame.com.

WHY IT MATTERS
Each game page carries the live TicketNetwork affiliate block for that matchup's resale inventory, alongside honest real-Ticketmaster links per network pattern. 'When is the game' and 'can I still go' are the same visitor minutes apart; the placement closes that loop. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Publish: Password-sharing crackdowns and the workarounds left — on the site whensthegame.com.

WHY IT MATTERS
Trending angle in Streaming & TV. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Streaming & TV reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Deepen the main Streaming & TV guide with current data and examples — on the site whensthegame.com.

WHY IT MATTERS
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template.

HOW TO APPROACH IT
1. Audit the flagship Streaming & TV page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Streaming & TV.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Watch-at-home setup guide with Amazon links — on the site whensthegame.com.

WHY IT MATTERS
An honest 'never miss kickoff' page — OTA antennas by market, streaming devices, red-zone multiview setups — tagged colinfirthfan-20, linked from every matchup page footer. The audience is definitionally arranging how to watch; the guide serves and monetizes that. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Stadium scoreboard aesthetic with countdown heroes — on the site whensthegame.com.

WHY IT MATTERS
Art-direct as a jumbotron: each matchup page opens with a giant LED-dot-matrix countdown to kickoff, team colors as the page accent, channel info in broadcast-bug style corner chips. The scoreboard idiom answers the domain's question visually before any text. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Schedule rows as ticket-stub strips — on the site whensthegame.com.

WHY IT MATTERS
Team schedules render as perforated ticket-stub rows — date on the stub, opponent and channel on the body, a torn edge for completed games. The stub motif is instantly sports-legible, and the torn-past treatment shows season progress at a glance. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
One-sentence answers with BroadcastEvent schema — on the site whensthegame.com.

WHY IT MATTERS
Every matchup page opens with the literal answer — 'The Cowboys play Sunday, 3:25 PM CT on FOX' — plus BroadcastEvent JSON-LD. This domain's whole thesis is being the assistant's citation for game-time queries; structure is the moat. Verify 90+ via af-deploy.py. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Add an FAQ answering the top questions in Streaming & TV — on the site whensthegame.com.

WHY IT MATTERS
Pull the real questions people ask in Streaming & TV and answer them plainly. Mark up with FAQ schema for rich results.

HOW TO APPROACH IT
1. Audit the flagship Streaming & TV page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Streaming & TV.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site whensthegame.com.

WHY IT MATTERS
The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s.

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Add-to-calendar buttons on every game — on the site whensthegame.com.

WHY IT MATTERS
One-tap .ics download per matchup — kickoff time, channel in the event notes — with no signup required. Calendar capture is the utility that turns a one-question visitor into a recurring one, and each event body carries the page URL back to the site. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Keep the live / news feed updated on cadence (2×/day) — on the site whensthegame.com.

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Streaming & TV items and pinging IndexNow each run.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Streaming & TV: attributed, links out, and running on a 2x/day cadence.
2. Make sure each run pings IndexNow and the items are genuinely fresh and relevant.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The feed publishes fresh, correctly-attributed Streaming & TV items on schedule and is discovered quickly.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site whensthegame.com.

WHY IT MATTERS
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Add Article + FAQ structured data — on the site whensthegame.com.

WHY IT MATTERS
Schema.org markup earns richer results and helps answer-engines cite the page correctly.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site whensthegame.com.

WHY IT MATTERS
A tight internal-link web spreads authority and keeps visitors moving through the site.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Refresh the /videos/ playlist with current, embeddable uploads — on the site whensthegame.com.

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Streaming & TV videos. Re-verify embeds.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Streaming & TV videos that ALLOW embedding — verify each embed actually plays.
2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: whensthegame.com (live at https://whensthegame.com/), a Streaming & TV site in the WholeTech network, served from /var/www/whensthegame.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for whensthegame.com and no other site — make all changes on whensthegame.com. Act like a senior editor and web engineer who knows the Streaming & TV niche cold.

GOAL (on whensthegame.com)
Verify affiliate links and ad placement resolve correctly — on the site whensthegame.com.

WHY IT MATTERS
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value.

HOW TO APPROACH IT
1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup.
2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Links resolve and can earn, and placement is tasteful and does not hurt the reading experience.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.