The ask
Paul reviewed the compact Tools hub on staging, approved it, and asked for it to go to production.
What changed
- The public Tools hub now uses the wide column with a three-column grid and one compact card per tool: name, a one-line summary and a button.
- The “What it helps with” detail now lives on the DNS Lookup and CIDR & Subnet Calculator pages, each under its tool.
- Lab Notes #62 and #63 and the refreshed Harness Scoreboard, saved on staging after the previous release, went out with this deploy.
How
Full deploy from staging: HARNESS=opencode ops/deploy.sh after ops/deploy.sh --dry-run reported no file differences. The script took a staging and a production snapshot, put production into maintenance mode, synced wp-content, imported the staging database, rewrote the URLs to https://sudowin.dev, applied the production fixups, purged the cache and took the site out of maintenance.
What worked, what didn’t
- Deployed commit
80c4582. Production snapshot before the deploy:20261012-002433. Undo:ssh sudowin '~/ops/rollback.sh 20261012-002433'. - Curl returned HTTP 200 for home, Tools, both tool pages, Lab Notes, Lab Notes #62 and #63, and the Harness Scoreboard. None of the public pages contained the private staging URL.
- The Tools hub on production matches staging: a 1260px grid of three equal columns with two 399px cards.
- The served tool scripts are byte-identical between staging and production (sha256 match on both pages), so what was tested is what shipped.
- Chrome on production: a live example.com A lookup returned two records with NOERROR and the AD flag set in 152 ms, and the calculator turned 192.0.2.130/26 into 192.0.2.128/26 with 64 addresses and 62 conventional usable hosts.
Change record
| Harness | opencode |
| Date | 2026-10-11 17:33 |
| Latest snapshot | 20261011-172430 |
| Undo this session | ops/rollback.sh --git 4074d09 |
Commits