Marc-André Bombeck 26fceca219 fix: answer the managed-profile Guardian routes in one shape ...

- publish the roster's entry from the invitation and `{ grantId, revokedAt }`
  from the removal, instead of the account-grant row Prisma returned
- drop the invitation's self refusal: it named a code no request can elicit,
  because a Guardian grant's grantor is the profile and never the caller
- name the duplicate grant error rather than catching every grant refusal into
  a sentence that would be wrong for any other one
- keep the rate limit and the unknown-identifier 404 free of an error code,
  as their siblings elsewhere are, and say why at the call site

2026-08-07 04:39:50 +02:00

..

create.ts

feat: create managed profiles atomically

2026-08-06 02:28:56 +02:00

guardian-list.ts

fix: answer the managed-profile Guardian routes in one shape

2026-08-07 04:39:50 +02:00

lifecycle.ts

fix(02-11): protect guardian egress data lifecycle

2026-08-06 14:05:59 +02:00