Task: Build the member's Security screen

Run Protect my account in ores.web against the real server, on variant B of the accepted prototype: the places the account is signed in lead, and the password form and the sign-in state share the row under them.

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

Done 2026-10-01.

Security is a route behind the signed-in shell. It reads the account's login record, the tenant's sessions for the account and the server's password policy, and changes the password through the route that already existed. The screen is the accepted prototype's variant B.

Two things the server cannot do yet are stated on the screen rather than hidden: ending one other sign-in has no operation, so no row offers it; and nothing writes a session's end time, so the list holds every session the deployment has created and an old one cannot be told from a live one.

Verification: 334 tests green in three packages (bff 97 in 20 files, web 186 in 17, wire-protocol 51 in 7), typecheck clean, Prettier clean. The screen's copy is plain English and not in the three locales yet, which the story records as its own follow-up.