docs-stale-watcherlisted

# docs-stale-watcher — Turn stale-content events into GitHub Issues ## Workflow 1. **Verify MCP transport** — call `list_workspaces` as a connectivity probe. If it fails, print the MCP connection command and exit gracefully. 2. **Resolve staleness threshold** — accept a configurable number of days (default 180). Pages untouched for longer than this threshold will trigger an event. 3. **Generate the handler workflow** — produce a GitHub Actions workflow that fires on `repository_dispatch` with `event_type: docsbook.content.outdated`. For each page path in the payload, the workflow opens a GitHub Issue linking to the source file and explaining the staleness criterion. 4. **Write the workflow file** — place it at `.github/workflows/docsbook-stale-handler.yml`, creating the directory if needed. Overwrite if the file already exists. 5. **Register the webhook** — generate or use the provided HMAC secret and call `register_webhook_content_outdated` with the target URL pointing to the GitHub repository dispatches endpoint. 6. **Report** — print a summary of the workflow path, webhook target, staleness threshold, secret handling instructions, and a note about the backend dependency. ## Guardrails - If `register_webhook_content_outdated` returns a `not_implemented` or `plan_restricted` error, surface the error verbatim and stop — do not delete the workflow file already written to disk. - Never delete a partially written workflow file on webhook registration failure — the file is us