Marc-André Bombeck b2e225470b test: read the account payload as the release publishes it ...

Four cases in the accountAccess integration test were written against a
contract this release rejected. They asserted an entry of seven fields and a
block of three, both of which gained one; and they asserted that a MANAGE
grant publishes `access: "manage"`.

It does not, by design. `access` is the v1.36.0 name and its union is
`read | write` — a client compiled against that release decodes it as a
closed set. MANAGE therefore publishes as `write` there and as `manage` on
`level`, and the entry schema raises a validation issue unless a manage
entry carries exactly legacy write access and whole scope. The expectations
move; the schema does not.

`recordKind` is required on an entry and on the block. Both are asserted
now, including the block-level value moving from `self` to `shared` across
a switch, so a value stuck on either reads as two cases disagreeing.

2026-08-07 06:00:29 +02:00

..

fixtures/v137

test: cover sharing accessibility states

2026-08-06 23:46:43 +02:00

integration

test: read the account payload as the release publishes it

2026-08-07 06:00:29 +02:00