Install a package
Installs a package from a registry reference or a local path. The response is 202 with an install job, because a package carrying Go code triggers a rebuild and binary swap; poll the job (or watch events) for progress. Resource-only packages complete near-instantly. Conflicts — two packages claiming one slot — surface asynchronously, on the failed job’s error envelope, as NRY-0006 naming both claimants (enable/disable are the one synchronous exception: they report a slot conflict as a direct 409 instead, since they have no job to poll). A failed build never leaves the user without a working agent: the previous binary stays in place (NRY-0007). A hosted home refuses it 422: a package is compiled and run on the host’s own machine, and an extension registered at an HTTPS address is the hosted way.
Authorizations
Enforced on every transport, with no exempt operation. A person's request — over the default local unix socket exactly as over a TCP listener — must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011. The socket's file permissions are transport and are not an authorisation.
Body
Request to install a package.
A registry reference or a local directory path.
1024Must be true when source carries compiled Go code: installing it means trusting it fully — it runs in the host's own process, with no sandbox. Omitted or false on a code-carrying source is rejected (422) naming the acknowledgement, before any install is attempted.
Response
Install job started. Poll it for progress.
An asynchronous package operation. Code-carrying packages resolve, build and swap the binary; a failure at any stage leaves the previous binary intact and serving — the user is never left without a working agent.
resolving, building, swapping, done, failed 2561024Present when status is failed; the previous binary is intact.

