export-catalogue

# Skill: export-catalogue Produce a **redistributable derivative** of this catalogue at a target path — for an organization rebrand or a domain re-purposing — in one of two modes, with a **fail-closed** leak check. One mechanism; the transform is three declared lists + a gate. Full manifest: [`references/transform-manifest.md`](references/transform-manifest.md). ## Output rendering Status list — Lead each row with a status glyph — ● running, ✓ done, ○ idle, ⚠ blocked — status first, one item per line, labels aligned. ## Modes - **`white-label`** (default) — strip *all* upstream identity; zero trace. For private/org forks and anything that must not disclose provenance. - **`attributed`** — strip governance + colliding branding, but keep a declared attribution-back credit (a `NOTICE`/README block). The ecosystem-growth lever: a public re-purposed catalogue credits its origin. Attribution lives **only** in the sanctioned notice surface. ## Procedure 1. **Validate the target.** The operator-supplied target path is non-empty and does not overlap/nest in the running repo tree; all writes go through `agentbundle.safety.write_jailed`. 2. **Choose the include-set** — which packs travel (drop SDLC packs for a creative-writing catalogue; always keep the engine, a `core`, and `catalogue-curation` itself so the fork can self-curate). Determines which seeds to plant (step 4) and which guides to stage (step 5). 3. **Strip** (deny-by-default, both modes) — copy ...