Launch checklist: UplinkWitness v1.2.0 public rollout

[LucaXTech]

Goal

Prepare UplinkWitness v1.2.0 for its first deliberate public launch under the new name without inflating compatibility claims or creating avoidable repository noise.

Must do before promotion

• Replace the existing v1.1-era dashboard screenshots with screenshots that visibly show the UplinkWitness brand
• Keep screenshots anonymized: no public/WAN IPs, PPPoE identifiers, credentials, private hostnames or other installation-specific data
• Verify README badges, release links and clone instructions all resolve under LucaXTech/UplinkWitness
• Verify the latest release is UplinkWitness v1.2.0 and remains non-draft / non-prerelease
• Verify production continues appending samples and both linewatch.service / linewatch-dashboard.service remain healthy after the rebrand

Screenshot assets now live at:

• docs/screenshots/dashboard-desktop.png
• docs/screenshots/dashboard-mobile.png

Repository cleanup

• Delete obsolete/merged topic branches after confirming main contains their work
• Disable the unused GitHub Wiki; documentation lives in the repository
• Keep issues Compatibility reports: broaden generic Linux validation #3, Define a stable router-adapter contract #4 and Evaluate OpenWrt as the next enhanced router adapter #5 as the focused public roadmap rather than opening speculative feature issues

Verified final repository state:

• only main remains as a branch
• GitHub Wiki disabled
• delete_branch_on_merge = true
• issues Compatibility reports: broaden generic Linux validation #3, Define a stable router-adapter contract #4 and Evaluate OpenWrt as the next enhanced router adapter #5 remain open as the public near-term roadmap

Public launch routing

r/selfhosted

UplinkWitness is younger than three months, so it should not be submitted as a standalone project post yet. Use the current New Project Megathread instead.

Suggested disclosure: AI was used extensively as a development assistant for implementation, refactoring, tests and documentation; architecture, hardware validation, release decisions and production testing were directed and verified by the maintainer.

r/homelab

Do not post yet. Revisit once the repository has enough public history for the community's current software-project rules.

Show HN

Technically eligible, but better as a second launch after the first outside installs/compatibility reports. Focus on the technical idea and motivation rather than the release number.

Launch sequence

1. First external exposure: current r/selfhosted New Project Megathread.
2. Ask for real compatibility reports, not stars.
3. Use the concrete differentiator: UplinkWitness records local evidence to classify link vs gateway vs Internet vs DNS/HTTP vs optional router/WAN failures.
4. Lead with the physical Raspberry Pi / Debian / cable-unplug validation and generic Linux mode; FRITZ!Box is an optional enhanced adapter, not the product identity.
5. Consider a Show HN after the first outside installs/feedback, using different copy and a technical angle.
6. Revisit r/homelab later rather than forcing an early software-project post.
7. Do not claim OpenWrt, MikroTik or UniFi support until Define a stable router-adapter contract #4/Evaluate OpenWrt as the next enhanced router adapter #5 produce a validated implementation.

Success signal

The useful early signal is not raw stars. It is a few external installs / compatibility reports that exercise hardware and routers different from the maintainer's current setup.

Current public release: v1.2.0.