expeditelisted

# expedite The expeditor at the pass drives tickets from the board to plated, in priority order, and lets nothing leave half-cooked. This skill takes an audit backlog (from line-check, bug-hunt, or security-sweep) and executes it: highest-leverage finding first, one focused change at a time, each one verified before the next is started. The audit trio is read-only on purpose. This is the separate step it hands off to. Findings already carry severity, effort, location, and a fix; the work is execution discipline, not re-analysis. ## Preconditions Check before touching anything; stop and report if any fail: - A backlog exists. The input is an audit report following the report contract (a `## Backlog` section, or `## Findings` to sort yourself). No report? Run line-check, bug-hunt, or security-sweep first, do not freelance. - Working on a branch, never the default branch. Create one if needed (`expedite/<audit>-<date>`). - Clean tree to start, so each finding's change is isolable. ## Execution Work the backlog in leverage order (impact relative to effort), the order the report already sorted. If the report has only a `## Findings` section and no `## Backlog`, sort it yourself first: cheap high-impact items float to the top, severity breaks ties. An `L`-effort finding that cannot land in one focused session is not a half-job: attempt it only if it is cleanly isolable, otherwise surface it under Remaining with an estimate rather than leaving the tree mid-change. For each fi