Add focused integration coverage for real git branch freshness checks, degraded MCP startup reporting, policy routing, prompt misdelivery recovery, and telemetry JSONL roundtrips.
Constraint: Keep coverage isolated to new integration test files so existing in-progress workspace edits stay untouched
Rejected: Expand existing unit tests instead | user requested integration coverage across runtime and telemetry boundaries
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep these scenarios in integration tests because they depend on cross-module behavior and serialized output contracts
Tested: cargo test --workspace
Not-tested: Remote push hooks or CI-only environment differences
Add typed lane lifecycle telemetry entries and mirror them into session trace and JSONL output using the dotted lane.open/lane.close wire names. This keeps lane lifecycle data queryable without routing it through generic analytics events.
Constraint: Keep telemetry crate changes backward-compatible for existing HTTP and analytics event consumers
Rejected: Reuse generic analytics events for lane lifecycle | loses dedicated typed telemetry variants
Rejected: Keep snake_case lane_open/lane_close wire names | does not match the requested lane.open/lane.close event names
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Preserve lane.open/lane.close wire names and the lane_id attribute key unless downstream consumers are migrated together
Tested: cargo build --workspace; cargo test --workspace
Not-tested: Runtime wiring that emits lane open/close events from higher-level crates