@zortexhq/install 0.1.24 → 0.1.26

package/README.md

@@ -63,24 +63,26 @@ a bare `zortex` starts the same automatic agent onboarding.
    zortex autopilot connect-status <receipt-id>
    ```
 
-   For each question Codex selects the minimum relevant connected sources and
-   runs `zortex retrieve <source> --query <provider-query> --json`. Each read is
-   bounded to at most ten matching records; no queryless or account-wide scan
-   starts implicitly.
-5. Codex uses the read-only `indra.context` bridge over those retrieved records
-   and cites the returned Zortex references.
-
-There is no onboarding sample or background backfill. If one bounded query is
-too narrow for the user's request, Codex asks for a narrower scope instead of
-silently scanning the account.
+   For each question Codex selects the minimum relevant connected sources and a
+   question-sized batch, then runs
+   `zortex retrieve <source> --query <provider-query> --limit <n> --json`.
+   If evidence is insufficient it increases the limit. An explicit complete or
+   all-results request uses `--all` and exhausts only matching provider pages.
+5. Codex incrementally catches up the standing index, then uses the read-only
+   `indra.context` bridge over those retrieved records and cites the returned
+   Zortex references. A successful retrieval is immediately readable rather
+   than count-only.
+
+There is no onboarding sample or background backfill. Every answer reports the
+query scope, records retrieved, and whether all matches were exhausted.
 
 ### Supported Windows Autopilot sources
 
 | Source | Connection and question-time read | Notes |
 | --- | --- | --- |
-| `gmail` | OAuth connection; up to 10 matching messages per query | Uses the existing read-only Gmail connector and its declared exclusions. |
-| `google-drive` | OAuth connection; up to 10 matching files per query | Uses the existing read-only Drive connector and its declared exclusions. |
-| `outlook` | OAuth connection; up to 10 matching messages per query | Uses the existing read-only Outlook connector. |
+| `gmail` | OAuth connection; adaptive matching-message pages | Uses the existing read-only Gmail connector and its declared exclusions. |
+| `google-drive` | OAuth connection; adaptive matching-file pages | Uses the existing read-only Drive connector and its declared exclusions. |
+| `outlook` | OAuth connection; adaptive matching-message pages | Read-only Graph connector; refresh-token renewal prevents false post-connect expiry. |
 | `notion` | Connector fabrication | No released automatic authorization route yet; request files or joins a D29 build order. |
 | `posthog` | Connector fabrication | No released automatic authorization route yet; request files or joins a D29 build order. |
 | `whatsapp` | Deferred | Not part of this Windows Preview. |
@@ -107,8 +109,8 @@ records. Use the product's audited privacy-erasure path for data deletion.
   repair. Do not paste a credential or run a repair command yourself.
 - `codex` not found: install/start the local Codex CLI first, then rerun the
   explicit onboarding command.
-- Broad question: narrow its date, sender, file name, or subject so a bounded
-  provider query can answer it.
+- Broad question: use a precise provider query and increase its batch until the
+  evidence is sufficient; use `--all` only when the user explicitly asks.
 
 When Codex invokes the npm launcher with no command, it starts
 `zortex onboard --agent --host codex`. That scripted onboarding first proves