@bnbagent/studio-cli 0.0.6-alpha.5 → 0.0.6-alpha.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bnbagent/studio-cli",
-  "version": "0.0.6-alpha.5",
+  "version": "0.0.6-alpha.7",
   "description": "The `bag` CLI: scaffold, run, deploy, and monetize a single seller agent on BNB Chain (ERC-8004 identity, ERC-8183 commerce, x402 payments).",
   "license": "Apache-2.0",
   "repository": {
@@ -26,7 +26,7 @@
     "bag": "./dist/bag.js"
   },
   "dependencies": {
-    "@bnbagent/sdk": "0.5.0-alpha.2",
+    "@bnbagent/sdk": "0.5.0-alpha.3",
     "ai": "^7.0.29",
     "archiver": "^8.0.0",
     "commander": "^15.0.0",
@@ -38,7 +38,7 @@
     "tar": "^7.4.0",
     "viem": "^2.54.0",
     "yaml": "^2.9.0",
-    "@bnbagent/studio-runtime": "0.0.6-alpha.5"
+    "@bnbagent/studio-runtime": "0.0.6-alpha.7"
   },
   "devDependencies": {
     "@a2a-js/sdk": "^0.3.14",

package/recipes/agent/recipe.toml

@@ -11,7 +11,7 @@ node = [
     # neutral. The agent project's serving deps (@a2a-js/sdk / MCP SDK / ai)
     # come from the runtimes/<R>/ recipe selected at `bag init` time.
     "@bnbagent/studio-runtime",
-    "@bnbagent/sdk@0.5.0-alpha.1",
+    "@bnbagent/sdk@0.5.0-alpha.3",
 ]
 
 [env]

package/recipes/runtimes/agentcore/recipe.toml

@@ -32,7 +32,7 @@ node = [
     # BNBAGENT_RUNTIME_SECRET_ID is set (default secretsmanager mode + platform).
     "@aws-sdk/client-secrets-manager@^3.600.0",
     "@bnbagent/studio-runtime",
-    "@bnbagent/sdk@0.5.0-alpha.1",
+    "@bnbagent/sdk@0.5.0-alpha.3",
     # The LLM work hook (generateText + tools) and the model factory.
     "ai@^7.0.29",
     # Tool input schemas (AI SDK tools + MCP registerTool).

package/recipes/runtimes/azure-foundry/recipe.toml

@@ -19,7 +19,7 @@ status = "v1"
 [dependencies]
 node = [
     "@bnbagent/studio-runtime",
-    "@bnbagent/sdk@0.5.0-alpha.1",
+    "@bnbagent/sdk@0.5.0-alpha.3",
     # The LLM work hook (generateText + tools) and the model factory; the
     # Foundry host's OpenAI-compatible client comes from @ai-sdk/openai
     # (built from the BNBAGENT_LLM_* env the deploy injects).

package/recipes/x402-buyer/recipe.toml

@@ -6,7 +6,7 @@ status = "v0.0.x"
 [dependencies]
 node = [
     "@bnbagent/studio-runtime",
-    "@bnbagent/sdk@0.5.0-alpha.1",
+    "@bnbagent/sdk@0.5.0-alpha.3",
     "ai@^7.0.29",   # AI SDK `tool` wrappers around the buyer functions
     "zod@^3.25.0",  # tool input schemas
 ]

package/skills/bnbagent-studio.md

@@ -97,7 +97,7 @@ prices retain the paid merchant flow.
 
 ## CLI groups at a glance
 
-`init`, `scan`, `recipe`, `skills`, `wallet`, `erc8004`, `erc8183`, `x402`, `agents`, `config`, `env`, `dev`, `doctor`, `audit`, `deploy`, `platform`, `llm`, `bundle`, `budget` — see `bag --help` for details. `bag deploy [--provider bnb\|aws]` is the primary deploy command; `prepare`, `verify`, `status`, `info`, `destroy`, `logs`, `fix-gitignore`, and `provision-cognito` remain lifecycle subcommands (`deploy agent` is a deprecated compatibility alias). Provider deploy/status/logs/destroy and deploy-time credential validation are delegated to pinned `@bnbagent/deploy-cli@0.4.14`.
+`init`, `scan`, `recipe`, `skills`, `wallet`, `erc8004`, `erc8183`, `x402`, `agents`, `config`, `env`, `dev`, `doctor`, `audit`, `deploy`, `platform`, `llm`, `bundle`, `budget` — see `bag --help` for details. `bag deploy [--provider bnb\|aws]` is the primary deploy command; `prepare`, `verify`, `status`, `info`, `destroy`, `logs`, and `fix-gitignore` remain lifecycle subcommands (`deploy agent` is a deprecated compatibility alias). Provider deploy/status/logs/destroy and deploy-time credential validation are delegated to pinned `@bnbagent/deploy-cli@0.4.14`.
 
 ## Tool surface
 

package/skills/references/bnbagent-studio-adding-to-project.md

@@ -189,16 +189,16 @@ ERC-8004/8183 **last** with the deployed AgentCore endpoint:
 
 ```bash
 bag deploy prepare                 # readiness sweep
-bag deploy provision-cognito       # emits the Cognito CDK app you run (cdk deploy); wires discoveryUrl/clientId
 bag deploy --provider aws          # ship the Agent to AgentCore
 bag deploy verify --provider aws   # delegated status + reconcile ERC-8004 identity
 ```
 
-Gotcha: to serve external buyers, configure the Cognito authorizer
-(`provision-cognito` → `cdk deploy --outputs-file` → `provision-cognito --wire`);
-`bag deploy prepare` warns (W9) if unset but does NOT block. With no authorizer
-the runtime is IAM/SigV4 owner-only (never anonymous) — external buyers without
-AWS creds just can't reach it.
+Gotcha: `bag deploy --provider aws` provisions the Cognito user pool and the
+buyer M2M client itself and prints the token URL, client id, and scope — hand
+those to each buyer (Cognito has no public M2M self-registration; retrieve the
+client secret read-only from the AWS Console). Do not run
+`bag deploy provision-cognito`: it is deprecated and its CDK pool is never used
+by a deploy.
 
 Gotcha: `dispute_window` is read from the on-chain policy contract (24h on
 testnet). Buyers can dispute within that window after submit — the Agent can't

package/skills/references/bnbagent-studio-operating.md

@@ -25,7 +25,7 @@ wallet/LLM/budget ops.
 directory (Claude Code: `~/.claude/skills/bnbagent-studio/references/`; Cursor:
 `bnbagent-studio/references/` beside the `.mdc` rules). READ
 the file when the topic comes up — don't answer from memory:
-- `bnbagent-studio-use-aws-agentcore.md` — the delegated AgentCore lifecycle (`bag deploy --provider aws` / `status` / `logs` / `verify` / `destroy`, `provision-cognito`) + AWS prerequisites
+- `bnbagent-studio-use-aws-agentcore.md` — the delegated AgentCore lifecycle (`bag deploy --provider aws` / `status` / `logs` / `verify` / `destroy`) + AWS prerequisites
 - `bnbagent-studio-use-bnb-trial.md` — GitHub device login, 48h eligibility, staging verification, and the delegated BNB trial lifecycle
 - `bnbagent-studio-using-twak-wallet.md` — `[wallet].kind = "twak"` create / fund / SIWE-bind / container deploy / limitations
 - `bnbagent-studio-extending-signing.md` — `PolicyViolation` / `X402PolicyError` diagnosis + extending the EIP-712 allowlist
@@ -136,7 +136,6 @@ Returns a rich table of checks across the `app/agent/` sub-project:
 | Wallet tBNB balance | 0 tBNB | Faucet: testnet.bnbchain.org/faucet-smart |
 | Wallet U balance | 0 U | Transfer from holder, or ask for sponsor U |
 | 8004 registered | Not registered | Normally registered automatically at `bag deploy verify`. Manual: `bag erc8004 register --endpoint <url>` (only if you need an on-chain identity before deploy). WARN-only in `bag doctor` — it doesn't block local dev. |
-| Cognito authorizer (W9) | External-buyer readiness: `agentcore.json` carries no `authorizerConfiguration` / protocol metadata has placeholder `OAUTH_*` values | WARN-only (does NOT block) — needed to serve **external** buyers, not to deploy. With no authorizer the runtime is IAM/SigV4 owner-only (never anonymous). To open it to buyers: `bag deploy provision-cognito` → `cdk deploy --outputs-file cdk-outputs.json` → `bag deploy provision-cognito --wire`. |
 
 WARN-only items don't block; FAIL items do (exit 1).
 

package/skills/references/bnbagent-studio-scaffolding-agent.md

@@ -490,10 +490,10 @@ Local dev (from workspace root <name>/):
                                      # seller's skills). For MCP, use an MCP client.
 
 When ready to deploy:
-  bag deploy provision-cognito       # emit the Cognito CDK app — you run `cdk deploy`,
-                                     # then its discoveryUrl/clientId wire into the OAuth2 authorizer
   bag deploy prepare                 # readiness sweep
   bag deploy --provider aws          # ship the Agent to AgentCore (selected faces);
+                                     # provisions the Cognito pool + buyer M2M client and
+                                     # prints the token URL / client id / scope;
                                      # keystore injected via Secrets Manager (never in the CodeZip)
   bag deploy verify --provider aws --endpoint <url> # delegated status + reconcile ERC-8004
 
@@ -529,13 +529,12 @@ Edit (from workspace root):
   `TWAK_WALLET_PASSWORD` for twak — reconstructed at cold start, never in the
   package; the testnet-only `--secrets-mode envvars` fallback is refused on
   mainnet.
-- **AgentCore seller endpoints are never anonymous.** With no authorizer the runtime defaults
-  to IAM/SigV4 (owner-only, NOT open); to serve **external** buyers configure the
-  Cognito OAuth2 authorizer — `bag deploy provision-cognito` emits a CDK app the
-  user `cdk deploy --outputs-file`s, then `provision-cognito --wire` patches
-  `agentcore.json` + the card env. `bag deploy prepare` warns (W9) if unset but
-  does NOT block. Locally, `bag dev` runs without Cognito env, so the card omits
-  the scheme and is reachable without a token.
+- **AgentCore seller endpoints are never anonymous.** `bag deploy --provider aws`
+  provisions the Cognito OAuth2 pool + buyer M2M client itself and prints the
+  token URL / client id / scope to hand to buyers (`bag deploy provision-cognito`
+  is deprecated — a deploy uses its own pool regardless). Locally, `bag dev` runs
+  without Cognito env, so the card omits the scheme and is reachable without a
+  token.
 - **ERC-8183 does NOT require ERC-8004** at the protocol level (commerce contract
   doesn't check the identity registry). Local two-agent dev can run end-to-end
   without ever touching 8004. Use 8004 only when you actually want discoverable

package/skills/references/bnbagent-studio-selling-via-8183.md

@@ -160,12 +160,11 @@ Full Pieverse credit decisions live in `funding-pieverse-llm` (project-scope ski
 
 ERC-8183 / ERC-8004 registration is a **deploy-time** concern: the public
 AgentCore endpoint must exist before you register, so register **last**. The
-agent endpoint has no anonymous mode, so you must provision the Cognito OAuth2
-authorizer first.
+agent endpoint has no anonymous mode; `bag deploy` provisions the Cognito
+OAuth2 authorizer as part of the deploy.
 
 ```bash
 bag deploy prepare                  # readiness sweep
-bag deploy provision-cognito        # emit the Cognito CDK app; run `cdk deploy`, wire discoveryUrl/clientId
 bag deploy --provider aws           # ship the agent to AgentCore (selected protocol)
 bag deploy verify --provider aws    # delegated status + reconcile ERC-8004 identity
 ```
@@ -178,7 +177,7 @@ asks bnbagent-deploy for live status first, then performs the reconcile.
 
 **Hard rules**:
 - The endpoint must be **reachable** when registered. For A2A, smoke test the normalized card URL directly, for example `curl <agentcore-invocations-url>/.well-known/agent-card.json` (or `curl <already-registered-card-url>` if the endpoint already includes `/.well-known/agent-card.json`). For MCP, connect an MCP client to the deployed `/mcp` URL. Chain doesn't verify reachability, but buyers will see failures.
-- To serve external buyers, configure the Cognito authorizer (`provision-cognito` → `cdk deploy --outputs-file` → `provision-cognito --wire`); `bag deploy prepare` warns (W9) if unset but does NOT block. With no authorizer the runtime is IAM/SigV4 owner-only (never anonymous) — buyers without AWS creds just can't reach it.
+- `bag deploy --provider aws` provisions the Cognito user pool + buyer M2M client and prints the token URL, client id, and scope. Hand those to each buyer (the client secret is retrieved read-only from the AWS Console — studio never stores it). `bag deploy provision-cognito` is deprecated; its CDK pool is never used by a deploy.
 - Price bounds (`min_price`/`max_price`) live with the Agent — it clamps + signs the quote.
 
 ## Stage 5 — How a SUBMITTED job happens

package/skills/references/bnbagent-studio-use-aws-agentcore.md

@@ -106,7 +106,7 @@ flags); cloud execution is the pinned bnbagent-deploy's job.
 | `bag deploy status [--provider aws]` | List every recorded deployment and delegated live state (read-only); `--no-probe` is local-only. |
 | `bag deploy logs [--provider aws] [--follow] [--since 10m]` | Delegate runtime logs to bnbagent-deploy. |
 | `bag deploy destroy [--provider aws]` | Dry-run teardown plan; `--execute` delegates `destroy --yes`; `--purge` also deletes retained ECR/log resources. |
-| `bag deploy provision-cognito [--wire]` | Emit (then wire) the optional Cognito CDK app for operator-managed buyer credentials. |
+| `bag deploy provision-cognito [--wire]` | **Deprecated** (hidden from `--help`). Emits a Cognito CDK app whose pool a deploy never uses. |
 
 ## Typical workflows
 
@@ -129,21 +129,19 @@ plus a container engine.
 > without asking the user first.
 
 > 🔒 **Inbound auth is auto-provisioned.** An AgentCore seller endpoint is
-> **never anonymous**. When `agentcore.json` carries no authorizer of its own,
-> the delegated deploy auto-provisions a Cognito inbound OAuth (account pool +
-> per-agent M2M client) so the runtime is token-gated. To mint buyer
-> credentials the operator manages directly, use the optional CDK path:
+> **never anonymous**. The delegated deploy provisions a Cognito inbound OAuth
+> (account pool + per-agent M2M client) so the runtime is token-gated, then
+> writes the live token URL, scope, client id, and discovery URL back into
+> `studio.toml`, `agentcore.json`, and the printed buyer block. Hand those to
+> each buyer; the client secret is retrieved read-only in the AWS Console
+> (Cognito → User pools → App clients → "Show client secret") — never
+> persisted by studio.
 >
-> 1. `bag deploy provision-cognito` emits a self-contained Cognito CDK app
->    (UserPool + M2M app client) — the user runs `cdk deploy --outputs-file
->    cdk-outputs.json` themselves.
-> 2. `bag deploy provision-cognito --wire` reads that local outputs file and
->    patches `agentcore.json`'s `authorizerConfiguration.customJwtAuthorizer` +
->    the card's `OAUTH_TOKEN_URL` / `OAUTH_SCOPE` (no AWS call). The client
->    secret is retrieved read-only in the AWS Console (Cognito → User pools →
->    App clients → "Show client secret") — never persisted by studio.
+> `bag deploy provision-cognito` (the CDK path) is **deprecated**: a deploy
+> provisions and uses its own pool regardless, so the CDK stack is a billable
+> orphan and anything wired from it gets overwritten.
 >
-> Buyers then reach the agent over plain HTTPS + an OAuth2 Bearer (the
+> Buyers reach the agent over plain HTTPS + an OAuth2 Bearer (the
 > client-credentials grant) — **no AWS SigV4 / IAM credentials**. Locally,
 > `bag dev` runs without Cognito env, so the card omits the scheme.
 

package/skills/references/bnbagent-studio-using-twak-wallet.md

@@ -254,6 +254,9 @@ registers a `Container` runtime and `app/agent/Dockerfile` builds the image
 | No wallet import | S-6 | Switching wallet kinds changes your address → re-run `bag 8004 register` (new on-chain identity). |
 | Programmatic wallet creation forces password onto argv | S-8 | Bridged by `bag wallet twak-init` (you supply it via stdin / 0600 file / hidden prompt; studio forwards it on the child's argv because twak requires the flag); the manual twak commands remain a fallback. |
 | CLI has no daily/monthly caps | — | Studio's policy layer (`[budget].max_per_day_usd`, host allowlist, per-request caps) is the spend authority for both wallet kinds. |
+| `twak wallet balance --chain bsctestnet` rejects the chain | BUG-031 | Fails with `CHAIN_UNSUPPORTED` even though `wallet address` and `erc8183` accept `bsctestnet`. Use `bag wallet balance` (RPC-based, works on testnet), or raw RPC: `eth_getBalance` for tBNB and an `eth_call` of `balanceOf(address)` on the U token for token balance. |
+| `twak tx <hash> --chain bsctestnet` rejects the chain | BUG-032 | Same chain-registry gap on the readback path: transactions twak itself just mined on `bsctestnet` cannot be inspected with `twak tx`. Use public RPC (`eth_getTransactionByHash` / `eth_getTransactionReceipt`) or BscScan testnet instead. |
+| Raw `twak erc8183 create-job` has no expiry preflight | BUG-030 | An `--expires-at` inside the policy's dispute window is accepted, all four funding steps succeed, and only the final `submit` reverts `SubmissionTooLate()` (`0x15e5dd74`). Prefer the SDK path (`ERC8183Client` preflights this); if you must use the raw CLI, set `expires_at ≥ now + deadline + dispute_window` — on testnet's 24h window, `now + 172800` (48h) is a safe floor. |
 
 ## 7. Quick health checks