[CodingDiego]

Two commits, kept apart by a rebase merge. Changes are under Unreleased in the changelog; the crate version stays 1.0.0-rc.2.

Commit 1: native FTP listing, fuzz targets, UI-thread timing, budgets, a one-hour soak

• FTP (Compatibility: FTP verified or dropped #36). An ftp:// folder is listed by rexplorer itself. The shell's FTP folder only enumerates on a single-threaded apartment, so the listing runs on one, and everything it made there is released there before the list reaches the window (ShellFolder::park and rebind). The embedded Explorer view the handoff recommended was tried first: the server log showed no connection at all. connect::redact keeps the password out of titles, the address box, recents, the session file and error texts.
• Fuzzing (Testing: Fuzzing #57). All seven targets link and run on MSVC; the workflow fails a target that never reports its runs, and fails when no target is listed.
• UI-thread timing (Performance: UI-thread budget tooling #49). Every dispatched message is timed; a debug build logs each one over 50 ms with its message, window class and operation.
• Budgets (Performance: Budgets in CI #48). scripts\budgets.ps1 gains reload churn and slowest-UI-message budgets; CI runs them on every PR.
• Soak (Reliability: Soak test #29). The release soak is one hour, with a floor on the rounds done.
• scripts\ftp-check.ps1 and scripts\ftp-server.py: twelve live checks against a local read-only FTP server.

Commit 2: display and accessibility fixes, review fixes, one crash

• Text size and scale (Accessibility: Text scaling #24, Compatibility: Display scaling and multi-monitor #33). Folder options, Connect and the archive password prompt stay inside the work area and scroll when their content is larger (fit.rs). The palette shows the rows the screen has room for. Small list icons follow the window's scale after it changes. Tooltips follow the text size.
• Screen readers and keyboard (Accessibility: UI Automation for every custom control #21, Accessibility: Full keyboard reach #22, Accessibility: High contrast #23). Folder options' check boxes and radio buttons are real buttons with a role and a state; its combo and edits have names. Toolbar menu buttons report collapsed. The palette's box has a name and recents read by name. A focused, unselected row shows an outline in every theme. About names the contrast theme. The README's keys table covers the tree, the palette and the dialogs.
• Strings (Localization: Externalized strings #37). Two archive errors were English in every language; they come from the string table now.
• Crash, with a vendored dependency. A multi-volume .rar could crash rexplorer now and then while it was listed or extracted. At each change of volume unrar-ng 0.7.7 copies 2048 characters from the pointer libunrar passes, which is a std::wstring only as long as the next volume's name; when the read leaves mapped memory the process dies in memcpy (stack from a traced test run: archive::list > RARProcessFileW > MergeArchive > DllVolNotify > Internal::callback > U16CString::from_ptr_truncate). 0.7.7 is the newest release, so the crate is built from vendor/unrar-ng through [patch.crates-io]: the published src/ with that one read changed to stop at the NUL (diff -r against the registry copy shows only that hunk; VENDORED.md has the details). The whole core test binary died with an access violation in 3 of 47 runs before and in 0 of 60 after. The fuzz workspace has the same patch.
• Two reviews by a second reviewer (reports kept out of the repo): the test FTP server refuses every path outside its root and exits by itself; redact ends the authority where the shell does (/, ?, #), handles IPv6 hosts, backslash passwords and several addresses in one text; an error from the FTP worker carries only its code across threads; a message that began a loop of its own is timed up to that loop.

How it was tested

On the final tree, on a quiet machine (Windows 11, toolchain 1.99.1):

• cargo build --release --locked --all-targets with -D warnings; cargo test --release --locked three times (app 278, core 257, data_ops 11, all green); cargo clippy --workspace --all-targets --locked -- -D warnings clean.
• scripts\smoke.ps1 -Hosted: 32 PASS, 8 SKIP, 0 FAIL, with the new fit check (Folder options did not fit at 225 % and its OK button was reached by scrolling; Connect and the palette fit).
• scripts\ftp-check.ps1: 12 of 12, six runs in a row.
• scripts\budgets.ps1 with the CI values: start 334 ms, 100,000-file list 305 ms, idle CPU 0.0 %, churn 0.1 reloads/s, slowest UI-thread message 59 ms.
• The whole core test binary 60 times after the RAR fix: no access violation in memcpy (3 in 47 runs before).
• Display and accessibility, earlier the same day on this branch: a probe at a forced Text size of 225 % (Folder options, Connect and the palette inside the work area, OK reachable by scrolling) and an MSAA probe (check boxes and radio buttons with role and state, the combo named, menu buttons collapsed, the palette box named, a ::{GUID} recent shown by its name).
• Two reviews of the diff by a second reviewer, security included, and a re-check of each fix.

Not done

• No real Windows setting was changed for this PR: Text size 225 % was forced through REXPLORER_TEXT_SCALE, and the scale change by a unit test of the icon scaling. A re-test under the real settings, with Narrator, and under a contrast theme (the new check boxes there) is still to run.
• On a screen where both dialogs fit at 225 %, the smoke fit check does not exercise scrolling; its line says which case ran.
• Left from the reviews as notes: the palette resolves each recent place on the UI thread when it opens; Folder options paints a content-sized bitmap on every erase; a raw FTP password that is all digits up to a /, or one in ftp:user:pw@host without slashes, is shown.
• FTP is read and copy-out only as tested; uploads, renames and deletes on a server were not tested.
• One of those 60 runs died somewhere else: an access violation inside Windows' DUI70.dll while the menu, tree and undo tests (the ones that show shell UI) ran. It is the only such event in this machine's log for 30 days and is not traced yet.
• Smoke look and sidebar-shell fail now and then on a loaded machine (a sidebar row not there within 5 s). The master build fails the same way under the same load, and both pass 24 of 24 on a quiet machine.

Issues

Related to #36, #49, #48, #84, #37, #22, #23 (each gets its verdict and is closed by hand after the merge), #57 and #29 (they wait for a green hosted "Fuzz and soak" run), #21, #24, #33 (a live re-test is left).