Stub city content enrichment (11 pages)

What was done

• Eleven service-area city pages enriched from placeholder (TODO: City-specific intro… + generic 3-line bullet list) to production prose with city-specific intro paragraph + 3–4 enriched engineering bullets per page.
• Blaine County (4): Bellevue, Hailey, Ketchum, Sun Valley. Wood River Valley framing, Big Wood River floodplain, hillside overlays (Hailey 30% threshold, Ketchum 25% Mountain Overlay), Ketchum/Sun Valley design review, SVWSD utility delegation. Ketchum gets 4 bullets (design review is a meaningful fourth beat).
• Owyhee County (3): Homedale, Marsing, Murphy. Snake River farming framing for Homedale/Marsing (Gem Irrigation District coordination, floodway setbacks, split municipal/well-septic utilities). Murphy uses a variant template — intro explicitly states unincorporated + Owyhee County-managed; bullet label is “Planning & Zoning (Owyhee County)” not “Planning & Zoning”; named contacts Mary Huff, AICP (Planning Director) and Brook Russell (Planner); no references to a Murphy planning department.
• Elmore County (2): Mountain Home, Glenns Ferry. Mountain Home gets 4 bullets including AICUZ (Mountain Home AFB Air Installation Compatibility Use Zone), Mountain Home Plateau aquifer water rights, floodplain, and military housing pipeline dynamics. Glenns Ferry covers I-84/ITD corridor, Snake River SFHA, and aging utility infrastructure (citing the April 2023 IWRB grant).
• Boise County (2): Horseshoe Bend (WUI + well/septic + steep Payette canyon), Idaho City (Historic Preservation Overlay with Certificate of Appropriateness process, WUI, hillside). Verified both retain their own P&Z commissions (not delegated to Boise County).
• Extended src/scripts/verify-build.sh with Check 20: “No placeholder strings in 11 stub city pages” — scans for TODO: City-specific intro, Contact {city} planning department (per-city interpolation), Refer to {county} comprehensive plan (per-county), and Site-specific assessment required. Build fails on any hit. Sub-check: intro uniqueness warn at ≥80% Jaccard similarity (never fails, only warns — caught the pre-transplant all-identical-templates baseline at 1.00 across 55 pairs).
• All 11 .astro files now render a nested .info-sublist ul for the Engineering Considerations bullet — consistent styling across the 11 pages; CSS scoped inside each file.

Why

Backlog item “City page content audit — apply v1 rewrites to 11 stub pages” had flagged these as placeholders in production. Murphy was the most urgent: its “Contact Murphy planning department” bullet was actively misleading (no such department exists; Murphy is unincorporated). Scope decisions (B/A/A per spec):

• B — content enrichment only, no template migration. Bespoke stub layouts stay; don’t convert to CityPage.astro (that’s the separate 25–45 hour “city page content audit” backlog item).
• A — fill existing 4-piece shape (intro + 3 bullets). No new sections. Smallest scope that resolves all placeholder content.
• A — staging drafts for self-review, Kelli reviews on live prototype. .tmp/stub-enrichment-drafts/ served as the pre-flight checkpoint before 11 page edits; Kelli’s review happens on prototype.baileyengage.com/service-areas/{county}/{city}/.

How this was executed (methodology worth preserving)

Research was delegated to 4 parallel subagents (one per county) to keep raw web research out of the main context. Each subagent read the spec + plan, executed its county batch, and reported distilled summaries — not raw source dumps. Follow-up agents handled self-review consistency pass, verifier extension, and the mechanical transplant. Total working time ~3 hours vs. the 5-hour estimate; parallelism was the biggest lever.

Files affected

Created

• docs/superpowers/specs/2026-04-22-stub-city-content-enrichment.md
• docs/superpowers/plans/2026-04-22-stub-city-content-enrichment.md
• .tmp/stub-enrichment-drafts/ (11 draft files + README tracker + transplant-notes.md — disposable after Kelli approval)

Modified

• 11 stub .astro files under src/pages/service-areas/{county}/{slug}/index.astro: Blaine (bellevue, hailey, ketchum, sun-valley), Owyhee (homedale, marsing, murphy), Elmore (mountain-home, glenns-ferry), Boise County (horseshoe-bend, idaho-city)
• src/scripts/verify-build.sh (added Check 20 + intro uniqueness sub-check)
• BACKLOG.md (mark item complete pending Kelli live-prototype signoff)

Kelli research support (landproDATA session 2026-04-23) — durable findings

Kelli ran a ~25 min authenticated landproDATA session to pre-answer the 23 escalation questions compiled during research. Most couldn’t be answered from landproDATA records, but the session produced useful calibration context worth preserving:

• Bailey project presence per county — Blaine: 0; Owyhee: 1 (Birmingham Estates, Jan 2026); Elmore: 13 (all Trilogy corridor — Blue Yonder West + Thunderbolt Landing); Boise County: 2 (both Horseshoe Bend on David Bailey’s personal property). Interpretation: our desk research approach was correctly calibrated — we did NOT claim Bailey practice experience on pages where we have none (Blaine, Idaho City, Glenns Ferry).
• Mary Huff, AICP confirmed as Owyhee County Planning Director (contact for Murphy). Already captured in the Murphy draft by the Owyhee research subagent; landproDATA dig validated the identification.
• Comp plan adoption years are not in landproDATA — 5 cities (Sun Valley, Homedale, Marsing, Murphy, Idaho City) flagged as weak primary carry forward as candidates for a phone-call pass to respective City Clerks during the next quarterly refresh.
• 17+ questions remain unanswered post-landproDATA — they require Bailey institutional knowledge (Kelli’s direct input) or city phone calls. These are documented in .tmp/stub-enrichment-drafts/README.md under “Kelli review questions” and should ride with the live-prototype review.

Known gaps / pending

• Kelli live-prototype review on prototype.baileyengage.com/service-areas/{county}/{city}/ — pending OneDrive sync completion. One pass across 11 cities; 23 open questions pre-compiled in the project tracker at .tmp/stub-enrichment-drafts/README.md.
• 5 weak-primary comp-plan flags (Sun Valley 2015, Homedale/Marsing/Murphy undated, Idaho City undated) — carry into the next quarterly refresh with a phone-call-to-City-Clerks pass for adoption years.
• 3 AICUZ-specific escalations for Mountain Home — site-specific noise contour/APZ boundaries not in public sources; Bailey-practice knowledge would tighten the AICUZ bullet. Not blocking; can tighten in a follow-up edit.
• Draft cleanup (.tmp/stub-enrichment-drafts/) deferred until Kelli’s live-prototype signoff lands. Drafts are the record of what the pages rendered with at transplant time, useful if corrections surface.
• Mountain Home + Horseshoe Bend Bailey-experience sentences deliberately NOT added. These pages are for prospective developers/applicants; Bailey-experience storytelling is “Why Bailey” territory. Kelli can choose to foreground Trilogy corridor work / David’s Horseshoe Bend land during her review if she wants.

Spec drift caught during implementation

None. All 11 stub files matched the expected placeholder pattern exactly — no one-offs in the transplant phase (transplant-notes.md records the clean pattern confirmation). The pattern matching from the YouTube-integration dev log (“don’t trust the spec’s stub list verbatim — count from the filesystem”) held here too: the plan correctly enumerated 11 stubs in 4 counties and the filesystem confirmed.