@bpmnkit/docspack 0.0.2 → 0.0.4

package/.llms/chunks/getting-started.concepts.the-fluent-builder.md

@@ -38,4 +38,4 @@ Each branch builder starts at the gateway. Branches merge automatically when two
 the same element.
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/concepts/
+Source: https://bpmnkit.com/docs/getting-started/concepts

package/.llms/chunks/getting-started.concepts.zeebe-extensions.md

@@ -22,4 +22,4 @@ The builder exposes these as first-class TypeScript options:
 ```
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/concepts/
+Source: https://bpmnkit.com/docs/getting-started/concepts

package/.llms/chunks/getting-started.installation.md

@@ -35,4 +35,4 @@ pnpm add @bpmnkit/api
 ```
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/installation/
+Source: https://bpmnkit.com/docs/getting-started/installation

package/.llms/chunks/getting-started.installation.runtime-requirements.md

@@ -10,4 +10,4 @@
 All packages are **ESM-only** (`"type": "module"`). CommonJS is not supported.
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/installation/
+Source: https://bpmnkit.com/docs/getting-started/installation

package/.llms/chunks/getting-started.installation.svg-canvas-viewer.md

@@ -35,7 +35,7 @@ casen reebe            # start local workflow engine
 
 Then in Claude Code: `/implement an invoice approval process`
 
-See [AI-Driven Implementation](/guides/ai-implement/) for a full walkthrough.
+See [AI-Driven Implementation](/docs/guides/ai-implement) for a full walkthrough.
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/installation/
+Source: https://bpmnkit.com/docs/getting-started/installation

package/.llms/chunks/getting-started.installation.worker-client.md

@@ -37,4 +37,4 @@ For browser/bundler projects (Vite, Webpack, etc.), use:
 ```
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/installation/
+Source: https://bpmnkit.com/docs/getting-started/installation

package/.llms/chunks/getting-started.quick-start.md

@@ -28,4 +28,4 @@ console.log(xml); // valid BPMN 2.0 XML
 The `xml` string is a complete, valid BPMN 2.0 document that any standards-compliant engine can load.
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/quick-start/
+Source: https://bpmnkit.com/docs/getting-started/quick-start

package/.llms/chunks/getting-started.quick-start.step-2-simulate-locally.md

@@ -25,4 +25,4 @@ await new Promise<void>((resolve) => {
 ```
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/quick-start/
+Source: https://bpmnkit.com/docs/getting-started/quick-start

package/.llms/chunks/getting-started.quick-start.step-3-deploy-to-camunda-8.md

