@layers/amba 4.1.0 → 4.1.1

package/dist/commands/monetization.d.ts

@@ -22,11 +22,13 @@
  *                                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.
+ *                                App Store products with push intent in App
+ *                                Store Connect, and Google Play one-time
+ *                                products with push intent in Google Play)
+ *                                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/index.js

@@ -2853,7 +2853,7 @@ All SDKs expose the same surface: \`Amba.configure({ projectId, apiKey })\`, the
 - **analytics** — funnels + retention. Query via \`amba_analytics_get\`.
 
 ### Infrastructure
-- **collections** — your own typed key-value tables. Define with \`amba_collections_create\`; read/write from SDK \`Amba.client.*\`.
+- **collections** — your own relational Postgres tables (typed columns, foreign keys, transactions, unique indexes, vector search). Define with \`amba_collections_create\`; read/write from SDK \`Amba.client.*\`.
 - **functions** — serverless TypeScript handlers. Deploy with \`amba_functions_deploy\`; schedule with \`amba_functions_schedule\`.
 - **sites** — static site hosting at \`*.app.amba.host\`. Deploy with \`amba_sites_deploy\`.
 - **media** — file storage + CDN. Upload via \`amba_media_upload\`.
@@ -3490,7 +3490,7 @@ When the user asks you to wire Amba into this codebase, run this journey end-to-
 - **gamification** — XP, achievements, streaks, leaderboards, challenges (\`amba://setup/gamification\`).
 - **economy** — currencies, catalog, stores, inventory (\`amba://setup/economy\`).
 - **social** — friends, groups, feeds, messaging, moderation, reviews (\`amba://setup/social\`).
-- **infrastructure** — collections (typed tables), functions, AI prompts, secrets, configs, integrations, media, sites (\`amba://setup/infrastructure\`).
+- **infrastructure** — collections (relational Postgres tables), functions, AI prompts, secrets, configs, integrations, media, sites (\`amba://setup/infrastructure\`).
 
 ## SDKs
 
@@ -6901,11 +6901,13 @@ async function paymentsPayoutsCommand(input) {
 *                                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.
+*                                App Store products with push intent in App
+*                                Store Connect, and Google Play one-time
+*                                products with push intent in Google Play)
+*                                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.
@@ -9528,7 +9530,7 @@ async function diffConfigCommand(file = DEFAULT_BUNDLE_FILE, options = {}) {
 //#endregion
 //#region src/index.ts
 const program = new Command();
-program.name("amba").description("amba — agent-native backend-as-a-service for mobile apps.").version("4.1.0");
+program.name("amba").description("amba — agent-native backend-as-a-service for mobile apps.").version("4.1.1");
 program.option("--token <pat>", "Use a Personal Access Token for headless / CI / agent use (overrides ~/.amba/credentials.json + AMBA_PAT env)");
 program.hook("preAction", (thisCommand) => {
 	setBearerOverride(resolveTokenSource({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@layers/amba",
-  "version": "4.1.0",
+  "version": "4.1.1",
   "description": "amba — agent-native backend-as-a-service. Functions, collections, storage, AI, email, queues, sites, and `amba ship` to take an Expo app live on the App Store + Google Play. `npx @layers/amba init` to start.",
   "type": "module",
   "bin": {
@@ -49,8 +49,8 @@
     "tsdown": "^0.12.5",
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
-    "@layers/amba-shared": "4.0.4",
-    "@layers/amba-mcp": "4.0.6"
+    "@layers/amba-mcp": "4.0.6",
+    "@layers/amba-shared": "4.0.4"
   },
   "scripts": {
     "build": "tsdown && tsc --emitDeclarationOnly",

package/skill-bundle/SKILL.md

@@ -176,7 +176,7 @@ For each surface in the confirmed set, read the relevant reference file and exec
 - **gamification** (XP rules, achievements, streaks, leaderboards, challenges) → `references/gamification.md`
 - **economy** (currencies, catalog, stores, inventory) → `references/economy.md`
 - **social** (friends, groups, feeds, messaging, moderation, reviews) → `references/social.md`
-- **infrastructure** (collections / DB tables, functions, analytics, AI prompts) → `references/infrastructure.md`
+- **infrastructure** (collections / relational Postgres tables, functions, analytics, AI prompts) → `references/infrastructure.md`
 
 Each reference file has, in order:
 

package/skill-bundle/references/infrastructure.md

@@ -1,14 +1,14 @@
 # Infrastructure
 
-The plumbing that sits behind every other surface: custom database tables (Collections — schema-first, per-tenant), serverless functions (run server-side code without standing up a backend), analytics (events + sessions), AI prompts (managed LLM templates, callable from the SDK with per-tenant keys), secrets, runtime configs, feature flags, third-party integrations (RevenueCat / Superwall / Resend / Stripe / etc.), media (file storage + CDN), and sites (static asset hosting at `*.app.amba.host`).
+The plumbing that sits behind every other surface: relational Postgres tables (Collections — schema-first, per-tenant), serverless functions (run server-side code without standing up a backend), analytics (events + sessions), AI prompts (managed LLM templates, callable from the SDK with per-tenant keys), secrets, runtime configs, feature flags, third-party integrations (RevenueCat / Superwall / Resend / Stripe / etc.), media (file storage + CDN), and sites (static asset hosting at `*.app.amba.host`).
 
 If gamification, economy, and social are the playable surface, **infrastructure is what you build a custom product on top of**. Anything that doesn't fit the canned surfaces lands here.
 
 ## MCP tools
 
-### Collections (typed tables)
+### Collections (relational Postgres tables)
 
-A collection is a schema-first table inside the project's isolated tenant database. You describe the columns, the server creates the table and any indexes. Rows are scoped to the signed-in `app_user` automatically (server-enforced auto row-level isolation) for SDK clients — admin tools bypass this.
+A collection is a relational Postgres table inside the project's isolated tenant database — typed columns, foreign keys, transactions, unique indexes, and vector search. You describe the columns, the server creates the table and any indexes. Rows are scoped to the signed-in `app_user` automatically (server-enforced auto row-level isolation) for SDK clients — admin tools bypass this.
 
 | Tool | Purpose | Example args |
 | --- | --- | --- |