@layers/amba 4.0.4 → 4.1.0

package/README.md

@@ -5,7 +5,7 @@ Amba is the agent-native backend-as-a-service for mobile and web apps. This pack
 ## Install
 
 ```bash
-npm install -g @layers/amba@1.0.1
+npm install -g @layers/amba
 ```
 
 …or run on demand:
@@ -50,10 +50,10 @@ amba login             # browser-based auth (skip with --token / AMBA_PAT)
 amba projects list
 ```
 
-Track your first event from the CLI:
+Check the project is live:
 
 ```bash
-amba events track app_opened --prop source=cli
+amba status --detailed
 ```
 
 ## Common commands

package/dist/api-client.d.ts

@@ -384,12 +384,15 @@ export interface FunctionLogsResponse {
     truncated: boolean;
     since: string;
     until: string;
+    /** Present when `since_request_id` anchored the range — the anchor event's timestamp. */
+    anchor?: string;
 }
 export declare function getFunctionLogs(projectId: string, functionName: string, options?: {
     since?: string;
     until?: string;
     limit?: number;
     requestId?: string;
+    sinceRequestId?: string;
 }): Promise<ApiResponse<FunctionLogsResponse>>;
 export interface QueueBinding {
     queue_name: string;
@@ -476,7 +479,7 @@ export declare function deleteSecretViaApi(projectId: string, name: string, opti
     deleted: true;
 }>>;
 /** Closed set of column types the server accepts. */
-export type CollectionColumnType = 'uuid' | 'text' | 'integer' | 'bigint' | 'numeric' | 'boolean' | 'timestamptz' | 'date' | 'jsonb' | 'vector';
+export type CollectionColumnType = 'uuid' | 'text' | 'integer' | 'bigint' | 'numeric' | 'boolean' | 'timestamptz' | 'date' | 'jsonb' | 'vector' | 'text[]' | 'integer[]' | 'bigint[]' | 'numeric[]' | 'boolean[]' | 'uuid[]';
 export interface CollectionColumn {
     name: string;
     type: CollectionColumnType;

package/dist/commands/collections.d.ts

@@ -20,6 +20,7 @@
  * Multi-op alters are issued sequentially so the operator audit trail
  * stays one-to-one with developer actions.
  */
+import { type CollectionColumn, type CollectionIndex } from '../api-client.js';
 export interface CollectionsCreateOptions {
     /** Field specs in `name:type[:nullable]` form. May repeat. */
     field: string[];
@@ -46,3 +47,57 @@ export declare function collectionsListCommand(): Promise<void>;
 export declare function collectionsDropCommand(name: string, options?: {
     confirm?: string;
 }): Promise<void>;
+/**
+ * Parse a `--field` spec into a `CollectionColumn`.
+ *
+ * Accepted grammars:
+ *
+ *   1. **Plain column:** `name:type[:nullable]`
+ *      Examples: `letter_id:uuid`, `parsed:jsonb:nullable`, `tags:text[]`,
+ *      `scores:integer[]:nullable`. Array types (`text[]`, `integer[]`,
+ *      `bigint[]`, `numeric[]`, `boolean[]`, `uuid[]`) follow the same
+ *      grammar as scalars and unlock the contains/containedBy/overlaps
+ *      query operators.
+ *
+ *   2. **Foreign key:** `name:type:fk(<table>[.<column>][:onDelete])`
+ *      Examples:
+ *        `plan_id:uuid:fk(plans)` — references `plans(id)`, default no-action
+ *        `plan_id:uuid:fk(plans.id)` — explicit column
+ *        `plan_id:uuid:fk(plans.id:cascade)` — ON DELETE CASCADE
+ *        `parent_id:uuid:fk(comments:set_null)` — ON DELETE SET NULL
+ *
+ *      Note: a `user_id` FK to `app_users(id)` is auto-emitted on every
+ *      collection server-side. Customers don't need to declare it.
+ *
+ *   3. **Vector:** `name:vector:<dim>` or `name:vector(<dim>)`
+ *      Examples:
+ *        `embedding:vector:1536` — OpenAI text-embedding-3-small
+ *        `embedding:vector(384)` — sentence-transformers / all-MiniLM
+ *      Dimension is validated client-side as 1..4096. For an HNSW /
+ *      IVFFlat index on the column, supply `--index 'embedding'`
+ *      separately.
+ *
+ *   4. **Vector + nullable:** `name:vector:<dim>:nullable`
+ *      Vector columns can be nullable for "embedding generated lazily".
+ *
+ * Multi-arg combinations (e.g. fk + nullable on the same column) parse
+ * left-to-right: the third segment is the FK / vector / nullable
+ * marker; if it's an FK or vector, the optional fourth segment is
+ * `nullable`. Plain columns put `nullable` in slot 3.
+ *
+ * Exported for tests.
+ */
+export declare function parseColumnSpec(spec: string): CollectionColumn;
+/**
+ * Parse an index spec into the wire shape data's API expects.
+ *
+ * Input syntax (CLI-friendly): `"col1 [asc|desc], col2 [asc|desc]"`.
+ * Wire shape (per data's contract): `{ columns: ['col1 desc', 'col2 asc'] }` —
+ * direction is embedded in each column string and parsed by the DDL emit.
+ *
+ * Bare column names (no direction) are passed through verbatim; the
+ * default sort direction is the DDL emit's responsibility.
+ *
+ * Exported for tests.
+ */
+export declare function parseIndexSpec(spec: string): CollectionIndex;

package/dist/commands/functions-logs.d.ts

@@ -6,6 +6,10 @@
  *   - `--tail`: print the last hour's events, then poll every 3s for
  *     new events past the highest seen `EventTimestampMs`. Ctrl+C to stop.
  *
+ * `--since-request-id <r_...>` anchors the range start at the oldest event
+ * mentioning that request id ("show me everything from this request
+ * onward") — the server resolves the anchor; works in both modes.
+ *
  * Output formatting:
  *   - `--json`: NDJSON to stdout (one event per line) so `| jq` works.
  *   - default: human-readable lines:
@@ -28,5 +32,12 @@ export interface FunctionsLogsOptions {
     json?: boolean;
     /** Only show events whose log/exception text mentions this request id (`r_...`). */
     requestId?: string;
+    /**
+     * Anchor the range start at the oldest event mentioning this request id
+     * ("everything from this request onward"). Searched within the last 24h
+     * (or within --since/--until when given). Composes with --requestId, which
+     * filters instead of anchoring. Works with --tail (anchors the backfill).
+     */
+    sinceRequestId?: string;
 }
 export declare function functionsLogsCommand(functionName: string, options?: FunctionsLogsOptions): Promise<void>;

package/dist/commands/monetization.d.ts

@@ -13,10 +13,20 @@
  *                                so the next plan is a no-op. Writes ONLY Amba's
  *                                own state — never the provider. Idempotent.
  *   amba monetization apply    — push the declared config to the provider.
- *                                ADDITIVE only: create entitlements/offerings/
- *                                packages/paywall-drafts + attach products.
- *                                Refuses if the provider drifted since the plan;
- *                                never does destructive changes.
+ *                                DURABLE: the API returns a pollable
+ *                                operation_id and the CLI polls it to a
+ *                                terminal state. Additive changes apply
+ *                                automatically; destructive changes run only
+ *                                behind --confirm (which approves the exact
+ *                                plan_hash — a pending apply awaiting
+ *                                confirmation is approved by re-running with
+ *                                --confirm). STORE-PRODUCT steps (creating
+ *                                declared products in the provider and, for
+ *                                App Store products with push intent, in App
+ *                                Store Connect) ALWAYS wait for an explicit
+ *                                approval of the started apply — an up-front
+ *                                --confirm never auto-runs them. Refuses if
+ *                                the provider drifted since the plan.
  *
  * Project is resolved via `loadProjectConfig` — same pattern as the other
  * project-scoped CLI commands.

package/dist/commands/ship.d.ts

@@ -0,0 +1,47 @@
+/**
+ * `amba ship` — take this Expo app from code-complete to live on the App Store
+ * and Google Play, and `amba ship init` to scaffold its config.
+ *
+ *   amba ship                 run the full pipeline (preflight → monetization →
+ *                             build → submit → metadata → release)
+ *   amba ship --phase build   run a single phase
+ *   amba ship --dry-run       print the plan; touch nothing
+ *   amba ship init            scaffold amba.ship.json
+ *
+ * Build/submit/release shell out to `eas` (the Expo toolchain owns the build,
+ * the signing credentials, and the store submit). Monetization delegates to the
+ * Amba control plane (`amba monetization`). Steps no API can do — create the
+ * store app record, the Apple Paid-Apps agreement, screenshots, store review —
+ * are detected and surfaced as manual gates with the exact console action.
+ */
+import { type ShipConfig } from '../ship/config.js';
+import { type Executor } from '../ship/exec.js';
+export interface ShipCommandOptions {
+    phase?: string;
+    platform?: string;
+    dryRun?: boolean;
+    force?: boolean;
+    config?: string;
+}
+/** Test seam: override the cloud-touching + clock dependencies. */
+export interface ShipCommandDeps {
+    exec?: Executor;
+    resolveProjectId?: () => Promise<string | null>;
+    adminGet?: <T>(path: string) => Promise<{
+        data: T;
+    }>;
+    now?: () => string;
+    sleep?: (ms: number) => Promise<void>;
+    stateBaseDir?: string;
+    releasePollMs?: number;
+    releaseMaxWaitMs?: number;
+}
+/** Read + parse + validate a ship config file. Throws with every error joined. */
+export declare function loadShipConfig(file: string): Promise<ShipConfig>;
+export declare function shipCommand(options?: ShipCommandOptions, deps?: ShipCommandDeps): Promise<void>;
+export interface ShipInitOptions {
+    config?: string;
+    force?: boolean;
+    slug?: string;
+}
+export declare function shipInitCommand(options?: ShipInitOptions): Promise<void>;