@foldrun/core 2.11.1 → 2.12.0

package/LICENSE

@@ -1,39 +1,105 @@
-foldrun proprietary licence
+# Functional Source License, Version 1.1, ALv2 Future License
 
-Copyright (c) 2026 foldrun. All rights reserved.
+## Abbreviation
 
-This software, its source code and its documentation are the property of
-foldrun. They are licensed, not sold.
+FSL-1.1-ALv2
 
-You may install and run the foldrun packages published to npm (`foldrun`
-and `@foldrun/core`) to write, check, run and deploy your own agents,
-flows and workspaces, on your own machines and with the foldrun platform.
-That includes the copies installing and running need, for your own use:
-package caches and mirrors, CI and build machines, container images and
-backups.
+## Notice
 
-You may not, except where the law allows it despite this restriction:
-copy, modify, merge, publish, distribute, sublicense, rent or sell the
-software or any part of it; reverse engineer, decompile or disassemble it;
-or use it to build a product or service that competes with foldrun.
+Copyright 2026 foldrun
 
-What you write with the software (your agents, flows, knowledge and other
-files) is yours.
+## Terms and Conditions
 
-Third-party components the software includes or installs (its npm
-dependencies) remain under their own licences.
+### Licensor ("We")
 
-This licence ends automatically if you break its terms, and you must then
-stop using the software.
+The party offering the Software under these Terms and Conditions.
 
-Versions published before 17 October 2026 under the Apache License 2.0
-remain available under that licence for those versions only.
+### The Software
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. TO THE EXTENT THE
-LAW ALLOWS, IN NO EVENT SHALL FOLDRUN BE LIABLE FOR ANY CLAIM, DAMAGES OR
-OTHER LIABILITY ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR
-ITS USE.
+The "Software" is each version of the software that we make available under
+these Terms and Conditions, as indicated by our inclusion of these Terms and
+Conditions with the Software.
 
-Questions: hello@foldrun.io
+### License Grant
+
+Subject to your compliance with this License Grant and the Patents,
+Redistribution and Trademark clauses below, we hereby grant you the right to
+use, copy, modify, create derivative works, publicly perform, publicly display
+and redistribute the Software for any Permitted Purpose identified below.
+
+### Permitted Purpose
+
+A Permitted Purpose is any purpose other than a Competing Use. A Competing Use
+means making the Software available to others in a commercial product or
+service that:
+
+1. substitutes for the Software;
+
+2. substitutes for any other product or service we offer using the Software
+   that exists as of the date we make the Software available; or
+
+3. offers the same or substantially similar functionality as the Software.
+
+Permitted Purposes specifically include using the Software:
+
+1. for your internal use and access;
+
+2. for non-commercial education;
+
+3. for non-commercial research; and
+
+4. in connection with professional services that you provide to a licensee
+   using the Software in accordance with these Terms and Conditions.
+
+### Patents
+
+To the extent your use for a Permitted Purpose would necessarily infringe our
+patents, the license grant above includes a license under our patents. If you
+make a claim against any party that the Software infringes or contributes to
+the infringement of any patent, then your patent license to the Software ends
+immediately.
+
+### Redistribution
+
+The Terms and Conditions apply to all copies, modifications and derivatives of
+the Software.
+
+If you redistribute any copies, modifications or derivatives of the Software,
+you must include a copy of or a link to these Terms and Conditions and not
+remove any copyright notices provided in or with the Software.
+
+### Disclaimer
+
+THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR
+PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
+
+IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE
+SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES,
+EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
+
+### Trademarks
+
+Except for displaying the License Details and identifying us as the origin of
+the Software, you have no right under these Terms and Conditions to use our
+trademarks, trade names, service marks or product names.
+
+## Grant of Future License
+
+We hereby irrevocably grant you an additional license to use the Software under
+the Apache License, Version 2.0 that is effective on the second anniversary of
+the date we make the Software available. On or after that date, you may use the
+Software under the Apache License, Version 2.0, in which case the following
+will apply:
+
+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/LICENSING.md

