pi-link-extension 0.1.0 — experimental source distribution

Only pi-extension/ is the logical source Pi package. This generated virtual repository preserves its shared paths; do not install the source repository root as a Pi package.

Requires Pi 1.0.4 (minimum actually validated) and Node 22.23+. Runtime SDK peers are supplied by Pi, not bundled. Four extension entries, owned/vendor skills, prompts and subagents exports are retained. No lifecycle scripts, automatic native builds, downloads, network/model calls or factory timers are added. Optional independent ask-user companion is not included or automatically installed.

Install with Pi

After this exact version is actually published to the registry:

pi install npm:[email protected]

Reload Pi when idle. Do not load a second local Pi Link, standalone subagents or Todo copy at the same time; resource migration is explicit and never deletes credentials/history. Package generation alone is not publication proof.

Selected packaged-own-code license: MIT; the operator authorized MIT for own code in this npm package, not all private repository contents. Vendor MIT notices/provenance are retained unchanged. See LICENSE-NOTICE.txt and pi-extension/PROVENANCE.md.

Optional native source build (manual only)

The source-only archive intentionally lacks target/ and pi_link_core.node. Offline prerequisites: existing Rust 1.97.0 + locked Cargo cache, a compatible Unix C toolchain, Node headers next to the Node binary, Bash, and permission to write this extracted package. From this package root, explicitly run:

cargo +1.97.0 build -p pi-link-relay --locked --offline
bash bindings/node/build.sh

The build script also builds the locked crypto core. No prerequisites are downloaded automatically. Windows native builds are not proven; the Unix linker script is not a portable Windows build recipe. Without the addon, /pi-link selftest reports fail-closed; no control capability is granted. /remote-connect remains an explicit experimental local/USB flow requiring native relay/addon, local approval and an authorized current session, not configured production service. A phone APK is separate. No production authentication, hardware, provider or G claim.

The distribution is bound to the source head/tree in SOURCE-INVENTORY.json. The release owner must review and test that exact artifact before publication and verify registry name, version, license and account rights. Archive generation alone does not establish a published release.