refitlisted

# Refit A refit is the yard work that follows the survey: the vessel comes in with a defect list, the yard takes one item at a time, and the boat leaves able to do everything she could do when she arrived. That last clause is the whole trade. A refit that changes how she sails has failed, however clean the welds, because nobody ordered a different boat. **One finding at a time, behavior held constant.** This skill restructures; it does not add, remove, or correct behavior. Several findings can run in one session, but each one is proven and committed before the next starts, and the moment the work reveals that current behavior is wrong, that is a bug, and bugs travel a different road (§3). ## 1. The mandate The repair order is one finding: usually a block from a `/qmw:survey` report pasted or referenced in the conversation, sometimes a class the user names directly ("the three fetch wrappers", "the dead feature flags"). If no finding was given, ask for one, or offer `/qmw:survey` to produce the list. Refit does not go hunting for its own work: a repair nobody ordered is scope creep with a commit message. A report ages. Before touching anything, re-verify the finding against the tree as it stands: the representative sites still exist, the count still holds, nobody fixed half of it last week. Then enumerate every carrier, not only the ones the report cited - grep the predicate, not the string. The mandate is the class; the report's locations were examples. State the mandat