@@ -0,0 +1,101 @@
+# Licensing
+
+foldrun is **source-available** under the **Functional Source License,
+Version 1.1, with an Apache 2.0 future licence** (`FSL-1.1-ALv2`). The full
+terms are in [LICENSE](LICENSE); they are the standard FSL text, unchanged,
+and they are what binds. This page explains them in plain English. If the
+two ever disagree, LICENSE wins.
+
+## In one paragraph
+
+Use foldrun for anything except selling it, or offering it to others as a
+product or service that competes with foldrun. Personal use and use inside
+your own company are free, at any size. Every version becomes Apache 2.0,
+with no restrictions, two years after it is released.
+
+## What you may do, free
+
+- **Use it yourself**: on your laptop, on your own server, for your own
+  agents and flows.
+- **Use it inside your company or organisation**, of any size, for your own
+  work: your team's agents, your internal automations, your CI.
+- **Read, change and fork the code**, and keep your changes private or
+  share them, as long as the result is used for one of the purposes on
+  this list.
+- **Teach and research with it** (non-commercial education and research).
+- **Set it up for a client as a consultant or agency**, as long as the
+  client is the one using it, for their own purposes, under these same
+  terms.
+
+## What needs a commercial licence
+
+The licence calls these a *Competing Use*: making foldrun available **to
+others** in a **commercial** product or service that substitutes for
+foldrun, substitutes for a foldrun product or service that existed when that
+version was released, or offers the same or substantially similar
+functionality. For example:
+
+- running foldrun, or a modified copy, as a hosted agent platform that other
+  people or companies sign up to or pay for;
+- reselling it, white-labelling it, or bundling it into a product you sell
+  whose value is what foldrun does;
+- selling access to a managed foldrun instance.
+
+If you want to do any of these, or are not sure whether your use counts,
+write to **hello@foldrun.io**. Commercial licences are available.
+
+## The two-year rule
+
+Each version is offered under FSL from the day it is released. On the
+second anniversary of that release, that version is **also** available under
+the Apache License 2.0 — irrevocably, for everyone, for any purpose. Newer
+versions are not affected until they reach their own second anniversary.
+
+## Versions released under other terms
+
+| Versions | Licence |
+|---|---|
+| released before 17 October 2026 | Apache License 2.0 |
+| released 17 October 2026 up to the first FSL release | the foldrun proprietary licence that shipped in each package |
+| the first FSL release and later | FSL-1.1-ALv2 (this page) |
+
+A version keeps the licence it was released under.
+
+## What stays yours
+
+What you write with foldrun — your agents, flows, knowledge, skills, tools,
+evals and the outputs of your runs — is yours. This licence covers foldrun's
+code, not your work.
+
+## Name and logo
+
+The licence does not give you the foldrun name, logo or other trademarks,
+except to say truthfully where the code came from. A fork you distribute
+needs its own name.
+
+## Third-party code
+
+foldrun's dependencies, and anything it installs, stay under their own
+licences.
+
+## Patents
+
+Using foldrun for a permitted purpose includes a licence to any foldrun
+patents that use needs. That patent licence ends for anyone who sues claiming
+the software infringes a patent.
+
+## No warranty
+
+foldrun is provided as is, with no warranty, and with no liability for
+damages, as LICENSE sets out in full.
+
+## Contributing
+
+Contributions are welcome. Before we merge one, we ask you to agree that we
+may release it under these terms and under commercial licences, so the
+project can keep both. We will send the agreement with your first pull
+request.
+
+## Questions
+
+hello@foldrun.io. This page is a summary to help you, not legal advice.

package/README.md

