[rennf93]

Cargo.lock still pinned guard-core-engine and guard-core-rs at 4.3.2 while the sibling guard-core-rs master (the path dependency CI checks out) and crates.io are at 4.3.3, so every cargo run rewrote the lock. That drift is what made cargo publish refuse to package in tower-guard-rs #58. The first commit updates only those two lock entries; the Cargo.toml floors stay at 4.3.2, which 4.3.3 satisfies.

CI on the first commit failed the 100% line gate on the two lines inside the cloud-refresh test's wait loop: while scheduler.refresh_in_flight() && ... { sleep } never runs its body when the background refresh finishes before the first check, so line coverage depended on timing (master passed the same gate). The second commit replaces it with (0..500).any(|_| { sleep; !in_flight }), whose closure always runs, with the same 5 second ceiling. A loop/if/break form was not enough: llvm-cov then reports the if's closing brace as uncovered when the first check succeeds.

The Docs Update workflow has failed on every master push since at least 2026-10-09 at its Lint markdown step: README.md:61 was a second consecutive blank line (MD012). The third commit removes it.

Local gates: make lint, make test, cargo llvm-cov plus .github/scripts/enforce_line_coverage.py (100% of executable lines), the docs.yml markdown lint and mkdocs build --strict all pass.