wrapuplisted

# Wrapup — Session Close Procedure Every step below is mandatory unless explicitly marked optional. Skipping a mandatory step and reporting SHIP is a protocol violation. The wrapup exists to produce a faithful, verifiable record of the session and deliver it to the destinations the user configured — nothing more, nothing less. ## Core principles 1. **Fidelity first.** The summary reflects what actually happened. Do not smooth over failures, abandoned approaches, or unresolved blockers. 2. **Configured, not assumed.** Destinations, paths, and formats come from `config/wrapup.config.json`. If a destination is not configured and enabled, it does not exist for this run. 3. **Evidence over claims.** Completion is proven with returned links, file paths, or API confirmations per destination — not with "done." 4. **User-agnostic.** This skill ships with no personal names, no machine paths, and no references to any individual's infrastructure. Everything personal lives in config. --- ## Configuration ### File layout ``` wrapup/ ├── SKILL.md ├── config/ │ └── wrapup.config.json # active config (generated by onboard.py or hand-edited) └── templates/ └── destinations.example.json # schema + example, ships with the skill ``` ### Destination schema Each destination in `wrapup.config.json` has exactly these fields: | Field | Type | Description | |-------|------|-------------| | `id` | string | Unique slug, e.g. "transcript-archive", "knowledge-base" | | `type` | s