What to do next on this site

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

GOAL (on austinfestivalcalendar.com)
Build the definitive Austin Life cornerstone guide — on the site austinfestivalcalendar.com.

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

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

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

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

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

GOAL (on austinfestivalcalendar.com)
Add an interactive tool and an email capture for Austin Life — on the site austinfestivalcalendar.com.

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

GOAL (on austinfestivalcalendar.com)
Publish: A current, data-backed explainer in Austin Life — on the site austinfestivalcalendar.com.

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

GOAL (on austinfestivalcalendar.com)
Add-to-calendar ICS buttons on every festival — on the site austinfestivalcalendar.com.

WHY IT MATTERS
Generate an ICS file per festival and a master subscribe feed so readers add dates to Google or Apple Calendar in one tap. Subscribed calendars resurface the domain every time a festival approaches, manufacturing return visits without any email. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

GOAL (on austinfestivalcalendar.com)
Publish: The question your Austin Life audience is searching most right now — on the site austinfestivalcalendar.com.

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

GOAL (on austinfestivalcalendar.com)
Twelve-month calendar with per-festival pages — on the site austinfestivalcalendar.com.

WHY IT MATTERS
Cover the full Austin festival year, SXSW, ACL, Pecan Street, Blues on the Green, Trail of Lights, with one permanent page per festival holding dates, venue, and history from official announcements. Permanent URLs accumulate rank year over year instead of resetting. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

GOAL (on austinfestivalcalendar.com)
Monthly festivals-this-month roundup post — on the site austinfestivalcalendar.com.

WHY IT MATTERS
Publish a tight roundup on the first of each month listing everything happening, feeding recurring pages through /root/gen-live.py, and offer it as a subscription via the wholetech.com/newsletter/widget.js embed. A predictable monthly artifact is what local sites and groups link. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

GOAL (on austinfestivalcalendar.com)
Publish: A 'what changed in 2026' round-up for Austin Life — on the site austinfestivalcalendar.com.

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

GOAL (on austinfestivalcalendar.com)
TicketNetwork links on ticketed festival pages — on the site austinfestivalcalendar.com.

WHY IT MATTERS
Use the live Impact TicketNetwork integration for resale tickets on ACL, SXSW-adjacent shows, and other ticketed festivals, placed under each event's details with clear disclosure. Ticket intent on a festival calendar is the most natural affiliate fit in the network. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

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

GOAL (on austinfestivalcalendar.com)
Travala hotel links for out-of-town attendees — on the site austinfestivalcalendar.com.

WHY IT MATTERS
On major destination festivals, add a clearly labeled where-to-stay section with Travala affiliate links for festival-weekend Austin hotels. Out-of-town ACL and SXSW visitors book lodging anyway; capturing that intent on the dates page is honest and useful. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

GOAL (on austinfestivalcalendar.com)
AdSense across the calendar grid pages — on the site austinfestivalcalendar.com.

WHY IT MATTERS
Run shared AdSense pub-7759195213529699 on month-view and roundup pages where browsing sessions are long, keeping individual festival detail pages lighter so add-to-calendar and ticket actions stay prominent above the fold. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

GOAL (on austinfestivalcalendar.com)
Gig-poster typography and wristband navigation — on the site austinfestivalcalendar.com.

WHY IT MATTERS
Art-direct from Austin's poster culture: stacked lineup-poster type hierarchy on festival pages, screen-print texture and limited ink colors, and a nav bar styled as a fabric festival wristband. The site should look like the poster wall at a venue, not a utility calendar. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

GOAL (on austinfestivalcalendar.com)
Add an FAQ answering the top questions in Austin Life — on the site austinfestivalcalendar.com.

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

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

GOAL (on austinfestivalcalendar.com)
Event schema and when-is FAQs, IndexNow pinged — on the site austinfestivalcalendar.com.

WHY IT MATTERS
Mark up every festival with Event schema, dates, venue, and answer when-is questions in dated FAQ blocks. Maintain both sitemaps and ping IndexNow immediately when official dates drop, because being first-indexed on date announcements wins the annual query surge. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

GOAL (on austinfestivalcalendar.com)
Month headers as pennant bunting, dates as stubs — on the site austinfestivalcalendar.com.

WHY IT MATTERS
Draw each month view with triangular pennant-bunting headers and render individual event dates as small ticket-stub chips with perforated edges. The festival-grounds vocabulary makes the calendar grid itself feel like an event, distinct from every generic events site. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

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

GOAL (on austinfestivalcalendar.com)
Filterable festival worksheet by month and type — on the site austinfestivalcalendar.com.

WHY IT MATTERS
Build an alldomains-style sortable table of all festivals: month, genre, neighborhood, free-or-ticketed, family-friendly, with search chips and row-to-detail cards. One filterable master view serves planners better than paging through months and earns the bookmark. (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: austinfestivalcalendar.com (live at https://austinfestivalcalendar.com/), a Austin Life site in the WholeTech network, served from /var/www/austinfestivalcalendar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinfestivalcalendar.com and no other site — make all changes on austinfestivalcalendar.com. Act like a senior editor and web engineer who knows the Austin Life niche cold.

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

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Austin Life items and pinging IndexNow each run.

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

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

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

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

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

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

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

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

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Austin Life 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.