Service accounts created through the identities API are assigned the developer role in the request's org, whose shipped policy permits read and write across the org -- the permit alone did not scope the canary. Install a matching org-canary-grant-forbid policy (access.CanaryGrantForbidPolicy) that negates exactly the permit's surface for the canary identity; a forbid wins within the level, so the role can no longer widen access. Engine tests pin the surface with the principal carrying the developer role, and the rehearsal now proves it live: the scoped token gets 403 on /api/access/policies and 200 on /api/chat/update, and the full canary loop runs on it. task check passes; task canary:rehearse green (REHEARSE_EXIT=0).