@orchestraworks/cli 0.3.0 → 0.5.0

package/node_modules/@orchestraworks/client/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orchestraworks/client",
-  "version": "0.3.0",
+  "version": "0.5.0",
   "description": "Orchestra public API TypeScript client",
   "author": "Living Computers",
   "repository": {

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@orchestraworks/cli",
-  "version": "0.3.0",
+  "version": "0.5.0",
   "type": "module",
-  "description": "Orchestra: the orchestra CLI, and the FDK construct library for declaring a factory as code",
+  "description": "The Orchestra command line.",
   "license": "Apache-2.0",
   "author": "Living Computers",
   "homepage": "https://orchestraworks.ai",
@@ -17,7 +17,8 @@
     "dist",
     "skills",
     "templates",
-    "README.md"
+    "README.md",
+    "docs/REFERENCE.md"
   ],
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -108,17 +109,15 @@
   },
   "dependencies": {
     "@agentclientprotocol/sdk": "1.3.0",
-    "@orchestraworks/client": "0.3.0",
-    "@orchestraworks/worker": "0.0.134",
-    "@orchestraworks/workflow-render": "0.3.0",
+    "@orchestraworks/client": "0.5.0",
+    "@orchestraworks/worker": "0.0.136",
     "commander": "^14.0.0",
     "liquidjs": "^10.28.0"
   },
   "optionalDependencies": {
-    "@orchestraworks/local": "0.0.134"
+    "@orchestraworks/local": "0.0.136"
   },
   "bundleDependencies": [
-    "@orchestraworks/workflow-render",
     "@orchestraworks/client"
   ],
   "devDependencies": {

package/skills/orchestra/SKILL.md

@@ -477,7 +477,9 @@ verbs; --output json; --body @file.json; --file; values masked; approval default
 auth.ts:1-45 (ORCHESTRA_API_TOKEN, then the login profile, then the machine's edge; default address
 api.orchestraworks.ai; ORCHESTRA_BASE_URL), cli/src/cli/core/profile.ts:39-52 (profiles in
 ~/.config/orchestra/config.json, "default"), cli/src/cli/core/invocation.ts:19 (--profile),
-cli/src/generated/cli-commands.json ("me get"). -->
+cli/src/generated/cli-commands.json ("me get"; each command's answer), cli/src/cli/core/output.ts:94-113 and
+:143-145 (json prints the answer as it is), cli/src/cli/core/errors.ts:287-296 and :366-370 (the json error, on
+stderr), cli/src/cli/core/login.ts:361-363 (a pasted token keeps no refresh token). -->
 
 The `orchestra` command does two jobs. *Factory as code* (section 15) is where change happens. *Platform commands*
 read and probe what exists: observe with commands, change in code.
@@ -487,19 +489,43 @@ read and probe what exists: observe with commands, change in code.
   `delete`. Commands keep their own verb, such as `work-items assign`, `work-items move` and
   `sessions interrupt`. `orchestra sessions wait <session id>` waits for a turn to end. `orchestra <noun> --help` lists a noun's
   verbs and flags.
-- **Output.** `--output json` on every platform command. The default is a table for people.
+- **Output.** `--output json` on every platform command. The default is a table for people. JSON mode prints
+  the API's answer as it is on stdout, with key values masked. Read the field you need from its place:
+  - A list answers a page: `{"data":[…],"page":1,"limit":20,"total":42}`. The rows are in `data`. This is
+    true for every `list` verb, and for list verbs with another name, such as `sessions list-items`.
+  - `get`, `update` and most `create` verbs answer the resource itself: `{"id":"…",…}`.
+  - Some verbs wrap the resource with what came with it. `sessions start` answers
+    `{"session":{…},"firstItem":{…}}`, so the session id is `.session.id`. `sessions append-item` answers
+    `{"item":{…},"turnState":"…"}`, and `sessions interrupt` answers `{"session":{…},"withdrawnItems":[…]}`.
+  - A create that shows a key once answers the resource beside the key, such as `gateway-keys create`,
+    `{"gatewayKey":{…},"token":"…"}`. `files create` answers `{"file":{…},"upload":{…}}`.
+  - `orchestra sessions wait` prints the session itself, as `sessions get` does. A delete prints `null`.
+  - An error prints `{"status":404,"message":"…"}` on stderr, and the command exits non-zero.
 - **Input.** `--body @file.json` sends a full request body. `--file <path>` uploads bytes on `files create`.
 - **Values.** Key values in answers print masked.
 - **Approval.** A platform command asks first only for key values and access changes.
   `--require-approval never` skips the question, only after the person approved.
 - **Sign-in.** `orchestra auth login --org <organization>` signs in through the browser and saves a *profile* in
   `~/.config/orchestra/config.json`. `--no-browser` asks for an API token at a hidden prompt instead. `--profile
-  <name>` picks another saved profile. It signs in to `https://api.orchestraworks.ai` unless  `ORCHESTRA_BASE_URL` or `--base-url` says otherwise.
+  <name>` picks another saved profile. It signs in to `https://api.orchestraworks.ai` unless `ORCHESTRA_BASE_URL`
+  or `--base-url` says otherwise. The browser sign-in renews itself. A token typed at the `--no-browser`
+  prompt cannot renew itself, so it suits a short run only.
 - **Who am I.** `orchestra me get` shows the signed-in user, and `orchestra organizations list` the organization.
 - **Scripts.** `ORCHESTRA_API_TOKEN` and `ORCHESTRA_BASE_URL` in the shell are used before the profile. On an
   Orchestra machine, the network edge signs the agent's calls, so it needs no token.
 - **Fallback.** `orchestra api <METHOD> </path>` makes a raw call when a typed command is missing.
 
+A first look at an organization, in the order a new reader runs it:
+
+```bash
+orchestra auth login --org <organization>
+orchestra me get
+orchestra agents list --output json
+orchestra work-items list --output json
+orchestra sessions wait <session id>
+orchestra api GET /agents
+```
+
 **Writes outside the code.** A write command on something the code declares warns: the next apply sets it back.
 
 ## 17. Connections

package/skills/orchestra-fdk/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: orchestra-fdk
-description: Use when building and applying an Orchestra factory with the factory development kit for a developer's codebase - installing the kit, signing in, writing the engineering-team starter, explaining its plan, the first apply without tokens, proving the machines locally first and applying them, the "Set up" item that runs the repository from a git bundle, the role grant, then connecting the code host and the tracker, and starting Study. Reads the orchestra skill for the platform's ideas and references/environment.md for the machines.
+description: Use when building and applying an Orchestra factory with the factory development kit for a developer's codebase - installing the kit, signing in, the bug-fix fast path (one agent, one bug, a pull request), writing the engineering-team starter, explaining its plan, the first apply without tokens, proving the machines locally first and applying them, the "Set up" item that runs the repository from a git bundle, the role grant, then connecting the code host and the tracker, and starting Study. Reads the orchestra skill for the platform's ideas and references/environment.md for the machines.
 ---
 
 # Build and apply an Orchestra factory
@@ -17,6 +17,57 @@ folder. Use it to answer a case the steps do not cover, and never promise one of
 Ask questions with your question tool: `AskUserQuestion` in Claude Code, its counterpart in Codex. Ask one
 thing at a time. Never ask the developer to paste a token into the chat.
 
+## The bug-fix fast path
+
+`orchestra fdk init` without `--template` writes the bug-fix starter: one agent that takes a bug as its
+first message and answers with a pull request and a report. Take this path when the developer wants one bug
+fixed in a GitHub repository. Do steps 1 and 2 below first. Then:
+
+1. Make a new folder beside the codebase, `<codebase>/../orchestra-factory`, called `<factory>`. In it, run
+   `npm init -y`, then `npm install @orchestraworks/cli`.
+2. Write the starter. `<owner>/<name>` is the GitHub repository. Add `--model-key anthropic` or
+   `--model-key openai` only when the organization brings its own model key.
+
+   ```bash
+   npx orchestra fdk init --repository <owner>/<name>
+   ```
+
+3. Run `npm install`, then `npm run typecheck`. Both must pass.
+4. Fill in `<factory>/skills/codebase/SKILL.md` with how the codebase installs, tests and starts, and the
+   services it needs. When the codebase has an `AGENTS.md` or `CLAUDE.md`, write one line naming it instead.
+5. Set the shell inputs. `main.ts` reads them, and `init` printed each with what it is. They come with the
+   hand-over note: `ORCHESTRA_FDK_IMAGE_REPOSITORY`, `ORCHESTRA_FDK_RUNTIME_IMAGE`,
+   `ORCHESTRA_FDK_MODEL_GATEWAY_HOST`, `ORCHESTRA_FDK_IMAGE_PULL_ACCESS_KEY_ID` and
+   `ORCHESTRA_FDK_IMAGE_PULL_SECRET_ACCESS_KEY`, plus `ORCHESTRA_FDK_ANTHROPIC_API_KEY` or
+   `ORCHESTRA_FDK_OPENAI_API_KEY` with `--model-key`. Ask the developer to write them into a file only they
+   can read, as in step 9, and load it in each command that runs `orchestra`:
+   `set -a; . ~/.config/orchestra/fdk-inputs.env; set +a`. Docker on this computer must also be signed in
+   to the image registry, with the details in the same note.
+6. Run `npx orchestra fdk diff` and show the developer the change list. On their yes, run
+   `npx orchestra fdk apply --require-approval never`. It builds and pushes the image, then prints a GitHub
+   App install link and waits until the developer installs the app. Give them the link.
+7. Send the bug. The agent's id is `<factory name>-bugfix`, where the factory name is the one `init` printed:
+
+   ```bash
+   npx orchestra sessions start --agent-id <factory name>-bugfix --content "<the bug, in the reporter's words>" --output json
+   ```
+
+   The answer is `{"session":{…},"firstItem":{…}}`. The session id is `.session.id`.
+8. Wait for the turn to end, in the foreground, with one blocking command:
+
+   ```bash
+   npx orchestra sessions wait <session id> --timeout 540
+   ```
+
+   Do not start the wait in the background and end your turn. A headless agent exits when its turn ends,
+   and the waiting command goes with it. `--timeout 540` ends the wait before a ten-minute command limit.
+   When it times out, it prints the session's last status and exits non-zero: run the same command again.
+9. `sessions wait` shows no progress. To see what the agent did, read the conversation's items:
+   `npx orchestra sessions list-items <session id> --output json`. The rows are in `data`. The developer
+   can watch the same session live in the console at `https://app.orchestraworks.ai`.
+
+**Check:** the session's status is `COMPLETE`, and its last message names the pull request and the report.
+
 ## The steps
 
 Do them in order. Each step ends with a check. Do not go on until the check passes.
@@ -42,12 +93,15 @@ After the first apply, the steps follow the Onboarding order:
 
 ### 1. Install the kit
 
-The kit is the `orchestra` command and the library the factory code imports. You installed it globally
-with `npm install -g @orchestraworks/cli` before this skill was linked. `npm update -g @orchestraworks/cli`
-keeps it and its skills current.
+The kit is the `orchestra` command and the library the factory code imports. It was installed before this
+skill was linked, in one of two places. Keep it and its skills current with the command that matches:
+
+- Globally, with `npm install -g @orchestraworks/cli`. Update it with `npm update -g @orchestraworks/cli`.
+- In the factory folder, with `npm install @orchestraworks/cli` there. Update it with
+  `npm update @orchestraworks/cli`, run in that folder. Run the command there as `npx orchestra`.
 
 1. Find the developer's codebase folder. Call it `<codebase>`.
-2. Run `orchestra --help`.
+2. Run `orchestra --help`, or `npx orchestra --help` in the factory folder.
 
 **Check:** `orchestra --help` prints the command list, and `orchestra fdk init --help` lists `--template`.
 Node 22 or later is needed.
@@ -65,10 +119,14 @@ a building block this skill does not cover.
    ```
 
    `<organization>` is the organization name from the hand-over note. The CLI opens the browser and waits
-   for the answer on a local port of this computer. It signs in to `https://api.orchestraworks.ai` unless   `ORCHESTRA_BASE_URL` or `--base-url` says otherwise. Its first line names the address.
-3. If the browser cannot open on this computer, use `orchestra auth login --no-browser --org <organization>`.
-   It asks for an API token at a hidden prompt. The developer creates the token in the console at
-   `https://console.orchestraworks.ai` and types it into the terminal themselves.
+   for the answer on a local port of this computer, so the browser must run on this same computer. It
+   signs in to `https://api.orchestraworks.ai` unless `ORCHESTRA_BASE_URL` or `--base-url` says otherwise.
+   Its first line names the address. This sign-in renews itself, so a long run stays signed in.
+3. Use this browser sign-in. `orchestra auth login --no-browser` asks for a token at a hidden prompt
+   instead, and a typed token cannot renew itself: it stops working when it expires. Use it only for a short
+   run, with a token someone hands the developer. Users cannot create their own API keys in the console
+   yet; that is coming. If no browser can open on this computer, tell the developer, and ask them to run
+   you on a computer where one can.
 4. Read the two lines the login prints: `Signed in as <email>.` and
    `Logged in to organization <id> (<slug>).` Tell the developer both. Note the organization id.
 
@@ -245,7 +303,7 @@ computer.
    the Manager Agent's conversation on the item.
 6. Watch it: `npx orchestra work-items get <id> --output json` lists the item's `sessions`. Run
    `npx orchestra sessions wait <session id> --timeout 3600`. The developer can watch the same session in the console at
-   `https://console.orchestraworks.ai`.
+   `https://app.orchestraworks.ai`.
 7. When it ends, read the agent's report with the developer. Fix a failed step in the environment: go back
    to `references/environment.md`, prove the fix on this computer, apply it as in step 6, then assign the
    item again to wake the agent.

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,9 +46,9 @@ 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
+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 on credits 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.
@@ -150,7 +150,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 +497,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 +1011,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/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.