pi-herdsman 0.3.2 → 0.5.0

package/docs/agent-api.md

@@ -78,7 +78,7 @@ question.
 
 ## Pass evidence through handoffs
 
-Read [Handoffs and files](guides/handoffs.md) for `files`, result paths, body
+Read [Handoffs and files](guides/handoffs.md) for `files`, result references, body
 references, and coordination artifacts. That guide owns the evidence-transfer
 workflow; the `agent` reference owns the accepted request fields.
 

package/docs/concepts/agents.md

@@ -32,8 +32,9 @@ my-review
 
 Use the exact `agent` value from `agent list` only for
 `steer.agent`, `reply.agent`, or `close.agent` while those actions are listed
-in `available_actions`. An agent label is the live execution identity for one
-assignment, not a continuation handle.
+in `available_actions`. An agent label is the stable logical name across
+sequential generations of one managed session, not a continuation selector.
+It is a control target only for the currently live generation.
 
 Labels must begin with a lowercase letter, contain only lowercase letters,
 digits, `_`, or `-`, and be at most 32 characters.
@@ -43,14 +44,13 @@ digits, `_`, or `-`, and be at most 32 characters.
 Every managed agent has an exact Pi session. The list may expose the session
 ID and path for correlation.
 
-A session path or full UUID can be supplied as `delegate.session` to continue
-historical work. Session delegation creates a new agent generation for one new
-assignment and uses the saved session's cwd and historical context. With
-`delegate.session`, omitting `label` chooses a fresh available label derived
-from the saved definition; supplying one chooses the exact live label for that
-generation. The Pi session remains the continuation identity, not a
-live-control identity. An exact active or unresolved managed representation
-blocks concurrent activation of that session.
+A session path or full UUID can be supplied to the `continue` action to continue
+historical work. Continuation creates a new agent generation for one new
+assignment and uses the saved session's cwd, definition, logical label, and
+historical context. The caller cannot rename the continued session. The Pi
+session remains the continuation identity, not a live-control identity. An
+exact active or unresolved managed representation blocks concurrent activation
+of that session.
 
 ### herdr identities
 
@@ -104,18 +104,17 @@ and runtime state are cleaned up. Failed assignments follow the same terminal
 cleanup path.
 
 The Pi session remains available after agent cleanup. To continue the same
-conversational context, delegate a new assignment with the exact session ID or
-session path returned with the result. This creates a new agent generation,
-which uses the current effective authorized configuration for the saved agent
-definition. To derive a separate context instead, use `fork` on a definition
-delegation.
+conversational context, use `continue` with the exact session ID or session path
+returned with the result. This creates a new agent generation, which uses the
+current effective authorized configuration for the saved agent definition. To
+derive a separate context instead, use `fork` on a `delegate` action.
 
 The identities are therefore:
 
 ```text
 agent definition → configuration for new work
 Pi session       → durable conversational context and continuation identity
-agent label     → live control identity for one assignment
+agent label     → stable logical name across sequential generations; live control target only for the current generation
 ```
 
 ## See also

package/docs/concepts/lifecycle.md

@@ -102,11 +102,11 @@ exactly-once delivery for both completed and failed terminal results.
 ## Session continuation
 
 Agent cleanup does not delete the Pi session. To continue completed context,
-use the exact returned session with `delegate.session`; Pi Herdsman starts a new
-agent generation for the new assignment. The continuation uses the saved cwd
-and session history together with the current effective authorized definition
-configuration. Use `delegate.definition` with `fork` when a separate derived
-session is required.
+use the exact returned session with `continue`; Pi Herdsman starts a new agent
+generation for the new assignment. The continuation uses the saved cwd, session
+history, definition, and logical label together with the current effective
+authorized definition configuration. The caller cannot rename the continued
+session. Use `delegate` with `fork` when a separate derived session is required.
 Session continuation does not retain the old Herdr tab. A still-live
 generation may be restored from its exact managed identity, while ordinary
 same-workspace tab movement remains presentation-only and does not change

package/docs/concepts/supervision.md

@@ -60,7 +60,7 @@ correlated `staff reply`; a reply clears the pending ask only after accepted
 follow-up delivery. A replacement chief can answer an existing ask using its
 current lease and unchanged ask ID. Chief and staff message actions accept
 files; their text is prepared with the same canonical attachment renderer and
