RFC: surface time-bound commitments as a new classifier prefix

Filing this from daily-user experience — the gap that keeps jumping out at me is around **time-bound commitments**. A Slack confirmation of a 1:1, a Linear ticket I said I'd handle by Friday, an interview slot I just agreed to — they currently land as one line of prose inside `event-YYYY-MM-DD.md` and stop being queryable as structured data. The schema already gestures at this — `prompts/schema.md:20` says "Scheduled events / appointments / interviews belong in the non-event file for whichever entity anchors them (person-/org-/project-) when they represent a durable fact" — and `mcp/server.py:396` advertises `search(query="deadline Friday")` as a sample query. But `prompts/classifier.md` explicitly rejects this category in "What does NOT qualify": > A single-occurrence event, appointment, or deadline — that is already in `event-YYYY-MM-DD.md`, which is the event log. So today the data is captured but unreachable: the classifier won't promote it, person-bob.md won't reference it, and an agent over MCP can't answer "what did I commit to in the next 7 days?" because the answer exists only as buried sentences. ### Proposal A new classifier output prefix — `commitment-` (or `agenda-`; bikeshed) — written by the classifier alongside the existing six prefixes when a session contains a time-bound fact with explicit `when` + `what`. Minimum entry shape: ```yaml - id: c-2026-04-25-bob-q3 when: "2026-04-29T15:00+08:00" # ISO; null if relative-only ("next Tues") what: "1:1...