[boburning]

Program mapping

• v3 work item: NET-10 — inherited VNC retirement
• Base/dependency: current upstream main at a091d17bcc7830ebe5fffc6895c53e01f644a2da; no stacked implementation dependency
• Closes NET-10: retire unauthenticated inherited VNC #638

Summary

• remove the provenance-unresolved stable vncserver and libvncserver.so.1 payloads
• remove the Tweaks VNC launcher and its unauthenticated TCP/5900 controls
• classify inherited TCP/5900 and vncserver processes as prohibited in the listener audit
• disable the legacy vncServer flag and stop only the exact inherited process during networking reconciliation
• replace current VNC instructions with an explicit retirement notice and the supported key-only SSH/SFTP administration route
• keep CI risk-scoped while forcing the exhaustive shell and full ARM packaging gates for changes to the retired payload paths
• regenerate the legacy manifest and dependency identity records after removing the payload

Validation

• legacy manifest validation: 326 components / 1,967 files / 260,659,274 bytes
• provenance validation: 7 checks passed
• transfer-policy validation: 6 roots passed
• RetroArch build identity: 3/3 passed
• branding validation: 6 classified literals passed
• POSIX syntax: bloom-listener-audit and update_networking.sh passed
• focused networking, manifest, provenance, payload, CI-scope, and compatibility tests: 47/47 passed
• follow-up isolation after the exhaustive run exposed stale cross-service assertions: 31/31 passed
• exhaustive shell suite: 818/818 passed across 8 shards with zero not ok results
• native unit suite: 595/595 passed in 18.77 seconds
• ASan unit suite: 595/595 passed in 31.71 seconds
• Tweaks cppcheck: passed in 1.20 seconds (pre-existing informational notes only)
• pinned SSD202D ARM Tweaks build: stripped ARM EABI5 binary, SHA-256 8885a1b5b656801126dfc142f01f9f4f413af585f3ad9ef50d13d9fb954a20cf
• final git diff --check: passed

The first exhaustive shell run correctly found two stale cleanup-loop assertions in bloom_shell_runtime.bats and samba_source_build.bats. Those assertions were corrected on this branch, the affected isolation set passed 31/31, and the complete final exhaustive run passed 818/818.

Device evidence and safety boundary

• No Mini Plus state was changed for this host-safe retirement slice: no deployment, Wi-Fi/profile/listener mutation, input injection, reboot, power action, overlay change, or update transaction.
• The currently installed signed baseline and recovery overlay were deliberately preserved.
• Host validation and the pinned ARM build prove payload composition, code paths, and executable architecture; they do not constitute physical Mini Plus, Mini V1-V4, or Mini Flip certification.
• A coherent signed Full Mini Plus checkpoint remains required before NET-10 is considered physically integrated.

Limitations

• This intentionally provides no replacement remote-display service. BloomOS retains key-only SSH/SFTP for supported remote administration.
• Historical versioned documentation and community references are not rewritten by this change.
• Physical LCD, controls, Wi-Fi recovery, update rollback, shutdown, gameplay, save semantics, and other-device behavior were not exercised in this slice.