@orchestraworks/cli 0.3.0 → 0.5.1

package/skills/orchestra-fdk/references/authoring.md

@@ -6,11 +6,11 @@ deterministic, value-free plan; `apply` reconciles that plan against the platfor
 last-writer-wins on the fields you manage. Nothing in the platform is edited by hand — the code is
 the source of truth, and every byte of the plan traces to a line someone wrote.
 
-Read the kit's README for the full reference — it ships inside the installed package. This file is
-`skills/orchestra-fdk/references/authoring.md` inside that package, so the README always sits exactly two
-directories above the `orchestra-fdk` skill folder. Select whichever Claude Code link exists for this
+Read the kit's full reference, `docs/REFERENCE.md` — it ships inside the installed package. This file is
+`skills/orchestra-fdk/references/authoring.md` inside that package, so the package root always sits exactly
+two directories above the `orchestra-fdk` skill folder. Select whichever Claude Code link exists for this
 scope, resolve it, then go up two —
-`skill_link=.claude/skills/orchestra-fdk; [ -e "$skill_link" ] || skill_link=~/.claude/skills/orchestra-fdk; cat "$(realpath "$skill_link")/../../README.md"`
+`skill_link=.claude/skills/orchestra-fdk; [ -e "$skill_link" ] || skill_link=~/.claude/skills/orchestra-fdk; cat "$(realpath "$skill_link")/../../docs/REFERENCE.md"`
 (use `.agents/skills/orchestra-fdk` and `~/.agents/skills/orchestra-fdk` for Codex). Do not guess a path under
 `node_modules`; with workspace hoisting the package is not beneath your factory directory. This skill
 teaches *how to author* — the shape of a factory, the construct model, the loop you run, and the six
@@ -46,10 +46,10 @@ fails with `ERR_PACKAGE_PATH_NOT_EXPORTED`.
 orchestra fdk init --repository acme/shop
 ```
 
-writes a bug-fix factory for that GitHub repository: `fdk.json`, `main.ts`, the machine image under
-`image/`, the agent's standing instructions and an empty codebase skill. It sets `"type": "module"` and
-adds `tsx` in `package.json`. `--model-key anthropic` or `--model-key openai` adds the organization's own
-model key; without it the agent runs on credits through the model gateway. It touches no platform and
+writes a bug-fix factory for that GitHub repository: `fdk.json`, `tsconfig.json`, `main.ts`, the machine
+image under `image/`, the agent's standing instructions and an empty codebase skill. In `package.json` it
+sets `"type": "module"`, adds a `typecheck` script, and adds `tsx`, `typescript` and `@types/node`. `--model-key anthropic` or `--model-key openai` adds the organization's own
+model key; without it the agent runs through the model gateway. It touches no platform and
 overwrites nothing. **Setting up a factory for a codebase is the `orchestra-fdk` skill's job**: the fast
 path from `orchestra fdk init` to a first fix, and the traps on the way.
 
@@ -103,6 +103,17 @@ entrypoint decides what answers. Omit `harness`, or misspell it, and synth fails
 a message naming the five; there is no default, because guessing which one an author meant would pick a
 different program than the one they wanted.
 
+### Platform skills are attached by id
+
+An agent uses a platform skill only when its `skills` list names it: `Skill.fromId(factory, "skill_<key>")`
+in the kit, or `skillIds` on the API. Not released yet: managed skills that the kit and the create request
+add by default (`includeManagedSkills`).
+
+### Not released yet: an environment's working folder, `workingDirectory`
+
+Today the harness starts outside the code. The agent clones or uses its code under `/work` in its own first
+turn, as the starter's agents do.
+
 ### Identity comes from the construct path
 
 With no explicit `slug`, a resource's slug is the **factory name + full construct path**,
@@ -150,7 +161,7 @@ Importers resolve at apply and are never created or mutated:
 Secret.fromSlug(factory, "shared-openai-key");
 Agent.fromSlug(factory, "existing-agent");
 Skill.fromSlug(factory, "skill_zendesk");
-Connection.fromEnv(factory, "SFDK_ZENDESK_CONNECTION_ID", { provider: Providers.Zendesk });
+Connection.fromEnv(factory, "ORCHESTRA_FDK_ZENDESK_CONNECTION_ID", { provider: Providers.Zendesk });
 ```
 
 Prefer `Connection.fromEnv` over `fromId` whenever the plan is committed: it resolves the id from
