Tool "bash" conflicts with pi-patty-bg-tasks at startup (load-time registration still races)

[RaviTharuma]

Environment

• pi-tool-display 0.5.0
• pi-patty-bg-tasks 1.1.6
• @earendil-works/pi-coding-agent (Homebrew current)
• Both packages enabled in ~/.pi/agent/settings.json

Repro

1. Enable both packages:

   {
     "packages": [
       "npm:pi-tool-display",
       "npm:pi-patty-bg-tasks"
     ]
   }

2. Leave default ownership (registerToolOverrides.bash: true / missing config).
3. Start pi in any project.

Actual

Error: Failed to load extension ".../pi-patty-bg-tasks/index.ts": Tool "bash" conflicts with .../pi-tool-display/index.ts
Hint: Start without extensions using "pi -ne".

Expected

pi-tool-display should yield bash when another extension already owns it, as documented under Tool ownership conflicts / deferred ownership discovery (see closed #29 / #17).

Root cause

registerToolDisplayOverrides() still calls registerIfOwned("bash", ...) and other built-ins during extension load. Ownership is checked via pi.getAllTools() at that moment, so a later package cannot claim the slot cleanly. Pi then reports a hard tool-name conflict diagnostic.

README currently says overrides are deferred to before_agent_start, but that is only true for MCP decoration — built-ins still register immediately.

Workaround

In ~/.pi/agent/extensions/pi-tool-display/config.json:

{
  "registerToolOverrides": {
    "bash": false
  }
}

Optionally load pi-patty-bg-tasks before pi-tool-display.

Fix

PR: #34

Defer all built-in override registration to session_start / before_agent_start and re-evaluate ownership against the full tool graph before registering.

Related: #17, #29

[itcook]

Same root cause reproduces with read/grep too, and the #29 fix is not in any released code:

• Repro: pi-fff (registers functional read/grep tools at load) + default pi-tool-display config → startup fails:

  Error: Failed to load extension ".../pi-tool-display/index.ts": Tool "read" conflicts with .../pi-fff/index.ts
  Error: Failed to load extension ".../pi-tool-display/index.ts": Tool "grep" conflicts with .../pi-fff/index.ts
  

• Verified: cloned main today and checked published npm 0.5.0 — neither contains registerDeferredBuiltInToolOverrides; PR fix: defer built-in tool overrides until session lifecycle #34 is still open/unmerged. So the "completed" close on Built-in tool override ownership check is load-order-dependent, causing hard crash when another extension owns read/edit/etc. #29 is misleading: the fix was never landed.
• Root cause (same as this issue): registerIfOwned() calls pi.getAllTools() at extension-load time, which throws Extension runtime not initialized, the error is swallowed, and the override is registered anyway → pi reports a hard conflict diagnostic and exits.
• Workaround (current): registerToolOverrides.read/grep: false in ~/.pi/agent/extensions/pi-tool-display/config.json — works, but loses the compact read/grep rendering.

PR #34 (defer registration to session_start/before_agent_start where getAllTools() works) fixes all of these cases at once — would love to see it merged and released.