VOID: redesign launch acceptance HTTP example
===========================================

Requires Node.js 22 or later. Extract the ZIP, open its folder in a terminal:

  node redesign-launch-acceptance-fixture.mjs

No packages, accounts, keys or website URL are needed. The program starts
two temporary servers at 127.0.0.1, checks broken and repaired modes, prints
the observations, and closes both. No remote system is contacted.

WHAT IT CHECKS

The retained authored baseline supplies the required service answer. The
old /drain-cleaning.html URL returns 301 directly to /services/drain-cleaning,
preserving the sample campaign and test ID. The destination returns 200,
retains the required answer and form, and declares a canonical without the
query. A distinct unchanged service page remains 200 and self-canonical.

The form POST returns 303 to a 200 thank-you page in both modes. The site
also receives HTTP 202 acknowledgements from the separate sample event
and enquiry stores in both modes. Those acknowledgements are not receipts.

Broken: the event-receipt GET returns 200 with no matching event. The
enquiry-receipt GET returns 503, so its matching-record count is null
(unavailable), not zero. The local acceptance decision is blocked.

Repaired: separate receipt GETs each return 200 with exactly one record
matching the test ID, service, campaign and landing path. Posting the same
token again leaves one record in each store during this server run. The
decision passes for this bounded local sample.

BROWSER WALKTHROUGH

  node redesign-launch-acceptance-fixture.mjs --serve broken

Open the printed local URL and choose Submit sample enquiry. Follow the
two receipt links on the thank-you page; each reads the other local server.
Stop with Ctrl+C, then repeat with:

  node redesign-launch-acceptance-fixture.mjs --serve repaired

Each server run stops after 120 seconds. Ports and sample IDs can change.
Forms work without JavaScript. Only fixed sample data is accepted; there
are no customer name, email, phone or free-text fields. All sample records
are held in memory and disappear when the servers stop.

USE IT ON A REAL MIGRATION

This is an authored HTTP model, not a GA4 or CRM integration. Its small
parsers cover its own markup only. It compares the required answer and a
small route/control set, not every page or all rendered content. It does
not measure Google indexing, attribution, qualified leads or revenue.

Use your release candidate's real old-to-new map and required-content
contract. With the appropriate system access, confirm the exact event in
the intended analytics property and the test enquiry in the destination
system. Match the approved test key and fields. Leave unavailable evidence
unavailable. Apply the same critical-path checks after production release.

Guide: https://www.void-agency.com/insights/website-redesign-seo-measurement-migration#worked-launch-sample
Existing blank map: https://www.void-agency.com/tools/redesign-migration-checklist
