Yuneng Jiang 4c66635ee5 test(proxy_behavior): trim debug diagnostics, restore default max-failures ... Followup to the CI-bring-up sequence: now that the suite is green in CI (130 → 129 tests after this trim; 156s wall-time on ubuntu-latest), drop the diagnostic noise left over from debugging the master_key wipe: * Rename ``test_aaa_world_seed.py`` back to ``test_world_seed.py`` — no longer needs to run first. * Remove ``test_auth_resolver_returns_correct_user_id_and_role`` — that test reached into private auth helpers to localize the bug between the DB and ``UserAPIKeyAuth``; it has served its purpose and isn't HTTP-boundary. * Keep ``test_proxy_admin_actor_can_create_keys_for_others`` (without the failure-time dump) — it's a real authz contract that pins the PROXY_ADMIN bypass on /key/generate, and would catch a regression of the same conftest interaction this sequence revealed. * Drop the workflow's ``max-failures: 200`` override — that was a debug aid for seeing the full failure surface in CI. Default of 10 is right for a stable suite.		2026-05-20 13:38:42 -07:00
..
management	test(proxy_behavior): trim debug diagnostics, restore default max-failures	2026-05-20 13:38:42 -07:00
__init__.py	test(proxy_behavior): scaffold session-scoped async ASGI client + liveness smoke	2026-05-19 21:21:00 -07:00