@@ -497,7 +508,7 @@ on a person's Claude subscription token rather than an API key:
 
 ```ts
 const claudeSignIn = new Secret(factory, "claude-sign-in", {
-  value: SecretValue.fromEnv("SFDK_CLAUDE_CODE_OAUTH_TOKEN"),
+  value: SecretValue.fromEnv("ORCHESTRA_FDK_CLAUDE_CODE_OAUTH_TOKEN"),
   injection: {
     headers: [{ name: "authorization", value: "Bearer ${secret}" }],
     removeHeaders: ["x-api-key"], // stripped before injection
@@ -1011,15 +1022,15 @@ orchestra skills install --harness claude --scope user
 
 `--harness` is `claude`, `codex` or `both`, and `--scope` is `user` or, for a kit installed in this
 project, `project`; both are required. It **links** — never copies — both skills from the running package
-into that harness's skills directory, each under its own name, so `npm update -g @orchestraworks/cli`
-keeps the teaching current. Then read each `SKILL.md` it prints: a harness loads a new skill only at its
+into that harness's skills directory, each under its own name, so updating the kit keeps the teaching current: `npm update -g @orchestraworks/cli`
+for a global install, or `npm update @orchestraworks/cli` in the folder that installed it. Then read each `SKILL.md` it prints: a harness loads a new skill only at its
 next start.
 
 ## Where to look next
 
-The kit's README — its full reference — sits two directories above this file inside the package.
-Select whichever Claude Code link exists for this scope, resolve it, then go up two:
-`skill_link=.claude/skills/orchestra-fdk; [ -e "$skill_link" ] || skill_link=~/.claude/skills/orchestra-fdk; cat "$(realpath "$skill_link")/../../README.md"`
+The kit's full reference is `docs/REFERENCE.md` at the root of the package, two directories above the
+`orchestra-fdk` skill folder. Select whichever Claude Code link exists for this scope, resolve it, then go up two:
+`skill_link=.claude/skills/orchestra-fdk; [ -e "$skill_link" ] || skill_link=~/.claude/skills/orchestra-fdk; cat "$(realpath "$skill_link")/../../docs/REFERENCE.md"`
 (use `.agents/skills/orchestra-fdk` and `~/.agents/skills/orchestra-fdk` for Codex). It ships inside the package, so it
 is already on disk in any project that has orchestra installed, wherever the install landed. Go there
 for what this skill states without unpacking: the complete egress rule shapes (`paths[]` scoping, several

package/skills/orchestra-fdk/references/environment.md

@@ -1,6 +1,7 @@
 # Port a codebase's setup to Orchestra machines
 
-Step 6 of the orchestra-fdk skill sends you here. When you finish, go back to that step.
+Step 8 of the orchestra-fdk skill, "Set up the machines", sends you here, and so does its step 3 for a new
+environment in an existing factory. When you finish, go back to the step that sent you.
 
 An agent can fix, test or show a codebase only if its machine can install and run it. You find out how
 this team sets up their code, prove it on this computer first, write it into the factory, and apply it.
@@ -10,9 +11,15 @@ An *environment* is the declared shape of a machine, and every machine an agent
 The orchestra skill, sections 4 to 6, explains environments, machines, network rules and secrets, and says what
 they cannot do yet. Read those sections before you choose a mode.
 
-In the engineering team template, every environment is built by `declareEnvironment` in
-`<factory>/lib/environment.ts`. You edit only the section marked `WHAT THE CODE NEEDS`, and the end of
-`<factory>/lib/setup.sh`, unless the chosen path needs more.
+Where you edit depends on the starter:
+
+- *Engineering-team starter:* every environment is built by `declareEnvironment` in
+  `<factory>/lib/environment.ts`. You edit only the section marked `WHAT THE CODE NEEDS`, and the end of
+  `<factory>/lib/setup.sh`, unless the chosen path needs more.
+- *Bug-fix starter:* each environment is a `new Environment` in `<factory>/main.ts`. Its setup script is
+  `<factory>/image/setup.sh`, and its image is built from `<factory>/image/Dockerfile`.
+
+Below, *the setup script* and *the environment code* mean these files for your starter.
 
 ## 1. Find the sources
 
@@ -74,7 +81,7 @@ the computer's own operating system picks among them.
 
 Even when rows 1 and 2 do not work, a Linux full VM is the preferred cloud machine, on a Mac or Windows
 computer too. Use a hosted Mac or a Windows full VM only when the project truly depends on that operating
-system, such as iOS or Xcode. A hosted Mac is a dedicated Apple machine, billed for a 24-hour minimum.
+system, such as iOS or Xcode. A hosted Mac is a dedicated Apple machine.
 Today Orchestra launches no Mac: path B says what works now.
 
 **Open: proving a Linux full VM locally on a Mac or Windows computer.** The host outpost there runs on
@@ -149,16 +156,16 @@ proves the agent works in the environment.
 
 ### The agent's model key, locally
 
-The local agent needs a model key. The developer picks one of three sources, in this order, and exports
+The local agent needs a model key. The developer uses one of three sources, the one they have, and exports
 it in the shell that starts `orchestra local`:
 
 1. **A local token from their own subscription,** such as the one `claude setup-token` prints for Claude
    Code.
 2. **An API key from the model provider.**
-3. **A model gateway key from Orchestra,** when neither of those is at hand. It is a separate key for local
-   work, such as `local-dev`, with a monthly cap. The developer creates it in the console at
-   **Settings > Gateway keys**, which shows the value once. The model gateway is a public service at
-   `models.orchestraworks.ai`, so the key works locally too. Usage is charged to the organization's credit.
+3. **A model gateway key from Orchestra.** It is a separate key for local work, such as `local-dev`, with a
+   monthly cap. The developer creates it in the console at **Settings › Gateway keys**, which shows the
+   value once. The model gateway is a public service at `models.orchestraworks.ai`, so the key works locally
+   too.
 
 **What each harness itself accepts:**
 
@@ -183,7 +190,7 @@ sign-in is reported by the Orchestra team and not yet verified in pi's docs.
 | `pi` | `ANTHROPIC_OAUTH_TOKEN` for Anthropic. OpenAI: not wired yet | Anthropic and OpenAI keys: not wired yet | `ANTHROPIC_OAUTH_TOKEN` (not proven yet) |
 | `script`, `custom` | No key needed | No key needed | No key needed |
 
-The path that works tonight is a `claude` agent with `CLAUDE_CODE_OAUTH_TOKEN`. Use it unless the agent
+The path that works today is a `claude` agent with `CLAUDE_CODE_OAUTH_TOKEN`. Use it unless the agent
 must run another harness.
 
 - **For a gateway key,** also export
@@ -222,9 +229,12 @@ the settings are stored as plain text and shown on every read.
 2. The two export lines point `orchestra` at this local run. Load them only into the commands meant for the
    run. Never load them into a command meant for Orchestra's cloud.
 3. Create the environment and an agent on the run with `npx orchestra environments create --body @<file>` and
-   `npx orchestra agents create --body @<file>`. Build each body from the `manager-work-lg` and `manager-agent`
-   entries in `<factory>/fdk.out/plan.json`. Keep the setup script from `<factory>/lib/setup.sh` in the
-   environment's body. The network rules may stay: the local environment does not enforce them. Set the
+   `npx orchestra agents create --body @<file>`. Build each body from the entries in
+   `<factory>/fdk.out/plan.json` for the environment you are proving and an agent on it. For a new
+   engineering-team factory, that is `manager-work-lg` and `manager-agent`. For a new environment in an
+   existing factory, it is the environment and the agent you added. Keep that environment's setup script in
+   its body: `<factory>/lib/setup.sh` or `<factory>/image/setup.sh`, as the top of this file says. The
+   network rules may stay: the local environment does not enforce them. Set the
    agent's model settings for the key source, as "The agent's model key, locally" says.
    `npx orchestra fdk apply` does not work against a run: it stops at the first thing the run does not serve.
 4. Cut a git bundle of the default branch outside the codebase:
@@ -240,7 +250,7 @@ the settings are stored as plain text and shown on every read.
    `orchestra local status` shows checks 1 and 2 (the machine started, and the harness opened its
    conversation).
 2. Find the machine's container with `docker ps`. Copy in the bundle with `docker cp`.
-3. Change the setup in `<factory>/lib/setup.sh`, so the script you prove is the script you apply. Then
+3. Change the setup in the setup script, so the script you prove is the script you apply. Then
    update the environment on the run and start a new machine.
    *Fallback until the local environment runs the setup script:* copy the script in with `docker cp` and run
    it as root yourself: `docker exec -u root <container> bash /tmp/setup.sh`.
@@ -308,10 +318,10 @@ The local key is never carried over. It stays on the developer's computer. In th
 Orchestra Secret, and our network edge adds it to each model call, so no machine and no person holds it:
 
 - For the gateway, `apply` creates the gateway key and its secret. The starter already declares them.
-- For a provider key, declare a Secret and a rule that adds it on the provider's host (orchestra skill,
-  sections 6 and 7).
+- For a subscription token or a provider key, declare a Secret and a rule that adds it on the provider's
+  host, as step 6 of the orchestra-fdk skill says (orchestra skill, sections 6 and 7).
 
-Ask the developer to revoke the `local-dev` gateway key, at **Settings > Gateway keys**, when local work is
+Ask the developer to revoke the `local-dev` gateway key, at **Settings › Gateway keys**, when local work is
 done.
 
 **Check:** milestones 1 and 2 pass and the agent turn completes in the chosen mode, or you know which one
@@ -346,6 +356,8 @@ agent can run the team's own `docker compose up` unchanged.
    32 CPU, md 16, sm 2.
 6. When the project runs containers, keep the disk at `/var/lib/docker`. The starter declares it. It keeps
    the inner Docker's images across machine starts (next part).
+7. Not released yet: `workingDirectory`, the folder where every conversation starts. Today each agent clones
+   or uses its code under `/work` in its own first turn, as the starter's agents do.
 
 #### Setup script or a baked image
 
@@ -404,23 +416,26 @@ Write down what is missing and stop here. Report it to the developer, and go bac
 
 ## 6. Write and check
 
-1. Edit `lib/environment.ts` for the chosen path.
+1. Edit the environment code for the chosen path: `lib/environment.ts` in the engineering-team starter,
+   `main.ts` and `image/` in the bug-fix starter.
 2. In `<factory>`, run `npm run typecheck`, then `npx orchestra fdk synth`. The starter is one program, at the folder's
    root.
 3. Read `<factory>/fdk.out/plan.json`. Every environment has your setup script, ports and settings, and
-   the `model-gateway` rule. No environment has a Bitbucket or Jira rule yet: those come with the tokens,
-   in step 10 of the orchestra-fdk skill.
+   the model rule from step 6 of the orchestra-fdk skill: the `model-gateway` rule,
+   or a Secret's rule on the provider's host. On a new factory, no environment has a Bitbucket or Jira rule
+   yet: those come with the tokens, in step 12 of the orchestra-fdk skill. On an existing factory, with its
+   inputs loaded, the rules it has now stay as they are.
 4. Write `ENVIRONMENT.md` in `<factory>`: what you found and where, the mode you proved in and its result
    for each success criterion, the commands, every outbound attempt the proof logged, and what is still
    unknown.
 
-**Check:** the typecheck and the synth pass, and the plan is as in item 3. Go back to step 6 of the
-orchestra-fdk skill for the apply.
+**Check:** the typecheck and the synth pass, and the plan is as in item 3. Go back to the orchestra-fdk
+step that sent you for the apply.
 
 ## 7. The cloud
 
 The cloud is the fallback when no local mode can run. It is also the confirmation after the local proof:
-the Manager Agent's "Set up" item, which step 7 of the orchestra-fdk skill starts. It proves what only the
+the Manager Agent's "Set up" item, which step 10 of the orchestra-fdk skill starts. It proves what only the
 cloud can: the micro VM, Docker, the network rules and the tokens. The Engineer Agents' machines cannot clone from
 Bitbucket, so the Set up item also proves the tests run from a git bundle.
 

package/templates/bug-fix/tsconfig.json

@@ -0,0 +1,12 @@
+{
+  "compilerOptions": {
+    "target": "ES2022",
+    "module": "NodeNext",
+    "moduleResolution": "NodeNext",
+    "strict": true,
+    "noEmit": true,
+    "skipLibCheck": true,
+    "types": ["node"]
+  },
+  "include": ["main.ts"]
+}

package/templates/engineering-team/lib/setup.sh

@@ -10,6 +10,7 @@
 #   15  building the certificate bundle that trusts the egress edge failed
 #   16  preparing the /work disk for the agent failed
 #   17  installing Playwright's Chromium failed, only when its block below is turned on
+#   18  installing the chosen Node version failed, only when its block below is turned on
 
 # In the cloud every HTTPS connection goes through the egress edge, which re-signs it with the authority at
 # SFDK_EGRESS_CA_FILE, so every step that downloads comes after this block. The worker has already added that
@@ -44,6 +45,21 @@ chown agent:agent /work || exit 16
 
 # ---- Add the team's system setup here: packages, language runtimes, tools. -----------------------------------
 
+# Optional, off by default: a Node major version other than the image's. To turn it on, remove the leading `# `
+# from the lines from NODE_MAJOR to `esac`, and set NODE_MAJOR. It replaces the image's Node in /usr/local. The
+# image's own npm and corepack go first: unpacking a second Node over them leaves a mix of two npm versions, and
+# every npm command then exits 1. Use this Node's own corepack for pnpm or yarn.
+# NODE_MAJOR=24
+# case "$(node --version 2>/dev/null)" in "v$NODE_MAJOR".*) ;; *)
+#   case "$(uname -m)" in aarch64 | arm64) node_arch=arm64 ;; *) node_arch=x64 ;; esac
+#   node_version=$(curl -fsSL --retry 3 https://nodejs.org/dist/index.json |
+#     sed -n "s/.*\"version\":\"\(v$NODE_MAJOR\.[0-9.]*\)\".*/\1/p" | head -n1)
+#   [ -n "$node_version" ] || exit 18
+#   rm -rf /usr/local/lib/node_modules/npm /usr/local/lib/node_modules/corepack
+#   curl -fsSL --retry 3 "https://nodejs.org/dist/$node_version/node-$node_version-linux-$node_arch.tar.xz" |
+#     tar -xJ -C /usr/local --strip-components=1 || exit 18
+# ;; esac
+
 # Optional, off by default: a headless Chromium, so an Engineer Agent can check a UI fix in a browser. To turn
 # it on, remove the leading `# ` from the two lines below. Name the Playwright version the repository uses, as
 # playwright@<version>, so the browser matches its tests. The first line installs the system libraries as root;

