Add entry: Release rehearsal — live publishing check

catalog/release-rehearsal-live-publishing-check/index.md

@@ -0,0 +1,56 @@
+---
+layout: entry
+render_with_liquid: false
+title: "Release rehearsal — live publishing check"
+slug: release-rehearsal-live-publishing-check
+published: "2026-08-28"
+featured: false
+thumbnail: ""
+organization: Template release rehearsal
+solution_type: Internal tool
+use_case_category: Administrative & task automation
+area:
+  - Emergency preparedness
+stage: Pilot
+summary: "A deliberately non-sensitive rehearsal submission that walks the template's own publishing path end to end: web form, generated issue, scaffolded pull request, required checks, human merge, Pages deploy and search index. It exists to prove the release candidate's flow on this repository and will be removed immediately after verification."
+impact: The submission-to-published-page path verified live on the release candidate.
+review_status: Under review
+security_review: ""
+ai_role: AI was used to build it
+ai_types: []
+ai_tools: []
+platform: []
+vendor: ""
+expertise: Anyone on staff
+readiness: []
+repo_url: "https://github.com/crypticpy/phct"
+demo_url: ""
+docs_url: ""
+resources: []
+screenshots: []
+deck_pdf: ""
+also_deployed_by: []
+license: MIT
+access_terms: ""
+portability: "Yes — platform-agnostic"
+portability_notes: ""
+reused_from: []
+cost_band: No new spend
+run_cost: No ongoing cost
+procurement:
+  - No procurement needed
+approvals: []
+equity_note: ""
+no_pii_attestation: true
+data_sensitivity:
+  - Public data only
+data_sources: []
+audience: Internal staff
+data_governance_notes: ""
+contact_name: Release Rehearsal
+contact_title: ""
+contact_email: "rehearsal@example.org"
+submitter_github: crypticpy
+---
+
+This entry is a live release rehearsal, not a real use case. It was submitted through the repository's own issue form to prove, on the current release candidate, that a public submission becomes a scaffolded pull request, passes the required checks, publishes through Pages after a human merge, and lands in the search index — and that the whole thing can then be taken down cleanly through the same reviewed path. If you can read this on the deployed site, the rehearsal worked and the removal pull request is already on its way.