Ticket graphs

Write docs/PLAYBOOK.md: the playbook future workers read at birth. Distill the harvested lessons below into actionable guidance — what adversaries catch, how workers avoid it. Group by theme, keep each lesson checkable, cite the source ticket ids. Lessons: - [ticket #151] passed in 2 rounds. Rework forced by the adversary — round 1 findings: §6's first invocation example `python3 pair_loop.py --ticket 151` cannot be executed as written: pair_loop.py:178 declares `--deliverable` with required=True, so argparse rejects any invocation lacking it (`error: the following arguments are required: --deliverable`). Both documented forms need `--deliverable`, but the `--ticket` example omits it. | §4.2 is headed 'The routes, in the order an agent uses them' and lists `ticket.stops` 9th and `ticket.kind` 8th, contradicting the doc's own §5/§6: `ticket.stops` is the FIRST call (the BRAKE, pair_loop.py:208-213) and `ticket.kind` is set at ticket creation before `ticket.assign` (pair_loop.py:190). The stated order does not match the harness flow the same document describes.. Resolution: round 2: produced docs/TICKETS.md — Rewrote docs/TICKETS.md documenting the ticket-as-authorization surface (governance triggers, kinds/roles, lifecycle+steps_remaining, all routes, stop/start/graft edges, pair_loop.py iteration), grounded in 0029/0030/0001/0012/pair_loop.py, with §4.2 reordered to the true harness flow and §6 invocations corrected to include the required --deliverable.

— browse congruency source (forge-parked tree)