release: engine 0.13.0 re-sync — crates.io deps, drop vendored reports & pycache

[Szowesgad]

Why

The 2026-07-03 engine sync (#59) predates the 0.13.0 crates.io publish (2026-07-05), so the mirror still claimed "0.13.0 crate line is not yet published", carried `publish = false`, a vendored `reports/` crate and a stray `pycache` fixture artifact.

What

Snapshot re-sync from suite release ref `a38afb8aba01` through the registry-mode sync machinery:

• `report-leptos = "0.13.0"` consumed from crates.io — vendored `reports/` removed (−32k lines)
• `publish = false` gone; `repository` casing fixed to `Loctree/loctree`
• `pycache` .pyc removed; minimal public `.gitignore` added
• fresh SYNC-MANIFEST.md (source commit `a38afb8aba01`, dependency mode: crates.io registry)

Verification (V-01 falsification report)

• mirror manifests byte-identical to published crates' `Cargo.toml.orig`
• src diff vs crates = comment/test-literal sanitization only; `cargo test -p loctree --lib` 1729/0
• `cargo check --workspace` green on clean registry; `semgrep p/secrets` 0 findings

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request removes the local reports workspace member (which contains the Leptos-based HTML report renderer and its WASM sub-crate) and transitions to consuming the report-leptos crate directly from the crates.io registry at version 0.13.0. Corresponding updates have been made to the workspace Cargo.toml, Cargo.lock, README.md, and SYNC-MANIFEST.md to reflect this dependency mode change. I have no feedback to provide as there are no review comments to assess.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.