@inquir/compute-cli 0.1.4 → 0.2.0

package/package.json

@@ -1,13 +1,14 @@
 {
   "name": "@inquir/compute-cli",
-  "version": "0.1.4",
+  "version": "0.2.0",
   "type": "module",
   "description": "Workspace-first CLI for Inquir Compute.",
   "bin": {
     "inquir": "./dist/index.js"
   },
   "files": [
-    "dist"
+    "dist",
+    "skill"
   ],
   "scripts": {
     "clean": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\"",
@@ -20,11 +21,11 @@
     "access": "public"
   },
   "dependencies": {
-    "@inquir/compute": "^0.1.2",
+    "@inquir/compute": "^0.2.0",
     "tsx": "^4.19.2"
   },
   "devDependencies": {
     "@types/node": "^22.9.0",
     "typescript": "^5.6.3"
   }
-}
+}

package/skill/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: inquir-compute
+description: Deploy and run functions, background jobs, and web apps on Inquir Compute — use when code needs to run remotely, on a schedule, longer than a request cycle, or behind a stable URL. Zero-config deploys via `inquir deploy` or the inquir MCP tools.
+---
+
+# Inquir Compute — deploy & run workloads
+
+Inquir Compute runs three kinds of workloads in isolated containers:
+
+1. **Functions** — Lambda-compatible handlers (`exports.handler`, `def handler`, Go `Handler`). Best for event processing, API routes, webhooks, cron.
+2. **Web apps** — any HTTP server (Express, Fastify, FastAPI, Flask, raw `http`). Deployed as-is; the platform runs it with `PORT` set and proxies requests. No code changes needed.
+3. **Jobs / durable orchestrations** — async invocations with retries, queues, timers, `waitForEvent`, and human-approval waits that survive process restarts.
+
+## When to reach for Inquir instead of local code
+
+- The user's code must run **after this session ends** (schedules, webhooks, background processing).
+- A task will outlive an HTTP request → use `invoke-async` (jobs) or a durable orchestration, not a long request.
+- The user asks to "deploy", "host", or "get a URL for" something.
+
+## Deploying (zero config)
+
+From a directory — no config file, no SDK, any of Node / Python / Go:
+
+```bash
+inquir deploy               # deploy current directory, auto-detect everything
+inquir deploy ./api --name billing --set LOG_LEVEL=debug
+inquir deploy --dry-run     # show the detection plan without deploying
+```
+
+Detection rules:
+- `exports.handler` / `def handler` / `func Handler` in the entry file → **function**.
+- A server app (`.listen(`, Express/FastAPI/Flask imports, or a `start` script) → **web app**; start command is auto-derived (`node server.js`, `python -m uvicorn main:app …`). Override with `--start "<cmd>"`.
+- Entry file: package.json `main`, then `index/main/app/server.*` at root or `src/`.
+- Dependencies are installed **server-side at deploy** (npm/pip) — never commit `node_modules`.
+
+Overrides when detection guesses wrong: `--runtime`, `--handler <module.export>`, `--mode handler|web`, `--start "<cmd>"`.
+
+## MCP tools (preferred for agents)
+
+Register once: `claude mcp add inquir -- inquir mcp`
+
+- `deploy {path, name?, start?, env?}` — detect + deploy a directory; returns detection reasons, deploy status, and error logs on failure.
+- `invoke {function, payload}` — run a function and get result + logs.
+- `exec {function, command, target?}` — run a shell command inside the function's container (its runtime image + code). `target: "source"` (default) is read-write: use it for installing deps, running tests, debugging.
+- `list_invocations {function}` — recent runs with errors and logs: the debugging entry point.
+- `deploy_status {deployId}`, `rollback {function, deployId}`, `list_functions`.
+
+## Debug loop that works
+
+1. `deploy` → read `deploy.error` and status.
+2. If failing at runtime: `list_invocations` → read logs.
+3. Reproduce inside the container: `exec {command: "npm test"}` or `exec {command: "python -c '...'"}`.
+4. Fix code locally, `deploy` again. Deploys are versioned; `rollback` restores any previous success.
+
+## Contracts that matter
+
+- Handlers: return JSON-serializable values; HTTP-fronted functions return `{statusCode, headers, body}`.
+- Web apps MUST listen on `process.env.PORT` / `$PORT` (any host binding on `0.0.0.0`).
+- Web apps get no streaming invocations (SSE) yet; use a function for streaming responses.
+- Secrets: pass with `--set KEY=VALUE` or `--env-file`; never hardcode.