STATIC PUBLICATION — RELEASE + HANDOFF CHECKLIST
TAHAI Web Services | Companion to “Publish Without a Database”

Use with the documentation for your chosen TAHAI-Press release.
A checkmark records a completed check; it does not perform the check.
Mark any untested item explicitly and assign an owner.
Do not include credentials or private source material in a public release.

RELEASE RECORD
Publication: [                            ]
Source repository: [                     ]
Source commit / release: [                ]
Approved production branch: [             ]
Node / tool versions: [                   ]
Prepared by: [                           ]
Editorial approver: [                     ]
Technical approver: [                     ]
Preview URL and access policy: [          ]
Intended production URL: [                ]
Prior known-good deployment: [            ]
Rollback authority / contact: [           ]

1. OWNERSHIP AND ACCESS
[ ] Repository, domain, hosting, and editor account ownership are documented.
[ ] Required access was tested using the actual authorized roles.
[ ] Production approval and branch behavior are understood.
[ ] Account recovery and multi-factor authentication arrangements are in place.
[ ] Secrets are kept in approved stores, not in source or the handoff ZIP.
[ ] Confidential working material is excluded from public source and output.

2. SOURCE AND IDENTITY
[ ] Chosen release and instructions match the checked-out source.
[ ] Publication name, description, contact, site_url, and identity are correct.
[ ] Example content, contributors, categories, and policy text were reviewed.
[ ] Images and documents are the intended versions and have publication approval.
[ ] Intended production template_mode and indexing behavior are confirmed.
[ ] Dependency lockfile is preserved and clean installation succeeds.

3. EDITORIAL REVIEW
[ ] Headline and summary accurately describe the article.
[ ] Assertions have appropriate sources; examples are clearly distinguished.
[ ] Author, category, dates, and classification are correct.
[ ] Image descriptions, captions, credits, and rights were reviewed.
[ ] Document-led stories have a meaningful text introduction and source link.
[ ] Privacy and source-disclosure review is complete.
[ ] Corrections and meaningful updates are visible where appropriate.
[ ] Publication review fields reflect actual review, not automatic defaults.

4. BUILD RECORD
Record the command, source revision, date, result, and evidence location.

Command/check: [                         ]
Environment: [                           ]
Result: [Pass / fail / blocked / not run]
Evidence: [                              ]
Limits: [                                ]

[ ] Dependencies installed using the release's documented lockfile workflow.
[ ] Content, configuration, references, and redirects passed applicable checks.
[ ] npm run ci completed successfully in the stated environment.
[ ] Cloudflare build settings match the intended release contract.
[ ] dist/ was inspected; source, private artifacts, and secrets are not shipped.
[ ] The release artifact is identifiable and reproducible from retained source.

5. PREVIEW — ACTUAL READER TASKS
[ ] Homepage, article, archive, and search paths were checked.
[ ] All article sections and the footer received full-size visual review.
[ ] Narrow mobile and desktop layouts were inspected.
[ ] Keyboard navigation, focus, links, and controls work.
[ ] Browser zoom and text enlargement were checked; content remains usable.
[ ] Essential content and direct document links work without optional JavaScript.
[ ] Embedded PDF fallback and direct download/open behavior were checked.
[ ] Meaningful images remain legible and correctly cropped.
[ ] Preview indexing restrictions are present.
[ ] Confidential previews use access control, not just noindex or robots rules.

6. PRODUCTION — AFTER AUTHORIZED DEPLOYMENT
[ ] The intended deployment is active on the correct production hostname.
[ ] HTTPS and real domain routing work.
[ ] Canonical links, sitemap, feeds, metadata, and sharing URLs use production.
[ ] Production indexing behavior is intentional; template blocks are removed
    only for content approved to become discoverable.
[ ] An unknown URL returns the intended real error status and page.
[ ] Relevant redirects reach the correct final content.
[ ] Reader workflows were repeated on the production site.
[ ] Caching/service-worker behavior was checked where those features are enabled.
[ ] Advertising/analytics/consent settings were separately verified if installed.
[ ] Account-dependent and physical-device checks are recorded, not assumed.

7. SCHEDULING AND CORRECTIONS
[ ] Scheduled-publishing workflow is enabled if it is being relied on.
[ ] Editors understand that the documented hourly scheduler can run late.
[ ] Normal corrections preserve the permanent article slug.
[ ] Required URL changes include reviewed previous-URL/redirect handling.
[ ] Editors know how to make a public correction note.

8. RECOVERY AND HANDOFF
[ ] Known-good production deployment and rollback process are identified.
[ ] Repository correction accompanies any delivery rollback.
[ ] Source/history, approved media, and release records have an independent backup.
[ ] Generated output is retained where useful but is not the only source backup.
[ ] The owner has the publishing, editing, deployment, and recovery instructions.
[ ] A supervised publishing cycle was completed with the intended operator.
[ ] Build-failure notices reach the responsible owner.
[ ] Remaining tasks have named owners and acceptance criteria.

FINAL RELEASE DECISION
Approved to deploy: [Yes / no / conditional]
Approved scope: [                         ]
Unresolved blockers: [                   ]
Accepted limitations and approver: [      ]
Next action / owner: [                    ]

Permission: You may copy and adapt this checklist for your own publication.
The checklist does not certify a release or replace review of its actual output.