Implement verified monitoring Path A and deterministic Path B

Outcome

Booked trips can be checked reliably without claiming host push behavior that M0-F did not prove.

Scope

• Implement traveler/run-scoped polling cursors and redacted deltas.
• Implement Path B when the user requests a status check in their own words; examples are illustrative, not an exact phrase contract.
• Enable schedule recording and Path A only for the exact M0-F-verified host behavior.
• Handle revocation and inactive-run polls truthfully.

Acceptance

• Path B always works in the active conversation for natural status-check wording.
• Path A requires explicit user consent and confirmed host schedule ID/cadence.
• Returning a recommended interval never claims to configure the host scheduler.
• Revoked access causes later scheduled/requested polls to fail authorization.
• Console and skill labels match the active path.

Dependencies

• #5, #16, #19, and #25.

Review

Demo-integrity review against observed host evidence.

Start by reading dependencies #5, #16, #19, and #25, then trace the existing monitoring, console, and skill paths. Verify the observed M0-F host behavior before implementing Path A, and use the acceptance checklist to confirm consent, authorization after revocation, truthful scheduler claims, and matching labels for both paths.