chore: write remedies for the issues a drain could not take

[REPPL]

This PR changes issue records only; no code changes.

A drain dry run found nine open issues with no remedy, which made them ineligible, and one that was already decided to wait for the decision-model spec.

• Remedies stated in the record itself, written without a question: iss-2609190200104841 (pairing lock on the discovered row), iss-2609200818340380 (colour swatch row), iss-2609200822241060 (one row per server in the picker), iss-2609200823585535 (README: simulator model needs Apple Intelligence on the Mac), iss-2609210738484563 (stable reasoning box while streaming).
• Remedies chosen by the maintainer in an interview:
  • iss-2609200817467659: scale the chat's fonts on macOS.
  • iss-2609200816105905: one bubble per heading section.
  • iss-2609202010356702: an operator Unload cancels an idle job's soft hold.
  • iss-2609211754253878: one bounded first completion during readiness, with the 2026-09-21 step floor untouched.
• iss-2610041945038826 now opens "Waits on" the decision-model spec, so a drain hands it back by rule.

One dated line in .abcd/work/DECISIONS.md records all of it. With the repository's drain rule in place, a dry run on this head gives 15 eligible, 46 handed back and 1 skipped.