Skip to content

release: v1.43.2 - #1234

Merged
MBombeck merged 2 commits into
mainfrom
fix/v1432-consent
Oct 16, 2026
Merged

MBombeck merged 2 commits into
mainfrom
fix/v1432-consent

Conversation

@MBombeck

Copy link
Copy Markdown
Owner

Patch release: AI consent receipts require an explicit confirmation; consent card in the web; ai.consent on /api/auth/me.

The AI settings page posted to /api/consent/ai/web on every mount and the
server minted an ai_full receipt for it, so an account that had agreed to
nothing sent its health data to the operator's provider from background
jobs. Native builds synced a receipt the same way on every launch.

- Both grant routes now require `confirm: true`; anything else writes
  nothing and answers 400 consent.ai.confirmRequired.
- Remove the mount-time heal. A consent card names the operator's service
  and the data that would go there, with one Agree button, in Settings > AI
  and on the Insights overview while AI is closed by the missing consent
  alone.
- Publish the standing consent as `ai.consent` on /api/auth/me (status,
  since, recipients); the settings card renders active-since and the
  withdraw control from it.
- Existing receipts stay valid.
- Guard that no client grants outside a click handler, route tests for the
  confirmation, and an integration test that a fresh operator-key account
  gets no background AI text until it agrees.
@MBombeck
MBombeck merged commit 59f910d into main Oct 16, 2026
25 checks passed
@MBombeck
MBombeck deleted the fix/v1432-consent branch October 16, 2026 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant