Skip to content

Add entry: Release rehearsal — live publishing check - #52

Merged
crypticpy merged 2 commits into
mainfrom
entry/release-rehearsal-live-publishing-check-51
Aug 28, 2026
Merged

Add entry: Release rehearsal — live publishing check#52
crypticpy merged 2 commits into
mainfrom
entry/release-rehearsal-live-publishing-check-51

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Scaffolded from issue #51.

Closes #51

The entry

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…

  • Organization: Template release rehearsal
  • What is being shared: Internal tool
  • Use case category: Administrative & task automation
  • Area of work: Emergency preparedness
  • Stage: Pilot
  • Result in one line: The submission-to-published-page path verified live on the release candidate.
  • Skills needed to set it up: Anyone on staff
  • License: MIT
  • Portable to other platforms: Yes — platform-agnostic
  • Cost to stand up: No new spend
  • Data it touches: Public data only
  • Who sees the output: Internal staff

Screenshots downloaded

None.

Maintainer checklist

Review criteria:

  • Completeness — Every required field is filled in, honestly.
  • Accuracy — The technology, licensing, open-source and portability claims are correct.
  • Data governance — No personal or protected health information in the resource or its documentation; the sensitivity notes are honest and complete.
  • Reuse readiness — Enough documentation, links and contact detail that another jurisdiction could realistically evaluate or adopt it.
  • Category fit — Correctly placed in one of the community's use-case categories.

Before merging:

  • The summary reads clearly to someone outside the submitting team
  • Front matter values match the schema options and nothing is missing
  • Screenshots opened at full size — no names, addresses, record numbers or email addresses visible
  • Any PDF or extra file is uploaded into catalog/release-rehearsal-live-publishing-check/
  • Validate Content is green on the latest commit (re-check after any bot thumbnail commit)
  • review_status set to Reviewed & approved (the scaffold wrote Under review) — or the pull request left open with review:revisions-requested and a comment saying what to change
  • Merge to publish

@github-actions github-actions Bot added the content:new-entry Submission from the entry form; automation opens a pull request label Aug 28, 2026
@github-actions
github-actions Bot requested a review from crypticpy as a code owner August 28, 2026 04:42
@github-actions github-actions Bot added content:new-entry Submission from the entry form; automation opens a pull request review:intake Awaiting intake triage: complete, contact reachable, nothing that looks like PII/PHI labels Aug 28, 2026
@github-actions github-actions Bot mentioned this pull request Aug 28, 2026
Closed
@crypticpy @claude
review: give the rehearsal entry a link and clear the empty deck path
84dd8bf 
The front-matter gate rightly refuses an entry with no link anywhere,
and the scaffolded deck_pdf names a file no one attached — the exact
maintainer amendments docs/admin-guide.md prescribes for both notices.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD
@crypticpy
crypticpy merged commit 3a3e717 into main Aug 28, 2026
19 checks passed
@crypticpy
crypticpy deleted the entry/release-rehearsal-live-publishing-check-51 branch August 28, 2026 04:55
@crypticpy crypticpy mentioned this pull request Aug 28, 2026
Merged
crypticpy added a commit that referenced this pull request Aug 28, 2026
@crypticpy @claude
chore: remove the release-rehearsal entry (#53)
0c4086a 
The "Release rehearsal — live publishing check" entry proved the
form → issue → pull request → checks → merge → Pages path live on this
repository (issue #51, PR #52) and was verified on the deployed
showcase. Its removal completes the rehearsal's cleanup promise.


Claude-Session: https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
@crypticpy crypticpy mentioned this pull request Aug 28, 2026
Merged
crypticpy added a commit that referenced this pull request Aug 28, 2026
@crypticpy @claude
Cut v1.9.0-rc.7 (#54)
b97432b 
* docs: cut the v1.9.0-rc.7 release record

Version, changelog section and compare links for the two rc.6
refresh-cycle robustness fixes (PR #49), the upgrade preview pointed at
rc.7, the executable plan ledger retargeted from rc.6 to rc.7, and the
readiness evidence updated: candidate provenance, the completed PHCT leg
of the live publish rehearsal (issue #51 -> PR #52 -> live -> removed in
PR #53), and the RR-H03 remainder narrowed to notification delivery.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD

* docs: record the rc.7 verify run at its exact commit

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@crypticpy crypticpy Awaiting requested review from crypticpy crypticpy is a code owner

Assignees

No one assigned

Labels

content:new-entry Submission from the entry form; automation opens a pull request review:intake Awaiting intake triage: complete, contact reachable, nothing that looks like PII/PHI

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Use case] Release rehearsal — live publishing check

1 participant

@crypticpy