docs: record the v0.9.8 deploy and what was checked after it

deploy.sh reported "0.9.6 -> 0.9.6" and an unchanged digest, which is #236
doing exactly what it is filed for: it reads both before the container is
replaced. What actually happened, checked independently: qn-website-dev is
healthy on v0.9.8 with 0 restarts, and its image id 62d076e3800d is the id of
the image release.sh built. Both front doors answer ok, the crawler audit is
clean across 18 pages as all five agents, 18 sitemap entries carry a lastmod,
and the device sweep against production reports zero findings across ten
profiles and 190 page loads.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/history/DEVELOPMENT_LOG.md

@@ -118,8 +118,28 @@ Exit codes were proven separately: 2 for an unreachable origin and for an
 unknown `--devices` name, because "nothing was swept" must never read as
 "nothing was wrong".
 
-**Next action:** deploy v0.9.7, which carries both the "25+ years of industry
+**Deployed as v0.9.8**, from 0e47183. Production ran 0.9.6 until now, so this
-experience" wording change and this sweep. Production is still on v0.9.6.
+is the first deploy carrying both the sweep fixes and the "25+ years of industry
+experience" wording.
+
+Checked after the recreate rather than trusting the deploy's own report, because
+#236 is still open and did exactly what it says it does: `deploy.sh` printed
+"0.9.6 -> 0.9.6" and an unchanged digest, having read both before the container
+was replaced. Independently: `status.sh` shows `qn-website-dev` healthy on
+v0.9.8 with 0 restarts, and its image id `62d076e3800d` is the id of the image
+`release.sh` built. Both front doors answer `{"status":"ok","db":"ok"}`. The
+crawler audit reports nothing wrong across 18 pages as all five agents, and 18
+sitemap entries carry a lastmod. The device sweep against production, all ten
+profiles and 190 page loads, reports zero findings, which is the first time this
+site has been measured on devices in production rather than locally.
+`qn.isnull.dev` reports one finding, the already-filed #237.
+
+**Next action:** #217, submitting the two service URLs to Google Search Console
+and Bing Webmaster Tools. Its release and deploy halves are done, at v0.9.8
+rather than the v0.9.6 the issue was written against.
+
+**Blockers:** #216 needs Levi's four vendor screenshots. #217 needs Null's or
+Levi's Search Console and Bing accounts.
 
 **Blockers:** #216 needs Levi's four vendor screenshots. #217 needs Google
 Search Console and Bing Webmaster Tools access to submit the two service URLs.