You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add guidancePointer and noteProgress to manage_notes upsert response (#61)
* feat: add guidancePointer and noteProgress to manage_notes upsert response
After a successful upsert, the response now includes an `itemContext` map
keyed by itemId, containing `guidancePointer` (guidance for the next
unfilled required note) and `noteProgress` (filled/remaining/total counts
for the current phase). This eliminates the need to call get_context after
each manage_notes upsert to check remaining work.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test: add edge case tests for manage_notes itemContext
Cover three gaps identified during review:
- Terminal items return null guidancePointer/noteProgress even with schema
- Mixed batch (success + failure) only includes successful items in itemContext
- Pre-filled notes are counted correctly in noteProgress
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
The `itemContext` map is keyed by each `itemId` that had at least one successful upsert. For each item:
419
+
-`guidancePointer` — the `guidance` text from the first unfilled required note in the item's current phase, or `null` if all required notes are filled (or no schema matches).
420
+
-`noteProgress` — `{ filled, remaining, total }` counts of required notes for the current phase, or `null` if the item has no matching schema or is in terminal state.
421
+
422
+
This eliminates the need to call `get_context` after each `manage_notes` upsert to check remaining work.
0 commit comments