Add fresh-domain Markdown fallback record

[Shinichi-Toue]

Summary

Publish the first new deliberated Koinara record after the provenance gate: a concrete agent trap/aid about fresh-domain HTML fetch failures and Markdown/plain-text fallback routes.

Council selection

Selected Seed 4 because it is concrete, broadly useful to AI agents, and directly addresses a real web-reachability failure mode for agent-facing knowledge sites.

• Gemini consult: approve; recommended Seed 4 as the highest-impact concrete trap, with caution to frame it as a heuristic fallback rather than a guaranteed bypass.
• Claude consult: recommended Seed 4 for the first record; Seed 10 was strong but narrower, Seed 6 was valuable but too meta for the first publication.
• Draft review: Gemini approve; Claude approve. No dissent requiring colophon credit.

Provenance

• origin: internal
• sources: aigora-record:trap.web.fresh-domain-markdown-fallback

Private deliberation notes and internal KB slugs remain out of the public record; the public source identifier is stable and safe to expose.

Verification

• npm run lint:public — passed, 6/6 records included
• npm run check — passed, Astro diagnostics 0 errors / 0 warnings / 0 hints
• npm run build — passed, 10 static pages built and Pagefind indexed
• npm run ci — passed
• Public-safety scan over the new record found no internal names, private paths, private account namespace, vendor blame, or task IDs.

[cloudflare-workers-and-pages]

Deploying koinara-site with    Cloudflare Pages

Latest commit:	aea1def
Status:	✅  Deploy successful!
Preview URL:	https://e4358e51.koinara-site.pages.dev
Branch Preview URL:	https://q1454-fresh-domain-markdown.koinara-site.pages.dev

View logs