What to do next on this site

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

GOAL (on colinfirth.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site colinfirth.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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Build the definitive Film & Actors cornerstone guide — on the site colinfirth.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Film & Actors 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 Film & Actors — 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 Film & Actors 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site colinfirth.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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site colinfirth.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 Film & Actors — 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 Film & Actors 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Lock down sensitive data — nothing private is publicly reachable — on the site colinfirth.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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Add an interactive tool and an email capture for Film & Actors — on the site colinfirth.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Film & Actors (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 Film & Actors — 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 Film & Actors 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Publish: Awards-season momentum and the films to watch — on the site colinfirth.com.

WHY IT MATTERS
Trending angle in Film & Actors. 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 Film & Actors 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Complete filmography database with detail pages — on the site colinfirth.com.

WHY IT MATTERS
Build a complete Colin Firth filmography — every film and series with year, role, director, and awards drawn from documented sources — each title getting a detail page. Actor-plus-title queries are the bread of fan-site traffic, and a complete, accurate database captures the entire long tail. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Publish: The streaming-vs-theatrical release shift — on the site colinfirth.com.

WHY IT MATTERS
Trending angle in Film & Actors. 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 Film & Actors 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Anniversary retrospectives on documented milestones — on the site colinfirth.com.

WHY IT MATTERS
Publish retrospectives pegged to real anniversaries — the 1995 Pride and Prejudice broadcast, the 2011 King's Speech Oscar, each Bridget Jones release — using documented production history. Anniversary spikes are predictable traffic events, and prepared retrospectives catch the surge that news sites only skim. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Publish: Restorations and re-releases worth a fresh look — on the site colinfirth.com.

WHY IT MATTERS
Trending angle in Film & Actors. 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 Film & Actors 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Verified trailers and interviews video page — on the site colinfirth.com.

WHY IT MATTERS
Curate a /videos/ page of official trailers and broadcast interviews, verifying each embed with check-embed.mjs and dropping any that fail embeddability. Fans binge interview archives, and a working curated reel keeps them on-site through long sessions instead of bouncing to YouTube after one clip. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Publish: What the latest interviews reveal about upcoming roles — on the site colinfirth.com.

WHY IT MATTERS
Trending angle in Film & Actors. 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 Film & Actors 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Per-film buy links on namesake tag — on the site colinfirth.com.

WHY IT MATTERS
Put disclosed Amazon buy links — Blu-ray, 4K, streaming purchase — on every filmography detail page using colinfirthfan-20, the tag literally named for this site. A fan reading a film's page is one click from owning it; per-title placement is this domain's most natural revenue by far. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
AdSense on retrospectives and news — on the site colinfirth.com.

WHY IT MATTERS
Run shared AdSense pub-7759195213529699 on retrospectives and news roundups where reading sessions are long, keeping filmography detail pages affiliate-only so each page type carries one clear monetization. Separation keeps the database feeling like a reference work rather than a banner farm. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Deepen the main Film & Actors guide with current data and examples — on the site colinfirth.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 Film & Actors 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 Film & Actors.
- 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Release-news fan newsletter, sourced only — on the site colinfirth.com.

WHY IT MATTERS
Offer a fan newsletter via wholetech.com/newsletter/widget.js covering confirmed casting and release news from cited trade sources — no rumor. Firth news arrives irregularly, which makes an alert list genuinely useful to fans. Every signup notification generates a Gmail DRAFT for review, never auto-sending anything. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Career timeline as film-strip graphic — on the site colinfirth.com.

WHY IT MATTERS
Render the career overview as a horizontal film-strip timeline — sprocket-holed frames, one per era, from early theatre through the Oscar year to current projects — each frame linking into the filmography. It gives the homepage a signature interactive graphic fans screenshot and share. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Regency letterpress art direction — on the site colinfirth.com.

WHY IT MATTERS
Art-direct from the roles that made him: Regency-era cream-and-ink palette, letterpress serif titling, gilt rule dividers, and film-still duotone frames for imagery. The Austen-adjacent visual world is instantly recognizable to this fanbase and elevates the site above generic celebrity-fan templates. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Add an FAQ answering the top questions in Film & Actors — on the site colinfirth.com.

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

HOW TO APPROACH IT
1. Audit the flagship Film & Actors 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 Film & Actors.
- 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Person schema with authoritative sameAs links — on the site colinfirth.com.

WHY IT MATTERS
Add Person schema for Firth with sameAs links to IMDb, Wikipedia, and other authoritative profiles, plus Movie markup on each filmography page. Ship both sitemaps per the two-sitemaps rule and ping IndexNow so engines treat the database as a structured, authoritative fan reference. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Sortable filmography worksheet: year, role, awards — on the site colinfirth.com.

WHY IT MATTERS
Present the filmography as an alldomains-model worksheet — sticky-number sortable table with year, title, role, director, and awards columns, rows expanding to the detail card. Sortable reference tables are what fans and journalists actually use when checking a fact, and they return to them. (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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

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

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

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Film & Actors: 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 Film & Actors 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Add source: The Film Stage — on the site colinfirth.com.

WHY IT MATTERS
Reviews & festivals Authoritative Film & Actors reference not yet linked on /sources/ — add it with a one-line note.

HOW TO APPROACH IT
1. Open the source and confirm it is authoritative and genuinely relevant to Film & Actors.
2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates.

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 link works, is annotated and well-placed, and is a reference a real Film & Actors expert would trust.
- 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site colinfirth.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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site colinfirth.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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Add Article + FAQ structured data — on the site colinfirth.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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site colinfirth.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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

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

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

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Film & Actors 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: colinfirth.com (live at https://colinfirth.com/), a Film & Actors site in the WholeTech network, served from /var/www/colinfirth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for colinfirth.com and no other site — make all changes on colinfirth.com. Act like a senior editor and web engineer who knows the Film & Actors niche cold.

GOAL (on colinfirth.com)
Verify affiliate links and ad placement resolve correctly — on the site colinfirth.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.