Refresh CMS-DEPLOYMENT-PLAN to current state

- Drop reference to examples/astro-cv/ (no longer in tree)
- Status header reflects clawdie-docs project rename and canonical
  cms jail name
- Success criteria and Next phases describe the canonical cms jail
  with legacy fallbacks noted, not {agent}-cms as the live target

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Operator & Claude Code 2026-05-10 20:42:10 +02:00
parent 4e2abfd18e
commit c6836d4bad

View file

@ -2,7 +2,7 @@
**Date:** 14.mar.2026
**Updated:** 15.mar.2026
**Status:** Core topology implemented — Astro path is live in `cms`; Strapi content migration still pending
**Status:** Astro/Starlight live in `cms` jail (project: `clawdie-docs`); Strapi still pending; canonical jail name is `cms`
**Goal:** Make the `cms` jail the Clawdie-owned web stack for Astro, docs, and
optional Strapi-managed content.
@ -104,8 +104,6 @@ content:
not a destructive export/import dump
- keep repo-native technical docs and generated content outside Strapi where
that remains simpler
- treat `examples/astro-cv/` as a prototype/reference, not the bootstrap source
for first FreeBSD deployment
## Non-goals
@ -120,16 +118,17 @@ content:
| Check | Expected |
|-------|----------|
| CMS jail running | `bastille list` shows `{agent}-cms` |
| Jail nginx serving | local fetch against `/usr/local/www/clawdie` in `{agent}-cms` returns 200 |
| Astro built in jail | build output exists inside `{agent}-cms` |
| CMS jail running | `bastille list` shows `cms` (or legacy `${AGENT_NAME}cms` / `${TENANT_ID}-cms` fallbacks) |
| Jail nginx serving | local fetch against `/usr/local/www/clawdie` in the cms jail returns 200 |
| Astro built in jail | build output exists inside the cms jail |
| Strapi kept internal | admin/API not public by default |
| Public exposure optional | docs site can be fronted by PF, external reverse proxy, or direct jail IP |
## Next phases
1. Finish the concrete `cms` setup step and keep `${AGENT_NAME}-cms` as the
active jail naming model.
1. Finish the concrete `cms` setup step. Canonical jail name is `cms`;
`${AGENT_NAME}cms` and `${TENANT_ID}-cms` are legacy fallbacks the
provisioner still recognizes.
2. Move Astro source and build automation out of the transitional static HTML
deploy flow.
3. Add an explicit edge-mode step or post-install workflow for public exposure.