a5ce43f211
fix(19.7): RB-WR-02 a padded token scope name fails boot
...
validatePluginTokenScope checked the trimmed name with
pact.ValidTokenScopeName while compileTokenScopes registered the
untrimmed one, so " blog:read" booted, was listed under its padded name
and could never be granted, and the duplicate check depended on
registration order. The name is now validated exactly as registered,
which is the shared rule pact.ValidTokenScopeName states.
2026-10-23 20:29:30 +02:00
ccf77b9103
test(19.7-09): named tests for every framework and admin SPA fix of plans 06 and 07
...
- pier: TestSessionReserve (A-WR-03), TestLockScope (A-WR-07),
TestScopeWidening (A-WR-04), TestStatelessFanOut (A-WR-05, A-WR-06),
TestPersonalTokenBinding (A-WR-09), TestDispatchHardening (A-WR-01,
A-WR-02, A-WR-08, A-IN-04, A-IN-05, A-IN-08), TestCatalogPathFields
(A-WR-02, A-IN-07), TestPromptWriteCeiling (C-IN-01),
TestTokenScopedRevoke (B-WR-04, C-IN-02), TestResolveClientAddress
(B-IN-04); test seam WrapStore
- pact TestFrontendTokenScopes, towel TestClientIP, cabana
TestTokenScopeNameParity
- cabana TestAccountContributionURL (B-WR-03), TestAccountContributionsIsolation
(B-WR-06, B-IN-03), TestRecordActionPromptLocalized (B-IN-02), and the
Postgres TestAccountTokenRevokeEvent (B-WR-04) and
TestResolveBackendTokenRemote (B-IN-04)
- vitest: hotkeysEditing.test.ts (B-WR-01, B-WR-02) and the extended
AccountContributions.test.ts (B-WR-03, B-WR-06, B-IN-01)
- check-phase19.7.sh requires every name (GO_TESTS, GO_TAGGED_TESTS,
DOCKER_TESTS, ADMIN_FILES) and scans the new files (PHASE_TEST_FILES)
2026-10-23 18:36:16 +02:00