-configured global byte limits as agent messages, while durable supervision
+configured Herdsman byte limits as agent messages, while durable supervision
 records remain text-only.
 
 ## Supervision state

package/docs/development/documentation.md

@@ -121,7 +121,7 @@ registry, or another synchronization subsystem.
 - One H1 per file.
 - Short descriptive headings.
 - Current behavior only.
-- Spell the visible product name `Pi Herdsman`, the package and repository identifier `pi-herdsman`, the local coordination directory `.pi-herdsman`, the settings namespace `piHerdsman`, and the upstream dependency `herdr`.
+- Spell the visible product name `Pi Herdsman`, the package and repository identifier `pi-herdsman`, the local coordination directory `.pi-herdsman`, the configuration file `config.json`, and the upstream dependency `herdr`.
 - No backlog task numbers in product docs.
 - Keep canonical user and reference pages focused on current behavior.
 - Examples must match current accepted schemas.

package/docs/development/smoke-testing.md

@@ -15,16 +15,19 @@ Verify:
 ```sh
 node --version
 pi --version
-herdr --version
+herdr status --json
 herdr integration status
 ```
 
+The `herdr status --json` output is the Herdr 0.9 CLI protocol compatibility
+preflight. It must report a Herdr client version of `>=0.9.0`,
+`server.running` as `true`, and `server.compatible` as `true`.
+
 The supported repository contract requires:
 
 - Node `>=22.19.0`
 - Pi `>=0.84.2 <0.86.0`
-- herdr `>=0.8.0`
-- herdr Pi integration version `2` or newer
+- herdr `>=0.9.0`
 
 Run focused tests and other intermediate checks before this smoke suite. Do
 not format during smoke testing; complete smoke testing and review before the
@@ -55,7 +58,7 @@ Use the exact returned session ID or path for a follow-up assignment:
 
 ```json
 {
-  "action": "delegate",
+  "action": "continue",
   "session": "<exact session>",
   "task": "Continue the investigation with one short follow-up."
 }
@@ -65,25 +68,27 @@ Verify:
 
 - the same Pi session and session file are used;
 - a new agent generation, run ID, request ID, and pane are created;
+- the saved logical label is reused exactly (there is no continuation label override);
 - the saved conversation context is available;
 - the current effective definition configuration is used;
 - exactly one result reaches the owner;
 - cleanup removes the second agent, pane, mailbox, and runtime.
 
-While the continuation assignment is active, submit another
-`delegate.session` request for the same exact session. Verify it fails with
+While the continuation assignment is active, submit another `continue` request
+for the same exact session. Verify it fails with
 `agent_busy`, creates no duplicate agent or pane, and leaves the active
 assignment unchanged. After both assignments finish, `agent list` must show
 no completed idle agent.
 
-## Historical session delegation
+## Historical session continuation
 
 Use an exact saved session path or full UUID.
 
 Verify:
 
 - saved definition and cwd are respected;
-- session delegation uses the saved cwd;
+- the saved logical label is reused exactly;
+- session continuation uses the saved cwd;
 - current effective agent override values are used for the new agent
   generation;
 - the exact session continues.
@@ -189,9 +194,9 @@ Verify the native Definitions selector shows:
 Structured `agent list` should still retain exact deterministic metadata.
 
 Select a disposable bundled, project, or global definition and change its
-model, thinking, and enabled state. Confirm that project discovery requires a
-trusted project's `piHerdsman.projectAgents: true` setting and that these edits
-write global overrides only, not project files.
+model, thinking, and enabled state. Confirm that project discovery requires Pi
+project trust and that these edits write global overrides only, not project
+files.
 
 Verify unrelated frontmatter and body remain unchanged, `Use default` removes
 only the selected field, fresh definition delegations and session continuations
@@ -249,7 +254,7 @@ substitutes for these checks.
 | Discover leads across multiple workspaces                                                                                            | NOT RUN |
 | Exclude managed agents and the active Chief from leads                                                                               | NOT RUN |
 | Agent exclusion uses the production validated snapshot and stale/ambiguous generations fail closed                                   | NOT RUN |
-| Herdr `agent_status ?? status` lifecycle normalization is reflected                                                                  | NOT RUN |
+| Herdr `agent_status` lifecycle normalization is reflected                                                                            | NOT RUN |
 | Nested agent aggregation attaches only to the proven lead                                                                            | NOT RUN |
 | A blocked agent does not mark its lead `needs you`                                                                                   | NOT RUN |
 | Duplicate live agents, coordination records, or agent evidence fail closed                                                           | NOT RUN |

package/docs/getting-started.md

@@ -10,9 +10,8 @@ path.
 
 You need:
 
-- [herdr](https://github.com/herdrdev/herdr) `>=0.8.0`;
+- [herdr](https://github.com/herdrdev/herdr) `>=0.9.0`;
 - Pi `>=0.84.2 <0.86.0` (the version range tested for this release);
-- herdr Pi integration version `2` or newer;
 - Node `>=22.19.0`.
 
 Install or refresh the herdr Pi integration:
@@ -83,10 +82,10 @@ Stop all…
 
 `Running` is the complete authoritative live-agent inventory and focuses the
 selected pane directly. `Definitions` manages the effective bundled, project,
-and global agent definitions. Project definitions participate only when the
-trusted project setting `piHerdsman.projectAgents` is `true`; effective precedence
-is bundled < project < global. `Layout` controls whether newly started agents
-use tabs or splits. `Stop all…` is destructive emergency control.
+and global agent definitions. Trusted projects contribute definitions from
+`.pi/agents/`; effective precedence is bundled < project < global. `Layout`
+controls whether newly started agents use tabs or splits. `Stop all…` is
+destructive emergency control.
 
 See [`/agents` commands](reference/commands.md) for exact behavior.
 
@@ -127,9 +126,9 @@ See [Status widget](reference/status-widget.md) for exact state, refresh, and
 rendering behavior.
 
 To continue a completed assignment with its existing conversational context,
-use the exact `session_id` returned with its result in a new `delegate.session`
-request. This starts a new agent generation with the saved session and current
-effective definition configuration.
+use the exact `session_id` returned with its result in a new `continue` request.
+This starts a new agent generation with the saved session and current effective
+definition configuration.
 
 ## 7. Recover only when needed
 

package/docs/guides/agent-definitions.md

@@ -29,26 +29,23 @@ Project definitions are optional and live in the current project:
 <cwd>/.pi/agents/
 ```
 