package/templates/engineering-team/package.json

@@ -9,7 +9,7 @@
     "typecheck": "tsc -p tsconfig.json"
   },
   "dependencies": {
-    "@orchestraworks/cli": "^0.3.0"
+    "@orchestraworks/cli": "^0.5.0"
   },
   "devDependencies": {
     "@types/node": "^22.10.0",

package/templates/todo-factory/package.json

@@ -9,7 +9,7 @@
     "typecheck": "tsc -p tsconfig.json"
   },
   "dependencies": {
-    "@orchestraworks/cli": "^0.2.0"
+    "@orchestraworks/cli": "^0.5.0"
   },
   "devDependencies": {
     "@types/node": "^22.10.0",

package/node_modules/@orchestraworks/workflow-render/LICENSE

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

package/node_modules/@orchestraworks/workflow-render/dist/constants.d.ts

@@ -1,98 +0,0 @@
-export declare const PAL: {
-    readonly ink: "#1a1d24";
-    readonly muted: "#5b6472";
-    readonly faint: "#7a8494";
-    readonly boxStroke: "#8b93a1";
-    readonly spineStroke: "#4f5b6b";
-    readonly edge: "#aab2bf";
-    readonly edgeSpine: "#4f5b6b";
-    readonly edgeFaint: "#d3d8e0";
-    readonly label: "#8b93a1";
-    readonly labelFaint: "#b0b7c3";
-    readonly laneProcessFill: "#f4f6fa";
-    readonly laneResultFill: "#eaeef5";
-    readonly bandStroke: "#dde2ea";
-    readonly phaseStroke: "#d7dde8";
-    readonly zoneFill: "#f3f4f7";
-    readonly zoneStroke: "#c6cdda";
-    readonly chipFill: "#f1f3f7";
-    readonly chipText: "#7a8494";
-    readonly innerRule: "#e2e6ee";
-    readonly white: "#ffffff";
-    readonly entryFill: "#f6f8fc";
-    readonly entryStroke: "#b4bdcc";
-    readonly entryMutedFill: "#f5f6f9";
-    readonly entryMutedStroke: "#c9d0dc";
-    readonly entryGlyph: "#79839a";
-    readonly entryGlyphMuted: "#a3abb9";
-    readonly entryDot: "#3f4a5a";
-    readonly barFill: "#e9ecf1";
-    readonly guardFill: "#eef4fd";
-    readonly guardStroke: "#7d9dcb";
-    readonly metaRule: "#b6bdc9";
-    readonly metaText: "#98a1b0";
-};
-export declare const ACCENTS: Record<string, {
-    stroke: string;
-    fill: string;
-    text: string;
-}>;
-export declare const GRAPH_FONT_FAMILY = "Helvetica, Arial, 'Liberation Sans', sans-serif";
-export declare const FS_NODE = 12.5;
-export declare const FS_EDGE = 10;
-export declare const FS_NOTE = 10;
-export declare const FS_ENTRY = 10.5;
-export declare const FS_ENTRY_SUB = 9;
-export declare const LH_ENTRY_SUB = 11.5;
-export declare const NODE_PAD = 12;
-export declare const NODE_MIN_W = 120;
-export declare const NODE_MAX_W = 200;
-export declare const PILL_PAD = 16;
-export declare const PILL_MIN_W = 62;
-export declare const PILL_H = 32;
-export declare const LINE_H = 15;
-export declare const BOX_R = 7;
-export declare const BAR_R = 5;
-export declare const PORT_PAD = 1;
-export declare const BAR_TALL_SPAN = 46;
-export declare const BAR_CAPTION_DROP = 18;
-export declare const CANVAS_MARGIN = 20;
-export declare const CORNER_R = 8;
-export declare const ENTRY_DOT_R = 4.5;
-export declare const ENTRY_DOT_GAP = 26;
-export declare const ENTRY_CARD_GAP = 44;
-export declare const ENTRY_STACK_GAP = 13;
-export declare const ENTRY_MIN_W = 118;
-export declare const ENTRY_MAX_W = 236;
-export declare const ENTRY_PAD_X = 9;
-export declare const ENTRY_PAD_Y = 8;
-export declare const ENTRY_GLYPH_W = 17;
-export declare const ENTRY_TIP = 9;
-export declare const ENTRY_CAPTION = "Steers the active run";
-export declare const GATE_MARK_SETBACK = 20;
-export declare const PARALLEL_CLEAR = 5;
-export declare const PARALLEL_MIN_RUN = 12;
-export declare const COINCIDENT_INK_MAX = 2;
-export declare const DETOUR_REPORT = 2.5;
-export declare const SPINE_SEARCH_EXPANSIONS = 4096;
-export declare const SPINE_DEPTH_CAP = 30;
-export declare const HANDLER_VERB_TEXT: Record<string, string>;
-export declare const EXCEPTIONAL_VERBS: ReadonlySet<string>;
-export declare const LAYOUT_LIMITS: {
-    readonly maxCellCoordinate: 4096;
-    readonly maxCellSpan: 256;
-    readonly maxCellArea: 1000000;
-    readonly maxNotes: 50;
-    readonly maxNoteTextChars: 200;
-    readonly maxSerializedBytes: number;
-    readonly maxNodeReferences: 500;
-};
-export declare const LAYERS: readonly ["edge", "node", "label"];
-export type Layer = (typeof LAYERS)[number];
-export declare const RING_INSET = 3.5;
-export declare const RING_OUTER_W = 1.4;
-export declare const RING_INNER_W = 1.2;
-export declare const RING_INNER_OPACITY = 0.55;
-export declare const GATE_BAR_LEN = 10;
-export declare const GATE_BAR_GAP = 5;
-export declare const GATE_BAR_W = 1.6;

package/node_modules/@orchestraworks/workflow-render/dist/context.d.ts

@@ -1,37 +0,0 @@
-import type { RenderContext } from "./types.js";
-export interface TriggerRowLike {
-    id?: string;
-    slug?: string;
-    status?: string | null;
-    expiresAt?: string | Date | null;
-    on?: {
-        connection?: string | null;
-        events?: readonly string[] | null;
-        schedule?: string | null;
-    } | null;
-    where?: readonly FilterNodeLike[] | null;
-    target?: {
-        onMissing?: string | null;
-        binding?: string | null;
-    } | null;
-}
-export interface FilterConditionLike {
-    field?: string | null;
-    op?: string | null;
-    value?: unknown;
-}
-export type FilterNodeLike = FilterConditionLike | {
-    all: readonly FilterNodeLike[];
-} | {
-    any: readonly FilterNodeLike[];
-} | {
-    not: FilterNodeLike;
-};
-export interface ClassifyOptions {
-    now?: Date;
-}
-export declare function renderFilter(node: FilterNodeLike, nested?: boolean): string | null;
-export declare function humanizeCron(cron: string | null | undefined): string | null;
-export declare function isRuntimeLiveTrigger(row: TriggerRowLike, now?: Date): boolean;
-export declare function classifyTriggerContext(rows: readonly TriggerRowLike[], options?: ClassifyOptions): RenderContext;
-export declare function hasStartCapableTrigger(context: RenderContext | null | undefined): boolean;