@oomol-lab/open-flow 0.1.0-beta.60 → 0.1.0-beta.62

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oomol-lab/open-flow",
-  "version": "0.1.0-beta.60",
+  "version": "0.1.0-beta.62",
   "description": "TypeScript contracts and Browser runtime for Open Flow.",
   "license": "Apache-2.0",
   "repository": {
@@ -10,6 +10,10 @@
   },
   "types": "./dist/index.d.ts",
   "exports": {
+    "./command": {
+      "types": "./dist/command/index.d.ts",
+      "import": "./dist/command/index.js"
+    },
     "./package.json": "./package.json",
     "./skills/open-flow/SKILL.md": "./skills/open-flow/SKILL.md",
     "./skills/open-flow/references/flow-authoring.md": "./skills/open-flow/references/flow-authoring.md",

package/skills/open-flow/SKILL.md

@@ -9,7 +9,8 @@ Use `<!-- agentic:var flowCommand -->` to operate the selected deployment.
 Consult the references relevant to the task:
 
 - [Flow capabilities and examples](references/flow-authoring.md): inspect, edit,
-  connect, validate, run and publish; concurrency and Run diagnostics.
+  connect, validate, run and publish; online entries and Flow enable/disable;
+  concurrency and Run diagnostics.
 - [n8n conversion](references/flow-n8n-conversion.md): represent collections,
   branches, provider operations and state while preserving source behavior.
 
@@ -28,5 +29,8 @@ Server; do not duplicate them in the CLI.
 <!-- agentic:endif -->
 
 Keep the requested boundary: editing a Draft does not authorize a Run,
-publication, or enabling automatic execution. Report the resulting Flow and
-Revision, verification result, and any unresolved configuration.
+publication, or enabling automatic execution. Inspecting an entry does not
+by itself authorize invoking it. For edits, report the Flow and Revision,
+verification result, and unresolved configuration. For a publication, report
+the Publication and available online entries. For a query, report the observed
+online state.

package/skills/open-flow/references/flow-authoring.md

@@ -28,6 +28,7 @@ supplies the edit operations. Use these when a configuration is unfamiliar.
 <!-- agentic:var flowCommand --> list --json
 <!-- agentic:var flowCommand --> create "Order summary" --json
 <!-- agentic:var flowCommand --> show FLOW_ID --json
+<!-- agentic:var flowCommand --> live FLOW_ID --json
 <!-- agentic:var flowCommand --> read FLOW_ID --json
 <!-- agentic:var flowCommand --> search FLOW_ID --input '{"query":"Customer summary","type":"agent"}' --json
 <!-- agentic:var flowCommand --> read FLOW_ID --input '{"revision":"REVISION","nodes":["NODE"]}' --json
@@ -35,7 +36,10 @@ supplies the edit operations. Use these when a configuration is unfamiliar.
 ```
 
 A known Flow ID avoids a list lookup. `show` gives lifecycle and publication
-state. `read` gives a graph outline, selected node details, or a text excerpt;
+state. `live` gives the current published version, enablement, and online entries,
+including Webhook URLs and request fields. `resourceReferences.draft` in Flow
+metadata describes Draft dependencies, not online resources. `read` defaults to
+the Draft and gives a graph outline, selected node details, or a text excerpt;
 `nodes` and `text` are alternative modes. `search` finds matches in names,
 configuration and source text, optionally restricted by node type.
 
@@ -326,6 +330,7 @@ large results without requiring the whole value in one response.
 ```bash
 <!-- agentic:var flowCommand --> publish FLOW_ID --expected-revision REVISION --expected-publication PUBLICATION_OR_NONE --idempotency-key PUBLISH_KEY --json
 <!-- agentic:var flowCommand --> enable FLOW_ID --expected-publication PUBLICATION --json
+<!-- agentic:var flowCommand --> disable FLOW_ID --expected-publication PUBLICATION --json
 <!-- agentic:var flowCommand --> workbench FLOW_ID --json
 <!-- agentic:var flowCommand --> open FLOW_ID
 ```
@@ -334,10 +339,35 @@ large results without requiring the whole value in one response.
 are for a requested release or automatic execution, and are unnecessary for a
 Draft test Run. `publications wait` follows an accepted pending publication.
 
+Flow is the only manual enable/disable unit: its switch controls all current Live
+Triggers together. Individual Triggers have no pause/resume operation. Disabling
+a Flow blocks new production admission without cancelling already accepted Runs.
+Use the observed Live publication ID for `--expected-publication`; if it changed,
+read the current state before deciding whether to apply the switch to that version.
+The MCP equivalent is `flow_set_enabled({ flowId, expectedPublicationId, enabled })`.
+
+Successful `publish` includes the same `live` details as `live FLOW_ID --json`;
+use that result without immediately querying again. Query `live` after waiting
+for an asynchronous publication, when details are missing, or when current state
+is needed later. An unpublished Flow returns `status: not-published` with no entries.
+
+For an authorized Webhook call, use the entry's `binding.endpointUrl`,
+`config.method`, and `config.body` field contracts. These retain schema,
+nullable and default semantics; methods without a request body have no body
+fields. Do not reconstruct URLs from node IDs. Flow `enabled` and `status` are
+independent of a binding's `health` and `listener`; a healthy
+subscription alone does not establish that automatic execution is enabled.
+Shared event source and account references can be inspected through their own
+commands when relevant.
+
 `workbench` returns a URL; `open` opens the system browser. Browser authentication
 belongs to the host. An open Workbench receives Revision notifications, so a CLI
 edit does not require a page reload.
 
+`live` includes Manual entry nodes without a runtime binding. `trigger search`
+and `trigger show` discover provider definitions; `live` inspects the Flow's
+current online entries. The MCP equivalent is `flow_live({ flowId })`.
+
 ## Recover without losing another change or repeating an effect
 
 - **Revision conflict:** another writer changed the Draft. Read the latest
@@ -348,6 +378,12 @@ edit does not require a page reload.
   resolve that uncertainty; a new key describes a new mutation.
 - **Saved with diagnostics:** the edit happened. Repair the saved Revision or
   investigate unavailable validation; resubmitting it is not a validation step.
+- **Published with detail warnings:** a succeeded `operation` confirms the
+  publication even if metadata or online details could not be read. Query `live`
+  rather than publishing again to retrieve an address. A pending operation still
+  requires observing that same operation. If `live.publication.publicationId`
+  differs from the successful operation's `publicationId`, the entries describe
+  the current Live version, not the earlier publication.
 - **Failed Run:** events and results identify the failing node and available
   inputs. Consider already-completed external effects before running it again.