-For example:
+Pi Herdsman discovers project definitions when Pi considers the project
+trusted. Precedence is:
 
 ```text
-.pi/
-├── settings.json
-└── agents/
-    └── reviewer.md
+bundled < project < global
 ```
 
-with project settings:
+Global definitions remain final user policy. For example:
 
-```json
-{ "piHerdsman": { "projectAgents": true } }
+```text
+.pi/
+└── agents/
+    └── reviewer.md
 ```
 
-They are discovered only when the trusted project settings contain
-`piHerdsman.projectAgents: true`. Precedence is `bundled < project < global`;
-global definitions remain final user policy. Project definitions apply only to
-their project cwd, and the Definitions UI writes global overrides, never
-project files.
+Project definitions apply only to their project cwd, and the Definitions UI
+writes global overrides, never project files.
 
 When Pi uses a custom agent directory, the global definitions live under that
 agent directory's `agents/` subdirectory.
@@ -56,6 +53,35 @@ agent directory's `agents/` subdirectory.
 A project or global definition whose `name` matches a lower-precedence
 definition overlays it. An unmatched definition is standalone.
 
+### Permission-aware extensions
+
+Agent definitions may include a `permission:` mapping for compatible
+permission-aware Pi extensions.
+
+[`pi-permission-system`](https://github.com/gotgenes/pi-packages/tree/main/packages/pi-permission-system)
+can consume the same global or trusted project-local agent definition as Pi
+Herdsman:
+
+```yaml
+---
+name: reviewer
+tools: ["read", "ls", "find", "grep"]
+permission:
+  "*": deny
+  read: allow
+  ls: allow
+  find: allow
+  grep: allow
+---
+```
+
+Pi Herdsman accepts and preserves `permission:` but does not evaluate its
+contents or make authorization decisions from it. Managed agents also publish
+the conventional active-agent identity and subagent lineage metadata used by
+compatible extensions. Permission policy is effective only when the
+compatible permission extension is loaded in that Pi session. The permission
+extension is optional; Pi Herdsman does not install or depend on it.
+
 ## Enable or disable a definition
 
 Definitions are enabled by default. Set `enabled: false` in a matching project
@@ -76,7 +102,7 @@ referencing a disabled definition can remain discoverable, but is rejected durin
 assignment or fresh agent startup with an explicit disabled-definition reason
 rather than silently dropping that definition.
 
-Definition and session delegations reject disabled definitions with an
+`delegate` and `continue` reject disabled definitions with an
 actionable error. An already active agent may finish and remains controllable
 according to its current available actions; disabling a definition does not
 mutate that assignment.

package/docs/guides/customizing-agents.md

@@ -229,7 +229,7 @@ Enable and disable write the scalar `enabled` field in the same global override.
 Removing that field inherits the bundled value, or `true` when no source
 declares it.
 
-Changes affect future definition delegations and session continuations, whose
+Changes affect future `delegate` assignments and `continue` assignments, whose
 runtime configuration comes from the current effective definition. They do not
 mutate an already-running agent or the lead Pi session.
 

package/docs/guides/handoffs.md

@@ -4,7 +4,7 @@
 
 Pi Herdsman has two text-file mechanisms with different purposes:
 
-- `files` supplies evidence to delegate (definition or session), steer, reply,
+- `files` supplies evidence to delegate, continue, steer, reply,
   or ask_owner.
 - whole-line body `@file` references put definition-owned text into the agent
   system prompt when a new agent generation is built.
@@ -14,7 +14,7 @@ canonical local references and are not copied or snapshotted.
 
 ## Message `files`
 
-For `delegate` with `definition`, `delegate` with `session`, `steer`, and
+For `delegate`, `continue`, `steer`, and
 `reply`, make the message self-contained. Do not attach or mention agent
 instruction files such as `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, or equivalents
 merely because they exist; rely on normal project or runtime discovery.
