---
name: velin-release-meta-rebuild
description: Rebuild VelinStyle meta/release artifacts via CLI; not a source rewrite apply.
---
# Release Meta Rebuild

## Purpose
Rebuilds velin-agent.json and llms.txt before publishing.

## Domain
B · category `release`

## Capabilities
- `build.meta`

## Permission
`write` · **requiresApproval: true**

## Allowed actions
- READ
- WRITE

## Forbidden actions
- APPLY
- ROLLBACK
- ACCEPT
- DEFER
- NOTE
- ACKNOWLEDGE
- CATALOG
- MANIFEST
- CLASSIFY
- invent-target

## Stop conditions
- SR-11

## Agent role / risk
Releaser · risk `low`

## Reuse (mandatory before build)

Follow `velin-reuse-gate` (BP-R01…R04):

1. **SEARCH** existing VelinStyle skills, components/Web Components, utilities, tokens, and patterns.
2. **EXISTING?** If a fit exists, document it.
3. **COMPATIBLE?** If yes → **REUSE** (or EXTEND). If no → document the incompatibility.
4. **NEW** only with evidenced gap — never "create because needed".
5. Skipping reuse on non-greenfield work → **STOP** (SR-12).

## Workflow
1. Confirm release intent; reuse existing meta pipelines.
2. Run meta rebuild CLI paths only.
3. Never treat this as rewrite Apply / SAFE_REWRITE change.

## Anti-patterns
- Skipping gates to "ship" migrated class rewrites.

## Inputs / Outputs
- Inputs: docs
- Outputs: meta-json, report