[JacobStephens2]

Summary

Bumps thirdshift to 0.2.0 and fixes a flaky test that has turned main's CI red twice (cd34e42, 89d0500).

 Cargo.toml
-version = "0.1.0"
+version = "0.2.0"

 waits_for_github_to_work_out_whether_the_pr_is_mergeable
   agent opens PR; mergeable reads UNKNOWN 3 times
+  agent posts green checks          # CI wait returns at once
-  run with 300ms grace period       # 4 fake gh spawns can outlast it on Ubuntu CI
+  run with 5000ms grace period
   expect exit 0

0.2.0 ships the changes merged since v0.1.0: #56 (push past target-repo hooks, keep unpushed work), #57 (merge the Base branch again when it moves during CI), #59 (resume a session once when its background work is killed).

Evidence

• Before: CI on main, Ubuntu test job: waits_for_github_to_work_out_whether_the_pr_is_mergeable ... FAILED with GitHub has not worked out whether PR .../pull/1 is mergeable (run 36214048018)
  After: the test passes in 1.45s; full cargo test --locked ran 5 times locally with no failures; cargo fmt --check and cargo clippy -D warnings are clean

Merge Danger

Door: two-way

The merge itself only changes a version number and one test. Pushing the v0.2.0 tag afterward is one-way: it publishes to crates.io, and a crates.io version can't be re-published.

Blast Radius: tests

🤖 Generated with Claude Code