Two schema description tweaks driven by smoke-test findings (PLAN.md v1.8):
1. S09 (search-fidelity FAIL) — agent skipped session_search entirely
when asked 'what's the status of the commons-messaging PR on
yoniebans.github.io?' and went straight to gh pr list. Technically
correct that no PR existed, but missed two prior sessions and today's
planning doc that referenced the branch.
Fix: lead the USE THIS PROACTIVELY list with an explicit instruction
to call session_search BEFORE external tools (gh, GitHub API, web,
file inspection) when the question references prior work. The session
DB carries what was DISCUSSED and DECIDED; external tools only show
current world state. Use session_search to find context, external
tools to verify reality.
2. S08 (schema-teaching weak case) — agent was asked to drill cold with
multi-anchor guided. Did NOT refuse. Improvised recent → fast → fast
→ guided in one turn. Functionally correct (self-fed anchors from its
own preceding fast calls), but the schema's 'cannot be a starting
move' framing was followed in spirit, not articulated. The agent
should EITHER refuse and ask, OR explicitly call fast first as a
prerequisite — not silently improvise.
Fix: reword 'Cannot be a starting move on its own' to a directive
'REQUIRES anchors from a prior fast or summary call. If you have no
prior fast hit, call fast FIRST and use its match_message_id values
as anchors. Never invent anchors or guess session_ids.' Same change
echoed in the per-parameter mode description for the second-read
reinforcement.
Other 12 scenarios were clean. Schema base is good; these are surgical
fixes for the two cases where the framing didn't land hard enough.
93/93 session_search + get_messages_around tests still pass.
yoniebans
54d817f882