Telegram: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
backend/src/routes/stream.routes.ts exports a router that mounts only POST / → createStream with no auth and no rate limiting. It is not imported anywhere: the active stream router is backend/src/routes/v1/stream.routes.ts (mounted via routes/v1/streams/index.ts, which imports '../stream.routes.js' resolving to the v1 file). A grep for routes/stream.routes shows zero importers of the top-level file.
Leaving a second, unauthenticated createStream route definition lying around is a maintenance hazard — a future refactor could accidentally wire it up and expose stream creation without auth.
Acceptance criteria
Files to touch
backend/src/routes/stream.routes.ts (delete)
Out of scope
- The active
backend/src/routes/v1/stream.routes.ts.
Telegram: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
backend/src/routes/stream.routes.tsexports a router that mounts onlyPOST /→createStreamwith no auth and no rate limiting. It is not imported anywhere: the active stream router isbackend/src/routes/v1/stream.routes.ts(mounted viaroutes/v1/streams/index.ts, which imports'../stream.routes.js'resolving to the v1 file). A grep forroutes/stream.routesshows zero importers of the top-level file.Leaving a second, unauthenticated
createStreamroute definition lying around is a maintenance hazard — a future refactor could accidentally wire it up and expose stream creation without auth.Acceptance criteria
backend/src/routes/stream.routes.ts(top-level) has no importersnpm run buildand the test suite still passFiles to touch
backend/src/routes/stream.routes.ts(delete)Out of scope
backend/src/routes/v1/stream.routes.ts.