@@ -30,4 +30,4 @@ console.log("Started instance:", instance.processInstanceKey);
 ```
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/quick-start/
+Source: https://bpmnkit.com/docs/getting-started/quick-start

package/.llms/chunks/getting-started.quick-start.what-s-next.md

@@ -1,14 +1,13 @@
 # Quick Start — What's next?
 
-- [AI-Driven Implementation](/guides/ai-implement/) — let Claude implement processes end-to-end from a description
-- [Core Concepts](/getting-started/concepts/) — understand how the builder, layout, and roundtrip work
-- [Building Processes](/guides/building-processes/) — tasks, events, sub-processes, and markers
-- [Gateways & Branching](/guides/gateways/) — exclusive, parallel, and event-based gateways
+- [AI-Driven Implementation](/docs/guides/ai-implement) — let Claude implement processes end-to-end from a description
+- [Core Concepts](/docs/getting-started/concepts) — understand how the builder, layout, and roundtrip work
+- [Building Processes](/docs/guides/building-processes) — tasks, events, sub-processes, and markers
+- [Gateways & Branching](/docs/guides/gateways) — exclusive, parallel, and event-based gateways
 
-:::tip[AI-first workflow]
-If you have Claude Code, the fastest path is: `casen skills install` then `/implement <description>`.
-Claude generates the BPMN, scaffolds workers, and deploys — all from a single prompt.
-:::
+> **AI-first workflow** — if you have Claude Code, the fastest path is `casen skills install`
+> then `/implement <description>`. Claude generates the BPMN, scaffolds workers, and deploys —
+> all from a single prompt.
 
 ---
-Source: https://docs.bpmnkit.com/getting-started/quick-start/
+Source: https://bpmnkit.com/docs/getting-started/quick-start

package/.llms/chunks/guides.ai-agents.deploy-grade-validation.md

@@ -16,4 +16,4 @@ can be misread as an arithmetic expression) — this is a known limitation of th
 not a real issue, and doesn't affect the `deploy` profile.
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-agents/
+Source: https://bpmnkit.com/docs/guides/ai-agents

package/.llms/chunks/guides.ai-agents.how-it-s-modeled.md

@@ -8,4 +8,4 @@
 None of this is hand-authored — it's generated by the `aiAgent` plan step.
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-agents/
+Source: https://bpmnkit.com/docs/guides/ai-agents

package/.llms/chunks/guides.ai-agents.md

@@ -15,4 +15,4 @@ generates this pattern the same way it generates everything else: deterministica
 Or, from the CLI directly: write an `aiAgent` plan step (see below), then `casen synth`.
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-agents/
+Source: https://bpmnkit.com/docs/guides/ai-agents

package/.llms/chunks/guides.ai-agents.see-also.md

@@ -1,7 +1,7 @@
 # AI Agents — See also
 
-- [Building Processes with AI](/guides/ai-implement/) — the overall plan/synth pipeline
-- [`casen connector`](/cli/connector/) — searching the catalog for connector-backed tools
+- [Building Processes with AI](/docs/guides/ai-implement) — the overall plan/synth pipeline
+- [`casen connector`](/docs/cli/connector) — searching the catalog for connector-backed tools
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-agents/
+Source: https://bpmnkit.com/docs/guides/ai-agents

package/.llms/chunks/guides.ai-agents.testing-without-a-real-llm-call.md

@@ -23,4 +23,4 @@ exercise the agent's actual tool-calling behavior, prompt quality, or model choi
 require a real (or sandboxed) LLM run, which is out of scope for `casen test`.
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-agents/
+Source: https://bpmnkit.com/docs/guides/ai-agents

package/.llms/chunks/guides.ai-agents.the-aiagent-plan-step.md

@@ -59,4 +59,4 @@ Key points:
 - **Secrets always use `{{secrets.NAME}}`** — never a literal API key or token.
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-agents/
+Source: https://bpmnkit.com/docs/guides/ai-agents

package/.llms/chunks/guides.ai-implement.deploying.md

@@ -43,7 +43,7 @@ Or start all workers at once:
 casen worker start
 ```
 
-See [Standalone Workers](/guides/workers-standalone/) for deployment options.
+See [Standalone Workers](/docs/guides/workers-standalone) for deployment options.
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-implement/
+Source: https://bpmnkit.com/docs/guides/ai-implement

package/.llms/chunks/guides.ai-implement.extending-an-existing-process.md

@@ -7,4 +7,4 @@
 This lifts the process back into plan form (`casen plan extract`), writes a small delta plan touching only the changed step, and merges it in (`casen synth --merge`) — the diff is reported at the element level, not as an XML diff.
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-implement/
+Source: https://bpmnkit.com/docs/guides/ai-implement

package/.llms/chunks/guides.ai-implement.lightweight-alternative-casen-skills-install.md

@@ -1,6 +1,6 @@
 # Building Processes with AI — Lightweight alternative: `casen skills install`
 
-If you don't want the full plugin, four minimal slash commands are available directly from the CLI — see [AIKit Skills](/cli/skills/):
+If you don't want the full plugin, four minimal slash commands are available directly from the CLI — see [AIKit Skills](/docs/cli/skills):
 
 ```sh
 casen skills install
@@ -25,4 +25,4 @@ project/
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-implement/
+Source: https://bpmnkit.com/docs/guides/ai-implement

package/.llms/chunks/guides.ai-implement.md

@@ -20,7 +20,7 @@ more reliable: write the plan, resolve connectors, and fix reported problems.
                 (for later edits)
 ```
 
