@bagdock/cli 0.3.0 → 0.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bagdock/cli",
-  "version": "0.3.0",
+  "version": "0.5.0",
   "description": "Bagdock developer CLI — build, test, and deploy apps and edges on the Bagdock platform",
   "keywords": [
     "bagdock",

package/skill-evals/bagdock-cli/evals.json

@@ -1,6 +1,6 @@
 {
   "skill": "bagdock-cli",
-  "version": "0.3.0",
+  "version": "0.5.0",
   "evals": [
     {
       "id": "login-flow",
@@ -147,6 +147,104 @@
       "input": "What apps do I have deployed?",
       "expected_commands": ["bagdock apps list --json"],
       "expected_behavior": "Lists all deployed apps with slugs, types, and status"
+    },
+    {
+      "id": "validate-before-submit",
+      "description": "Agent should validate before submitting",
+      "input": "Check if my adapter is ready to submit to the marketplace",
+      "expected_commands": ["bagdock validate --json"],
+      "expected_behavior": "Runs local checks on bagdock.json and bundle, returns pass/warn/fail"
+    },
+    {
+      "id": "submission-list",
+      "description": "Agent should list submissions",
+      "input": "Show me all my marketplace submissions for this app",
+      "expected_commands": ["bagdock submission list --json"],
+      "expected_behavior": "Lists submission history with IDs, versions, and dates"
+    },
+    {
+      "id": "submission-status",
+      "description": "Agent should check submission status",
+      "input": "What's the review status of submission iadpv_abc123?",
+      "expected_commands": ["bagdock submission status iadpv_abc123 --json"],
+      "expected_behavior": "Returns detailed review state including status, reason, and timestamps"
+    },
+    {
+      "id": "submission-withdraw",
+      "description": "Agent should withdraw a pending submission",
+      "input": "Withdraw my pending submission iadpv_abc123, I found a bug",
+      "expected_commands": ["bagdock submission withdraw iadpv_abc123"],
+      "expected_behavior": "Cancels submission, sets review_status back to draft"
+    },
+    {
+      "id": "open-dashboard",
+      "description": "Agent should open project in dashboard",
+      "input": "Open my adapter in the Bagdock dashboard",
+      "expected_commands": ["bagdock open"],
+      "expected_behavior": "Opens browser to dashboard URL for the current project"
+    },
+    {
+      "id": "inspect-app",
+      "description": "Agent should inspect app deployment details",
+      "input": "Show me the deployment details for smart-entry",
+      "expected_commands": ["bagdock inspect smart-entry --json"],
+      "expected_behavior": "Returns app details including worker URL, version, review status"
+    },
+    {
+      "id": "env-pull",
+      "description": "Agent should pull env vars for local development",
+      "input": "Pull the env var keys from my deployed adapter to a local .env file",
+      "expected_commands": ["bagdock env pull .env.local"],
+      "expected_behavior": "Creates .env.local with keys and empty values, warns that values need filling"
+    },
+    {
+      "id": "link-project",
+      "description": "Agent should link directory to a project",
+      "input": "Link this directory to my smart-entry adapter",
+      "expected_commands": ["bagdock link --slug smart-entry"],
+      "expected_behavior": "Creates .bagdock/link.json with slug, other commands use it as fallback"
+    },
+    {
+      "id": "switch-operator-sandbox",
+      "description": "Agent should switch to sandbox environment for testing",
+      "input": "Switch to test mode for the WiseStorage operator",
+      "expected_commands": ["bagdock switch --operator wisestorage --env test"],
+      "expected_behavior": "Updates active profile with operatorSlug=wisestorage and environment=test"
+    },
+    {
+      "id": "switch-interactive",
+      "description": "Agent should use interactive switch when operator unknown",
+      "input": "I want to switch to a different operator",
+      "expected_commands": ["bagdock switch"],
+      "expected_behavior": "Lists available operators, prompts selection, then prompts environment choice"
+    },
+    {
+      "id": "deploy-to-test",
+      "description": "Agent should deploy to sandbox environment",
+      "input": "Deploy my adapter to the sandbox for testing",
+      "expected_commands": ["bagdock --env test deploy --target staging --yes"],
+      "expected_behavior": "Deploys to staging target within the test/sandbox environment"
+    },
+    {
+      "id": "inspect-test-env",
+      "description": "Agent should inspect an app in test environment",
+      "input": "Show me the deployment details of my app in the sandbox",
+      "expected_commands": ["bagdock --env test inspect --json"],
+      "expected_behavior": "Returns app details from the sandbox tenant database"
+    },
+    {
+      "id": "link-with-env",
+      "description": "Agent should link directory with specific environment",
+      "input": "Link this directory to smart-entry in test mode",
+      "expected_commands": ["bagdock link --slug smart-entry --env test"],
+      "expected_behavior": "Creates .bagdock/link.json with slug and environment=test"
+    },
+    {
+      "id": "env-override-per-command",
+      "description": "Agent should use --env flag to override environment for a single command",
+      "input": "List apps on the live environment even though I'm currently in test mode",
+      "expected_commands": ["bagdock --env live apps list --json"],
+      "expected_behavior": "Lists apps from the live tenant database, does not change profile"
     }
   ]
 }

package/skills/bagdock-cli/SKILL.md

@@ -45,9 +45,19 @@ For CI/CD, set `BAGDOCK_API_KEY` in your environment. For interactive use, run `
 | `-q, --quiet` | Suppress status messages (implies `--json`) |
 | `--api-key <key>` | Override auth for this invocation |
 | `-p, --profile <name>` | Use a named profile (overrides `BAGDOCK_PROFILE`) |
+| `--env <live\|test>` | Override environment for this invocation |
 | `-V, --version` | Print version |
 | `-h, --help` | Print help |
 
+## Environment Context
+
+All API calls include `X-Environment` and `X-Operator-Slug` headers. Resolution:
+
+- **Environment**: `--env` flag > `.bagdock/link.json` > profile > `BAGDOCK_ENV` > `live`
+- **Operator**: `BAGDOCK_OPERATOR` env var > profile stored value
+
+Use `bagdock switch` to select operator and environment interactively, or pass `--env test` to any command.
+
 ## Available Commands
 
 | Command | Description |
@@ -62,11 +72,20 @@ For CI/CD, set `BAGDOCK_API_KEY` in your environment. For interactive use, run `
 | `env list` | List app environment variables |
 | `env set <key> <value>` | Set an environment variable |
 | `env remove <key>` | Remove an environment variable |
+| `env pull [file]` | Pull remote env var keys to local .env file |
 | `keys create` | Create a new API key (raw key shown once) |
 | `keys list` | List API keys |
 | `keys delete <id>` | Revoke an API key |
+| `validate` | Run local pre-submission checks on bagdock.json and bundle |
+| `submission list` | List marketplace submission history |
+| `submission status <id>` | Fetch detailed review state for a submission |
+| `submission withdraw <id>` | Cancel a pending submission |
+| `open [slug]` | Open project in Bagdock dashboard |
+| `inspect [slug]` | Show deployment details and status |
+| `link` | Link directory to a Bagdock app or edge |
+| `switch` | Switch operator and environment context (live/test) |
 | `doctor` | Run environment diagnostics (version, auth, config, agents) |
-| `auth list` | List stored profiles |
+| `auth list` | List stored profiles (with operator + env) |
 | `auth switch [name]` | Switch active profile |
 | `apps list` | List deployed applications |
 | `apps get <slug>` | Show details for an application |
@@ -112,6 +131,34 @@ bagdock keys list --json
 3. **Missing `bagdock.json`** — `deploy`, `submit`, and `env` commands require a `bagdock.json` in the current directory. Run `bagdock init` first.
 4. **Expired session** — If `whoami` fails, run `bagdock login` again. Sessions expire after 8 hours.
 
+### Validate before submitting
+
+```bash
+bagdock validate
+bagdock submit
+```
+
+### Check submission status
+
+```bash
+bagdock submission list --json
+bagdock submission status iadpv_xxx
+```
+
+### Link a directory and inspect
+
+```bash
+bagdock link --slug my-adapter
+bagdock inspect
+bagdock open
+```
+
+### Pull env vars for local dev
+
+```bash
+bagdock env pull .env.local
+```
+
 ## When to Load References
 
 Load specific reference files when the task involves:
@@ -121,3 +168,5 @@ Load specific reference files when the task involves:
 - **Environment variables** → `references/env.md`
 - **Local development** → `references/dev.md`
 - **Error codes or troubleshooting** → `references/error-codes.md`
+- **Marketplace submission lifecycle** → `references/marketplace.md`
+- **App management (open, inspect, link)** → `references/app-management.md`

package/skills/bagdock-cli/references/app-management.md

@@ -0,0 +1,63 @@
+# App Management Commands
+
+Commands for managing the relationship between your local directory and a Bagdock app or edge.
+
+## `bagdock link`
+
+Links the current directory to a Bagdock app or edge. Once linked, other commands (deploy, env, open, inspect, submission) use the linked slug as a fallback — no `bagdock.json` required.
+
+```bash
+# Interactive: select from your apps
+bagdock link
+
+# Non-interactive (CI/agents)
+bagdock link --slug my-adapter
+```
+
+Stores the link in `.bagdock/link.json`:
+
+```json
+{
+  "slug": "my-adapter",
+  "linkedAt": "2026-04-05T00:00:00.000Z"
+}
+```
+
+### Slug Resolution Order
+
+1. Explicit `--slug` or `--app` argument
+2. `bagdock.json` in current directory
+3. `.bagdock/link.json` (linked app)
+
+## `bagdock open [slug]`
+
+Opens the project in the Bagdock dashboard. Uses the slug resolution order above.
+
+```bash
+bagdock open
+bagdock open my-adapter
+```
+
+In JSON mode, returns the URL instead of opening the browser:
+
+```bash
+bagdock open --json
+# => {"url":"https://dashboard.bagdock.com/developer/apps/my-adapter","slug":"my-adapter"}
+```
+
+## `bagdock inspect [slug]`
+
+Shows deployment details for an app.
+
+```bash
+bagdock inspect
+bagdock inspect my-adapter --json
+```
+
+Displays:
+- Name, slug, ID
+- Type, category
+- Version, maintainer, visibility
+- Review status
+- Worker URL, namespace
+- Created, updated, published timestamps

package/skills/bagdock-cli/references/marketplace.md

@@ -0,0 +1,69 @@
+# Marketplace Submission Lifecycle
+
+The Bagdock marketplace uses a reviewed submission model. Developers submit, Bagdock reviews, then approves or rejects. `bagdock publish` is intentionally not a CLI command — final publication is handled by Bagdock staff.
+
+## Workflow
+
+1. `bagdock validate` — Run local checks before uploading
+2. `bagdock submit` — Upload bundle and request review (draft -> submitted)
+3. `bagdock submission list` — View all submissions
+4. `bagdock submission status <id>` — Check review progress
+5. `bagdock submission withdraw <id>` — Cancel before approval (submitted -> draft)
+
+## Commands
+
+### `bagdock validate`
+
+Local-only checks — no API call needed. Validates:
+
+- `bagdock.json` exists and parses
+- Required fields present (name, slug, version, type, category, main)
+- Type is `edge` or `app`
+- Entry point file exists
+- Bundle size under 10 MB
+
+```bash
+bagdock validate
+bagdock validate --json
+```
+
+Exit code 0 = pass/warn, 1 = fail.
+
+### `bagdock submission list`
+
+```bash
+bagdock submission list --app my-adapter
+bagdock submission list --json
+```
+
+### `bagdock submission status <id>`
+
+```bash
+bagdock submission status iadpv_abc123 --json
+```
+
+Returns: app name, version, review_status, type, visibility, change_reason, submitted_by, date.
+
+### `bagdock submission withdraw <id>`
+
+```bash
+bagdock submission withdraw iadpv_abc123
+```
+
+Only works when `review_status` is `submitted`. Returns the app to `draft` status so you can make changes and re-submit.
+
+## Status Values
+
+| Status | Meaning |
+|--------|---------|
+| `draft` | Not yet submitted |
+| `submitted` | Under review |
+| `approved` | Cleared for production |
+| `rejected` | Changes requested |
+
+## API Endpoints
+
+- `POST /v1/developer/apps/:slug/submit` — Submit
+- `GET /v1/developer/apps/:slug/submissions` — List
+- `GET /v1/developer/apps/:slug/submissions/:id` — Detail
+- `POST /v1/developer/apps/:slug/submissions/:id/withdraw` — Withdraw