Update docs/chat-verification.md from the earlier `3ffc126` record to the
current revision `ec27a2d`, which is both this lane's HEAD and main:
- revision, APK name/size/sha256 and LAN URL refreshed to the rebuilt
artifact `pipelines-debug-wip-ec27a2d.apk` (18,585,084 bytes,
sha256 5ee4b38c…da84);
- unit-test totals refreshed to 61 suites / 558 tests / 0 failures, and the
server-side `go build ./...` plus the chat/session/adopt Go tests recorded;
- a "Changes since the previous record" section describing the chat-relevant
delta `3ffc126..ec27a2d` (the `chat_adopt` request, the lazy
`MarkdownBlocks` renderer, the run-watch scope change) and correcting the
chat protocol file path to `data/protocol/Chat.kt`.
The change is documentation only: no app or server behaviour changes.
Checked where the change belongs: packaged templates (no template encodes
this record) and the packaged authoring skill references
(internal/author/skill/references/) — none is made stale by a
verification-record update, so none is touched. `go build ./...` passes.
The debug APK lives in the run's artifacts directory outside the repo and is
therefore not committed.
Refs: brief "Verify the chat end to end, on the phone, against the real server".
Add docs/chat-verification.md, the required record for the chat verification brief: per-flow table (flow, result, evidence path, notes), the known tree-level gaps, and the section on what could not be verified and why. Verification only; no app behaviour changed.
Checked: packaged templates (internal/author/skill/references/) do not mention this record - no template or skill reference needed updating. Shared README and topic docs are intentionally not touched (single-writer fold).