-1. **Check for a reusable domain pattern** — `casen pattern list`/`get` (see [Pattern Library](/guides/patterns/)) surfaces domain context (regulations, conventions) and realistic worker specs, used as reference while writing the plan below — not pasted in as a `ProcessPlan` directly.
+1. **Check for a reusable domain pattern** — `casen pattern list`/`get` (see [Pattern Library](/docs/guides/patterns)) surfaces domain context (regulations, conventions) and realistic worker specs, used as reference while writing the plan below — not pasted in as a `ProcessPlan` directly.
 2. **Resolve external interactions** — `casen connector search "<system>"` / `casen connector show <template-id>` find the right Camunda connector template and its required inputs, instead of guessing property keys.
 3. **Write the plan** — a `ProcessPlan` JSON file (`casen plan schema` prints the full format reference).
 4. **Compile** — `casen synth <plan>.json --output <file>.bpmn`. Problems are reported keyed by JSON path (e.g. `steps[2].connector.values.token`) — fix the plan, never the XML, and re-run.
@@ -29,4 +29,4 @@ more reliable: write the plan, resolve connectors, and fix reported problems.
 7. **Deploy** — `casen deploy deploy <file>.bpmn` (local Reebe) or `--target camunda8`.
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-implement/
+Source: https://bpmnkit.com/docs/guides/ai-implement

package/.llms/chunks/guides.ai-implement.the-claude-code-plugin.md

@@ -15,7 +15,7 @@ It's **CLI-first**: every skill drives `casen` via Bash — no MCP server, no pr
 
 Claude works through: resolve connectors → write the plan → compile → test → scaffold missing workers → present a summary → ask where to deploy.
 
-Related skills: `/bpmnkit:extend <file> <change>` (lift an existing process to a plan, apply a targeted delta, merge), `/bpmnkit:agent` (design an AI Agent Sub-process — see [AI Agents](/guides/ai-agents/)), `/bpmnkit:connect <file> <step> <service>` (wire an existing step to a connector), `/bpmnkit:review`, `/bpmnkit:test`, `/bpmnkit:deploy`.
+Related skills: `/bpmnkit:extend <file> <change>` (lift an existing process to a plan, apply a targeted delta, merge), `/bpmnkit:agent` (design an AI Agent Sub-process — see [AI Agents](/docs/guides/ai-agents)), `/bpmnkit:connect <file> <step> <service>` (wire an existing step to a connector), `/bpmnkit:review`, `/bpmnkit:test`, `/bpmnkit:deploy`.
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai-implement/
+Source: https://bpmnkit.com/docs/guides/ai-implement

package/.llms/chunks/guides.ai.claude-api-example.md

