403 Forbidden on Write Attempt with Trello Read-Only Token

Goal: Verify whether Trello’s API returns a 403 Forbidden status for every write‑type request made with a token that possesses only read‑only scope, regardless of the user’s role on the target board.

Constraints: The token is created with the read‑only scope flag; the authenticating user may be an administrator of the board; Trello’s scope documentation states that tokens are limited to the granted permissions but also notes that admin rights can allow certain board‑level changes, creating ambiguity about enforcement.

Questions: Does Trello always respond with 403 Forbidden for write attempts when the token lacks write scope? Can an admin‑privileged user bypass the scope restriction and succeed with a read‑only token? Which specific write endpoints (e.g., updating a card, modifying board settings) are affected by this scope check?