astro-wiki-publisherlisted

# Astro Wiki Publisher ## Purpose Coordinate the full publishing loop for content-driven Astro wikis: content collections, Markdown rendering, navigation, artifact data, public-copy quality, browser verification, media artifacts, and deploy truth. ## Required Skill Routing - Use `astro-framework` for Astro 5+, content collections, routing, i18n, hydration, view transitions, adapters, images, and static/server output decisions. - Use `markdown-rendering-regression` before claiming Markdown or public copy is fixed. - Use `webapp-testing` or `browser` for local preview, console errors, failed requests, screenshots, and layout overflow checks. - Use `site-architecture` for docs hierarchy, sidebars, route naming, breadcrumbs, and internal linking. - Use `copywriting`, `copy-editing`, `seo-audit`, and `ai-seo` for public reader/press copy and metadata. - Use `notebooklm` for live NotebookLM notebook/source/artifact verification. - Use `r2-notebooklm-artifact-portal` for R2-backed public artifact URLs, MIME, cache, and playback validation. - Use `cloudflare` or `wrangler` for Cloudflare platform operations only; do not duplicate platform syntax here. - Use `mermaid-to-gif` for animated Mermaid process/architecture visuals. - Use `hyperframes-cli` for launch trailer or video composition dev loop. - Use `animejs` only for deterministic HyperFrames micro-animations, not for live Astro route scroll behavior. ## Workflow 1. Confirm repo truth: cwd, branch, remote, dirty state, pack