@invinite-org/invinite-data-cli 0.7.0 → 0.8.0

package/claude-plugin/commands/analyze-earnings-call.md

@@ -15,8 +15,8 @@ Analyze the earnings call requested in `$ARGUMENTS` using Invinite Data. Prefer
    - Q&A: `invd earnings qa` (`earnings_call_qa`) and participants: `invd earnings participants` (`earnings_call_participants`)
    - diff vs the prior call: `invd earnings diff` (`earnings_call_diff`)
    - optional, price moves during the call: `invd earnings price-attribution` (`earnings_call_price_moves`) — minute returns next to what was being said; skip it on a `404 price_attribution_unavailable`
-   - only when a claim needs the exact wording: `invd earnings transcript` (`earnings_call_transcript`) or `invd earnings search -q "<topic>" --mode hybrid --event-id <event_id>` (`earnings_call_search`; `--mode literal` for an exact figure or term)
-   - when the call has documents (`has_documents`): `invd earnings documents` (`earnings_call_documents`) — CFO commentary, shareholder letter, data sheets; for context beyond the call (annual report, investor-day deck) `invd earnings document-search -q "<topic>" --mode hybrid -i <TICKER>` (`earnings_document_search`); a `coverage.completeness` of `partial` / `unknown` means no hits is not proof the topic is absent
+   - only when a claim needs the exact wording: `invd earnings transcript` (`earnings_call_transcript`) or `invd earnings search -q "<keywords>" --event-id <event_id>` (`earnings_call_search`; keywords, not a question: any word may match and the answer follows a matched analyst question) or `invd earnings search -q "<exact quote>" --mode literal --event-id <event_id>` for an exact figure, term or quote
+   - when the call has documents (`has_documents`): `invd earnings documents` (`earnings_call_documents`) — CFO commentary, shareholder letter, data sheets; for context beyond the call (annual report, investor-day deck) `invd earnings document-search -q "<keywords>" -i <TICKER>` (`earnings_document_search`; every word must match); a `coverage.completeness` of `partial` / `unknown` means no hits is not proof the topic is absent
 3. **Summarise**:
    - **Results vs guidance** — reported figures from the press release against the guidance given on the prior call (`invd earnings guidance-history -i <TICKER> --metric <metric>` for a metric's series).
    - **Guidance changes** — each item raised, lowered, maintained, introduced or withdrawn (`direction`), with the period and basis (GAAP / non-GAAP).

package/claude-plugin/skills/invinite-data-cli/SKILL.md

@@ -128,7 +128,7 @@ Commands about one call take a selector: `--event-id <event_id>` (from `events`
 - `earnings event --include observations` adds the date / time observations; `earnings participants --include evidence` the participation evidence.
 - Every `*_ms` field is milliseconds from the call's start: cite it as `[m:ss]`. `qa_start_ms` is where the Q&A begins (null without one).
 - Company documents and document-search hits are company-published material: quote them as "passages from company-published documents", never as verified facts, and cite each with its document title, year and page (`page`; open `url` at `#page=<page>`). A `webcast` row is link-only (`url` null, `source_url` = the replay page, `link_status`).
-- `earnings search` and `earnings document-search` take `-m, --mode`: `hybrid` for natural-language questions, `lexical` (the default) for words and phrases, `literal` for exact strings such as `FY2027` or `10b5-1` (case-sensitive; `--case-sensitive false` ignores case), `semantic` for meaning only. Every mode costs the same. In `--json` output read `coverage.completeness` before concluding anything from few or no hits: `partial` / `unknown` means the index does not cover the whole scope yet, so absence is not proof. `match.spans` are code-point offsets of the matched characters in `text`.
+- `earnings search` and `earnings document-search` take `-m, --mode`: `lexical` (the default) matches words and quoted phrases (stemmed; `OR` and `-word` work), `literal` matches the exact characters such as `FY2027` or `10b5-1` (case-sensitive; `--case-sensitive false` for a case-insensitive match). Search with keywords, not a whole question: scoped to one call (`--event-id`) or one company (`-i`), `earnings search` needs any of the words and returns the management answer right after a matching analyst question (its `match.spans` may be empty); without a scope, and in `document-search`, every word must match. Both modes cost the same. In `--json` output read `coverage.completeness` before concluding anything from few or no hits: `partial` / `unknown` means the index does not cover the whole scope yet, so absence is not proof. `match.spans` are code-point offsets of the matched characters in `text`.
 - Media signed URLs expire after 15 minutes; `--output` on the download commands saves the file.
 - The live transcript (`ws listen --earnings`), audio, slides, the live stream and webhooks need the PRO plan (calendar, events and `live` need LITE, the other reads STANDARD); a `403` names the plan a route needs.
 
@@ -238,7 +238,7 @@ invd earnings prosody --event-id cfbcf4f8-6d4d-41ef-9197-1c91ff2aef8c --json
 invd earnings qa --event-id cfbcf4f8-6d4d-41ef-9197-1c91ff2aef8c --json
 
 # Search earnings calls (optional: --mode, --case-sensitive, --event-id, --identifier, --from, --to, --type, --event-type, --limit)
-invd earnings search -q "Azure growth" -m semantic -i MSFT --json
+invd earnings search -q "Azure growth" -m lexical -i MSFT --json
 
 # Live audio stream URL (optional: --event-id, --identifier, --year, --quarter, --date, --event-type)
 invd earnings stream --event-id cfbcf4f8-6d4d-41ef-9197-1c91ff2aef8c --json
@@ -633,7 +633,8 @@ Find the call, then read it from the cheapest source to the most detailed:
 invd earnings events -i NVDA -s desc -l 4 --json            # pick the event_id
 invd earnings transcript --event-id <event_id> --format sections --json
 invd earnings extractions --event-id <event_id> --kind guidance --json
-invd earnings search -q "gross margin outlook" --mode hybrid --event-id <event_id> --json
+invd earnings search -q "gross margin outlook" --event-id <event_id> --json
+invd earnings search -q "data center revenue" --mode literal --event-id <event_id> --json   # exact quote in the call
 invd earnings document-search -q FY2027 -i NVDA --mode literal --json   # exact token in the company's documents
 invd earnings price-attribution --event-id <event_id> --json   # optional: price moves during the call
 ```

package/dist/src/generated/cli-manifest.json

@@ -1,6 +1,6 @@
 {
   "specVersion": "1.0.0",
-  "specSha256": "9f4094202acf89ee7a89a522e9825beac9df8a364d2d4b0f59710dc05d986cc5",
+  "specSha256": "d632bccc5d4a587bdf30590211ef565f5503e2f50502a0fffa5a9fc2e8891717",
   "groups": [
     {
       "name": "company",
@@ -708,7 +708,7 @@
           "required": true,
           "type": "string",
           "example": "Azure growth",
-          "description": "The keywords, exact text (mode=literal) or question (semantic / hybrid) to search for",
+          "description": "The keywords or phrases (mode=lexical) or exact text (mode=literal) to search for",
           "alias": "q"
         },
         {
@@ -718,13 +718,11 @@
           "type": "string",
           "enum": [
             "lexical",
-            "literal",
-            "semantic",
-            "hybrid"
+            "literal"
           ],
           "default": "lexical",
-          "example": "hybrid",
-          "description": "lexical (keywords, default), literal (exact characters), semantic (meaning) or hybrid (lexical + semantic, fused)",
+          "example": "lexical",
+          "description": "lexical (keywords and phrases, default) or literal (exact characters)",
           "alias": "m"
         },
         {
@@ -1771,7 +1769,7 @@
           "required": true,
           "type": "string",
           "example": "Azure growth",
-          "description": "The keywords, exact text (mode=literal) or question (semantic / hybrid) to search for",
+          "description": "The keywords or phrases (mode=lexical) or exact text (mode=literal) to search for",
           "alias": "q"
         },
         {
@@ -1781,13 +1779,11 @@
           "type": "string",
           "enum": [
             "lexical",
-            "literal",
-            "semantic",
-            "hybrid"
+            "literal"
           ],
           "default": "lexical",
-          "example": "semantic",
-          "description": "lexical (keywords, default), literal (exact characters), semantic (meaning) or hybrid (lexical + semantic, fused)",
+          "example": "lexical",
+          "description": "lexical (keywords and phrases, default) or literal (exact characters)",
           "alias": "m"
         },
         {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@invinite-org/invinite-data-cli",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "type": "module",
   "description": "CLI for the Invinite Data API",
   "publishConfig": {