What to do next on this site

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

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

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

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

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

GOAL (on coworkingretreat.com)
Build the definitive Coworking cornerstone guide — on the site coworkingretreat.com.

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

GOAL (on coworkingretreat.com)
Publish: Hybrid-work data and what it means for desk demand — on the site coworkingretreat.com.

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

GOAL (on coworkingretreat.com)
Add an interactive tool and an email capture for Coworking — on the site coworkingretreat.com.

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

GOAL (on coworkingretreat.com)
Destination guides for proven retreat hotspots — on the site coworkingretreat.com.

WHY IT MATTERS
Build 'coworking retreat in <place>' guides for documented hubs — Bali, Madeira, Tulum, Tenerife — listing real venues with coworking facilities, visa notes from official sources, and seasonal wifi/weather realities. These are the exact phrases remote teams search when scoping a workation, and thin listicles currently own them. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on coworkingretreat.com)
Team retreat agenda templates with work blocks — on the site coworkingretreat.com.

WHY IT MATTERS
Publish concrete 3-day and 5-day retreat agendas balancing deep-work blocks, meetings, and offsite activities, in copyable format. Ops managers and chiefs of staff search 'team retreat agenda' constantly before planning season. Practical templates earn bookmarks and links from HR newsletters better than any opinion piece. (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: coworkingretreat.com (live at https://coworkingretreat.com/), a Coworking site in the WholeTech network, served from /var/www/coworkingretreat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for coworkingretreat.com and no other site — make all changes on coworkingretreat.com. Act like a senior editor and web engineer who knows the Coworking niche cold.

GOAL (on coworkingretreat.com)
Publish: The amenities members will pay a premium for in 2026 — on the site coworkingretreat.com.

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

GOAL (on coworkingretreat.com)
Join the coworking family cross-link strip — on the site coworkingretreat.com.

WHY IT MATTERS
Add the shared strip connecting coworkingretreat with coworkingcamp, coworkingcongress, and coworkingcoalition. Retreat planners often also want the event calendar and the camps directory, so cross-traffic is genuine. The cluster interlinking also concentrates topical authority on coworking across all four domains. (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: coworkingretreat.com (live at https://coworkingretreat.com/), a Coworking site in the WholeTech network, served from /var/www/coworkingretreat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for coworkingretreat.com and no other site — make all changes on coworkingretreat.com. Act like a senior editor and web engineer who knows the Coworking niche cold.

GOAL (on coworkingretreat.com)
Publish: Community programming that lifts retention — on the site coworkingretreat.com.

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

GOAL (on coworkingretreat.com)
Travala booking links on every destination guide — on the site coworkingretreat.com.

WHY IT MATTERS
Each destination guide gets contextual lodging links through the live Travala affiliate integration — the single best-fit monetization on the network for this domain, since every reader is by definition planning travel. Place blocks beside the venue lists where booking intent peaks, disclosed as affiliate. (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: coworkingretreat.com (live at https://coworkingretreat.com/), a Coworking site in the WholeTech network, served from /var/www/coworkingretreat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for coworkingretreat.com and no other site — make all changes on coworkingretreat.com. Act like a senior editor and web engineer who knows the Coworking niche cold.

GOAL (on coworkingretreat.com)
Publish: Flex-lease vs. dedicated-desk economics now — on the site coworkingretreat.com.

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

GOAL (on coworkingretreat.com)
Retreat packing list with Amazon tag — on the site coworkingretreat.com.

WHY IT MATTERS
A 'work-anywhere packing list' — travel routers, noise-canceling headsets, universal adapters, packable laptop stands — using Associates tag colinfirthfan-20 with honest weight and airline-carry-on notes. Pre-trip gear buying is a reliable conversion moment, and the list naturally links from every destination guide. (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: coworkingretreat.com (live at https://coworkingretreat.com/), a Coworking site in the WholeTech network, served from /var/www/coworkingretreat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for coworkingretreat.com and no other site — make all changes on coworkingretreat.com. Act like a senior editor and web engineer who knows the Coworking niche cold.

GOAL (on coworkingretreat.com)
Featured placements for retreat operators — on the site coworkingretreat.com.

WHY IT MATTERS
Sell disclosed featured slots to retreat venues and organizers inside their destination's guide — photo, dates, direct booking link, flat seasonal fee. Operators already pay Instagram for weaker placement. Inquiry form produces draft notifications for Paul's review; no email ever auto-sends. (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: coworkingretreat.com (live at https://coworkingretreat.com/), a Coworking site in the WholeTech network, served from /var/www/coworkingretreat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for coworkingretreat.com and no other site — make all changes on coworkingretreat.com. Act like a senior editor and web engineer who knows the Coworking niche cold.

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

GOAL (on coworkingretreat.com)
Passport-stamp and boarding-pass art direction — on the site coworkingretreat.com.

WHY IT MATTERS
Style destination pages as passport spreads: stamp-motif badges per country, perforated boarding-pass dividers between sections, sun-faded film palette, and handwriting-annotation accents for tips. The travel-document visual world says 'you are going somewhere' in a way generic hero-photo layouts never do. (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: coworkingretreat.com (live at https://coworkingretreat.com/), a Coworking site in the WholeTech network, served from /var/www/coworkingretreat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for coworkingretreat.com and no other site — make all changes on coworkingretreat.com. Act like a senior editor and web engineer who knows the Coworking niche cold.

GOAL (on coworkingretreat.com)
Add an FAQ answering the top questions in Coworking — on the site coworkingretreat.com.

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

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

GOAL (on coworkingretreat.com)
Agendas rendered as resort daily-schedule cards — on the site coworkingretreat.com.

WHY IT MATTERS
Present retreat agendas as poolside daily-activity boards — time column down the left, hand-lettered-style headers, small weather and dress-code icons — the format guests already know from resort easels. It makes the work-block/leisure balance visible at a glance and prints beautifully for actual retreats. (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: coworkingretreat.com (live at https://coworkingretreat.com/), a Coworking site in the WholeTech network, served from /var/www/coworkingretreat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for coworkingretreat.com and no other site — make all changes on coworkingretreat.com. Act like a senior editor and web engineer who knows the Coworking niche cold.

GOAL (on coworkingretreat.com)
Schema-marked honest cost-range answers — on the site coworkingretreat.com.

WHY IT MATTERS
Publish 'how much does a coworking retreat cost' with real ranges assembled from operators' public pricing, segmented by region and group size, in 40-word liftable blocks with FAQ schema. Cost questions dominate this niche's AI queries, and honest sourced ranges get cited over vague content-farm answers. (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: coworkingretreat.com (live at https://coworkingretreat.com/), a Coworking site in the WholeTech network, served from /var/www/coworkingretreat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for coworkingretreat.com and no other site — make all changes on coworkingretreat.com. Act like a senior editor and web engineer who knows the Coworking niche cold.

GOAL (on coworkingretreat.com)
Static retreat budget calculator — on the site coworkingretreat.com.

WHY IT MATTERS
A no-backend JS calculator: headcount, nights, destination tier, and workspace needs in; per-person and total estimates out, using the same sourced ranges as the cost page. Planners share calculator links internally when making the case to leadership, pulling whole teams onto the site. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on coworkingretreat.com)
Add source: Coworking Insights — on the site coworkingretreat.com.

WHY IT MATTERS
Operator data & guides Authoritative Coworking reference not yet linked on /sources/ — add it with a one-line note.

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

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

WHAT "DONE" LOOKS LIKE
- The link works, is annotated and well-placed, and is a reference a real Coworking expert would trust.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

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

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

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

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

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

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

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

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

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

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

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

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

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