@@ -34,7 +34,10 @@ Example:
   "action": "delegate",
   "definition": "reviewer",
   "task": "Review the implementation against the approved plan.",
-  "files": [".pi-herdsman/plan.md", "/tmp/implementation-result"]
+  "files": [
+    ".pi-herdsman/plan.md",
+    "result:550e8400-e29b-41d4-a716-446655440000"
+  ]
 }
 ```
 
@@ -52,17 +55,35 @@ A reference-only file uses a self-closing tag:
 <file name="/absolute/canonical/path" bytes="123" />
 ```
 
-`name` is the canonical absolute path and `bytes` is the observed file size.
-A body means the complete submission-time UTF-8 snapshot was embedded; a
-self-closing tag means only the path and size reference was supplied. File
-content remains raw text. This markup frames evidence for the model and is not
-a security boundary.
+For an ordinary file, `name` is the canonical absolute path and `bytes` is the
+observed file size. For a result reference, an embedded file uses the exact
+`result:<request-id>` as `name`:
 
-`files` is supported by `delegate` with `definition`, `delegate` with `session`,
+```xml
+<file name="result:550e8400-e29b-41d4-a716-446655440000" bytes="123">
+contents
+</file>
+```
+
+A result that is supplied by reference keeps both identities in its
+self-closing envelope:
+
+```xml
+<file name="result:550e8400-e29b-41d4-a716-446655440000" path="/absolute/canonical/path" bytes="123" />
+```
+
+A body means the complete submission-time UTF-8 snapshot was embedded. For an
+ordinary file, a self-closing tag carries its canonical path and observed byte
+size; for a result reference, it carries the logical result name, the physical
+path attribute, and observed byte size. File content remains raw text. This
+markup frames evidence for the model and is not a security boundary.
+
+`files` is supported by `delegate`, `continue`,
 `steer`, `reply`, and `ask_owner`. For
 controller actions, relative paths resolve from the calling controller's cwd;
-for `ask_owner`, they resolve from the managed agent's cwd. Every accepted
-path is displayed using its canonical absolute path.
+for `ask_owner`, they resolve from the managed agent's cwd. Accepted ordinary
+filesystem paths retain canonical absolute-path names; `result:<request-id>`
+inputs retain the logical result reference as the model-facing name.
 
 Supplied paths must resolve to readable regular files. Missing, broken,
 unreadable, and non-regular paths reject the whole operation. Canonical
