Yuneng Jiang f576d94c8c ci(proxy-mgmt-behavior): diag — run world-seed test first + bump max-failures ... Third CI run failed identically: seeded PROXY_ADMIN actor's auth resolves to ``user_id=None`` even though the DB row has the right ``user_id``. The suite was aborting at maxfail=10 inside test_key_delete, so test_world_seed (which would tell us whether the seed itself is reachable) never ran in CI. Two diagnostic moves on this push, no behavior change: * Rename ``test_world_seed.py`` → ``test_aaa_world_seed.py`` so it's the first collected file. If it passes in CI we know the seed is fine and the bug lives downstream; if it fails the same way the bug is in the auth resolution path. * Bump ``max-failures`` to 200 for this workflow so we see the full failure surface instead of stopping at the first cascading setup error. Will tighten back down once the suite is green. Adds one new test ``test_proxy_admin_actor_can_create_keys_for_others`` that explicitly exercises the PROXY_ADMIN bypass via /key/generate with an explicit user_id — the same shape the matrix setup helper uses but without the matrix machinery muddying the diagnostic.		2026-05-19 22:23:54 -07:00
..
management	ci(proxy-mgmt-behavior): diag — run world-seed test first + bump max-failures	2026-05-19 22:23:54 -07:00
__init__.py	test(proxy_behavior): scaffold session-scoped async ASGI client + liveness smoke	2026-05-19 21:21:00 -07:00