[sketcherzee]

Closes #1380
Closes #1382
Closes #1383
Closes #1384

• BE-103: single-use WS ticket from an authenticated REST call, accepted via query param / Sec-WebSocket-Protocol; frontend socket hooks updated
• BE-112: request id -> queue key Redis hash so cancel removes staked requests; test added
• BE-113: active matches stored in Redis with TTL
• BE-114: GET/POST /v1/tournaments and POST /v1/tournaments/{id}/register backed by DB tables, 404/409 handling, tournament crate used for brackets

[drips-wave]

@sketcherzee Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[chinweobtagaz]

Merged, thanks @sketcherzee. To get it in, I resolved conflicts with main on your branch and fixed three compile errors in api/src/tournaments.rs:

• db_entity::tournament::Model needed Serialize/Deserialize derives to be returned as JSON.
• value was moved into Set(Some(value.into())) and then used again in Some(value). It now clones.
• "Test".into() was ambiguous because create_bracket takes impl Into<String>. Passing "Test" directly fixes it.

Requiring a WS ticket also broke __tests__/chessSocketSync.test.ts, which now needs an access token and a mocked ticket endpoint. That's fixed on main.

Next time: run cargo check --workspace --tests and npx vitest run before pushing, and update any tests that depend on behaviour you change (here, how sockets connect).