@lunnoa/client 1.0.0 → 1.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lunnoa/client",
-  "version": "1.0.0",
+  "version": "1.2.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

@@ -54,8 +54,12 @@ Run these before inventing resources or shipping UI code:
    browser (SDK throws when `window` exists).
 2. **Codegen** — When building typed UIs, run
    `npx @lunnoa/client codegen` against the deployment first.
-3. **Discover before inventing** — `workflowApps.list()`, `agents.list`,
-   `workflows.list`, `entityTypes.list` (and `discovery.enabledFeatures()`).
+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|projects list`, `features`.
+   SDK equivalents: `workflowApps.list()`, `agents.list`, `workflows.list`,
+   `entityTypes.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
@@ -361,6 +365,18 @@ const result = await lunnoa.runs.start(ping);
 // or lunnoa.runs.startAndWait(ping)
 ```
 
+Discover the catalogue **before** writing `defineAction` (do not guess ids):
+
+```bash
+npx @lunnoa/client tools list --json --for-agent
+npx @lunnoa/client tools search email --json --for-agent
+npx @lunnoa/client tools get http_action_send-request --json
+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):
 
 ```bash
@@ -510,7 +526,7 @@ emails (capped; not Azure object IDs).
 3. Call `discovery.enabledFeatures()` and hide unsupported areas.
 4. Build forms/tables from `attributeSchema` / `customInputConfig` (or the generated types).
 5. Render workflow progress from `executionPath`; handle `NEEDS_INPUT` with `submitInput`.
-6. For single-action calls, use `actions.run`; for linear multi-step, use `runs.start` / `defineWorkflow`. Deploy with `npx @lunnoa/client workflows|agents deploy`. Discover catalogue via `workflowApps.list()`.
+6. For single-action calls, use `actions.run`; for linear multi-step, use `runs.start` / `defineWorkflow`. Deploy with `npx @lunnoa/client workflows|agents deploy`. Discover catalogue via `npx @lunnoa/client tools list|get|search` (or `workflowApps.list()`).
 7. For Request Approval nodes, use `approvals.inbox` / `approvals.decide` (or `executions.submitApproval`).
 8. Chat: stream via SSE, handle resume (reconnects) and stop, load history from the task.
 9. Handle `LunnoaApiError`: 401 → re-auth; 403 → hide the capability; 429 → back off.

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

@@ -63,8 +63,9 @@ interrogation.
 ### Integrations
 
 - Which external systems? Prefer existing catalogue apps (Slack, HTTP, CRM…).
-- Do not invent action ids. Implementation must call `workflowApps.list()`
-  (or codegen) to see what this API key can use.
+- Do not invent action ids. Implementation must discover the catalogue for
+  this API key (`npx @lunnoa/client tools list --json --for-agent`, then
+  `tools get <actionId> --json`, or `workflowApps.list()` / codegen).
 
 ### Auth for any custom UI
 
@@ -96,8 +97,9 @@ interrogation.
 2. **Connections stay on Lunnoa.** Definitions only reference connection ids
    (or omit for sole/default resolution). Never ask the partner to put OAuth
    secrets in their app.
-3. **Do not invent catalogue actions.** Discover with `workflowApps.list()` /
-   codegen. Client `defineAction` binds existing catalogue actions; toolkit
+3. **Do not invent catalogue actions.** Discover with
+   `npx @lunnoa/client tools list|get|search --json` (or `workflowApps.list()`
+   / codegen). Client `defineAction` binds existing catalogue actions; toolkit
    `createAction` is a different product (in-platform apps).
 4. **Durable vs ephemeral:** experiments → `runs.start`; shared production
    automation → CLI `workflows deploy` / `agents deploy` by slug.
@@ -131,8 +133,8 @@ can execute. Use this shape:
 - Notes: <CORS, BFF, project id, env vars>
 
 ### Discovery (run first)
-- [ ] workflowApps.list() — catalogue actions for tools/steps
-- [ ] agents.list / workflows.list / entityTypes.list — reuse before create
+- [ ] `npx @lunnoa/client tools list --json --for-agent` then `tools get <id>`
+- [ ] agents / workflows / entity-types / projects list — reuse before create
 - [ ] codegen — if building typed entity/workflow accessors
 
 ### Resources
@@ -175,7 +177,7 @@ continue in a coding turn with that skill loaded.
 action)? Need approvals? Existing HTTP/CRM connections?
 
 **You conclude (example):** Pattern A BFF; Agent `order-status` with tools
-`defineAction` for ERP lookup (after `workflowApps.list`) + optional
+`defineAction` for ERP lookup (after `tools list` / `tools get`) + optional
 workflow for staff notifications; UI = chat only; no agent schedule.
 
 **You produce** the build brief, then hand off.