`SUBSPACES.md` still describes the older `authorize --to` delegation flow. The CLI and working ceremony on `744e75a7625f98dbe5e3a484f962769e506c5381` are: ```text owner: operate @space operator: getnewspaceaddress owner: delegate @space --to <operator-space-address> ``` The distinction matters: a plain num transfer does not establish the delegation relationship, and `delegate --to` requires the Space to have been operated first. Owner self-transfer or renewal revokes the delegation, after which `operate` plus `delegate --to` restores it. Could `SUBSPACES.md` be refreshed to document the current commands, the operate-before-delegate requirement, and the renewal/revocation consequence?