Apply style guide: add Source link to flows plugin page

build-an-oracle/reference/bundled-plugins/flows.mdx

@@ -4,6 +4,8 @@
 icon: "diagram-project"
 ---
 
+**Source:** [`packages/oracle-runtime/src/plugins/flows/`](https://github.com/ixoworld/ixo-oracles-boilerplate/blob/main/packages/oracle-runtime/src/plugins/flows/)
+
 | Attribute | Value |
 | --- | --- |
 | Feature key | `flows` |
@@ -21,7 +23,7 @@
 
 `flows` is a flow **builder** capability. The agent designs reusable flow *templates* — steps (action blocks), the data wired between them, conditions, schedules, assignees, and forms — and reads the live state of running flows. The agent never executes, signs, mints, holds a key, or enters a PIN; **the user runs the flow in the portal**, where signing and any state transitions happen.
 
 It coexists with the [`editor`](/build-an-oracle/reference/bundled-plugins/editor) plugin: flows are written as documents over the `@ixo/editor` Qi Flow engine, using oracle-runtime's native yjs reads/writes. The plugin does not require `editor` to be loaded — it contributes its own tool surface.
 
 ## When to use it
 
@@ -35,7 +37,7 @@
 
 - Editing prose, pages, or BlockNote documents — use [`editor`](/build-an-oracle/reference/bundled-plugins/editor).
 - Actually executing, running, or signing a step — that happens in the portal, by the user. No transaction tooling lives here.
 - IXO entity lookups — use [`domain-indexer`](/build-an-oracle/reference/bundled-plugins/domain-indexer).
 
 ## Environment variables
 
@@ -43,7 +45,7 @@
 
 | Var | Required | Description |
 | --- | --- | --- |
 | `MATRIX_BASE_URL` | yes (base schema) | Matrix homeserver base URL. |
 | `MATRIX_ORACLE_ADMIN_USER_ID` | yes (base schema) | Admin Matrix user ID. |
 | `MATRIX_ORACLE_ADMIN_ACCESS_TOKEN` | yes (base schema) | Admin Matrix access token. |
 
@@ -85,10 +87,10 @@
 - `connect_steps` — wire an upstream output to a downstream input.
 - `update_step` — per-block / delta edit that never disturbs sibling steps.
 
 **Settings** — per-step mutators with narrow scope.
 
 - `set_step_inputs` — set or replace a step's static inputs.
 - `set_step_conditions` — set `props.conditions` directly in the frontend evaluator's operator vocabulary.
 - `set_step_schedule` — set or clear a step's schedule.
 - `set_step_assignment` — set or clear a step's assignee.
 - `set_step_confirmation` — toggle the user-confirmation gate before a step runs.
@@ -104,7 +106,7 @@
 
 Follow a tight loop: **discover → plan → confirm → build → hand off.** One discovery pass, one short plan, one user confirmation, then build with the authoring tools. The plugin injects an operating guide into the system prompt while it is loaded — see the `FLOWS_OPERATING_GUIDE` exported from the package.
 
 Conditions are written **directly as `props.conditions`** in the frontend evaluator's operator vocabulary; the compiler's verbatim operators never evaluate at runtime.
 
 ## Opt in