@lunnoa/client 1.5.0 → 2.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lunnoa/client",
-  "version": "1.5.0",
+  "version": "2.0.0",
   "description": "TypeScript SDK for building applications on top of Lunnoa Automate — typed client for the Public API (agents, workflows, executions, entities, knowledge, queues), SSE agent chat streaming, and deployment-specific codegen",
   "type": "module",
   "main": "./dist/index.cjs",

package/skills/lunnoa-client/SKILL.md

@@ -57,14 +57,15 @@ Run these before inventing resources or shipping UI code:
 3. **Discover before inventing** — prefer the CLI (JSON for agents), then
    the SDK: `npx @lunnoa/client tools list --json --for-agent`,
    `tools get <actionId> --json`, `apps list`, `connections list`,
-   `agents|workflows|entity-types|tables|projects list`, `tables get <slugOrId>`,
+   `agents|workflows|entity-types|tables list`, `tables get <slugOrId>`,
    `features`.
    SDK equivalents: `workflowApps.list()`, `agents.list`, `workflows.list`,
    `entityTypes.list`, `tables.list`, `discovery.enabledFeatures()`.
    Do not invent catalogue action ids.
 4. **Run vs deploy** — Ad-hoc: `actions.run` / `runs.start` /
    `workflows.execute`. Durable shared automation: CLI
-   `npx @lunnoa/client workflows|agents deploy` (upsert by slug).
+   `npx @lunnoa/client workflows|agents deploy`. Upsert is by slug
+   inside the workspace on the API key. URL and API key are enough.
 5. **Toolkit boundary** — Client `defineAction` ≠ toolkit `createAction`.
 
 ---
@@ -319,7 +320,6 @@ const result = await lunnoa.actions.run({
   appId: 'http',
   actionId: 'http_action_send-request',
   // connectionId: '<Connection.id UUID>', // required if needsConnection + multiple
-  // projectId: '<project UUID>',          // required if multiple projects
   input: { method: 'GET', url: 'https://example.com' },
   name: 'Ping example',
 });
@@ -390,11 +390,11 @@ npx @lunnoa/client connections list --app gmail --json
 `tools get` returns `inputConfig` / `inputFields` and a `defineAction` sketch.
 `tools list` is compact; use `get` for the schema. `--json` is for coding agents.
 
-Deploy to Automate UI (upsert by slug; prefer CLI):
+Deploy to Automate UI (upsert by slug inside the workspace on the API key; prefer CLI):
 
 ```bash
-npx @lunnoa/client workflows deploy ./ping.ts --url … --api-key … --project-id …
-npx @lunnoa/client agents deploy ./triage.ts --url … --api-key … --project-id …
+npx @lunnoa/client workflows deploy ./ping.ts --url … --api-key …
+npx @lunnoa/client agents deploy ./triage.ts --url … --api-key …
 ```
 
 `defineAction` binds catalogue actions only. Toolkit `createAction` is a

package/skills/lunnoa-solution-design/SKILL.md

@@ -145,11 +145,11 @@ can execute. Use this shape:
 
 ### Auth
 - Pattern: A (server API key) | B (browser JWT)
-- Notes: <CORS, BFF, project id, env vars>
+- Notes: <CORS, BFF, env vars LUNNOA_URL and LUNNOA_API_KEY>
 
 ### Discovery (run first)
 - [ ] `npx @lunnoa/client tools list --json --for-agent` then `tools get <id>`
-- [ ] agents / workflows / entity-types / tables / projects list — reuse before create
+- [ ] agents / workflows / entity-types / tables list — reuse before create
 - [ ] codegen — if building typed entity/workflow accessors
 
 ### Resources (every row says REUSED or CREATED)