@bpmnkit/docspack 0.0.2 → 0.0.4

package/.llms/chunks/guides.gateways.inclusive-gateway-or.md

@@ -40,4 +40,4 @@ Waits for the _first_ of several events to occur, then takes that path:
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/gateways/
+Source: https://bpmnkit.com/docs/guides/gateways

package/.llms/chunks/guides.gateways.nested-branching.md

@@ -24,4 +24,4 @@ Branches can contain further gateways:
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/gateways/
+Source: https://bpmnkit.com/docs/guides/gateways

package/.llms/chunks/guides.gateways.parallel-gateway-and.md

@@ -23,4 +23,4 @@ const xml = Bpmn.export(
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/gateways/
+Source: https://bpmnkit.com/docs/guides/gateways

package/.llms/chunks/guides.patterns.how-matching-works.md

@@ -14,4 +14,4 @@ Examples:
 | "custom blockchain process" | _(no match — Claude works from scratch)_ |
 
 ---
-Source: https://docs.bpmnkit.com/guides/patterns/
+Source: https://bpmnkit.com/docs/guides/patterns

package/.llms/chunks/guides.patterns.md

@@ -23,4 +23,4 @@ them entirely when nothing relevant matches.
 | `order-fulfillment` | E-commerce / supply chain | Inventory validation, payment, warehouse order, shipment tracking |
 
 ---
-Source: https://docs.bpmnkit.com/guides/patterns/
+Source: https://bpmnkit.com/docs/guides/patterns

package/.llms/chunks/guides.patterns.pattern-schema.md

@@ -35,4 +35,4 @@ pattern object to `ALL_PATTERNS` via the `findPattern` API. Contributions to the
 are welcome via pull request.
 
 ---
-Source: https://docs.bpmnkit.com/guides/patterns/
+Source: https://bpmnkit.com/docs/guides/patterns

package/.llms/chunks/guides.patterns.see-also.md

@@ -1,7 +1,7 @@
 # Pattern Library — See also
 
-- [Building Processes with AI](/guides/ai-implement/) — how Claude uses patterns during `/bpmnkit:implement`
+- [Building Processes with AI](/docs/guides/ai-implement) — how Claude uses patterns during `/bpmnkit:implement`
 - [`@bpmnkit/patterns` source](https://github.com/bpmnkit/monorepo/tree/main/packages/patterns)
 
 ---
-Source: https://docs.bpmnkit.com/guides/patterns/
+Source: https://bpmnkit.com/docs/guides/patterns

package/.llms/chunks/guides.patterns.using-patterns-from-the-cli.md

@@ -27,4 +27,4 @@ console.log(invoice?.workers.map((w) => w.jobType))
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/patterns/
+Source: https://bpmnkit.com/docs/guides/patterns

package/.llms/chunks/guides.patterns.what-a-pattern-contains.md

@@ -15,4 +15,4 @@ options (e.g. "SAP, NetSuite, or QuickBooks" for a payment trigger).
 so Claude can adapt the flow to the user's specific context.
 
 ---
-Source: https://docs.bpmnkit.com/guides/patterns/
+Source: https://bpmnkit.com/docs/guides/patterns

package/.llms/chunks/guides.simulation.dmn-decision-evaluation.md

@@ -48,4 +48,4 @@ describe("order process", () => {
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/simulation/
+Source: https://bpmnkit.com/docs/guides/simulation

package/.llms/chunks/guides.simulation.instance-state.md

@@ -26,4 +26,4 @@ console.log(vars.transactionId); // output from a task
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/simulation/
+Source: https://bpmnkit.com/docs/guides/simulation

package/.llms/chunks/guides.simulation.md

@@ -48,4 +48,4 @@ const instance = engine.start("order", {
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/simulation/
+Source: https://bpmnkit.com/docs/guides/simulation

package/.llms/chunks/guides.simulation.message-correlation.md

@@ -27,4 +27,4 @@ const instance = engine.start("order", {}, {
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/simulation/
+Source: https://bpmnkit.com/docs/guides/simulation

package/.llms/chunks/guides.simulation.multiple-deployments.md

@@ -11,4 +11,4 @@ const processes = engine.getDeployedProcesses();
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/simulation/
+Source: https://bpmnkit.com/docs/guides/simulation

package/.llms/chunks/guides.vscode.commands.md

@@ -0,0 +1,14 @@
+# VS Code Extension — Commands
+
+| Command | Where |
+| --- | --- |
+| **BPMN Kit: Open Diagram to the Side** | Editor title bar, command palette |
+| **BPMN Kit: Compare Diagram with HEAD** | Source Control context menu, editor title bar |
+| **BPMN Kit: Compare Diagrams Visually** | Explorer, with exactly two `.bpmn` files selected |
+| **BPMN Kit: Open FEEL Playground** | Command palette — pre-filled from the selection |
+| **BPMN Kit: Copy Diagram as ASCII** | Editor title bar, Explorer, command palette |
+| **BPMN Kit: Deploy to Camunda 8** | Command palette |
+| **BPMN Kit: Deploy and Start Instance** | Explorer, command palette |
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.installing.md

@@ -0,0 +1,22 @@
+# VS Code Extension — Installing
+
+The extension is **pre-1.0 and not on the Marketplace yet** — it is built from the monorepo
+and ships when the packages it is built from do:
+
+```sh
+git clone https://github.com/bpmnkit/monorepo
+cd monorepo && pnpm install
+pnpm --filter bpmnkit build
+pnpm --filter bpmnkit package     # → apps/vscode/bpmnkit.vsix
+```
+
+Then install the `.vsix`: **Extensions → … → Install from VSIX…**, or
+
+```sh
+code --install-extension apps/vscode/bpmnkit.vsix
+```
+
+It activates on a workspace containing a `.bpmn` file, and requires VS Code 1.90 or newer.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.md

@@ -0,0 +1,13 @@
+# VS Code Extension
+
+**BPMN Kit for VS Code** puts the toolkit where the code already is. It renders `.bpmn`,
+`.dmn` and `.form` files, reports the same findings `casen lint` reports, compares a diagram
+against `HEAD`, runs the process without a cluster, and edits the file without reformatting
+it.
+
+The renderer is [`@bpmnkit/canvas`](/docs/packages/canvas), the same from-scratch BPMN 2.0
+implementation the website and the browser editor use. There is no bpmn.io anywhere in the
+extension, which is the point: the files it shows you are the files git has, byte for byte.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.settings.md

@@ -0,0 +1,19 @@
+# VS Code Extension — Settings
+
+| Setting | Default | What it does |
+| --- | --- | --- |
+| `bpmnkit.lint.enabled` | `true` | Report findings in the Problems panel |
+| `bpmnkit.lint.run` | `onType` | `onType` or `onSave` |
+| `bpmnkit.lint.forceEngineRules` | `false` | Apply Camunda 8 rules to an engine-neutral diagram |
+| `bpmnkit.viewer.grid` | `true` | Dot grid behind the diagram |
+| `bpmnkit.viewer.minimap` | `true` | Minimap in the BPMN viewer |
+| `bpmnkit.simulation.enabled` | `true` | Offer step-through simulation in the preview |
+| `bpmnkit.editing.enabled` | `true` | Let the diagram editor change the file |
+
+Findings are reported for `.bpmn` files that are open; a file the editor has not loaded is
+not analysed, same as every other linter in VS Code. Set `bpmnkit.editing.enabled` to `false`
+for the same editors with editing switched off, when a diagram should be openable with no
+chance of changing it.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.support.md

@@ -0,0 +1,11 @@
+# VS Code Extension — Support
+
+The extension is pre-1.0 and community-supported, developed in the open in the
+[monorepo](https://github.com/bpmnkit/monorepo) alongside the packages it is built from.
+Minor versions may change behaviour before 1.0: the features above will not disappear, but
+setting names and command titles may still move. Bugs and requests go to
+[GitHub issues](https://github.com/bpmnkit/monorepo/issues). MIT-licensed, like everything
+else in the repository.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.what-it-does-a-feel-playground-on-your-selection.md

@@ -0,0 +1,8 @@
+# VS Code Extension — What it does — A FEEL playground on your selection
+
+Select an expression anywhere in the XML and open the playground: it comes up pre-filled,
+with a context you can edit and the result evaluated as you type. Unary tests too, for
+decision-table input entries.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.what-it-does-a-visual-diff-in-source-control.md

@@ -0,0 +1,11 @@
+# VS Code Extension — What it does — A visual diff in Source Control
+
+Right-click a `.bpmn` file in Source Control to see it against `HEAD`, or select exactly two
+in the Explorer to compare them with each other. Added, removed, changed and moved elements
+are marked on synchronised canvases — a moved element reads as *moved*, not as two unrelated
+pictures. The text diff stays where it was; this is a second view of the same change, not a
+replacement for the first. The same comparison is available as
+[`casen diff bpmn`](/docs/cli/diff) and on a [drop](/docs/guides/drop).
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.what-it-does-copy-the-diagram-as-text.md

@@ -0,0 +1,8 @@
+# VS Code Extension — What it does — Copy the diagram as text
+
+For a code review, where a picture cannot go. **BPMN Kit: Copy Diagram as ASCII** renders the
+layout into a fenced block that pastes into a pull request, an issue or a commit message,
+dedented so the diagram is not mostly margin.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.what-it-does-deploy-against-your-own-clusters.md

@@ -0,0 +1,21 @@
+# VS Code Extension — What it does — Deploy against your own clusters
+
+Deployment targets come from `casen`'s profile store — the same file
+[`casen profile create`](/docs/cli/casen#connection-profiles) writes — so there is no second
+place to configure a cluster and no credentials in your workspace settings:
+
+```sh
+casen profile create staging --base-url https://<cluster>.camunda.io/<id> \
+  --auth-type oauth --client-id … --client-secret …
+```
+
+Every `c8` profile then appears in the extension. Deploy the open file, or deploy and start
+an instance with variables; the instance key comes back in a notification. Deploy-and-start
+also offers the payloads it finds in `.camunda/payloads/*.json`, walking up from the diagram,
+so the inputs a process is always tried with are a pick rather than a paste.
+
+Credentials are read only to sign the request — nothing in the extension stores, displays or
+logs them.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.what-it-does-editing-that-leaves-a-readable-diff.md

@@ -0,0 +1,22 @@
+# VS Code Extension — What it does — Editing that leaves a readable diff
+
+The diagram editor is a **text** custom editor: it edits the same `TextDocument` a text
+editor would open. The file is dirty when the document is, <kbd>Ctrl</kbd>+<kbd>S</kbd>
+saves it, hot exit restores it, undo is the editor's own undo, and a text editor open on the
+same file is a second view of one document rather than a competing copy. Type in the XML and
+the diagram follows; move a box and the XML follows.
+
+Saving writes a diff a reviewer can read. A visual editor normally serialises the whole
+model, which reformats the file on the first change and buries one edit in a rewrite of
+everything. This one writes the file that was already there: renaming a task changes the
+line with the task on it, moving a box changes two numbers, and your indentation, attribute
+order and comments come back untouched. Opening a diagram and saving it without editing
+anything leaves the file byte for byte. Form files get the same treatment — indentation, key
+order and trailing newline all survive.
+
+That behaviour is not extension-specific; it is
+[`exportPreserving()`](/docs/packages/core#exportpreservingoriginal-definitions) from
+`@bpmnkit/core`, available to anything that writes a model back over a file it parsed.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.what-it-does-findings-in-the-problems-panel.md

@@ -0,0 +1,13 @@
+# VS Code Extension — What it does — Findings in the Problems panel
+
+The same static analysis `casen lint` runs — flow reachability, naming, FEEL syntax, data
+flow, Camunda 8 deployability — reported against the element that caused it, so clicking a
+problem takes you to the tag rather than to line 1.
+
+The analysis matches the file. A diagram that declares no `modeler:executionPlatform` is not
+judged against Camunda 8 deployability, because "this service task has no
+`zeebe:taskDefinition`" is not a defect in a diagram that was never going to be deployed to
+Zeebe. Turn on `bpmnkit.lint.forceEngineRules` to apply those rules anyway.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.what-it-does-preview-beside-the-source.md

@@ -0,0 +1,12 @@
+# VS Code Extension — What it does — Preview beside the source
+
+`.bpmn`, `.dmn` and `.form` all render, with a minimap and zoom for BPMN. The preview
+follows the buffer as you type rather than on save, and when the XML is momentarily
+unparseable it keeps the last drawing that worked rather than blanking.
+
+The text editor stays the default for all three file types. Open the diagram with
+**BPMN Kit: Open Diagram to the Side**, with *Reopen Editor With…*, or make it your default
+through `workbench.editorAssociations`.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.vscode.what-it-does-run-the-diagram-in-the-editor.md

@@ -0,0 +1,9 @@
+# VS Code Extension — What it does — Run the diagram in the editor
+
+[`@bpmnkit/engine`](/docs/packages/engine) is a BPMN engine written in TypeScript, so the
+preview does not need a cluster to execute what is on screen. Press **Run** and watch tokens
+move; press **One Step** to advance the instance one element at a time, reading the variables
+as they change. Nothing is deployed and nothing leaves your machine.
+
+---
+Source: https://bpmnkit.com/docs/guides/vscode

package/.llms/chunks/guides.workers-standalone.anatomy-of-a-worker.md

@@ -39,4 +39,4 @@ for await (const job of client.poll(JOB_TYPE)) {
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/workers-standalone/
+Source: https://bpmnkit.com/docs/guides/workers-standalone

package/.llms/chunks/guides.workers-standalone.camunda-saas.md

@@ -40,4 +40,4 @@ Built-in workers (provided by the proxy):
 | `bpmnkit:email:send:1` | Send email via SMTP |
 
 ---
-Source: https://docs.bpmnkit.com/guides/workers-standalone/
+Source: https://bpmnkit.com/docs/guides/workers-standalone

package/.llms/chunks/guides.workers-standalone.environment-variables.md

@@ -11,4 +11,4 @@
 For local development with reebe, only `ZEEBE_ADDRESS` matters (or leave it at the default).
 
 ---
-Source: https://docs.bpmnkit.com/guides/workers-standalone/
+Source: https://bpmnkit.com/docs/guides/workers-standalone

package/.llms/chunks/guides.workers-standalone.md

@@ -32,4 +32,4 @@ workers/
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/workers-standalone/
+Source: https://bpmnkit.com/docs/guides/workers-standalone

package/.llms/chunks/guides.workers-standalone.running-workers.md

@@ -58,4 +58,4 @@ docker run -e ZEEBE_ADDRESS=http://reebe:26500 my-org/send-invoice
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/workers-standalone/
+Source: https://bpmnkit.com/docs/guides/workers-standalone

package/.llms/chunks/guides.workers-standalone.see-also.md

@@ -1,7 +1,7 @@
 # Standalone Workers — See also
 
-- [`@bpmnkit/worker-client`](/packages/worker-client/) — full API reference
-- [AI-Driven Implementation](/guides/ai-implement/) — scaffold workers as part of `/implement`
+- [`@bpmnkit/worker-client`](/docs/packages/worker-client) — full API reference
+- [AI-Driven Implementation](/docs/guides/ai-implement) — scaffold workers as part of `/implement`
 
 ---
-Source: https://docs.bpmnkit.com/guides/workers-standalone/
+Source: https://bpmnkit.com/docs/guides/workers-standalone

package/.llms/chunks/packages.api.incident-resolution.md

@@ -28,4 +28,4 @@ await client.messages.publish({
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/api/
+Source: https://bpmnkit.com/docs/packages/api

package/.llms/chunks/packages.api.observability-events.md

@@ -10,4 +10,4 @@ client.on("retry",    (e) => logger.warn(`Retrying ${e.url} (attempt ${e.attempt
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/api/
+Source: https://bpmnkit.com/docs/packages/api

package/.llms/chunks/packages.api.overview.md

@@ -46,4 +46,4 @@ const client = new CamundaClient({
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/api/
+Source: https://bpmnkit.com/docs/packages/api

package/.llms/chunks/packages.api.process-operations.md

@@ -57,4 +57,4 @@ worker.close();
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/api/
+Source: https://bpmnkit.com/docs/packages/api

package/.llms/chunks/packages.api.resource-namespaces.md

@@ -17,4 +17,4 @@ All methods are grouped by resource type:
 | `client.authorizations` | list, create, delete |
 
 ---
-Source: https://docs.bpmnkit.com/packages/api/
+Source: https://bpmnkit.com/docs/packages/api

package/.llms/chunks/packages.canvas.events.md

@@ -53,4 +53,4 @@ type CanvasPlugin = {
 | `@bpmnkit/canvas-plugin-ai-bridge` | AI chat integration |
 
 ---
-Source: https://docs.bpmnkit.com/packages/canvas/
+Source: https://bpmnkit.com/docs/packages/canvas

package/.llms/chunks/packages.canvas.options.md

@@ -21,4 +21,4 @@ type CanvasOptions = {
 | `canvas.destroy()` | Clean up the canvas and remove from DOM |
 
 ---
-Source: https://docs.bpmnkit.com/packages/canvas/
+Source: https://bpmnkit.com/docs/packages/canvas

package/.llms/chunks/packages.canvas.overview.md

@@ -32,4 +32,4 @@ await canvas.loadXML(bpmnXml);
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/canvas/
+Source: https://bpmnkit.com/docs/packages/canvas

package/.llms/chunks/packages.connector-gen.body-expansion.md

@@ -15,4 +15,4 @@ generate(spec, { idPrefix: "com.myorg", expandBody: true })
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/connector-gen/
+Source: https://bpmnkit.com/docs/packages/connector-gen

package/.llms/chunks/packages.connector-gen.catalog-reference.md

@@ -51,4 +51,4 @@ const stripe = getCatalogEntry("stripe")
 | `brex` | Brex API | oauth-client-credentials-flow |
 
 ---
-Source: https://docs.bpmnkit.com/packages/connector-gen/
+Source: https://bpmnkit.com/docs/packages/connector-gen

package/.llms/chunks/packages.connector-gen.catalogentry-type.md

@@ -15,7 +15,7 @@ interface CatalogEntry {
 ## CLI
 
 The same functionality is available via `casen connector generate` and `casen connector catalog`.
-See the [CLI reference](/cli/connector/).
+See the [CLI reference](/docs/cli/connector).
 
 ---
-Source: https://docs.bpmnkit.com/packages/connector-gen/
+Source: https://bpmnkit.com/docs/packages/connector-gen

package/.llms/chunks/packages.connector-gen.generating-from-the-catalog.md

@@ -41,4 +41,4 @@ type AuthHint =
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/connector-gen/
+Source: https://bpmnkit.com/docs/packages/connector-gen

package/.llms/chunks/packages.connector-gen.installation.md

@@ -39,4 +39,4 @@ console.log(`Wrote ${files.length} templates`)
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/connector-gen/
+Source: https://bpmnkit.com/docs/packages/connector-gen

package/.llms/chunks/packages.connector-gen.lower-level-api.md

@@ -28,4 +28,4 @@ await writeTemplates(templates, {
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/connector-gen/
+Source: https://bpmnkit.com/docs/packages/connector-gen

package/.llms/chunks/packages.connector-gen.overview.md

@@ -13,4 +13,4 @@ REST connector element templates — the `.json` files imported into Camunda Mod
 - Zero dependencies beyond `yaml` for YAML parsing
 
 ---
-Source: https://docs.bpmnkit.com/packages/connector-gen/
+Source: https://bpmnkit.com/docs/packages/connector-gen

package/.llms/chunks/packages.connector-gen.writeoptions.md

@@ -23,4 +23,4 @@ Auth is auto-detected from `components.securitySchemes`. The detected or specifi
 pre-selected in the template dropdown.
 
 ---
-Source: https://docs.bpmnkit.com/packages/connector-gen/
+Source: https://bpmnkit.com/docs/packages/connector-gen

package/.llms/chunks/packages.core.dmn-support.md

@@ -33,4 +33,4 @@ import type {
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/core/
+Source: https://bpmnkit.com/docs/packages/core

package/.llms/chunks/packages.core.installation-ad-hoc-sub-processes-children-are-a-set-not-a-chain.md

@@ -0,0 +1,42 @@
+# @bpmnkit/core — Installation — Ad-hoc sub-processes: children are a set, not a chain
+
+Sequential calls in a builder chain auto-connect with sequence flows. Inside
+`.adHocSubProcess()` they do not: BPMN defines an ad-hoc sub-process's children as an unordered
+set of independently-invocable activities, and Camunda 8's agentic AI runtime reads that
+structurally — a child *without* an incoming flow is an LLM-invocable tool, a child *with* one
+is part of an internal sub-flow and not a tool at all.
+
+```typescript
+.adHocSubProcess("agent", (s) => {
+  s.serviceTask("listUsers",  { taskType: "io.camunda:http-json:1" });
+  s.serviceTask("loadUser",   { taskType: "io.camunda:http-json:1" });
+  s.serviceTask("createUser", { taskType: "io.camunda:http-json:1" });
+}, { name: "Handle request" })
+// → three tools, no sequence flows, no <bpmndi:BPMNEdge> between them
+```
+
+Auto-chaining them produced a file that lints clean and deploys, while the agent saw one tool
+and a two-step sub-flow — so the default is off rather than opt-out.
+
+An internal sub-flow inside the container stays expressible: say so with `.connectTo()`, which
+still creates a flow from the cursor.
+
+```typescript
+.adHocSubProcess("agent", (s) => {
+  s.serviceTask("listUsers", { taskType: "io.camunda:http-json:1" });   // a tool
+  s.serviceTask("step1", { taskType: "work" }).connectTo("step2");      // an internal sub-flow
+  s.serviceTask("step2", { taskType: "work" });
+})
+```
+
+Each child's LLM-facing description is its `documentation`, which every builder method accepts:
+
+```typescript
+s.serviceTask("listUsers", {
+  taskType: "io.camunda:http-json:1",
+  documentation: "Call this to retrieve all users. Returns id, name, email.",
+});
+```
+
+---
+Source: https://bpmnkit.com/docs/packages/core

package/.llms/chunks/packages.core.installation-applybpmnoperations-definitions-operations-options.md

@@ -0,0 +1,23 @@
+# @bpmnkit/core — Installation — `applyBpmnOperations(definitions, operations, options?)`
+
+Applies edit operations to the full model. The operation vocabulary is the same one an LLM
+produces; applying it here rather than to a `CompactDiagram` means an edit touches only what it
+names and leaves the document's pools, lanes, data wiring and Zeebe detail alone.
+
+```typescript
+import { applyBpmnOperations } from "@bpmnkit/core";
+
+const { definitions, applied } = applyBpmnOperations(parsed, [
+  { op: "rename", id: "Task_1", name: "Approve invoice" },
+  { op: "update", id: "Task_1", patch: { jobType: "approve" } },
+]);
+```
+
+**Strict by default.** An operation naming an element that does not exist throws an
+`OperationError` and nothing is applied — the previous implementation skipped such operations
+silently, so a patch with a misspelled id reported success and changed nothing. Pass
+`{ strict: false }` to get `{ definitions, applied, problems }` instead and decide for
+yourself. The input is never mutated either way.
+
+---
+Source: https://bpmnkit.com/docs/packages/core

package/.llms/chunks/packages.core.installation-bpmn.continueprocess-definitions-processid.md

@@ -0,0 +1,45 @@
+# @bpmnkit/core — Installation — `Bpmn.continueProcess(definitions, processId)`
+
+Continue an existing model instead of generating a replacement for it. `build()` returns *that
+document* with the named process's contents replaced, so other processes, the collaboration,
+lanes, diagram interchange, root elements and unmodelled content all survive. The input is not
+mutated.
+
+```typescript
+const updated = Bpmn.continueProcess(Bpmn.parse(xml), "order-process")
+  .insertAfter("validate")
+  .serviceTask("notify", { name: "Notify", taskType: "notify" })
+  .build();
+```
+
+Also available as `ProcessBuilder.from(definitions, processId)`.
+
+**`.at(nodeId)`** continues from a node whose path is open — no outgoing sequence flow, or a
+gateway, where several outgoing flows are the point. It refuses a node that is not directly in
+that process (a node inside a sub-process means building that sub-process), an end event, and a
+node that would gain a second outgoing flow — that is an uncontrolled split, and almost always
+means you wanted to insert.
+
+**`.insertAfter(nodeId)`** splices what you build next into the path leaving an existing node:
+`validate → end` becomes `validate → notify → end`. The existing flow keeps its **id and its
+target** and only changes where it starts, so an edge nobody asked to move keeps its identity
+in the diagram and in a diff. It refuses a node with no outgoing flow, and one with several,
+where "after" is ambiguous.
+
+Which of the two you mean is not guessable, so it is not guessed.
+
+**Continuing never infers gateways.** `ProcessBuilder` normally inserts join gateways for
+branches you build; on a parsed model that reads the whole topology and retargets edges you
+never touched, so continue mode does not do it. A branch that needs a join here says so with
+`.connectTo(joinId)`. `build()` refuses outright if anything would rewire a sequence flow the
+document already had.
+
+**Diagram interchange is not regenerated.** Existing shapes keep their positions, and elements
+you add have none until `.withAutoLayout()` or a later `applyAutoLayout()` gives them one.
+
+`isExecutable` and the process name are left as they were unless you call `.executable()` or
+`.name()`. BPMN reads an absent `isExecutable` as false, so writing the builder's default onto
+a process that never carried it would make a non-executable process executable.
+
+---
+Source: https://bpmnkit.com/docs/packages/core

package/.llms/chunks/packages.core.installation-bpmn.creatediagram-id.md

@@ -15,4 +15,4 @@ const defs = Bpmn.createDiagram("OrderSystem")
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/core/
+Source: https://bpmnkit.com/docs/packages/core

package/.llms/chunks/packages.core.installation-bpmn.createprocess-id-name.md

@@ -7,4 +7,4 @@ const builder = Bpmn.createProcess("my-process", "My Process");
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/core/
+Source: https://bpmnkit.com/docs/packages/core

package/.llms/chunks/packages.core.installation-bpmn.export-definitions.md

@@ -7,4 +7,4 @@ const xml = Bpmn.export(definitions);
 ```
 
 ---
-Source: https://docs.bpmnkit.com/packages/core/
+Source: https://bpmnkit.com/docs/packages/core