ente-cli 0.4.87 → 0.4.89

package/README.md

@@ -339,6 +339,21 @@ at most 20 address candidates with continuation. For example:
 ente agent user-mailbox --request '{"operation":"recipients","connectionId":"<permitted-private-connection>","query":"Alex Morgan"}'
 ```
 
+For interactive name resolution, add `"resolve":true` (without `cursor`). The
+server discovers names and updates all candidate addresses in one recency pass.
+It uses a shared ceiling of 20 cached pages of at most 200 records (4000 reads
+across both passes, with a separate byte bound per page), or 4 provider pages
+of at most 20 matching headers (80 fetched headers; native searches, metadata
+requests and retries are additional network operations). It returns terminal
+`resolutionComplete`, `discoveryComplete`, `recencyComplete` and budget metadata.
+If incomplete or truncated, ask for an explicit address or selection. Do not
+claim uniqueness or latest contact, automatically restart resolution, or expand
+to provider research. Preserve all requested recipients. Provider source is for
+explicitly requested or necessary provider/older correspondence searches.
+Use sufficient visible compose/reply context and selected recipients directly;
+an explicit email address requires no discovery unless validation was requested.
+
+Without `resolve`, keep the historical cursor workflow:
 Follow every cursor. For name matches, repeat lookup with each candidate exact
 email and follow those cursors too: newer headers may omit the name. Combine
 exact-address results using maximum `lastContactAt` before preferring the most

package/dist/SKILL.md

@@ -510,6 +510,21 @@ at most 20 address candidates with continuation. For example:
 ente agent user-mailbox --request '{"operation":"recipients","connectionId":"<permitted-private-connection>","query":"Alex Morgan"}'
 ```
 
+For interactive name resolution, add `"resolve":true` (without `cursor`). The
+server discovers names and updates all candidate addresses in one recency pass.
+It uses a shared ceiling of 20 cached pages of at most 200 records (4000 reads
+across both passes, with a separate byte bound per page), or 4 provider pages
+of at most 20 matching headers (80 fetched headers; native searches, metadata
+requests and retries are additional network operations). It returns terminal
+`resolutionComplete`, `discoveryComplete`, `recencyComplete` and budget metadata.
+If incomplete or truncated, ask for an explicit address or selection. Do not
+claim uniqueness or latest contact, automatically restart resolution, or expand
+to provider research. Preserve all requested recipients. Provider source is for
+explicitly requested or necessary provider/older correspondence searches.
+Use sufficient visible compose/reply context and selected recipients directly;
+an explicit email address requires no discovery unless validation was requested.
+
+Without `resolve`, keep the historical cursor workflow:
 Follow every cursor. For name matches, repeat lookup with each candidate exact
 email and follow those cursors too: newer headers may omit the name. Combine
 exact-address results using maximum `lastContactAt` before preferring the most