Read first — JSONL piping, batch read, pagination, dry-run/digest/confirm, and recovery live there. is authoritative. Tickets use the object type (plural, e.g. ). 1. Discover pipeline + stages (portal-specific, run every session) Stage IDs differ in every portal — never hard-code them. The stage table prints each stage's and ("New", "Waiting on contact", "Closed", etc.). / also return each pipeline's full array in / , so one call is enough to map a value to its label. 2. Verify enum option values for THIS portal , , and are all properties — option values are portal-configurable. List the allo…