MacFleet Dash v0.8.0 — fleet groups and Windows bridge

MacFleet Dash v0.8.0 — fleet groups and private Windows bridge

Prepared by Codex · October 14, 2026.

Changes

• All computers, Mac/Linux, Windows, Servers and Range computers are views of one fleet.
• Location filters intersect each view. Pending inventory is separate from monitored and resource totals.
• Optional encrypted private WinRM reads execute the reviewed collector in memory; no Windows install, firewall opening, VPN enrollment, credential change or service restart is included.
• Windows details show every fixed drive, separate network adapters, original source clock, authenticated receipt and latest attempt.
• Source-clock warnings, retained readings, client route failures, partial data and not-enrolled entries remain explicit. Missing readings never become zero or healthy.
• Duplicate native Windows identities are rejected. Changed targets lose prior metrics/history, and reboots invalidate cross-boot network rates.
• Availability warnings honor only explicitly configured hours; no business schedule is guessed.

Verification

• 58 Python unit tests; 19 JavaScript model/release tests; 33/33 original collector self-checks.
• Desktop/mobile browser interaction checks, Windows retained-reading details, range location filters, history and token-filter regressions.
• Staged-source secret scan passed. Private configuration, credentials, telemetry, machine inventory and verification screenshots are not release assets.
• Exact-commit GitHub CI passed: https://github.com/sgtworkman/macfleet-dash/actions/runs/38630359417
• Source archive SHA-256: 27c8cbbda8d828fdc07d7b782e1e62cca6a63ffd5aa307ea16ea9436217beff1

Deployment and coverage

• Viewer v0.8.0; optional bridge v0.1.0. Original collector, probe and endpoint remain unchanged at v0.6.0.
• Refresh the existing private viewer; the original collector needs no restart. Keep its existing private listener binding.
• This is a source/UI release, not proof that unattended Windows monitoring or any range enrollment is complete. A successful manual poll, installed scheduler, or zero-exit snapshot publication does not prove scheduled host reads.
• Existing access, a supported client scheduler, successful natural later polls and startup readback must be verified separately for each actual deployment.
• For rollback, restore the retained previous viewer source or revert this release commit through normal Git history. Do not reset private runtime data or change Windows security settings.