pi-background-tasks 2.6.0 → 2.6.2

package/docs/INDEX.md

@@ -133,7 +133,7 @@ Generated navigation for every package-local documentation page. This index inte
 | command | `bg-clear` | `command:bg-clear` | `always` | yes | `src/extension.ts:793` |
 | command | `bg-tasks` | `command:bg-tasks` | `always` | yes | `src/extension.ts:785` |
 | command | `bg-update` | `command:bg-update` | `always` | yes | `src/extension.ts:801` |
-| command | `claude-cache` | `command:claude-cache` | `feature:attribution` | yes | `src/core/anthropic-attribution.ts:3206` |
+| command | `claude-cache` | `command:claude-cache` | `feature:attribution` | yes | `src/core/anthropic-attribution.ts:3220` |
 | command | `fusion` | `command:fusion` | `feature:fusion` | yes | `src/fusion-extension.ts:1083` |
 | command | `fusion-models` | `command:fusion-models` | `feature:fusion` | yes | `src/fusion-extension.ts:1123` |
 | command | `jobs` | `command:jobs` | `always` | yes | `src/extension.ts:850` |

package/docs/commands/claude-cache.md

@@ -12,7 +12,7 @@ covers_sources: []
 <!-- pi-docs:begin name="command-contract-claude-cache" generator="scripts/docs/generate.mjs" -->
 | Command | Availability | Default | Description | Provenance |
 | --- | --- | --- | --- | --- |
