docs(plan): #232 closed — UpToDate on 2 nodes via blockstor, no manual drbdadm

  test-worker-1: auto-rd role:Secondary disk:UpToDate
                   test-worker-2 role:Secondary peer-disk:UpToDate
  test-worker-2: auto-rd role:Secondary disk:UpToDate
                   test-worker-1 role:Secondary peer-disk:UpToDate

Full happy path: kubectl apply RD + 2 Resource → controller →
satellite → loopfile + drbdadm adjust + auto-primary --force → both
peers UpToDate without anyone running drbdadm by hand.

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>

Author: kvaps

PLAN.md

@@ -250,7 +250,7 @@ Full scope list lives in `docs/csi-api-surface.md` (to be created in Phase 1).
 - [x] Resource reconciler (`pkg/satellite.Reconciler`) routes DesiredResource batches: storage provider CreateVolume per volume, ConfFileBuilder writes /etc/drbd.d/<name>.res, drbdadm create-md (first activation, non-DISKLESS) + adjust. Status writeback from events2 stream is the next slice.
 - [x] Status writeback complete: satellite agent runs `drbdsetup events2` → `pkg/drbd.Watcher` → `Observer.Translate` → `Controller.ReportObserved` client-streaming RPC; controller's `applyObserved` writes DrbdState prop + Resource.State.InUse onto the matching Resource so REST clients (linstor-csi, kubectl-linstor) see live runtime status. Per-volume disk-state schema lands when the CRD's volume-level status fields are pinned.
 - [x] Auto-primary seed: Dispatcher tags one replica per diskful RD with `drbd_options[auto-primary]=true`; satellite `applyDRBD` runs `drbdadm primary --force` on firstActivation and immediately drops back to Secondary, so a brand-new RD reaches UpToDate without an operator's `drbdadm` invocation.
-- [ ] Resource on 2 nodes replicates and goes UpToDate (real DRBD smoke)
+- [x] Resource on 2 nodes replicates and goes UpToDate (real DRBD smoke) — **closed end-to-end** with auto-primary seed (2026-05-08): `kubectl apply RD + 2 Resource` → controller → satellite → loopfile + drbdadm adjust + auto-primary --force → both peers `disk:UpToDate peer-disk:UpToDate` without any manual drbdadm. Cross-node TCP convergence works under hostNetwork DaemonSet on the Talos stand.
       — **gRPC plumbing is now complete on the stand**: proto split
       into `service Controller` (Hello + ReportObserved) and `service
       Satellite` (ApplyResources + snapshot RPCs); the satellite