docs-release-announcelisted

# docs-release-announce — Announce new releases to Slack and/or email ## Workflow 1. **Verify MCP transport** — call `list_workspaces` as a connectivity probe. If it fails, print the MCP connection command and exit gracefully. 2. **Validate inputs** — confirm that at least one notification channel is selected. Validate that a Slack URL starts with `https://hooks.slack.com/` when Slack is selected; validate that an email address is well-formed when email is selected. 3. **Register the release webhook** — generate a fresh HMAC secret and register a webhook that fires when a new release is published on the workspace repository. Surface the secret to the user once. 4. **Generate the handler workflow** — produce a GitHub Actions workflow file configured for the selected channels. The workflow triggers on the `release: published` event and dispatches notifications using secrets stored in the repository. 5. **Write the workflow file** — place it at `.github/workflows/docsbook-release-announce.yml`, creating the directory if needed. Overwrite if the file already exists. 6. **Report** — print the workflow path, selected channels, and the names of the repository secrets the user must configure. ## Guardrails - Require at least one channel — Slack or email; reject a call with neither. - Never hardcode channel credentials in the workflow file — always reference repository secrets. - If the webhook registration tool is not available on the connected MCP server, fall back to wiring the