current-cli 0.1.54__tar.gz → 0.1.56__tar.gz

{current_cli-0.1.54 → current_cli-0.1.56}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: current-cli
-Version: 0.1.54
+Version: 0.1.56
 Summary: Command line interface for the Current API, generated from its OpenAPI schema at runtime
 Author-email: Orin <your-email@example.com>
 License-Expression: MIT

{current_cli-0.1.54 → current_cli-0.1.56}/current_cli/schema.yml

@@ -1668,12 +1668,13 @@ paths:
   /api/observations/observations/by-project/:
     get:
       operationId: observations_observations_by_project_retrieve
-      description: Which projects hold the matching observations, and how many each
-        holds. Takes the same filters as the list. Answers 'which projects have activity
-        of this kind in this window' in one call — paging every matching row and grouping
-        them by hand is the same question asked badly, and it miscounts. Projects
-        are ordered by count and capped; narrow the window rather than expect every
-        project back.
+      description: 'Which projects hold the matching observations: how many each holds
+        and when the latest happened. Takes the same filters as the list. A project
+        absent from the result has no matching activity at all — not old activity.
+        To find projects that have gone quiet, leave the window open, sort by latest_occurred_at
+        and compare each project''s latest to your cutoff; never infer a quiet set
+        by subtracting a recent one. Pages by project: read total_projects and follow
+        next_offset.'
       parameters:
       - in: query
         name: facets
@@ -1690,6 +1691,16 @@ paths:
         schema:
           type: string
         description: Comma-separated observation UUIDs
+      - in: query
+        name: limit
+        schema:
+          type: integer
+        description: Projects per page (default 100, cap 200)
+      - in: query
+        name: offset
+        schema:
+          type: integer
+        description: Project page offset (default 0)
       - in: query
         name: order
         schema:
@@ -1729,6 +1740,17 @@ paths:
           learned of it). ISO-8601; a bare date means the START of that day. A value
           with no offset is read in the workspace's timezone when exactly one workspace
           is in scope, otherwise UTC.
+      - in: query
+        name: sort
+        schema:
+          type: string
+          enum:
+          - -count
+          - -latest_occurred_at
+          - latest_occurred_at
+        description: 'Project order. ''-count'' (default) puts the busiest first.
+          ''latest_occurred_at'' puts the quietest first: the projects whose most
+          recent matching activity is oldest.'
       - in: query
         name: source
         schema:
@@ -5888,6 +5910,10 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/SourceReview'
+        proposed_sources:
+          type: array
+          items:
+            $ref: '#/components/schemas/ProposedSource'
         related_shipments:
           type: array
           items:
@@ -5908,6 +5934,7 @@ components:
       - attachments
       - conflicts
       - proposals
+      - proposed_sources
       - related_shipments
       - set
       - sources
@@ -7067,6 +7094,52 @@ components:
       - reason
       - type
       - version
+    ProposedSource:
+      type: object
+      description: |-
+        A shipment's packing list proposed as belonging to this invoice. Shown
+        beside the invoice so a person can compare and decide; its values are not
+        part of the invoice (conflicts, exports) until the match is accepted.
+      properties:
+        document:
+          type: string
+          format: uuid
+        extraction:
+          type: string
+          format: uuid
+        filename:
+          type: string
+        prefix:
+          type: string
+        source_path:
+          type: string
+        record: {}
+        checks:
+          type: array
+          items:
+            $ref: '#/components/schemas/ArithmeticCheck'
+        relationship:
+          type: string
+          format: uuid
+        version:
+          type: integer
+        reason:
+          type: string
+        set:
+          type: string
+          format: uuid
+      required:
+      - checks
+      - document
+      - extraction
+      - filename
+      - prefix
+      - reason
+      - record
+      - relationship
+      - set
+      - source_path
+      - version
     ProviderInfo:
       type: object
       properties:

{current_cli-0.1.54 → current_cli-0.1.56}/llms.txt

@@ -567,17 +567,20 @@ Invalidate the auth token on the server and forget it locally.
 
 ### current observations by-project retrieve
 
-Which projects hold the matching observations, and how many each holds. Takes the same filters as the list. Answers 'which projects have activity of this kind in this window' in one call — paging every matching row and grouping them by hand is the same question asked badly, and it miscounts. Projects are ordered by count and capped; narrow the window rather than expect every project back.
+Which projects hold the matching observations: how many each holds and when the latest happened. Takes the same filters as the list. A project absent from the result has no matching activity at all — not old activity. To find projects that have gone quiet, leave the window open, sort by latest_occurred_at and compare each project's latest to your cutoff; never infer a quiet set by subtracting a recent one. Pages by project: read total_projects and follow next_offset.
 
 GET /api/observations/observations/by-project/
 
 Options:
 - `--facets` - Add 'by_source' to the response: how many matching observations each source holds. Costs one extra grouped query, so it is opt-in — ask for it when you need to know this workspace's actual mix rather than assume one.
 - `--ids` - Comma-separated observation UUIDs
+- `--limit` - Projects per page (default 100, cap 200)
+- `--offset` - Project page offset (default 0)
 - `--order` - Sort key. Defaults to -occurred_at when project, since or until is given, because a window is a question about world time, and to -observed_at otherwise, because the stream is a work queue ordered by when Current learned of things.
 - `--project` - Filter by project UUID
 - `--revisions` - Observations are immutable, so an edited Chatter post is a second row sharing payload.record_key. 'all' (default) returns every revision, which is what the project audit log shows. 'current' returns only the latest revision of each post or comment, which is what a count of what people said means.
 - `--since` - Keep observations that happened at or after this instant. Bounds occurred_at (when it happened in the world), not observed_at (when Current learned of it). ISO-8601; a bare date means the START of that day. A value with no offset is read in the workspace's timezone when exactly one workspace is in scope, otherwise UTC.
+- `--sort` - Project order. '-count' (default) puts the busiest first. 'latest_occurred_at' puts the quietest first: the projects whose most recent matching activity is oldest.
 - `--source` - Keep only observations from this source; repeat to accept several. Common names work as well as the stored value: 'chatter' finds 'sitetracker_feed'. An unknown source is refused with the recorded ones named, because an empty page would read as 'nothing happened'.
 - `--status` - Filter by status (pending/ingested)
 - `--until` - Keep observations that happened at or before this instant, inclusive. A bare date means the END of that day, so since=2026-09-01&until=2026-09-14 is the fourteen days a person means by that.

{current_cli-0.1.54 → current_cli-0.1.56}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "current-cli"
-version = "0.1.54"
+version = "0.1.56"
 description = "Command line interface for the Current API, generated from its OpenAPI schema at runtime"
 readme = "README.md"
 requires-python = ">=3.10"