Initial commit: BlueCap Strategies Astro site

Static Astro 5 site for BlueCap Strategies with exact live-site content
parity, deployed to k3s via GitOps (ArgoCD).

- Page copy in Markdown content collections (services, focus-areas, pages,
  insights) with a Zod SEO schema enforced at build time
- Homepage + About restored to exact live copy; real live-site imagery
- Build-time SEO linter (scripts/seo-lint.mjs) and Playwright e2e suite
- Multi-stage Dockerfile (nginx serves dist/) and Kustomize manifests (k8s/)
- Per-agent robots.txt; config-driven PostHog + Umami analytics scaffold
- ADRs and engineering docs under docs/

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/adr/0006-launch-insights-blog.md

@@ -0,0 +1,26 @@
+# ADR-0006: Launch a blog at /insights/
+
+**Status:** Accepted — 2026-07-15
+
+## Context
+
+The live WordPress site has **no published blog** (0 posts, 0 `project` entries) but does have an
+**unpublished, empty "Insights & Resources" draft** (`page_id=303`) — a blog scaffolded but never
+launched. The rebuild already has an `/insights/` section (routes, RSS, content collection, one
+example draft). The parity plan and SEO/AEO plan both identify thought leadership as a core
+authority/GEO asset.
+
+## Decision
+
+**Launch the blog at `/insights/`** in the rebuild. Keep the existing Astro content-collection
+scaffold (Markdown/MDX, RSS, tags, canonical for cross-posts). Publish only **real,
+owner-reviewed** content — no fabricated or unreviewed AI-generated articles. Candidate first
+pieces: PFAS remediation as a capital-formation problem; scaling marine conservation finance;
+making island/coastal infrastructure investable.
+
+## Consequences
+
+- Gives AEO/GEO a surface to be cited from; `Article`/`BlogPosting` schema per SEO plan §3.
+- Content is owner-gated — the section can ship empty or with 1–2 real posts; do not backfill with
+  placeholder articles.
+- Insights carry `publishDate`/`modifiedDate`; RSS and sitemap `lastmod` derive from these.