@zortexhq/install 0.1.24 → 0.1.25

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -63,24 +63,24 @@ a bare `zortex` starts the same automatic agent onboarding.
63
63
  zortex autopilot connect-status <receipt-id>
64
64
  ```
65
65
 
66
- For each question Codex selects the minimum relevant connected sources and
67
- runs `zortex retrieve <source> --query <provider-query> --json`. Each read is
68
- bounded to at most ten matching records; no queryless or account-wide scan
69
- starts implicitly.
66
+ For each question Codex selects the minimum relevant connected sources and a
67
+ question-sized batch, then runs
68
+ `zortex retrieve <source> --query <provider-query> --limit <n> --json`.
69
+ If evidence is insufficient it increases the limit. An explicit complete or
70
+ all-results request uses `--all` and exhausts only matching provider pages.
70
71
  5. Codex uses the read-only `indra.context` bridge over those retrieved records
71
72
  and cites the returned Zortex references.
72
73
 
73
- There is no onboarding sample or background backfill. If one bounded query is
74
- too narrow for the user's request, Codex asks for a narrower scope instead of
75
- silently scanning the account.
74
+ There is no onboarding sample or background backfill. Every answer reports the
75
+ query scope, records retrieved, and whether all matches were exhausted.
76
76
 
77
77
  ### Supported Windows Autopilot sources
78
78
 
79
79
  | Source | Connection and question-time read | Notes |
80
80
  | --- | --- | --- |
81
- | `gmail` | OAuth connection; up to 10 matching messages per query | Uses the existing read-only Gmail connector and its declared exclusions. |
82
- | `google-drive` | OAuth connection; up to 10 matching files per query | Uses the existing read-only Drive connector and its declared exclusions. |
83
- | `outlook` | OAuth connection; up to 10 matching messages per query | Uses the existing read-only Outlook connector. |
81
+ | `gmail` | OAuth connection; adaptive matching-message pages | Uses the existing read-only Gmail connector and its declared exclusions. |
82
+ | `google-drive` | OAuth connection; adaptive matching-file pages | Uses the existing read-only Drive connector and its declared exclusions. |
83
+ | `outlook` | OAuth connection; adaptive matching-message pages | Uses the existing read-only Outlook connector. |
84
84
  | `notion` | Connector fabrication | No released automatic authorization route yet; request files or joins a D29 build order. |
85
85
  | `posthog` | Connector fabrication | No released automatic authorization route yet; request files or joins a D29 build order. |
86
86
  | `whatsapp` | Deferred | Not part of this Windows Preview. |
@@ -107,8 +107,8 @@ records. Use the product's audited privacy-erasure path for data deletion.
107
107
  repair. Do not paste a credential or run a repair command yourself.
108
108
  - `codex` not found: install/start the local Codex CLI first, then rerun the
109
109
  explicit onboarding command.
110
- - Broad question: narrow its date, sender, file name, or subject so a bounded
111
- provider query can answer it.
110
+ - Broad question: use a precise provider query and increase its batch until the
111
+ evidence is sufficient; use `--all` only when the user explicitly asks.
112
112
 
113
113
  When Codex invokes the npm launcher with no command, it starts
114
114
  `zortex onboard --agent --host codex`. That scripted onboarding first proves