@@ -38,4 +38,4 @@ const xml = await generateProcess(
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai/
+Source: https://bpmnkit.com/docs/guides/ai

package/.llms/chunks/guides.ai.mcp-server.md

@@ -17,4 +17,4 @@ Available MCP tools:
 - `validate` — validates the diagram and returns any schema errors
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai/
+Source: https://bpmnkit.com/docs/guides/ai

package/.llms/chunks/guides.ai.md

@@ -8,7 +8,7 @@ produces valid BPMN without requiring the AI to write raw XML.
 ## The Compact Format
 
 Raw BPMN XML is far too verbose for LLMs — a simple three-node process generates ~60 lines.
-The compact format represents the same information as a small JSON object:
+The compact format carries the topology and the common Zeebe bindings as a small JSON object:
 
 ```typescript
 import { Bpmn, compactify, expand } from "@bpmnkit/core";
@@ -28,5 +28,28 @@ const updatedDefinitions = expand(modified);
 const updatedXml = Bpmn.export(updatedDefinitions);
 ```
 
+> **`expand()` does not restore what `compactify()` left behind.** `CompactElement` models
+> about fifteen properties; collaborations, participants, message flows, lanes, data stores,
+> artifacts, root-level messages and errors, multi-instance loop characteristics, full
+> `zeebe:ioMapping` entries and most diagram interchange are not among them.
+>
+> The loop above is safe for a model **you generated** from a compact definition. Running it
+> over a file authored elsewhere — a Camunda blueprint, anything touched in Web Modeler —
+> will silently strip those parts.
+>
+> **Use `reconcileCompact` instead when editing an existing file.** It applies the same compact
+> input as changes rather than expanding it over the model, so what the compact form cannot
+> describe survives:
+>
+> ```typescript
+> import { reconcileCompact } from "@bpmnkit/core";
+>
+> const { definitions } = reconcileCompact(Bpmn.parse(existingXml), modified);
+> const updatedXml = Bpmn.export(definitions);
+> ```
+>
+> If the model returns edit operations rather than a whole diagram, `applyBpmnOperations` takes
+> them directly against the full model.
+
 ---
-Source: https://docs.bpmnkit.com/guides/ai/
+Source: https://bpmnkit.com/docs/guides/ai

package/.llms/chunks/guides.ai.minimal-empty-diagram.md

@@ -29,4 +29,4 @@ Rules:
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai/
+Source: https://bpmnkit.com/docs/guides/ai

package/.llms/chunks/guides.ai.openai-function-calling.md

@@ -37,4 +37,4 @@ const xml = Bpmn.export(expand(compact));
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/ai/
+Source: https://bpmnkit.com/docs/guides/ai

package/.llms/chunks/guides.building-processes.boundary-events.md

@@ -44,4 +44,4 @@ builder cursor to the boundary event itself:
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/building-processes/
+Source: https://bpmnkit.com/docs/guides/building-processes

package/.llms/chunks/guides.building-processes.call-activities.md

@@ -44,4 +44,4 @@ const xml = Bpmn.export(defs); // both processes in one XML file
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/building-processes/
+Source: https://bpmnkit.com/docs/guides/building-processes

package/.llms/chunks/guides.building-processes.events.md

@@ -54,4 +54,4 @@
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/building-processes/
+Source: https://bpmnkit.com/docs/guides/building-processes

package/.llms/chunks/guides.building-processes.multi-instance.md

@@ -16,5 +16,71 @@ Run a task or sub-process once per item in a collection:
 })
 ```
 
+
+## Generated IDs
+
+You name every flow node. The builder names everything else, and it derives those names from
+the model so that rebuilding an unchanged process produces unchanged BPMN — a diff that shows
+only what you actually changed.
+
+A sequence flow is named after the two elements it connects:
+
+```typescript
+Bpmn.createProcess("orders")
+  .startEvent("start")
+  .serviceTask("validate", { taskType: "validate" })
+  .endEvent("done")
+  .build()
+// Flow_start_validate, Flow_validate_done
+```
+
+When several flows connect the same pair — the branches of a gateway converging on one join —
+each gets a discriminator taken from the branch name, or from its condition when the branch is
+unnamed:
+
+```typescript
+.exclusiveGateway("gw")
+.branch("approved", (b) => b.connectTo("done"))
+.branch("rejected", (b) => b.connectTo("done"))
+// Flow_gw_gw_join_approved, Flow_gw_gw_join_rejected
+```
+
+Because the id comes from the connection rather than from a counter, adding or reordering an
+unrelated element leaves the other flows' ids alone. The same is true of root definitions
+created from event options — `Message_Order_Received` for `messageName: "Order Received"`, and
+likewise `Error_`, `Signal_` and `Escalation_` from the code or name they carry.
+
+Two consequences worth knowing:
+
+- **Ids are only as stable as the elements they name.** Omitting an element id (`.startEvent()`
+  with no argument) gets you a generated one that changes on every build, and the flow ids
+  around it inherit that. Name the nodes you care about.
+- **`defaultFlow` becomes predictable.** Setting a gateway's default by id no longer requires
+  knowing a random value: `{ defaultFlow: "Flow_gw_gw_join_rejected" }`. `.branch().defaultFlow()`
+  is still the shorter way to say it.
+
+`continueProcess()` never renumbers what the document arrived with: flows the builder did not
+create keep their ids, and new ones avoid them.
+
+### Naming a root definition yourself
+
+When the id of a message, error, signal or escalation matters — because a message flow in another
+pool, a worker, or a deployed process already refers to it — declare it before the events that
+use it:
+
+```typescript
+Bpmn.createProcess("orders")
+  .message("Msg_OrderReceived", { name: "Order Received" })
+  .error("Err_OutOfStock", { code: "OUT_OF_STOCK", name: "Out of stock" })
+  .signal("Sig_Cancelled", { name: "Order Cancelled" })
+  .escalation("Esc_Review", { code: "NEEDS_REVIEW" })
+  .startEvent("start", { messageName: "Order Received" })   // messageRef: Msg_OrderReceived
+```
+
+Events still name these by name or code, exactly as before — the declaration only decides the id
+they resolve to. Order matters: an event built first declares the definition itself, and
+declaring it afterwards under a different id throws rather than leaving two definitions of one
+message behind.
+
 ---
-Source: https://docs.bpmnkit.com/guides/building-processes/
+Source: https://bpmnkit.com/docs/guides/building-processes

package/.llms/chunks/guides.building-processes.service-tasks.md

@@ -36,4 +36,4 @@ A user task waits for a human actor. Optionally attach a Camunda form:
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/building-processes/
+Source: https://bpmnkit.com/docs/guides/building-processes

package/.llms/chunks/guides.building-processes.sub-processes.md

@@ -37,4 +37,4 @@ An event sub-process starts when a boundary event fires:
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/building-processes/
+Source: https://bpmnkit.com/docs/guides/building-processes

package/.llms/chunks/guides.building-processes.task-defaults.md

@@ -15,4 +15,4 @@ Bpmn.createProcess("my-flow")
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/building-processes/
+Source: https://bpmnkit.com/docs/guides/building-processes

package/.llms/chunks/guides.claude-code-plugin.ambient-hooks.md

@@ -21,4 +21,4 @@ still exists for Claude Desktop, Cursor, or other MCP-only hosts, but it's unrel
 this plugin.
 
 ---
-Source: https://docs.bpmnkit.com/guides/claude-code-plugin/
+Source: https://bpmnkit.com/docs/guides/claude-code-plugin

package/.llms/chunks/guides.claude-code-plugin.configuration.md

@@ -7,7 +7,7 @@ When the plugin is enabled, Claude Code prompts for two optional values:
 | `camunda_endpoint` | Camunda 8 REST API endpoint (leave blank for local Reebe) |
 | `camunda_token` | Camunda 8 OAuth2 token (leave blank for local Reebe) |
 
-Leave both blank to use the local [Reebe engine](/cli/reebe).
+Leave both blank to use the local [Reebe engine](/docs/cli/casen#local-engine-reebe).
 
 ---
 
@@ -51,7 +51,7 @@ Design and add a Camunda AI Agent Sub-process.
 
 Works out the provider/model, prompts, and tools (each mapped via connector search or an
 existing worker job type), then compiles and mock-tests the agent step. See
-[AI Agents](/guides/ai-agents/) for the full pattern.
+[AI Agents](/docs/guides/ai-agents) for the full pattern.
 
 ---
 
@@ -123,4 +123,4 @@ List open incidents with suggested resolution actions.
 ---
 
 ---
-Source: https://docs.bpmnkit.com/guides/claude-code-plugin/
+Source: https://bpmnkit.com/docs/guides/claude-code-plugin

package/.llms/chunks/guides.claude-code-plugin.md

@@ -44,4 +44,4 @@ Or add to your project's `.claude/settings.json`:
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/claude-code-plugin/
+Source: https://bpmnkit.com/docs/guides/claude-code-plugin

package/.llms/chunks/guides.claude-code-plugin.reference-docs.md

@@ -58,4 +58,4 @@ Investigate and resolve the open incidents
 ---
 
 ---
-Source: https://docs.bpmnkit.com/guides/claude-code-plugin/
+Source: https://bpmnkit.com/docs/guides/claude-code-plugin

package/.llms/chunks/guides.deployment.ci-cd-deploy-on-push.md

@@ -44,4 +44,4 @@ console.log(`Deployed ${result.deployments.length} processes`);
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/deployment/
+Source: https://bpmnkit.com/docs/guides/deployment

package/.llms/chunks/guides.deployment.deploying-a-process.md

@@ -49,4 +49,4 @@ const instance = await client.process.startInstance({
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/deployment/
+Source: https://bpmnkit.com/docs/guides/deployment

package/.llms/chunks/guides.deployment.handling-jobs.md

@@ -47,4 +47,4 @@ const variables = await client.variables.list({
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/deployment/
+Source: https://bpmnkit.com/docs/guides/deployment

package/.llms/chunks/guides.deployment.managing-incidents.md

@@ -30,4 +30,4 @@ client.on("error", (e) => {
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/deployment/
+Source: https://bpmnkit.com/docs/guides/deployment

package/.llms/chunks/guides.deployment.md

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

package/.llms/chunks/guides.drop.md

@@ -0,0 +1,12 @@
+# Drop — Share & Co-edit
+
+[BPMN Kit Drop](/drop) is the shortest path between a diagram on your machine and the
+person who needs to look at it. Drag a file onto the page, get a short link back, send it.
+Whoever opens the link sees the diagram rendered in their browser — no account, no modeler
+install, and no Camunda cluster anywhere in the story.
+
+It is also where a review happens. A drop is not frozen: anyone with the link can take the
+edit baton, change the diagram, and everyone else watching sees the change arrive.
+
+---
+Source: https://bpmnkit.com/docs/guides/drop

package/.llms/chunks/guides.drop.reviewing-it-together.md

@@ -0,0 +1,45 @@
+# Drop — Share & Co-edit — Reviewing it together
+
+Everything below happens on the share page itself — there is nothing to install on either
+end.
+
+**Live presence.** The topbar counts the people who have the drop open, and says when one
+of them is editing. A diagram moving under a reader's eyes is only unsettling when nothing
+on the page explains it.
+
+**One writer at a time.** Editing is a baton, not a merge. Press **Edit** to claim it and
+the diagram becomes editable for you and stays live for everyone else; press **Done** to
+hand it back. A second person pressing Edit while you hold it is told who has it. There is
+no conflict resolution because there is never a second writer to conflict with.
+
+**No save button.** Changes persist as you make them, so there is no moment at which a
+reviewer can lose work by closing the tab — and none at which they can be asked whether
+they meant it. That is what makes the version log below load-bearing rather than a nicety.
+
+**Version history.** Every file keeps the original it was uploaded as, pinned and never
+overwritten, plus its ten most recent milestones. Repeated saves inside an hour collapse
+into one milestone, and a new editing session always starts its own, so a stranger editing
+at 10:45 cannot overwrite the previous editor's 10:30 state. Restoring **appends**: the
+state being replaced becomes a milestone first, so restoring can never be the thing that
+loses work. Undoing a restore is another restore.
+
+**Visual diff.** Two drops can be put side by side at `/drop/<before>/diff/<after>`: added,
+removed, changed and *moved* elements marked on synchronised canvases, with pan and zoom
+locked together. The same diff is available offline as
+[`casen diff bpmn`](/docs/cli/diff) and as a plugin in `@bpmnkit/plugins`.
+
+Editing is limited to BPMN files with a single process — the editor handles one process at
+a time — and the built-in demo drop is read-only, though **Edit a copy** will upload it as a
+drop of your own.
+
+### Rate limiting the edit baton
+
+Because a drop is editable by anyone holding the link, claiming the baton can be put behind
+a [Turnstile](https://developers.cloudflare.com/turnstile/) challenge — one challenge per
+editing session, not per keystroke. It is invisible to somebody who takes the baton once and
+edits for half an hour, and a real cost to a script that wants to rewrite every drop it can
+find. On a self-hosted deployment it is configuration (`TURNSTILE_SITE_KEY` and
+`TURNSTILE_SECRET`); with neither set, claims are not challenged.
+
+---
+Source: https://bpmnkit.com/docs/guides/drop

package/.llms/chunks/guides.drop.running-your-own.md

@@ -0,0 +1,21 @@
+# Drop — Share & Co-edit — Running your own
+
+Drop is a single Cloudflare Worker in the monorepo (`apps/drop`), MIT-licensed like
+everything else. Files live in D1 as the typed `@bpmnkit/core` model alongside the
+byte-faithful original; presence and live editing are a Durable Object per share.
+
+```sh
+pnpm --filter @bpmnkit/drop build
+wrangler d1 migrations apply bpmnkit-drop --local
+wrangler dev --local --port 8787 \
+  --var DROP_ADMIN_TOKEN:devtoken --var REPORT_IP_SALT:devsalt
+```
+
+That runs the Worker, D1 and the Durable Object in a local simulator, so the whole app works
+offline with no Cloudflare account. For a real deployment,
+`pnpm --filter @bpmnkit/drop provision` is an idempotent script that creates the database,
+applies the migrations, builds the client bundles and deploys the Worker; re-running it
+skips whatever is already in place. See `apps/drop/DEPLOY.md` for the full runbook.
+
+---
+Source: https://bpmnkit.com/docs/guides/drop

package/.llms/chunks/guides.drop.sharing-a-file.md

@@ -0,0 +1,42 @@
+# Drop — Share & Co-edit — Sharing a file
+
+Open <https://bpmnkit.com/drop> and drop a file onto the page — the whole page is the
+target — or paste one from the clipboard. `.bpmn`, `.dmn` and `.form` are all rendered;
+`.xml` and `.json` are accepted and sniffed for the kinds above.
+
+| Limit | Value |
+| --- | --- |
+| Files per drop | 20 |
+| Size of a single file | 900 KB |
+| Total per drop | 5 MB |
+| Retention | 90 days after the last view or edit |
+
+The share id is 11 base58 characters — about 64 bits, so a drop is unguessable and
+unlistable, but it is **not** access-controlled: anyone holding the link can view the
+diagram and take a turn editing it. Treat a drop the way you would treat an unlisted link,
+not the way you would treat a private repository.
+
+You can also start a drop from a diagram you just drew rather than a file you already had:
+the [browser editor](/editor) has **Share as a drop** in its main menu, which uploads the
+open diagram through the same endpoint and the same checks.
+
+### From the command line
+
+A drop is a plain HTTP upload, so `curl` works:
+
+```sh
+curl -s -X POST https://bpmnkit.com/drop/api/drops \
+  -F files=@order-process.bpmn
+# → { "shareId": "7Fq2mKd9xTs", "url": "https://bpmnkit.com/drop/7Fq2mKd9xTs", "files": [...] }
+```
+
+And the stored file comes back either as uploaded or as the parsed model:
+
+```sh
+curl -s https://bpmnkit.com/drop/<shareId>/manifest.json
+curl -s "https://bpmnkit.com/drop/<shareId>/f/order-process.bpmn"                # original bytes
+curl -s "https://bpmnkit.com/drop/<shareId>/f/order-process.bpmn?format=json"    # @bpmnkit/core model
+```
+
+---
+Source: https://bpmnkit.com/docs/guides/drop

package/.llms/chunks/guides.drop.what-drop-is-not.md

@@ -0,0 +1,12 @@
+# Drop — Share & Co-edit — What Drop is not
+
+- **Not a permission system.** Link-holders are editors. If a diagram should not be
+  editable by whoever it reaches, do not put it in a drop.
+- **Not storage.** A drop expires 90 days after it was last touched, and the version log
+  holds eleven states, not every state.
+- **Not a modeler.** It renders and edits one process at a time. For authoring, use the
+  [browser editor](/editor), the [VS Code extension](/docs/guides/vscode) or the
+  [builder API](/docs/packages/core).
+
+---
+Source: https://bpmnkit.com/docs/guides/drop

package/.llms/chunks/guides.gateways.branching-inside-sub-processes.md

@@ -24,4 +24,4 @@ Auto-join gateway insertion applies inside sub-processes the same way it does at
 top level — converging branches automatically get a matching join gateway.
 
 ---
-Source: https://docs.bpmnkit.com/guides/gateways/
+Source: https://bpmnkit.com/docs/guides/gateways

package/.llms/chunks/guides.gateways.exclusive-gateway-xor.md

@@ -38,4 +38,4 @@ Branch conditions are [FEEL expressions](https://docs.camunda.io/docs/components
 ```
 
 ---
-Source: https://docs.bpmnkit.com/guides/gateways/
+Source: https://bpmnkit.com/docs/guides/gateways