What problem does it solve? When sorting through incoming cargo records (proposals and postmortems), teams need a consistent way to read unsorted items and mark their state transitions — in work, fixed, released — without losing track of which records were handled or why a mark was refused. ## Core Features & Use Cases - Read unsorted records: Pull new proposals and postmortems in arrival order with npm run cargo:pull, including full texts via --text. - State marking: Move records through in_work, fixed, and released states with npm run cargo:mark, batching multiple records per call and supporting dry runs. - Foreign record closing: Close another tree's records with npm run cargo:close under a service account when your edition shipped their fix. - Refusal handling: Interpret refusal reasons (wrong key, skipped state, missing fix text or release version) and correct the call. - Use Case: After merging a fix into the main branch, mark the related postmortem as fixed with the fix description, then mark it released with the published version number. ## Quick Start Ask the assistant to read all new cargo records and mark the triaged ones as in work using the cargo-triage-mark pattern.
