test(BA-7809): let the user policy seed carry a concurrent-login cap

[jopemachine]

📚 Stacked PRs

Part of the resource policy scenario stack under BA-7809. Merge in order (bottom-up):

1. 👉 test(BA-7809): let the user policy seed carry a concurrent-login cap #14534 — test(BA-7809): user policy seed carries a concurrent-login cap ← you are here
2. test(BA-7809): add scenario tests for the project resource policy #14515 — test(BA-7809): project resource policy scenarios
3. test(BA-7809): add scenario tests for the keypair resource policy #14516 — test(BA-7809): keypair resource policy scenarios
4. test(BA-7809): add scenario tests for the user resource policy #14517 — test(BA-7809): user resource policy scenarios

Resolves BA-7809

Summary

• The one change to the shared scenario seeds the stack needs, on its own: SeedUserPolicy takes a max_concurrent_logins and says so in its detail.
• The cap is the only value of a user policy an update may clear, so the row that clears it (test(BA-7809): add scenario tests for the user resource policy #14517) needs a seeded policy holding one. The default stays None, so every row laid so far — and every existing report.md — reads the same.

Test plan

• test-scenario on CI for every component that lays a user policy passes with its report.md unchanged

🤖 Generated with Claude Code

https://claude.ai/code/session_019vFCmtPMD6GLPBJxJoFroD

[jopemachine]

Reopened as independent PRs against main, one issue each: #14547 (BA-7854 seed), #14548 (BA-7851 project), #14549 (BA-7852 keypair), #14550 (BA-7853 user).