Group G — markdown tech-debt cleanup (post-audit 2026-05-02).
- 36 SKILL.md files: added "## When to use" section. Was missing across the
catalog; orchestrator routing by keyword could not auto-dispatch.
- 20 code-implementer agent .md files: added Output Footer block prescribing
RULE 0.16 STATUS-TRUTH MARKER schema in agent's final report. Previously only
code-implementer-rust.md had it; other 27 language/role variants were silent
about the marker, breaking RULE 0.16 §3 status-truth aggregation for non-Rust
batches.
- skills/site-create/: added phase-5-preview.md and phase-6-deploy.md skeleton
files. SKILL.md table-of-contents referenced 7 phases; only 5 existed on disk.
- skills/{ai-animation,rag-pipeline}/skill.md: added migration banner comment
noting they should be SKILL.md (canonical filename). Case-rename via git is a
separate orchestrator task (macOS APFS is case-insensitive; Linux deploy needs
explicit rename).
- 3 deprecated skills (site-builder, competitor-analysis, design-inspiration):
added concrete removed-after dates (was vague "before v2").
- docs/CONVERGENCE-PLAN.md:129: TBD on _blocks/evidence-grading.md duplicate
resolved (file exists, not duplicated).
- docs/DNA-INDEX.md: count edits made then overwritten by auto-encyclopedia-refresh
hook during agent run. The .kei-registry-ignore files in test fixtures (Group F)
are the structural fix; kei-registry walker implementation is the follow-up.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
53 lines
1.4 KiB
Markdown
53 lines
1.4 KiB
Markdown
# Phase 5 — Preview Deploy
|
|
|
|
> Goal: deploy the site to a temporary preview URL so the user can inspect
|
|
> it in a real browser before committing to production.
|
|
> **Verify criterion:** preview URL is live and accessible; user has
|
|
> confirmed the site looks correct at the URL.
|
|
|
|
---
|
|
|
|
## 5.a — Run preview deploy
|
|
|
|
Invoke the preview deploy target:
|
|
|
|
```
|
|
/web-deploy --env preview
|
|
```
|
|
|
|
The deploy skill returns a preview URL (e.g. `https://preview-<hash>.vercel.app` or
|
|
a Netlify/CF Pages preview link depending on the project's deployment target).
|
|
|
|
If the project has no preview environment configured, build locally and start
|
|
a local server:
|
|
|
|
```bash
|
|
npm run build && npm run preview
|
|
# or: npx astro preview
|
|
```
|
|
|
|
In that case the "preview URL" is `http://localhost:4321` (or the port reported).
|
|
|
|
---
|
|
|
|
## 5.b — One AskUserQuestion: proceed to production?
|
|
|
|
Present the preview URL and ask:
|
|
|
|
- **Deploy to production** — site looks correct, proceed to Phase 6.
|
|
- **Return to audit** — found issues; loop back to Phase 4.
|
|
- **Return to sections** — a section needs rework; loop back to Phase 3.
|
|
- **Abort** — cancel the pipeline; site stays at preview only.
|
|
|
|
---
|
|
|
|
## 5.c — Verify criterion
|
|
|
|
- Preview deploy completed without error.
|
|
- User has visited the URL (or local server) and approved.
|
|
- No outstanding `mock-render status` drift rows.
|
|
|
|
Emit:
|
|
`Phase 5 done: preview live at <url>. Proceeding to production deploy.`
|
|
|
|
Proceed to Phase 6.
|