bundle-release-metadatalisted
Install: claude install-skill SenjuWoo/Ultimate-AI-Starter-Bundle
# Bundle release metadata
## When to Use
- You are about to commit a change to any shipped file in this bundle.
- CI is red on `MANIFEST verifies against the tree`, a version string, or a docs gate.
- You regenerated a preamble, an instruction archive or a bundled payload.
## Rule
Generated files are never hand-edited, and one of them (MANIFEST.json) is what
`TOOLS/build_release.py` uses to decide what ships. A stale manifest is a
missing file in the release, not a cosmetic diff.
| Generated | Producer |
|---|---|
| `MANIFEST.json` | `python TOOLS/generate_manifest.py .` |
| `3-PREAMBLES/history/*` | `python TOOLS/generate_preamble_history.py` |
| `BUNDLED-TOOLS/packs/*/legacy/*` | installer archive step |
| `BUNDLED-TOOLS/{CATALOG,PROFILES,OFFLINE-MANIFEST}.json`, `VALIDATION.json` | release stamps |
| `VERSION.txt` | single source for the installer banner and `install-state.json` |
## Order of operations
1. Edit content, then fan out skills: `python TOOLS/fanout_providers.py _CANONICAL-SKILLS .`
2. Archive preambles: `python TOOLS/generate_preamble_history.py`
3. Regenerate `MANIFEST.json` **last** — a local install or a test run can create
a new archive after you generated it.
4. Run `TOOLS\Refresh-Release-Metadata.ps1`, then `TESTS\Test-Pack.ps1`.
## Red CI on the manifest
```
python TOOLS/generate_manifest.py .
python .github/scripts/verify_manifest.py
git add MANIFEST.json && git commit -m "<version>: regenerate manifest" && git push
```
`ci.yml` now refres