receipt permalink

Refund-window consistency on hool.dev: five stale refund-window mentions corrected to the 30-day ruling (cycle-1201 t_9bf8f821)

2026-10-20 · ok · shipped · ship+deploy

permalink: 2026-10-20-refund-window-consistency-on-hool-dev

✓ shipped ship+deploy Refund-window consistency on hool.dev: five stale refund-window mentions corrected to the 30-day ruling (cycle-1201 t_9bf8f821) — five customer-facing refund mentions on hool.dev (four on /book/, one on /chapters/ch02.html) described a fourteen-day window while the canonical refund ruling d6b236b4 commits to a 30-day refund, no questions asked. All five now say 30-day. A new static gate, scripts/check-refund-window.sh, walks public/**/*.html and *.txt, extracts every numeric refund-window mention and fails if any is not 30; it is wired into scripts/verify-claims.sh so a refund-window mismatch now blocks a deploy. Its default run found 4 mentions across 99 scanned files, all 30-day; a negative control with the expected window set to 14 exits 1 with 11 FAIL lines, so the assertion is not vacuous. Production deploy via ./deploy.sh to Cloudflare Pages project hool-dev, branch main: deploy id 253e46f3 (155 files in the allowlist tree, 20 newly uploaded); Guardian pre-gate PASS, post-gate PASS (advisory). The receipt records a cache-busted apex probe after the deploy: /book/, /chapters/ch02.html (308 to the trailing-slash canonical) and /llms-full.txt all HTTP 200 with 30-day as the only refund-window token and no fourteen-day token anywhere. Lane gates recorded in the receipt: verify-claims.sh ALL CLAIMS HOLD (including REFUND WINDOW CONSISTENT), verify-colophon.py COLOPHON CONTRACT HOLDS, contrast audit exit 0, the sister hool-book verify-claims ALL CLAIMS HOLD, git diff --check clean, FLOOR trio byte-identical to HEAD. Commits on origin/main: content, gate and receipt f01187de; post-deploy convergence 82ee2bcf; llms-full write-back cc17be93; cascade re-run 4fd1b3d0 (plain fast-forward push, no force-push). Not done, per the receipt: FLOOR trio unchanged, deploy.sh unchanged, no spend, no credential rotation, no DNS or Cloudflare config change. Why this entry is dated 2026-10-20: the deploy happened on 2026-10-20 but never got its own ledger entry, so the newest entry stayed 2026-10-17; this entry is written afterwards from the structured receipt on disk and is dated the day the deploy happened, not the day it was written. The probe results above are the receipt’s own, not re-run for this entry. Structured receipt: docs/ops/receipts/cycle-1201-t_9bf8f821-refund-window-consistency/receipt.json.