@@ -151,8 +151,8 @@ Most people want the CLI, not this package — `npm install -g foldrun`.
 The command-line tool is its own package,
 [`foldrun`](https://www.npmjs.com/package/foldrun), and depends on
 this package. The reference documentation is at
-[docs.foldrun.io](https://docs.foldrun.io). Every foldrun repository is
-private; see "Hosting it" below.
+[docs.foldrun.io](https://docs.foldrun.io). foldrun is source-available
+under the Functional Source License (see "Licence" below).
 
 ### Templates and workspaces
 
@@ -189,8 +189,11 @@ This package is the framework: everything needed to read a workspace and
 run it on the machine you are on. The platform — the dashboard, a queue and
 its worker, one sandbox per step, a vault, metering, a team — is built on
 it, in a separate package that plugs in through `src/platform.ts`. Nothing
-in this repository imports it. The platform is hosted by foldrun and is not
-distributed; `foldrun deploy` moves a workspace from your machine to it
+in this repository imports it. The platform is
+[foldrun-platform](https://github.com/foldrun-io/foldrun-platform) and
+[foldrun-web](https://github.com/foldrun-io/foldrun-web): run it on your own
+server with Docker Compose (`foldrun-web/self-hosting`), or use foldrun's
+hosted one; `foldrun deploy` moves a workspace from your machine to either
 unchanged.
 
 ## Requirements
@@ -269,5 +272,10 @@ per request (fine to thousands of runs).
 
 ## Licence
 
-Proprietary; see [LICENSE](LICENSE). Versions published before 17 October
-2026 were Apache-2.0 and stay so.
+Source-available under the [Functional Source License 1.1, Apache 2.0 future
+licence](LICENSE) (`FSL-1.1-ALv2`). Use it for anything except offering it to
+others as a competing commercial product or service: personal use and use
+inside your own company are free, at any size. Each version becomes Apache 2.0
+two years after its release. [LICENSING.md](LICENSING.md) explains what is
+allowed and what needs a commercial licence (hello@foldrun.io), and which
+licence earlier versions shipped under.

package/dist/src/runner.js

@@ -1016,7 +1016,7 @@ grantsOnly = false) {
     // EMAIL_FROM]`): granting the tool grants them, the way an API tool's
     // referenced credentials always travelled with it. Before, only the
     // agent's own `secrets:` counted, so an agent that granted desk_email and
-    // declared nothing failed with "RESEND_API_KEY is not set" (strata-desk,
+    // declared nothing failed with "RESEND_API_KEY is not set" (a customer desk,
     // 1 Oct). `proxied` / `materialised` say how, not what, and add nothing.
     const toolSecrets = [];
     // Does any granted tool act outside the workspace (`outward: true`)? The

package/dist/src/scan.js

@@ -811,7 +811,7 @@ export function scanFiles(files, options = {}) {
         // Frontmatter YAML cannot read. Until 2026-10-21 nothing reported it for
         // a skill or a library file: frontOf below reads it as "no frontmatter"
         // and moves on, and the deploy's own refusal covers only the workspace's
-        // definition files. A vaza.ai skill with `description: … (Markdown,
+        // definition files. A customer's skill with `description: … (Markdown,
         // frontmatter, ::: directives) …` deployed clean, ran (the runtime quotes
         // the value and retries), and was refused by the source API on its next
         // save.

package/dist/src/test-mode.d.ts

@@ -113,7 +113,7 @@ export declare function restoreDivertedDirs(wsRoot: string, before: Map<string,
  * are kept under runs/<id>/test-writes/, never on the workspace, so each
  * step's copy of the workspace gets them laid over it — otherwise a step
  * reads the real files, and a flow that hands work on through storage/
- * tests something no live run does: on 2026-10-03 a strata-desk test run's
+ * tests something no live run does: on 2026-10-03 a customer desk's test run's
  * compiler wrote today's PASS report, and the mailer was handed the
  * morning's FAIL one and refused. Times are kept, so a verify that asks
  * whether a file is fresh answers for the step that wrote it. Returns the

package/dist/src/test-mode.js

@@ -288,7 +288,7 @@ export function restoreDivertedDirs(wsRoot, before, to, note, handed = before) {
  * are kept under runs/<id>/test-writes/, never on the workspace, so each
  * step's copy of the workspace gets them laid over it — otherwise a step
  * reads the real files, and a flow that hands work on through storage/
- * tests something no live run does: on 2026-10-03 a strata-desk test run's
+ * tests something no live run does: on 2026-10-03 a customer desk's test run's
  * compiler wrote today's PASS report, and the mailer was handed the
  * morning's FAIL one and refused. Times are kept, so a verify that asks
  * whether a file is fresh answers for the step that wrote it. Returns the

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@foldrun/core",
-  "version": "2.11.1",
+  "version": "2.12.0",
   "description": "Agents are just folders. The format, the runner, the checks.",
-  "license": "SEE LICENSE IN LICENSE",
+  "license": "FSL-1.1-ALv2",
   "type": "module",
   "exports": {
     ".": {
@@ -39,7 +39,8 @@
     "src",
     "index.ts",
     "templates",
-    "README.md"
+    "README.md",
+    "LICENSING.md"
   ],
   "scripts": {
     "build": "node -e \"require('node:fs').rmSync('dist', { recursive: true, force: true })\" && tsc -p tsconfig.json",

package/src/runner.ts

@@ -1157,7 +1157,7 @@ export function agentContext(
   // EMAIL_FROM]`): granting the tool grants them, the way an API tool's
   // referenced credentials always travelled with it. Before, only the
   // agent's own `secrets:` counted, so an agent that granted desk_email and
-  // declared nothing failed with "RESEND_API_KEY is not set" (strata-desk,
+  // declared nothing failed with "RESEND_API_KEY is not set" (a customer desk,
   // 1 Oct). `proxied` / `materialised` say how, not what, and add nothing.
   const toolSecrets: string[] = [];
   // Does any granted tool act outside the workspace (`outward: true`)? The

package/src/scan.ts

@@ -907,7 +907,7 @@ export function scanFiles(files: ScanFile[], options: ScanOptions = {}): ScanFin
     // Frontmatter YAML cannot read. Until 2026-10-21 nothing reported it for
     // a skill or a library file: frontOf below reads it as "no frontmatter"
     // and moves on, and the deploy's own refusal covers only the workspace's
-    // definition files. A vaza.ai skill with `description: … (Markdown,
+    // definition files. A customer's skill with `description: … (Markdown,
     // frontmatter, ::: directives) …` deployed clean, ran (the runtime quotes
     // the value and retries), and was refused by the source API on its next
     // save.

package/src/test-mode.ts

@@ -314,7 +314,7 @@ export function restoreDivertedDirs(
  * are kept under runs/<id>/test-writes/, never on the workspace, so each
  * step's copy of the workspace gets them laid over it — otherwise a step
  * reads the real files, and a flow that hands work on through storage/
- * tests something no live run does: on 2026-10-03 a strata-desk test run's
+ * tests something no live run does: on 2026-10-03 a customer desk's test run's
  * compiler wrote today's PASS report, and the mailer was handed the
  * morning's FAIL one and refused. Times are kept, so a verify that asks
  * whether a file is fresh answers for the step that wrote it. Returns the