Treating the token lifecycle as a table of 'what should happen' is a good way to force the team to make the logout and password-change windows an explicit decision. For the authorization matrix, it may be worth adding a column for the same action reached through a different route, such as a bulk endpoint, an export, or a GraphQL/search query, because object-level checks are often applied on the detail route and missed on the list or aggregate ones. Generating the matrix from the route table, and failing the suite when a new route has no row, would also keep it from going stale. Do you suggest the testers own that matrix or the developers?