---
description: Close the personal-rail session honestly — prove it still works, record what changed
---

# WRAP — close the session honestly

The point is that the next session lands on truth, not on what we hoped happened.

## Do

1. **Prove the rail still works.** Run `tests/smoke.py`. Report the result. If it fails, say which
   check and what the actual error was — never just the class name.
   **Not within an hour of a scheduled brief** — smoke calls `collect()` and moves live cursors.
2. **Confirm the schedule survived.** Both jobs still registered, still enabled, next run times
   sensible. If one vanished, that is the headline.
3. **Record decisions.** Anything you chose this session — a library, a structure, an approach —
   goes into `RUNBOOK.md` with one line on why. Rocky can't audit code but he can audit reasoning.
4. **Note what you found and didn't fix.** One line each at the bottom of `RUNBOOK.md` under
   `## Open`. A thing found and forgotten is worse than a thing not found.
5. **Check nothing leaked.** No secret value in any file you wrote this session. No `.env` value in
   `logs/`. No message body in a log. Run the scan over tracked files, don't eyeball it.
6. **Commit.** Uncommitted work doesn't exist. Data, state and logs are gitignored — check the
   staged list before committing, not after.

## Report

```
WRAP — {date} {time}

CHANGED
  {one line per real change}

PROVEN
  smoke        {pass/fail + detail}
  schedule     {both jobs + next fire}

OPEN
  {anything found and not fixed, one line each, or "nothing"}
```

## Rules

- **Claim nothing you didn't watch happen.** "Should work" is not a wrap line. Name the artefact —
  the file written, the message that arrived, the exit code.
- If you changed something and couldn't verify it, say **UNVERIFIED** in the wrap. That word is
  cheap; a false "done" costs a week.
- If the session broke something and you reverted it, say what and why. That's the most useful line
  in any wrap.
- Don't pad. A quiet session wraps in four lines.