docs(readme): Signal Booster link — canonical casing + prominence

[travisccook]

The README already links to DroidNet Signal Booster; this corrects the URL to the repo's canonical casing (DroidNetSignalBooster-releases) and bolds the product name so the link + blurb read as a clear callout. Links to the releases repo: https://github.com/travisccook/DroidNetSignalBooster-releases

[github-actions]

Review: PR #7 — docs(readme): canonical-case the Signal Booster link

Scope: README.md only (2 lines changed). No board JSON, libraries/manifest.json, releases.json, or src/*.js touched.

1. Checks

Ran on the merge commit:

• npm ci — ✅ installs cleanly (272 packages, 1 moderate audit advisory, pre-existing/unrelated).
• npm run validate — ✅ all 9 board files + manifest + cross-file checks pass.
• npm test — ✅ 7 suites / 137 tests pass.

2. Board-contribution rules (examples coverage, placeholder↔param mapping, enum refs, unique command ids, libraryVersion bump, confidence honesty)

Not applicable — no board file, manifest.json, or releases.json changed in this diff, so there is nothing for the validator's semantic checks to flag and no version bump is required.

3. Safety-class mislabeling (movement/power marked cosmetic)

Not applicable — no command.safety fields are touched by this PR.

4. src/*.js correctness / DOM-free engine / round-trip invariant

Not applicable — no engine or UI source files changed.

Content of the actual change (README.md:11-12)

-product. [DroidNet Signal Booster](https://github.com/travisccook/droidnetsignalbooster-releases)
-is one consumer (it powers the Signal Booster's visual WCB command builder), but
+product. **[DroidNet Signal Booster](https://github.com/travisccook/DroidNetSignalBooster-releases)**
+is one consumer — it powers the Signal Booster's visual WCB command builder — but

Fixes the repo path casing (droidnetsignalbooster-releases → DroidNetSignalBooster-releases) and bolds the link for visibility. GitHub repo paths are case-insensitive for routing, so the old lowercase link wasn't broken, but matching canonical case is still the right fix for clarity/consistency. I don't have network access in this review environment to independently confirm the exact casing GitHub reports for that repo, so please double-check the new casing (DroidNetSignalBooster-releases) against the actual repo before merging.

Verdict

Low-risk, docs-only change. No blocking issues found. All CI-equivalent checks pass. Recommend merging once the casing above is eyeballed against the real repo name.