[jlwaugh]

ADR 2: the consent change wallet owner actions need, before the strategy grant.

• Server: POST …/consent/text takes { owner: true } only at a wallet owner's choice: at connect, or to add it to a connection without it (anything else live is still already_connected). checkConsent accepts read+treasury or read+treasury+owner exactly. A DAO's consent never carries owner (the platform files a DAO's owner actions for its vote): asking for it is bad_request, nothing filed.
• Page: a checkbox to also allow owner actions when connecting; Allow owner actions on a connection without it, whose dialog says first that replacing the connection withdraws its open proposals. The scope wording names what this server now does (proposes, executes approved, deposit, link, sweep) and what owner allows (prepare owner actions and relay the owner's own signature; none takes effect without it).
• Tests: server unit (opt-in, upgrade, replacement revokes the old consent, already_connected after, DAO refusal, consent checks); stack (browser): the upgrade stored as owner, read and treasury, and an open proposal under the old consent reads withdrawn.