Yuneng Jiang 15c7a59d76 ci(proxy-mgmt-behavior): seed scratch keys via proxy_admin actor, not master ... Second CI run failed: ``/key/generate`` with explicit ``user_id`` returned 403 "User can only create keys for themselves. Got user_id=X, Your ID=None" in every test that called ``_create_scratch_key`` with a per-actor user_id. The bare master key's auth path was producing ``user_id=None`` in the fresh CI Postgres, which doesn't trigger the PROXY_ADMIN bypass in ``_user_can_only_create_keys_for_themselves`` reliably. Locally the same master key path worked, masking the issue. Fix: every ``_create_scratch_key`` helper now takes a seeder cleartext and the test bodies pass ``world.keys[Actor.PROXY_ADMIN].cleartext``. That actor was seeded with ``user_role=PROXY_ADMIN`` AND a concrete ``user_id``, so the bypass fires deterministically in both environments. No behavior shift in the matrices themselves — all 128 scenarios still pass locally; only the setup helper's auth identity changed. The bare-master smoke (test_smoke + test_scratch_teardown) is intentionally left on the master key path: those tests don't pass ``user_id`` in the body so they don't hit the user_id-mismatch gate.		2026-05-19 22:15:17 -07:00
..
management	ci(proxy-mgmt-behavior): seed scratch keys via proxy_admin actor, not master	2026-05-19 22:15:17 -07:00
__init__.py	test(proxy_behavior): scaffold session-scoped async ASGI client + liveness smoke	2026-05-19 21:21:00 -07:00