D1 fixup: split rollback guidance by migration stage to prevent read outage

Step 9 previously said 'flip the new entry's roles back to {"read":
false, "write": false} at any stage', which is unsafe after step 8
has already removed read from the ES 5 entry. Following that
instruction post-step-8 would leave zero read-capable hosts, causing
search errors for all in-flight requests.

Split the rollback note into two sub-bullets:
- Before step 8: removing the new entry is safe; ES 5 already serves
  reads.
- After step 8: restore ES 5 read role first (or simultaneously),
  then disable the new entry.

🤖 Generated by [robots](https://vyos.io)

0 files changed, 0 insertions, 0 deletions