CI: bridge-mqtt missing tsconfig.json blocks build-and-test on main

[pshkv]

Context

Pre-existing CI failures on main that are cargo-culting into unrelated PRs (flagged in #168 review).

Failing jobs

• build-and-test (22)
• generate-benchmark-report

Root cause

@sint/bridge-mqtt is missing tsconfig.json (per @ExpertVagabond's investigation on #168). The build fails at the workspace level, which blocks any PR that triggers the build-and-test matrix — even PRs that don't touch bridge-mqtt.

Fix

1. Add packages/bridge-mqtt/tsconfig.json (extending the workspace base config, matching siblings like bridge-http)
2. Verify @sint/bridge-mqtt builds cleanly via pnpm --filter @sint/bridge-mqtt run build
3. Re-run CI on main to confirm green

Priority

Medium — not blocking any correctness concerns, but blocks PR author confidence and makes new-PR CI noise. Every reviewer currently has to mentally subtract these from the red checks to decide whether a PR is actually clean.

[pshkv]

Status update: in the local checkout I'm working from, packages/bridge-mqtt/tsconfig.json is present and the package builds successfully in isolation.

What I do not have yet is the repo-level evidence I'd want before declaring this fully done on main: a fresh clean build / CI pass that proves the workspace and the historical GitHub failure mode are both gone.

I'm treating that as part of the production-readiness sequence now: deterministic token / persistence fixes first, then a clean main CI signal, then only after that widening the roadmap again.

[pshkv]

Update (2026-05-12): this issue remains tracked separately from PR #183 and is not modified by the canonicalization/persistence patch.\n\nCurrent status:\n- PR #183 is focused on token signing determinism + persistence round-trip correctness\n- tsconfig/build failure path still needs an independent -based CI confirmation and/or targeted fix PR\n\nKeeping this open as an explicit follow-up item in the production readiness queue.

[pshkv]

Correction/clarification: this issue is still open and separate from PR #183. PR #183 does not touch the bridge-mqtt tsconfig/build path on main; that remains a follow-up production-readiness item.

[pshkv]

Final verification update (2026-05-13): on a fresh origin/main branch, packages/bridge-mqtt/tsconfig.json is present and @pshkv/bridge-mqtt passes both local build and tests.\n\nEvidence run:\n- pnpm --filter @pshkv/bridge-mqtt run build ✅\n- pnpm --filter @pshkv/bridge-mqtt run test ✅\n\nGiven current main state, the original missing-tsconfig failure mode described in this issue is no longer reproducible. Closing as resolved.

[pshkv]

Closing per verified main-branch state and passing bridge-mqtt package build/test checks as of 2026-05-13.