Improve bridge timeout diagnostics

[deverman]

Summary

• reworks this PR to diagnostics only
• removes the periodic mutation redispatch workaround and removes the tuning env var
• keeps existing read/write dispatch behavior unchanged
• improves bridge timeout messages with pickupState and whether the existing single stranded redispatch was attempted

Why

After the machine restart, the original #46 branch completed and restored the test project without the #49 workaround. That points to local machine / OmniFocus dispatch pressure rather than a proven deterministic code bug. This PR should therefore improve observability only, not change retry behavior.

Validation

• swift test
• safe live preview: swift run focusrelay set-projects-completion jdiFnpbNXj- --state active --preview-only --verify --return-fields id,name,status,completionDate

Scope Discipline

No periodic redispatch. No new env var. No query behavior change. No plugin JavaScript change.

Stack order: merge after #46, before #35 only if we still want better diagnostics before project moves. Related to #47.

[deverman]

Scope correction: this PR is now diagnostics-only.

It no longer adds periodic redispatch or any new tuning env var. It only improves timeout errors with pickupState and strandedRedispatched. Parent #46 succeeded after machine restart without the workaround, so this PR should not be treated as a root-cause fix.

[deverman]

Stack note: #50 (move_projects for issue #35) is now stacked on this branch. Merge this PR first, then #50.

[deverman]

Merge-order note: #46 is merged into master, and this PR has been retargeted directly to master. This should merge before #35 only if we want the improved timeout diagnostics in place before structural project moves.

Scope check after rework:

• diagnostics only
• final diff vs master is limited to Sources/OmniFocusAutomation/BridgeClient.swift and Tests/OmniFocusIntegrationTests/BridgeClientTests.swift
• no plugin JavaScript change
• no periodic redispatch
• no new timeout env var
• no mutation-specific timeout default
• no query behavior change

What changed:

• bridge timeout errors now include pickupState, derived from request/response/lock files
• bridge timeout errors now include strandedRedispatched, indicating whether the existing single stranded redispatch path was attempted
• added Swift Testing coverage for pickupState labels

Validation:

• swift test passed (89 tests; existing MCP Content.text deprecation warnings remain)
• safe live preview passed: swift run focusrelay set-projects-completion jdiFnpbNXj- --state active --preview-only --verify --return-fields id,name,status,completionDate