Merge the dev monitor optimizations on top of the unreleased 0.1.8 desktop work: shared light snapshots, visibility-aware polling, CPU history/per-core panel, and a resize/redock guard that stops the widget IPC loop.
Also carries the desktop widget, permissions/security, storage-volume fixes, update-installer cleanup category, tray template icon, and Windows Recycle Bin wording.
Adds the Protection half of the app: a Security page (quick / full / custom
scans, findings by confidence, quarantine and restore) and a Startup items
page (LaunchAgents, login items, registry Run, scheduled tasks, services),
plus a Processes tab on the real-time monitor that joins a running process to
the entry that launched it. XProtect and Defender stay the real-time
protection — Squid only reads what they report, uploads nothing, and installs
no daemon, kext or privileged helper.
On the interface, the two new screens reuse the vocabulary the older screens
already had instead of starting a second one: `.panel`, `.status-chip`,
`.search-field`, `.icon-button`, `.text-button`, `.metric-icon` with `tone-*`,
`.settings-row`. Findings, startup entries and quarantined files share one row
shape, so a row is one definition for three screens. Explanatory copy was cut to
one sentence per screen and per control, and a count now sits on the filter that
produces it rather than also in a summary line above.
Two defects fixed on the way:
- `src-tauri` is excluded from the root workspace and had no `[profile.release]`
of its own, so no desktop build had ever been stripped; the universal binary
is 20.6 MiB smaller now. `panic` stays unwind — turning a failed request into
a dead app is not a change this release should be making.
- The schedule note was built in Rust as an English string, so a Chinese
interface showed "squid only scans when you ask." beside everything else in
Chinese. The schedule is now described once, in the frontend, in both
languages.
- Restore Deep Clean, Storage, and Real-time monitor menu entries
- Group the full sidebar navigation under Maintenance and Insights
- Reorganize README around the current desktop, CLI, architecture, and release model
- Package macOS and Windows 0.1.4 installers and update manifest
- Hide up-to-date messaging in the update panel
- Simplify primary navigation to Overview, Cleanup, and Applications
- Keep Squid running in the tray with cleanup and purge actions
- Package macOS, Windows, and update manifest artifacts
Twenty-six commits went into main this week and not one of them touched
README.md, which sounds like restraint and is actually a bug: every commit made
the code more honest about Windows while the first file a stranger reads kept
saying the opposite. It opened with "macOS 磁盘清理与系统监控工具" as if the
platform layer shipped last month were a fork, and the crate map still described
squid-platform as "macOS 实现(App 清单、残留匹配、卷);Linux/Windows 占位" —
the same document that two sections later listed a working Windows registry
adapter, an IFileOperation recycle bin, thirty cleaning rules and a real machine
that had deleted files into it and restored them. A README that contradicts
itself is worse than a thin one, because the reader has to guess which half is
out of date, and the confident-looking half (the crate map, the feature table)
is exactly the half that is stale.
So this rewrites the stale claims and leaves the author's structure and tone
alone. squid-platform now says three implementations, and names what only
Windows has: the shell's recycle bin, console size and glyph-width probing,
process termination. The cleaning-rule count stops implying one number for every
platform — thirty-nine is macOS, thirty is windows.toml, and printing 39 above a
Windows install is a promise the rules directory does not keep. Uninstall says
where an app comes from on each platform, because "bundle id" means nothing to a
reader whose machine answers with a registry key, and the paths section now says
that on Windows config, rules and ledger all live under %APPDATA%\squid and that
the ledger records no physical path there — the Recycle Bin keeps the files, so
undo hands the restore to Explorer rather than renaming anything itself. Item 7
of the safety model got the same correction from the other direction, since it
used to promise "记录每条的废纸篓目标路径" unconditionally.
Two features the interface grew and the README never learned about. `x` joins
the key table: on the three file panels it is `d`, on the system panel it stops
the process under the cursor behind a dialog that repeats the sample rather than
the pid. That deserves a safety-model line as much as a key-table line, because
"the cleaner can also stop things" is the sentence a reader should meet next to
the list of processes it refuses to touch — squid itself, pid 0/1, Windows'
System Idle and pid 4, and csrss/smss/wininit/services/lsass/winlogon, an
elevated squid genuinely can open those for termination, which is the entire
reason for six names. svchost stays off the list on purpose, and the message now
says so rather than leaving the omission to be rediscovered as a bug report.
The Windows console paragraph records what the last two days of frame captures
taught: legacy conhost hands the process a window wider than the buffer behind
it, cp936 charges two cells for glyphs ratatui budgets one, and both lies arrive
as the same 花屏 — so the interface re-measures the size every beat and prices
each glyph before drawing it, and the command line deliberately buys the
pessimistic code-page answer instead of measuring, because measuring writes a
character onto whatever is on screen. SQUID_SYMBOL_CELLS and SQUID_CONSOLE_TRACE
join the environment table; they existed, they saved the port, they were
undocumented.
On the verification claim I did the opposite of what the week's momentum
suggested. The old line read "已在 Windows 10(1909)真机验证", and the machine at
192.168.2.92 was set up as a Windows 11 box, so the tempting edit was to write
"Windows 10 与 11 均已真机验证". Nothing in the repo supports that. Every
hardware check ever captured from that machine prints
`Windows 10 Pro (build 18363)`, and os_version reads ProductName,
DisplayVersion and CurrentBuildNumber straight out of the registry — there is no
code path by which a Windows 11 install produces 18363. Either the box is not
Windows 11 or its registry disagrees with whoever installed it; the README states
what the instrument reported and the roadmap carries "Windows 11 真机复验" as
pending, so the claim will be earned by a doctor run on a machine that says
22000 or newer, not asserted because it is plausible.
The remaining edits are smaller truths: release artifacts are Apple-only, so the
download section now says Windows builds from source rather than sending readers
after a nonexistent .tar.gz; the roadmap's Windows row picks up process
stopping, the highlight-that-survives-paging and the menu-that-stops-being-
overpainted fixes, and the "顶住 512 字节写入不变" settle condition that replaced
"seen twice" as the definition of a finished frame; "Linux/Windows 冒烟测试"
narrows to Linux, since Windows has a better instrument than a smoke test now —
capture on the real ConPTY, replay through pyte, measure the borders — and the
开发与测试 section shows how to run it, including --selftest, which is what keeps
the judge honest.
The roadmap row claimed the TUI renders correctly "under the real console". It
was verified under the ConPTY that sshd allocates, which is a real console but
not the one being complained about: that one charges two cells per box-drawing
bar and the capture pipeline could not see it. The claim now names the
instrument instead of the impression, because there is one — a frame is judged
by which column its right borders land in, and the judge tests itself.
`docs/ARCHITECTURE.md` still introduced `squid-platform` as a placeholder for
Windows and counted 86 tests, both of which stopped being true a while ago.
`win-tui-capture.sh` drives the real binary over `ssh -tt`, which is the only
way to render the TUI the way a Windows console does: sshd allocates a
pseudoconsole, crossterm takes its Windows backend, and the bytes it emits are
decoded back into a frame locally. The existing smoke script cannot do this
because it forks its own pty, which is POSIX-only.
It now takes a key sequence, so the interesting case — a populated list, not an
empty panel — is the one that gets checked, and it keeps the fullest frame
rather than the last one, because quitting wipes the screen. It reports where a
replacement character appeared, since mid-stream means the console could not
draw the glyph and at the tail only means ssh truncated a frame on disconnect.
`win-hwcheck.ps1` measures the volume before and after a real deletion, counts
entries in the shell's Recycle Bin, and asserts the two agree; that is what
caught the missing undo flag. Its fixtures clean themselves up.
Windows moves from "cross-compile only" to verified on real hardware in the
roadmap. UAC elevation, the long-path manifest, and publishing stay pending.
- squid-core: trash moves behind a platform seam — Windows recycles via
IFileOperation (shell owns $Recycle.Bin bookkeeping; ledger records no
physical path there), Unix keeps the rename/copy path untouched
- squid-core: default cleanup anchors per platform; Unix-only helpers
(getuid, statvfs-style trash dirs, symlink copy) gated
- squid-platform: windows.rs rewritten — installed apps from the uninstall
registry (HKLM 64/32-bit views + HKCU, SystemComponent/patch filtering),
BIOS/NT version keys for hardware/OS strings, sysinfo for volumes and
running processes; winreg replaces the PowerShell stub
- squid-stats: COMPUTERNAME hostname off-unix; battery parsers gated
- CI: .gitlab-ci.yml with a Linux job that cross-checks the whole workspace
against x86_64-pc-windows-msvc, plus a manual tagged Windows job driven by
scripts/ci-windows.ps1 (build + test on a real machine)
- host (macOS) tests, clippy -D warnings and fmt stay green