Parfii-bot 036bc6a52e docs: SKILL.md triggers + STATUS-TRUTH footer + phase placeholders

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>

2026-05-02 21:41:41 +08:00

1.8 KiB

Raw Permalink Blame History

Phase 6 — Production Deploy

Goal: deploy the approved site to production and verify it is live. Verify criterion: production URL responds 200; deploy commit recorded; user notified with live URL and summary report.

6.a — Run production deploy

Invoke the production deploy target:

/web-deploy --env production

The deploy skill handles:

Final build (npm run build)
Upload / push to the configured hosting target (Vercel, Netlify, CF Pages, S3+CDN, VPS via rsync, etc.)
DNS propagation check (waits up to 60 s for the apex domain to resolve)

6.b — Post-deploy smoke test

After the deploy reports success, verify the live URL:

HTTP HEAD on the production URL → expect 200 OK.
Check <title> tag matches the project name from Phase 0.
If a sitemap was generated in Phase 4, verify <domain>/sitemap.xml returns 200.

If any check fails: report to user; do NOT mark phase complete.

6.c — One AskUserQuestion: final confirmation

Present the live URL and smoke-test results. Ask:

Done — mark pipeline complete — proceed to exit report.
Issue found — rollback — invoke /web-deploy --rollback to the previous production snapshot.

6.d — Exit report

Emit the pipeline completion summary:

=== SITE-CREATE PIPELINE COMPLETE ===
Project:   <project-name>
Live URL:  <production-url>
Phases:    0-6 all complete
Sections:  <N> locked (mock-render)
Audits:    <a11y / seo / responsive / perf findings applied>
Deploy:    <hosting target> — <deploy ID or commit SHA>

6.e — Verify criterion

Production URL live and smoke-tested (200 OK, correct <title>).
Deploy commit or deploy ID recorded in exit report.
User confirmed pipeline complete.

Pipeline ends here.

1.8 KiB Raw Permalink Blame History