pi-model-profiles@0.3.1 breaks npm install due to strict peer dependency on @earendil-works/pi-coding-agent@^0.75.4

[omar-elmountassir]

Problem

After updating to pi-model-profiles@0.3.1, running npm install in a project with multiple Pi extensions fails with ERESOLVE could not resolve.

Root cause

In v0.3.1, peer dependencies were migrated from the old @mariozechner/ namespace to @earendil-works/pi-coding-agent@^0.75.4. However, the version constraint ^0.75.4 is stricter than what other commonly-used Pi extensions require (^0.74.0), making them impossible to satisfy simultaneously.

Affected peer dependency chains

pi-model-profiles@0.3.1 requires:

• @earendil-works/pi-coding-agent@^0.75.4
• @earendil-works/pi-tui@^0.75.4

But other extensions (e.g. pi-btw@0.4.0, pi-hermes-memory@0.7.11, pi-lean-ctx@3.6.x) require:

• @earendil-works/pi-coding-agent@^0.74.0 or broader

npm strict mode cannot resolve both ^0.75.4 and ^0.74.0 for the same package in one tree.

Reproduction

mkdir test && cd test && npm init -y
npm install pi-model-profiles@0.3.1 pi-btw@0.4.0 pi-hermes-memory@0.7.11
# → ERESOLVE could not resolve

Suggested fix

Widen the peer dependency range to match what the rest of the ecosystem uses:

{
  "peerDependencies": {
    "@earendil-works/pi-coding-agent": ">=0.74.0",
    "@earendil-works/pi-tui": ">=0.74.0"
  }
}

This is safe because the extension doesn't use APIs introduced in 0.75.x — the namespace migration is purely organizational (same code, new package name).

Environment

• pi-coding-agent: 0.75.4
• pi-model-profiles: 0.3.1
• npm: 10.x