sb-releaselisted

# Release the milestone ## Apply project language style Before authoring any artifact or user-facing prose, read: ```sh specbind rule read language-style --for consume ``` Apply returned policy only to natural-language prose. `NO_CHANGE RULE_ABSENT` means no additional project preference; any `ERROR` line stops the workflow. The whole milestone or nothing. There is no partial release and no subset option. You orchestrate; the CLI owns every mutation of SpecBind state. **SpecBind never verifies that a publication happened** — you and the user judge that. ## 1. Read the state and bootstrap release policy once ```sh specbind milestone status specbind adapter read release --for consume specbind adapter read git --for consume ``` The Release adapter owns project release work. The Git adapter owns the narrow project checkpoints this run may need; reading it grants no authority beyond its current guidance. Classify the exact Release adapter read result before doing anything else: 1. `NO_CHANGE ADAPTER_ABSENT` or `NO_CHANGE ADAPTER_SCAFFOLD` means the adapter is **unconfigured** and enters the bootstrap flow. 2. Returned content with the required Front Matter and only whitespace after it is an **explicit empty adapter**. Do not bootstrap it. Continue to core release under the empty-body rule below. 3. Otherwise the returned active body is project policy. Never infer that an adapter is unconfigured merely because its returned body contains no instructions. The con