@@ -79,8 +100,10 @@ For each regular file:
 
 - complete strict UTF-8 text without NUL bytes is embedded when the complete
   message fits the effective configured `mailboxPayloadLimitBytes` boundary;
-- invalid UTF-8, NUL-containing, binary, and non-fitting files are represented
-  only by a canonical local path and observed byte size.
+- invalid UTF-8, NUL-containing, binary, and non-fitting ordinary files are
+  represented only by their canonical local path and observed byte size;
+  result references retain their logical name and carry the physical path and
+  observed byte size.
 
 The fixed 1 MiB mailbox protocol safety ceiling is a separate read limit for
 mailbox records; it does not replace the configured admission limit for new
@@ -92,7 +115,10 @@ or disappear after submission, and the recipient must already have local
 filesystem/tool access to inspect them. `files` supplies evidence and does not
 grant runtime capabilities.
 
-Files are read through their canonical `realpath` target.
+Files are read through their canonical `realpath` target. Ordinary file inputs
+are rendered with that canonical path; result references retain the
+`result:<request-id>` name so recipients can pass the same reference through
+`files` again.
 
 ## Canonical deduplication
 
@@ -184,22 +210,30 @@ definition configuration while preserving the saved Pi session context.
 
 ## Result handoff
 
-Successful agent completion may expose a private `resultPath`.
+Successful agent completion exposes a canonical `resultRef` such as
+`result:550e8400-e29b-41d4-a716-446655440000`.
 
-For dependent work, pass the exact result path through `files` rather than
-copying a large result manually:
+Pass the exact result reference directly through `files` rather than copying a
+large result or reconstructing its physical path:
 
 ```json
 {
   "action": "delegate",
   "definition": "reviewer",
   "task": "Review the implementation described in the supplied result.",
-  "files": ["/exact/resultPath"]
+  "files": ["result:550e8400-e29b-41d4-a716-446655440000"]
 }
 ```
 
-Successful agent completions persist their complete output at the canonical
-`resultPath`; they do not receive a separate completion overflow path.
+`files` accepts ordinary readable regular local file paths and result
+references. A result reference resolves internally to the normal private
+result file under Pi Herdsman's durable data directory; it is still validated,
+canonicalized, and deduplicated like any other file. Copy the exact reference
+returned by completion. Do not guess or reconstruct the underlying path.
+Completion results live under Pi's agent data directory
+(`~/.pi/agent/pi-herdsman/results` by default, respecting Pi's configured agent
+directory) rather than the OS temporary directory, so result handoffs are not
+subject to temporary-directory cleanup.
 Oversized non-completion registered-tool output may additionally expose
 `full_output_path` when overflow persistence succeeds. Model-visible content
 remains bounded in both cases.

package/docs/guides/recovery.md

@@ -65,7 +65,7 @@ Do not close solely because of inactivity.
 
 ## Startup failure
 
-Fresh and historical-session delegation startup is bounded.
+Fresh delegation and historical-session continuation startup is bounded.
 
 When herdr returns a structured failure, Pi Herdsman preserves it. When startup
 returns empty or malformed output and no better structured error is available,
@@ -116,16 +116,17 @@ not the normal model orchestration interface.
 
 ## Historical session failure
 
-A `delegate` with `session` requires an exact session path or full UUID.
+A `continue` requires an exact session path or full UUID.
 
 The saved session header must contain a non-empty working directory. Session
-delegation uses that saved cwd and does not accept a caller-supplied `cwd`.
+continuation uses that saved cwd and does not accept a caller-supplied `cwd`.
 
-The saved agent-definition name is resolved against the current effective
-definition roster. If it no longer exists, session delegation fails instead of guessing a
-replacement. The definition must also be enabled and authorized for the current
+The saved agent-definition name and logical label are restored from the managed
+session identity. If the definition no longer exists, continuation fails instead
+of guessing a replacement; a missing or malformed session identity also fails
+closed. The definition must also be enabled and authorized for the current
 controller, and its current effective configuration is used for the new agent
-generation.
+generation. Continuation cannot override or regenerate its saved label.
 
 An exact session that is already represented by active or unresolved managed
 work cannot be activated concurrently. The session-start exclusion applies to

package/docs/reference/agent-definition-schema.md

