What to do next on this site

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

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

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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

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

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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

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

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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Build the definitive Children's Stories cornerstone guide — on the site childrenstory.net.

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

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

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 Children's Stories — 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 Children's Stories 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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Add an interactive tool and an email capture for Children's Stories — on the site childrenstory.net.

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

GOAL (on childrenstory.net)
Publish: A current, data-backed explainer in Children's Stories — on the site childrenstory.net.

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

GOAL (on childrenstory.net)
Publish: The question your Children's Stories audience is searching most right now — on the site childrenstory.net.

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

GOAL (on childrenstory.net)
Anniversary retrospective of the site's history — on the site childrenstory.net.

WHY IT MATTERS
Publish a documented retrospective of the site's own 28-year run — launch era, design changes, what children's web publishing looked like in 1998 — using only real site history. Internet-nostalgia audiences on Reddit and Hacker News share genuine time-capsule stories, and this one is verifiably real. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Present the site as 1998 web time-capsule — on the site childrenstory.net.

WHY IT MATTERS
Lean into what this site uniquely is: a children's story site preserved from 1998. Write a front-door page framing it as a museum of the early web, and submit it to web-history galleries and vintage-web directories that celebrate preserved sites. Its age is the growth asset. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Publish: A 'what changed in 2026' round-up for Children's Stories — on the site childrenstory.net.

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

GOAL (on childrenstory.net)
Prominent bridge to childrenstory.org library — on the site childrenstory.net.

WHY IT MATTERS
Add a clear, museum-style pointer from the archive to childrenstory.org's living library of 824 stories and its podcast: looking for stories to read tonight, visit the library. The .net satisfies curiosity; the .org serves families — the bridge converts nostalgia visitors into library users. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
One quiet curated classics bookshelf — on the site childrenstory.net.

WHY IT MATTERS
Add a single labeled page recommending timeless children's story collections via Amazon Associates tag colinfirthfan-20, framed as the curator's reading list and kept entirely apart from the preserved 1998 pages. One gentle, disclosed shelf respects the museum feel while letting the archive earn modestly. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Deepen the main Children's Stories guide with current data and examples — on the site childrenstory.net.

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 Children's Stories 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 Children's Stories.
- 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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Shared gentle newsletter across both story sites — on the site childrenstory.net.

WHY IT MATTERS
Place the wholetech.com/newsletter/widget.js signup on the museum's front-door page, feeding the same calm parents-and-teachers list as childrenstory.org. One combined list keeps the pair efficient, and every signup notification arrives as a Gmail DRAFT for review — nothing auto-sends from a children's property. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Cross-promote the .org print anthology — on the site childrenstory.net.

WHY IT MATTERS
When childrenstory.org publishes its print-on-demand story collections, give the museum a quiet exhibit-shop page mentioning them. A museum gift-shop framing is honest, familiar, and entirely un-aggressive — visitors who loved the time capsule can take a real book home, and both sites share the earnings. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Museum exhibit-label chrome, originals untouched — on the site childrenstory.net.

WHY IT MATTERS
Never restyle the 1998 pages. Instead wrap them in thin curator's chrome: archival exhibit-label plaques with small-caps typography noting each page's date and context, like placards beside paintings. The contrast between crisp museum labels and untouched period pages is the entire design statement. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Add an FAQ answering the top questions in Children's Stories — on the site childrenstory.net.

WHY IT MATTERS
Pull the real questions people ask in Children's Stories and answer them plainly. Mark up with FAQ schema for rich results.

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

GOAL (on childrenstory.net)
Display 90s web artifacts as exhibit cases — on the site childrenstory.net.

WHY IT MATTERS
Present the site's genuine period artifacts — original GIFs, tiled backgrounds, hit counters, under-construction icons — in dedicated exhibit-case panels with captions explaining what each meant in 1998. Treating the site's own decorations as museum objects turns every dated pixel from embarrassment into curation. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Archive-collection schema and clean sitemaps — on the site childrenstory.net.

WHY IT MATTERS
Mark the site up as an archived collection — organization, founding date, archival status — so engines understand it is a preserved historical site rather than stale content, and ship both sitemaps per the two-sitemaps rule with an IndexNow ping. Correct framing protects it from freshness-based demotion. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

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

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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Curator's guided tour of the archive — on the site childrenstory.net.

WHY IT MATTERS
Build a single guided-tour page walking visitors through the archive's highlights in order — earliest pages, the story sections, the period artifacts — with next-stop navigation like a museum audio tour. First-time visitors get a narrative path instead of wandering unlabeled 1998 navigation alone. (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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Add a /live/ news feed for Children's Stories — on the site childrenstory.net.

WHY IT MATTERS
An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense.

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

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

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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

GOAL (on childrenstory.net)
Add Article + FAQ structured data — on the site childrenstory.net.

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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

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

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: childrenstory.net (live at https://childrenstory.net/), a Children's Stories site in the WholeTech network, served from /var/www/childrenstory.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for childrenstory.net and no other site — make all changes on childrenstory.net. Act like a senior editor and web engineer who knows the Children's Stories niche cold.

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

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Children's Stories videos. Re-verify embeds.

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

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

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.