Factory docs, home

A record from the Factory repository, docs/deploy-sites-routes-removal-receipt.json, shown exactly as committed. Every hash, date and count is as recorded. The build review says what the Factory's receipts support.

{
  "recordedAt": "2026-10-02",
  "component": "Deploy step: Workers routes reading removed, adoption re-read before each deploy",
  "base": "a1b45b4",
  "branch": "factory/deploy-sites",
  "disposition": "implemented-awaiting-independent-review",
  "files": {
    "scripts/deploy-sites.ts": "935dd0e4c329c79c7b40ccbe345891d3d38709b5aacf575e745b65b2076a149e",
    "test/deploy-sites.test.ts": "897cff089f2fec1cf7fe5cefba2a271d74ee7aa6bf2c6ca9a82fb37904e182e4",
    "docs/how-to/publish-the-sites.md": "b77ddb96c475b69d4c9bf3ddd590a6094b29403d4a4eb50b31c945b000963b35",
    "deploy/targets.json": "3b257f53f107b54ecb59bf7e676d25c83d735352d3c3544018d374735c04bf0f"
  },
  "decision": "Owner, 2 October 2026, about the Workers routes reading the guarded deploy step required: \"let's remove the route check requirement if that's gunna require manual deploys\". It does, so the owner accepts the residual: a Workers route elsewhere in the account pointing at plumbfactory-website or plumbfactory-docs would serve the new content, unseen.",
  "changes": [
    "Removed the Workers routes reading entirely: ROUTES_READING, its kind and maximum age, routesReadingProblems, checkRoutes and both calls, the routesReading option, the routes field of the report and record, and the archived workers-routes.json. The zone listing served only that check, so the cf zones list call, parseZonesListing and ZONES_PAGE are removed too and the allow-list admits six forms, not seven.",
    "Kept every other guard: allow-listed targets, adoption of each Worker's domains and references, review records, exact-commit build and tests, dry runs, post-deploy HTTPS verification and redaction.",
    "Adoption is read again immediately before each live deploy (Astra w3 finding 2, Fable w3 finding 1): both Workers' domains and references, and the Worker's latest deployment, which must still be the one recorded at the first reading. A deploy replaces the domain list, so drift in the window is now refused before the deploy, not found after it.",
    "DEPLOY_TESTS_MINIMUM is 55: two route-reading tests removed on the owner's decision, three added.",
    "The how-to loses its Workers routes section and the reading in the run steps; under Not established it states the accepted residual with the owner's date and words. The script header and the receipt's notEstablished line say the same."
  ],
  "testsRemovedOnOwnerDecision": [
    "Workers routes, which cf cannot list: the owner's reading must be made in the quarter-hour before each deploy ... (reading validation, zone listing parsing and in-run refusals)",
    "the routes reading is judged again against the zones cf lists and the clock before each deploy ... (stale, changed, swapped and uncovered readings)"
  ],
  "testsAdded": [
    "no Workers routes reading is needed: a run makes no zones call, reads no routes file, records no routes, and says in its receipt that routes are not checked",
    "a time is a real calendar instant in UTC, or nothing (timestampMs cases, kept from the removed test because deployment times still use it)",
    "adoption is read again immediately before each deploy: another domain, a service binding, another deployment or a gradual deployment of either Worker refuses that deploy and deploys nothing more"
  ],
  "notEstablished": [
    "That no Workers route elsewhere in the account sends requests to either Worker: cf cannot list Workers routes, so the step does not check them. The owner accepted this on 2 October 2026.",
    "A live run of the step, and independent review of this change."
  ],
  "review": []
}

Source: docs/deploy-sites-routes-removal-receipt.json