@@ -57,15 +57,15 @@ Global definitions by default:
 A matching project or global name overlays the lower-precedence definition.
 
 An unmatched project or global definition is standalone. Project definitions
-are loaded from `<cwd>/.pi/agents/` only when trusted project settings set
-`piHerdsman.projectAgents` to `true`. Precedence is `bundled < project < global`.
+are loaded from `<cwd>/.pi/agents/` when Pi considers the project trusted.
+Precedence is `bundled < project < global`.
 
 All effective definitions are sorted and validated together, including every
 `agents` reference.
 
 `enabled` controls definition availability. A disabled definition remains in the
 lead roster so it can be enabled again, but owner-visible definition lists omit
-it. Definition and session delegations reject a disabled definition. An already
+it. `delegate` and `continue` reject a disabled definition. An already
 active agent may finish and remains controllable according to its current
 available actions; disabling a definition does not mutate that assignment.
 
@@ -74,7 +74,7 @@ available actions; disabling a definition does not mutate that assignment.
 | Field                   | Accepted value                                                        | Omitted/default behavior                                          | Runtime/composition behavior                                                                           |
 | ----------------------- | --------------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
 | `name`                  | non-empty string                                                      | required                                                          | Effective definition identity.                                                                         |
-| `enabled`               | boolean                                                               | `true`                                                            | `false` makes definition and session delegation unavailable; it does not mutate an active agent.       |
+| `enabled`               | boolean                                                               | `true`                                                            | `false` makes `delegate` and `continue` unavailable; it does not mutate an active agent.               |
 | `description`           | string                                                                | absent                                                            | Display/selection description.                                                                         |
 | `model`                 | non-empty string                                                      | Pi default/current launch behavior                                | Passed as Pi model selection.                                                                          |
 | `thinking`              | `off`, `minimal`, `low`, `medium`, `high`, `xhigh`, `max`, or `false` | Pi default/current launch behavior                                | `false` launches as `off`.                                                                             |
@@ -84,6 +84,7 @@ available actions; disabling a definition does not mutate that assignment.
 | `noBuiltinTools`        | boolean                                                               | Pi normal built-in tool policy                                    | `true` emits `--no-builtin-tools`.                                                                     |
 | `tools`                 | array of non-empty strings                                            | no explicit allowlist                                             | Passed to Pi as a source-agnostic tool-name allowlist; matching overlay replaces whole array.          |
 | `excludeTools`          | array of non-empty strings                                            | no explicit exclusions                                            | Passed to Pi as source-agnostic tool-name exclusions; matching override replaces whole array.          |
+| `permission`            | mapping                                                               | absent                                                            | Opaque interoperability policy for permission-aware extensions; Pi Herdsman does not evaluate it.      |
 | `noSkills`              | boolean                                                               | skills disabled unless `inheritSkills: true`                      | Controls Pi native skill discovery; explicit `skills` values are still passed separately.              |
 | `inheritSkills`         | boolean                                                               | does not enable by itself unless `true`                           | `true` changes omitted `noSkills` default so native skills remain available. Explicit `noSkills` wins. |
 | `skills`                | array of non-empty strings                                            | no explicit skill arguments                                       | Each value is passed unchanged as a Pi skill path/resource.                                            |
@@ -93,6 +94,10 @@ available actions; disabling a definition does not mutate that assignment.
 | `inheritProjectContext` | boolean                                                               | `true` only for definition name `delegate`; otherwise `false`     | Controls project context-file inheritance.                                                             |
 | `inheritGlobalContext`  | boolean                                                               | follows effective `inheritProjectContext`                         | Controls global context-file inheritance.                                                              |
 
+`permission` is reserved for compatible permission extensions. Pi Herdsman
+accepts and preserves the mapping but does not validate its internal policy
+schema or make authorization decisions from it.
+
 Arrays supplied by an override replace the complete inherited array, including
 an explicit `[]`.
 
@@ -230,10 +235,13 @@ Pi base system prompt
 selected project/global context-file additions
     ↓
 shared herdr agent guidance
+    ↓
+<active_agent name="<definition>"/>
 ```
 
 The final effective body and shared guidance are delivered through private
-temporary prompt snapshots.
+temporary prompt snapshots. The active-agent tag is appended directly as
+interoperability metadata for compatible Pi extensions.
 
 ## Complete override example