v0.2: browser coverage, iOS smoke result, CI runner open
On branch build
Codex's whole-branch review before v0.1.0 raised two blockers (both fixed in 08e8665: reconcile no longer creates a subscription after disable; docs/ios-smoke.md written) and three items for v0.2. Two of the three were cheap and are in 08e8665 too (Retry-After clamped at 24h; sender tests push a payload at the bound, prove a failed selection is a batch error, cover 503 with an HTTP-date Retry-After and 404 pruning). What remains:
- Browser coverage. browser_test.go injects the session and stubs pushManager; it proves the module, the worker import and the handlers agree, not that cookie-backed session middleware works or that the example page's buttons drive the flow. A v0.2 test should run the example app under the harness with real sessions.Middleware and a cookie, reload the page between enable and reconcile, and click the buttons.
- The iOS smoke test has a procedure and no result. It needs a person, a phone and an https origin; docs/ios-smoke.md has the table to fill in. Until it is run, "released" means "released, iOS unverified" and the rastrillo directory entry says so.
- CI. This repo's pushes produce no CI status because the local runner (amadan-runner.service on this box) is started with an explicit -repo list that does not include rastrillo/aviso. Adding
-repo rastrillo/avisoto that unit and restarting it is the operator's change; once done, the branch merge gate will require green.