chore(deps): bump jwalk from 0.8.1 to 0.9.0 in /src-tauri

[dependabot]

Purpose

Evaluate Dependabot's jwalk 0.8.1 -> 0.9.0 update without integrating an explicitly unmaintained filesystem traversal dependency into protected main.

Exact current state

• Exact source head: 47484176ca58b2f0e09fad7ccd187eba7a2eba02.
• Protected main at the latest refresh: be418bac9bfbdc8aa41b1a698713833e3dbccfdc.
• PR remains open, Draft, and must not merge as a routine dependency update.
• jwalk is a direct production dependency: protected-main src-tauri/src/cloud.rs uses jwalk::WalkDir for bounded archive-file traversal, and active source owner feat: persist provider sync goals and runtime ADRs #213 also uses jwalk::WalkDir/Parallelism in its cloud/archive work.
• Upstream 0.9.0 explicitly declares the crate unmaintained and recommends moving away from it. Therefore a green compile of the version bump would not establish acceptable acquisition-grade supply-chain maintenance.

Correction made during maintenance

A prior repair attempt on this branch briefly treated jwalk as unused and removed the dependency. Fresh source evidence disproved that assumption before integration: the production archive collector still uses jwalk. The branch was immediately corrected by restoring jwalk = "0.9" and deleting the premature absence assertion. No compile-breaking dependency removal or false test remains in the current semantic branch state.

This correction is intentionally preserved in branch history as auditable evidence; no force-push or history rewrite is used.

Real repair owner

Issue #241 tracks the root-cause repair: replace the unmaintained traversal dependency with a maintained implementation while preserving DiskSage's bounded archive-walk semantics, including:

• no symlink/reparse-point traversal;
• excluded/cloud/regenerable-root pruning before descent;
• deterministic bounded candidate behavior;
• current archive/file classification and metadata behavior; and
• realistic regressions proving the replacement at the production collector boundary.

Because #213 currently owns overlapping src-tauri/src/cloud.rs production changes, do not race it with a competing traversal rewrite. Repair the earliest compatible source owner and then revalidate dependency/lockfile state on a fresh exact head.

Required before closure or merge

Do not merge this PR merely because 0.9.0 builds. Resolve #241 first by proving a maintained traversal replacement on the actual production path. After that replacement integrates, either deliberately rebuild this branch as the corresponding dependency-removal/lockfile cleanup if unique work remains, or close it as technically superseded with exact semantic evidence. Any changed successor must reacquire all applicable Test/Release/Security/SAST/central workflows, exact owned-production coverage, review-thread resolution, fresh live-base ancestry, and qualifying independent last-push approval. Pending, queued, stale, predecessor, status-only, model-only, or compile-only evidence is non-passing.

[seonghobae]

Superseded by the maintained walkdir migration already implemented in the provider-sync product branch: direct production jwalk usage is removed, traversal error handling is preserved, and this jwalk 0.9-only bump cannot compile because the old read_children_error API no longer exists. Closing this redundant dependency update; no data or runtime authority changes.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.