-| `/claude-cache` | `feature:attribution` | yes | Show or set Claude cache retention for this session (short, long, default) | `src/core/anthropic-attribution.ts:3206` |
+| `/claude-cache` | `feature:attribution` | yes | Show or set Claude cache retention for this session (short, long, default) | `src/core/anthropic-attribution.ts:3220` |
 <!-- pi-docs:end name="command-contract-claude-cache" -->
 
 Show or change the Anthropic cache-retention preference for the current session. Under the initialized-host contract, the command is registered only when `PI_BG_FEATURES` includes the ambient `attribution` capability (enabled by default); disabling that capability removes the command together with the parent provider/hooks. Its generated default availability is not a pre-bind availability guarantee: bare SDK sessions and empty/mode-only reloads require the explicit binding described in [Anthropic attribution](../subsystems/anthropic-attribution.md#initialized-host-sdk-contract-and-blocker).

package/docs/manifest.json

@@ -25,7 +25,7 @@
       "state": "stale-authored-prose"
     },
     {
-      "authored_body_sha256": "sha256:63e32141e9ae60dcc02b3b5e757c5ce39ab38adb1edb9b34ac459894607651fb",
+      "authored_body_sha256": "sha256:1668305b87b152b6fc98ba3f7bcf029269d4f042a4b39192232a3cc472fdc2ae",
       "covers_sources": [
         "extensions/anthropic-attribution-child.ts",
         "extensions/anthropic-attribution.ts",
@@ -79,7 +79,7 @@
       "state": "stale-authored-prose"
     },
     {
-      "authored_body_sha256": "sha256:5555c0344c4bdba65e71575163febe4d672a60a5ff944c260604270ceb4cdc69",
+      "authored_body_sha256": "sha256:d1e5920202ddc1368fa94148ad96906784937084d6ef5a72f1153f8dc3a4374e",
       "covers_sources": [
         "extensions/delegate-child.ts",
         "src/core/delegate/artifacts.ts",
@@ -135,7 +135,7 @@
       "state": "stale-authored-prose"
     },
     {
-      "authored_body_sha256": "sha256:b3b66442d3fdb151d99c93f2a536f93e85eec6604a074424d34929b0bce7935a",
+      "authored_body_sha256": "sha256:e1fdd8fbce4cb918fb8f361b4c13b1f78fadd455a5a18b22836a6f0b466f4119",
       "covers_sources": [
         "extensions/background-tasks.ts",
         "src/core/config.ts",
@@ -909,7 +909,7 @@
     "image": "https://raw.githubusercontent.com/ismailsaleekh/pi-background-tasks/main/logo.png",
     "name": "pi-background-tasks",
     "type": "module",
-    "version": "2.6.0"
+    "version": "2.6.2"
   },
   "public_surface_ids": [
     "command:bg",
@@ -990,7 +990,7 @@
         "id": "command:claude-cache",
         "kind": "command",
         "name": "claude-cache",
-        "source": "src/core/anthropic-attribution.ts:3206"
+        "source": "src/core/anthropic-attribution.ts:3220"
       },
       {
         "availability": "feature:fusion",

package/docs/operations/releasing.md

@@ -57,7 +57,7 @@ Use `npm pack --dry-run --json` output as the payload source of truth. Verify at
 - authoritative `extensions/` and runtime `src/` sources remain included for public source/API compatibility;
 - `docs/`, `README.md`, `TESTING.md`, `TEST_PLAN.md`, `PUBLISHING.md`, `BACKGROUND-TASKS-INSTRUCTIONS.md`, `THIRD_PARTY_NOTICES.md`, root `logo.png`, and `LICENSE` are included per current `package.json.files`;
 - tests, scripts, node_modules, local `.pi/` artifacts, generated evidence not meant for runtime, and nested tarballs are excluded;
-- TypeBox remains a Pi-provided peer and no private/nested runtime TypeBox copy is bundled;
+- TypeBox and `@earendil-works/pi-ai` remain Pi-provided peers and no private/nested runtime copies are bundled;
 - production dependencies use registry versions only; no exotic URL/git/file subdependency is shipped;
 - docs/assets/gateway/logo inclusion matches `package.json.files` exactly.
 

package/docs/operations/testing.md

@@ -72,7 +72,7 @@ Here, **cold** means a fresh process and empty JavaScript/Jiti module cache. It
 
 The benchmark requires an explicit `--runtime source|compiled` choice. Published package entrypoints select the compiled JavaScript distribution, while source mode remains an authoritative development control. Process-only startup no longer statically imports delegate/Fusion facades, dock UI, the attribution transport, or attested execution; enabled registrations still load their lightweight facade before the extension factory resolves. Neither mode supports a native-Windows or vendor compiled-Bun timing claim without separate runs.
 
-The package gate separately walks literal deferred imports, verifies every source target, builds its compiled counterpart, and requires the complete `dist/` closure in the tarball. A packed-copy regression then removes one verifier/producer module from an otherwise real tarball: package startup and immediate inventory still work, the first producer invocation fails with the bounded module-specific error, and no delegate artifact is created. This characterizes damaged payload behavior without weakening the real payload-closure check.
+The package gate separately walks literal deferred imports, verifies every source target, builds its compiled counterpart, and requires the complete `dist/` closure in the tarball. A packed-copy regression installs only the real production Turndown/Domino closure, proves all Pi SDK packages and TypeBox are absent beneath the package, and loads both compiled entrypoints through Pi's real SDK loader with default capabilities. Before damage injection it invokes `bg_delegate`, `bg_run_pi_attested`, `fusion_reason`, the task manager, and the Fusion selector; each must pass module loading and reach its expected post-import semantic boundary. It then removes one delegate producer module: startup and immediate inventory still work, the first producer invocation fails with the bounded module-specific error, and no delegate artifact is created. A source-graph guard also pins the host import on every internal dynamic-import issuer. This distinguishes supported package entrypoint traversal from unsupported direct Node imports of private `dist/src/**` chunks, without borrowing development dependencies or weakening the real payload-closure check.
 
 Lazy lifecycle SDK coverage deliberately blocks Fusion cleanup while asserting the shared synchronous fence has already closed delegate, result, command/UI, and both Fusion lanes. A real `AgentSession.reload()` control lets production delegate preparation finish a complete artifact tree before returning, then proves the unregistered transaction is rolled back with no starter or residual run bytes. A separate claim race proves shutdown cannot consume Fusion usage without a successful retrieval, and a registered-task control proves rollback never deletes registry-owned artifacts.
 

package/docs/operations/troubleshooting.md

@@ -42,6 +42,8 @@ Start from the symptom, verify the source-owned doc, then apply the remediation.
 | Fusion research URL rejected | Source URL is not declared/public http(s), has credentials, resolves to blocked address class, or redirects unsafely | Provide declared public source URLs with purpose; targeted fetch is not search. |
 | `/fusion-models` rejects in non-TUI mode | Selector requires interactive UI | Use an interactive Pi TUI session to edit config; headless path should fail loudly. |
 | `/bg-update` shows no update | Offline/opt-out/current-version/registry failure path | Check `PI_OFFLINE`, `PI_BG_DISABLE_UPDATE_CHECK`, `PI_BG_REGISTRY_URL`; update check is one-shot and non-blocking. |
+| `Cannot find package '@earendil-works/pi-ai' imported from .../dist/src/core/anthropic-attribution.js` during Pi startup | A stale compiled attribution gateway crossed its lazy native-import boundary before resolving Pi's host alias | Update the package to a fixed build. Do not install or bundle a private Pi SDK copy; the gateway must resolve and inject the host-owned adapter. Start temporarily with `PI_BG_FEATURES=process pi` or `pi -ne`. |
+| A custom extension directly imports `pi-background-tasks/dist/src/**` and reports a missing Pi SDK package | Private compiled implementation chunks were imported through Node instead of the package's Pi entrypoints | Load the package through `package.json.pi.extensions` or its documented public surfaces. If an actual package command/tool fails, report that invocation and full stack; do not install duplicate Pi SDK packages to make a private-chunk probe pass. |
 | TypeBox/compat failure | Installed package resolved a private/nested TypeBox or used removed APIs | Keep TypeBox as Pi-provided peer and verify installed payload. See `docs/operations/releasing.md`. |
 
 Detailed references: EventBus API (`docs/api/eventbus-v1.md`), context budgeting (`docs/concepts/context-projection-and-budgeting.md`), launch/durability (`docs/subsystems/child-launch-durability-and-safety.md`), runtime registry (`docs/reference/runtime-contracts.md`), testing (`docs/operations/testing.md`), releasing (`docs/operations/releasing.md`).

package/docs/reference/runtime-contracts.md

@@ -63,7 +63,7 @@ This generated registry lists production environment-variable references, runtim
 | `path` | read | `src/core/common.ts:963` |
 | `Path` | read | `src/core/common.ts:963` |
 | `PATH` | read | `src/core/common.ts:1017`<br>`src/core/common.ts:963`<br>`src/core/pi-launch.ts:425` |
-| `PI_ANTHROPIC_ACCOUNT_CONFIG_PATH` | read | `src/core/anthropic-attribution.ts:893` |
+| `PI_ANTHROPIC_ACCOUNT_CONFIG_PATH` | read | `src/core/anthropic-attribution.ts:896` |
 | `PI_API_BASE_URL` | remove | `src/core/attested-pi-run.ts:248`<br>`src/core/fusion/pi-child.ts:100` |
 | `PI_API_KEY` | remove | `src/core/attested-pi-run.ts:248`<br>`src/core/fusion/pi-child.ts:100` |
 | `PI_AUTH_FILE` | remove | `src/core/attested-pi-run.ts:248`<br>`src/core/fusion/pi-child.ts:100` |
@@ -82,7 +82,7 @@ This generated registry lists production environment-variable references, runtim
 | `PI_BG_REGISTRY_URL` | read | `src/extension.ts:665` |
 | `PI_BG_SHELL` | read | `src/core/common.ts:1042` |
 | `PI_BG_SHELL_PATH` | read | `src/core/common.ts:1043` |
-| `PI_CACHE_RETENTION` | read, write | `src/core/anthropic-attribution.ts:658`<br>`src/core/anthropic-attribution.ts:669`<br>`src/core/fusion/claude-cache.ts:57`<br>`src/core/fusion/pi-child.ts:273`<br>`src/core/fusion/pi-child.ts:274` |
+| `PI_CACHE_RETENTION` | read, write | `src/core/anthropic-attribution.ts:661`<br>`src/core/anthropic-attribution.ts:672`<br>`src/core/fusion/claude-cache.ts:57`<br>`src/core/fusion/pi-child.ts:273`<br>`src/core/fusion/pi-child.ts:274` |
 | `PI_FUSION_CANDIDATE_OUTPUT_RECOVERY_PATH` | read, remove, write | `src/core/fusion/pi-child.ts:100`<br>`src/core/fusion/pi-child.ts:1879`<br>`src/fusion-child-extension.ts:599` |
 | `PI_FUSION_RESEARCH_ENABLED` | read, remove, write | `src/core/fusion/pi-child.ts:100`<br>`src/core/fusion/pi-child.ts:1902`<br>`src/fusion-child-extension.ts:608` |
 | `PI_FUSION_SOURCE_POLICY_PATH` | read, remove, write | `src/core/fusion/pi-child.ts:100`<br>`src/core/fusion/pi-child.ts:1903`<br>`src/fusion-child-extension.ts:555` |
@@ -95,7 +95,7 @@ This generated registry lists production environment-variable references, runtim
 | `PI_SESSION_FILE` | remove | `src/core/delegate/launch.ts:330`<br>`src/core/fusion/pi-child.ts:100` |
 | `PI_SESSION_ID` | remove | `src/core/delegate/launch.ts:330`<br>`src/core/fusion/pi-child.ts:100` |
 | `PI_SKIP_VERSION_CHECK` | write | `src/core/delegate/launch.ts:352`<br>`src/core/fusion/pi-child.ts:272` |
-| `PIPELINE_ANTHROPIC_ATTRIBUTION_AUDIT_PATH` | read | `src/core/anthropic-attribution.ts:1170` |
+| `PIPELINE_ANTHROPIC_ATTRIBUTION_AUDIT_PATH` | read | `src/core/anthropic-attribution.ts:1173` |
 | `SHELL` | read | `src/core/common.ts:1102` |
 | `SystemRoot` | read | `src/core/windows-taskkill.ts:96` |
 | `WINDIR` | read | `src/core/windows-taskkill.ts:101` |

package/docs/subsystems/anthropic-attribution.md

@@ -13,9 +13,9 @@ This subsystem owns the package-wide Anthropic subscription attribution provider
 
 ## Global package behavior
 
-`package.json.pi.extensions` loads the compiled `dist/extensions/anthropic-attribution.js` entrypoint before the compiled background-task entrypoint; `extensions/anthropic-attribution.ts` remains its authoritative source. The light entrypoint parses the complete shared configuration before dynamically loading the attribution transport. With the default `attribution` capability, it activates the accepted implementation from `session_start`, after Pi has bound its public provider runtime; without that token the transport module is not imported and no parent provider, attribution lifecycle hooks, duplicate-owner responder, or `/claude-cache` command is registered. Invalid feature or dock configuration fails before ambient activation.
+`package.json.pi.extensions` loads the compiled `dist/extensions/anthropic-attribution.js` entrypoint before the compiled background-task entrypoint; `extensions/anthropic-attribution.ts` remains its authoritative source. The light entrypoint statically resolves the host-owned `anthropicMessagesApi` through Pi's alias-aware extension loader, parses the complete shared configuration, and then dynamically loads the attribution transport with that adapter injected. The deferred core has no runtime import of a Pi host package, so a native dynamic import cannot look for a private `@earendil-works/pi-ai` beside a production-only package installation. With the default `attribution` capability, the wrapper activates the accepted implementation from `session_start`, after Pi has bound its public provider runtime; without that token the transport module is not imported and no parent provider, attribution lifecycle hooks, duplicate-owner responder, or `/claude-cache` command is registered. Invalid feature or dock configuration fails before ambient activation.
 
-Before activation, the wrapper snapshots the effective provider plus the public legacy/native registration through `ctx.modelRegistry`. The accepted factory's provider call is then immediate rather than queued. A thrown application failure occurs before its command, hooks, or claim responder are published. A successful installation is owned only after a new current legacy-config object and changed effective provider are observed; that exact config object is the instance token. On shutdown the wrapper acts only while that token is still current. A later legacy or native owner is left untouched. Otherwise it restores the prior native registration directly, clears the package layer with the captured effective provider before reapplying a prior legacy config, or—when there was no prior dynamic registration—uses public unregister only after the exact token/later-owner checks to restore dynamic-registration absence and the captured built-in effective object. It never blindly deletes another owner's provider and never reads private host state. A subsequent real reload with attribution disabled therefore restores the host's prior public registration state. When enabled, the transport remains provider-gated: non-Anthropic sessions and payloads are unchanged.
+Before activation, the wrapper snapshots the effective provider plus the public legacy/native registration through `ctx.modelRegistry`. The accepted factory's provider call is then immediate rather than queued. A thrown application failure occurs before its command, hooks, or claim responder are published. A successful installation is owned only after a new current legacy-config object and changed effective provider are observed; that exact config object is the instance token. On shutdown the wrapper acts only while that token is still current. A later legacy or native owner is left untouched. Otherwise it restores the prior native registration directly, clears the package layer with the captured effective provider before reapplying a prior legacy config, or—when there was no prior dynamic registration—uses public unregister only after the exact token/later-owner checks to restore dynamic-registration absence. Postconditions verify the complete public registration state and a usable effective provider; they do not require a stale built-in object identity because Pi may legitimately refresh its host-owned provider while the package overlay is active. The wrapper never blindly deletes another owner's provider and never reads private host state. A subsequent real reload with attribution disabled therefore restores the host's prior public registration state. When enabled, the transport remains provider-gated: non-Anthropic sessions and payloads are unchanged.
 
 ## Initialized-host SDK contract and blocker
 
@@ -36,7 +36,7 @@ For Anthropic sessions it registers the package-owned `anthropic` provider trans
 
 The extension reads `userID` and `oauthAccount.accountUuid` without writing account configuration. The loader precedence is: an explicit `loadClaudeAttributionAccount(path)` argument (the programmatic/test seam), then `PI_ANTHROPIC_ACCOUNT_CONFIG_PATH`, then `~/.claude.json`. An explicit selection must be a non-empty absolute file path. The selected file must be readable JSON with both non-empty fields; failures identify the selected path and field without fabricating account data. The package does not infer a Claude config-directory convention. Package-owned children inherit the path variable unchanged without copying account contents into their environment.
 
-The registered provider can be reached with a non-`anthropic` model that uses the `anthropic-messages` API. That path passes the host-owned model, context, and options by identity to the matching host SDK's supported `anthropicMessagesApi().streamSimple` implementation and returns its event stream directly. The package neither validates against a frozen transcript shape nor reconstructs events/results: legacy top-level `Context` and normalized system-message `TranscriptContext` contracts remain owned by the host version, including shared live partial identity, optional fields, tool metadata, usage, callbacks, and terminal error settlement. It does not receive account, identity, cache, endpoint, or header rewriting and does not dispatch through the registered API adapter again. Missing/malformed account data on the target route, unsupported model policy, malformed payload/cache controls, and non-OAuth target transport fail loudly.
+The registered provider can be reached with a non-`anthropic` model that uses the `anthropic-messages` API. That path passes the host-owned model, context, and options by identity to the gateway-injected matching host SDK's supported `anthropicMessagesApi().streamSimple` implementation and returns its event stream directly. A missing injected adapter fails loudly rather than resolving or reconstructing a private fallback. The package neither validates against a frozen transcript shape nor reconstructs events/results: legacy top-level `Context` and normalized system-message `TranscriptContext` contracts remain owned by the host version, including shared live partial identity, optional fields, tool metadata, usage, callbacks, and terminal error settlement. It does not receive account, identity, cache, endpoint, or header rewriting and does not dispatch through the registered API adapter again. Missing/malformed account data on the target route, unsupported model policy, malformed payload/cache controls, and non-OAuth target transport fail loudly.
 
 ## Cross-provider history and cache lineage
 
@@ -68,7 +68,7 @@ Ambient discovery and the parent capability flag are both insufficient for child
 - Anthropic delegate children, before the delegate guard;
 - Anthropic attested Pi children.
 
-The child entrypoint directly invokes the accepted implementation and deliberately does not consult `PI_BG_FEATURES`. Non-Anthropic child argv does not resolve or add it. Missing package extension bytes fail before child creation; no route substitution or sanitizer fallback is attempted. Delegate and Fusion keep attribution before their guard/governor, and attested Anthropic argv adds the same entrypoint before the prompt.
+The child entrypoint resolves and injects the same host-owned adapter before directly invoking the accepted implementation, and deliberately does not consult `PI_BG_FEATURES`. Non-Anthropic child argv does not resolve or add it. Missing package extension bytes fail before child creation; no route substitution or sanitizer fallback is attempted. Delegate and Fusion keep attribution before their guard/governor, and attested Anthropic argv adds the same entrypoint before the prompt.
 
 Arbitrary shell commands started through `bg_run` are not rewritten. An Anthropic child `pi` launched this way may keep normal extension discovery enabled when ambient attribution is enabled. If the command deliberately uses `--no-extensions`, it must explicitly load this package's always-on `extensions/anthropic-attribution-child.ts` with `-e`/`--extension`; otherwise attribution and sanitization are bypassed and the launch is unsupported. The package does not parse or override arbitrary shell authority.
 

package/docs/subsystems/delegation.md

@@ -39,7 +39,7 @@ Enabled schemas, descriptions, argument preparation, renderers, and tool registr
 
 Each loader is activation-local and single-flight: simultaneous cold calls await one module import but continue as independent runs. Its states are `unloaded`, `loading`, `loaded`, `failed`, and `closed`. An import failure is wrapped with a bounded module-specific diagnostic and remains sticky for that activation. The entrypoint constructs one activation-local synchronous close fence and explicitly gives it to every enabled core, Fusion, delegate, and result lane. Its first shutdown handler closes every loader, advances Fusion generation, aborts Fusion controllers, and aborts delegate preparation before any later handler can await cleanup. A module arriving after closure is discarded before its operation can create an artifact, task, or child or touch stale host APIs. Reload constructs a new facade and may retry; the closed instance is never reopened, and no process-global cache stores `pi` or host context.
 
-The main entrypoint dynamically imports the lightweight delegate/result facade only when delegate or Fusion is enabled. Process-only startup therefore imports neither advanced facade nor verifier/producer code. Published Pi entrypoints execute precompiled JavaScript from `dist/`; authoritative TypeScript remains shipped for source/API compatibility and development tests.
+The main entrypoint dynamically imports the lightweight delegate/result facade only when delegate or Fusion is enabled. Process-only startup therefore imports neither advanced facade nor verifier/producer code. Published Pi entrypoints execute precompiled JavaScript from `dist/`; authoritative TypeScript remains shipped for source/API compatibility and development tests. The compiled `dist/src/**` files are private chunks reached through those Pi entrypoints, not standalone Node entrypoints. Packed-package tests exercise successful delegate/result first use without any package-local Pi SDK peer.
 
 ## Seed and context policy
 

package/docs/subsystems/docs-freshness-gate.md

@@ -16,7 +16,7 @@ The finite grammar recognizes only a top-level immutable binding returned by the
 Every registration-owning function, imported registrar, and supported activation callback is checked as a whole, including parameter declarations and initializers. Destructured registration bindings, computed or property registration methods on unknown hosts, default-parameter host aliases, initializer calls/throws/control flow, and unmodeled body returns or throws are rejected. The sole early-return form is the structurally validated synchronous Anthropic duplicate-owner guard: the exact production claim channel, exact schema field/value and closed probe shape, one local empty acknowledgement array, one adjacent direct claim emit with the exact acknowledgement append, and the positive-length bare return. A local pre-probe claim listener is not accepted. Returns inside command/tool/event handlers that own no registrations remain unrelated and legal. Extracted surfaces carry a normalized availability expression and source-derived default status through the manifest, INDEX/read gate, README facts, and generated surface contracts.
 
 <!-- pi-docs:begin name="docs-freshness-gate" generator="scripts/docs/generate.mjs" -->
-- Canonical package version: `2.6.0`
+- Canonical package version: `2.6.2`
 - Governed markdown docs: 42
 - Public surfaces extracted: 32
 - Public surfaces available by default: 31

package/docs/subsystems/host-ui-and-telemetry.md

@@ -13,7 +13,9 @@ This subsystem owns the extension entrypoint, command/tool registration, footer
 
 ## Entrypoint and registration
 
-The published `dist/extensions/background-tasks.js` entrypoint is compiled from `extensions/background-tasks.ts`, which re-exports the authoritative `src/extension.ts`. Before creating the registry or registering a surface, the extension strictly parses the shared capability/shortcut configuration. It dynamically imports delegate/Fusion facade registration only for enabled capabilities; the dock component is imported only when an interactive manager is opened. `process` is mandatory and registers:
+The published `dist/extensions/background-tasks.js` entrypoint is compiled from `extensions/background-tasks.ts`, which re-exports the authoritative `src/extension.ts`. Only the ordered paths in `package.json.pi.extensions` and the package-owned child extension paths are supported extension roots. Files under `dist/src/**` are private compiled implementation chunks, not standalone Node entrypoints. Importing one directly from an unrelated natively loaded extension bypasses Pi's Jiti host-module aliases and is unsupported. The packed-package gate instead exercises every public lazy lane through the real package entrypoint with no package-local Pi SDK or TypeBox installation.
+
+Before creating the registry or registering a surface, the extension strictly parses the shared capability/shortcut configuration. It dynamically imports delegate/Fusion facade registration only for enabled capabilities; the dock component is imported only when an interactive manager is opened. `process` is mandatory and registers:
 
 - commands: `/bg`, `/tasks`, `/bg-tasks`, `/bg-clear`, `/bg-update`, `/jobs`, `/logs`, `/kill`;
 - tools: `bg_run`, `bg_status`, `bg_logs`, `bg_kill`;

package/extensions/anthropic-attribution-child.ts

@@ -1,3 +1,10 @@
+import { anthropicMessagesApi } from '@earendil-works/pi-ai/compat';
+import spawnAnthropicAttribution, {
+  type PiExtensionHost,
+} from '../src/core/anthropic-attribution.js';
+
 // Always-on safety entrypoint for package-owned isolated Anthropic children.
 // Ambient parent capability selection must never disable this extension.
-export { default } from '../src/core/anthropic-attribution.js';
+export default function childAnthropicAttribution(pi: PiExtensionHost): void {
+  spawnAnthropicAttribution(pi, { hostAnthropicMessagesApi: anthropicMessagesApi });
+}

package/extensions/anthropic-attribution.ts

@@ -1,4 +1,5 @@
 import type { Provider } from '@earendil-works/pi-ai';
+import { anthropicMessagesApi } from '@earendil-works/pi-ai/compat';
 import type { ModelRegistry } from '@earendil-works/pi-coding-agent';
 import type { PiContextLike, PiExtensionHost } from '../src/core/anthropic-attribution.js';
 import { parseBackgroundTasksConfig } from '../src/core/config.js';
@@ -104,7 +105,9 @@ function restoreProviderInstallation(installation: ProviderInstallation): void {
   } else {
     // The exact package token and absence of a later native owner were proven above.
     // Public unregister is therefore owner-conditional here: it removes only this
-    // still-current package layer and restores the captured built-in source absence.
+    // still-current package layer and restores dynamic-registration absence. The host
+    // may legitimately refresh its built-in provider while our overlay is installed,
+    // so that host-owned effective object is not required to retain stale identity.
     registry.unregisterProvider(ANTHROPIC_PROVIDER);
   }
 
@@ -121,25 +124,13 @@ function restoreProviderInstallation(installation: ProviderInstallation): void {
         (before.native !== undefined
           ? restoredNative === before.native
           : restoredNative === undefined);
-  const streamIdentityRestored =
-    before.legacy !== undefined
-      ? restoredConfig?.streamSimple === before.legacy.streamSimple
-      : restoredEffective?.streamSimple === before.effective.streamSimple;
-  const effectiveIdentityRestored =
-    before.legacy !== undefined || restoredEffective === before.effective;
   const registeredIdRestored =
     before.legacy !== undefined || before.native !== undefined
       ? restoredIds.includes(ANTHROPIC_PROVIDER)
       : !restoredIds.includes(ANTHROPIC_PROVIDER);
-  if (
-    !registrationRestored ||
-    restoredEffective === undefined ||
-    !streamIdentityRestored ||
-    !effectiveIdentityRestored ||
-    !registeredIdRestored
-  ) {
+  if (!registrationRestored || restoredEffective === undefined || !registeredIdRestored) {
     throw new Error(
-      'pi_anthropic_attribution_restore_failed: the preexisting host provider was not restored by identity',
+      'pi_anthropic_attribution_restore_failed: the preexisting public provider registration state was not restored',
     );
   }
 }
@@ -154,7 +145,7 @@ export default async function ambientAnthropicAttribution(pi: PiExtensionHost):
     pi.on('session_start', (_event, context) => {
       const registry = (context as AmbientAttributionContext).modelRegistry;
       const before = captureProviderSnapshot(registry);
-      spawnAnthropicAttribution(pi);
+      spawnAnthropicAttribution(pi, { hostAnthropicMessagesApi: anthropicMessagesApi });
       installation = confirmProviderInstallation(registry, before) ?? installation;
     });
     pi.on('session_shutdown', () => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-background-tasks",
-  "version": "2.6.0",
+  "version": "2.6.2",
   "description": "Pi extension for durable background shell tasks, read-only delegated agents, local attested Pi runs, and fixed-purpose Fusion workflows through child Pi processes.",
   "type": "module",
   "license": "ISC",
@@ -88,6 +88,7 @@
     ]
   },
   "peerDependencies": {
+    "@earendil-works/pi-ai": "*",
     "@earendil-works/pi-coding-agent": "^0.81.1 || ^0.82.1 || ^0.83.0 || ^0.84.0",
     "@earendil-works/pi-tui": "^0.81.1 || ^0.82.1 || ^0.83.0 || ^0.84.0",
     "typebox": "*"

package/src/core/anthropic-attribution.ts

@@ -2,7 +2,6 @@ import { createHash } from 'node:crypto';
 import { appendFileSync, readFileSync } from 'node:fs';
 import { homedir } from 'node:os';
 import { isAbsolute, join } from 'node:path';
-import { anthropicMessagesApi } from '@earendil-works/pi-ai/compat';
 import type {
   AssistantMessageEventStream as HostAssistantMessageEventStream,
   Context as HostContext,
@@ -466,8 +465,12 @@ export interface PiSimpleStreamOptions {
   ) => Promise<void> | void;
 }
 
+export type HostAnthropicMessagesApiFactory =
+  typeof import('@earendil-works/pi-ai/compat').anthropicMessagesApi;
+
 export interface AnthropicTransportDependencies {
   readonly loadAccount?: () => ClaudeAttributionAccount;
+  readonly hostAnthropicMessagesApi?: HostAnthropicMessagesApiFactory;
 }
 
 export interface AssistantMessageLike {
@@ -2683,12 +2686,23 @@ function forwardToBuiltInAnthropic(
   model: PiModelLike,
   context: PiStreamContext,
   options: PiSimpleStreamOptions | undefined,
+  dependencies: AnthropicTransportDependencies,
 ): AssistantMessageEventStreamLike {
-  // Pi aliases these SDK imports to its own version while loading extensions.
-  // The host therefore owns both its legacy Context or normalized TranscriptContext
-  // input and the complete stream/event/result shape. These intersections only mark
-  // that host-owned boundary; no request, callback, event, or result is reconstructed.
-  const delegated = anthropicMessagesApi().streamSimple(
+  // The compiled gateway resolves this host-owned adapter through Pi's alias-aware
+  // extension loader and injects it across the lazy native-import boundary. Keeping
+  // the deferred core free of runtime Pi package imports prevents Node from trying to
+  // resolve a private @earendil-works/pi-ai installation beside a managed package.
+  const hostAnthropicMessagesApi = dependencies.hostAnthropicMessagesApi;
+  if (hostAnthropicMessagesApi === undefined) {
+    throw new Error(
+      "pi_anthropic_attribution_host_adapter_missing: the extension gateway did not inject Pi's anthropic-messages adapter",
+    );
+  }
+
+  // The host owns both its legacy Context or normalized TranscriptContext input and
+  // the complete stream/event/result shape. These intersections only mark that
+  // host-owned boundary; no request, callback, event, or result is reconstructed.
+  const delegated = hostAnthropicMessagesApi().streamSimple(
     model as HostForwardingModel,
     context as HostForwardingContext,
     options as HostForwardingOptions | undefined,
@@ -2703,7 +2717,7 @@ export function streamAnthropicViaBetaMessages(
   dependencies: AnthropicTransportDependencies = {},
 ): AssistantMessageEventStreamLike {
   if (model.provider !== 'anthropic') {
-    return forwardToBuiltInAnthropic(model, context, options);
+    return forwardToBuiltInAnthropic(model, context, options, dependencies);
   }
 
   const stream = createAssistantMessageEventStream();