All POST /api/send traffic now rides the new "test" channel at index 3 instead of "testowy" (index 2). The device-side channel was added earlier this session (empty key, SECONDARY role).
Test assertions for the send path updated in place (24/24, no coverage change); rx examples on other channels intentionally untouched — inbound packets can arrive on any channel
Verification
npm run build ✓
npm test — 24/24 passed
v0.5.0, CHANGELOG entry added
## What
All `POST /api/send` traffic now rides the new **"test"** channel at **index 3** instead of "testowy" (index 2). The device-side channel was added earlier this session (empty key, SECONDARY role).
- `MESH_SEND_CHANNEL` default: `2` → `3` (env override unchanged)
- docker-compose.yml sets no env var, so the deployed container picks up the new default on rebuild — no compose change needed
## Details
- Service pinning comment + controller Swagger (@ApiOperation description, /api/channels example, /api/messages tx example) updated to index 3 / "test"
- README + AGENTS.md endpoint docs updated (default `3`, channel name `test`)
- Test assertions for the send path updated in place (24/24, no coverage change); rx examples on other channels intentionally untouched — inbound packets can arrive on any channel
## Verification
- `npm run build` ✓
- `npm test` — 24/24 passed
- v0.5.0, CHANGELOG entry added
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
All
POST /api/sendtraffic now rides the new "test" channel at index 3 instead of "testowy" (index 2). The device-side channel was added earlier this session (empty key, SECONDARY role).MESH_SEND_CHANNELdefault:2→3(env override unchanged)Details
3, channel nametest)Verification
npm run build✓npm test— 24/24 passed