Support release staging across versions

[olegberman]

Summary

• let the N-1 lifecycle gate recognize 0.1.14's Compose action and 0.1.15's New email action without loosening the exact accessible-name match
• preserve useful app-shell diagnostics when a page contains inline scripts
• stop treating the expected absence of a Git tag on an untagged draft as cleanup failure

Root cause

Signed release workflow run #20 correctly bootstrapped the previous stable 0.1.14 build. The staging test introduced in PR #44 only recognized the new 0.1.15 action name, so the N-1 phase could no longer complete. The failed draft was deleted; gh release delete --cleanup-tag then returned 422 because draft releases do not create the v0.1.15 Git ref before publication.

Validation

• CI=true WRANGLER_LOG_PATH=/tmp/hqbase-release-0.1.15-cross-version-check-wrangler.log pnpm check
• CI=true WRANGLER_LOG_PATH=/tmp/hqbase-release-0.1.15-cross-version-dry-run-wrangler.log pnpm deploy:dry-run
• node scripts/check-docs.mjs
• failed 0.1.15 draft absent and v0.1.15 absent before the next full release run