Rename src/agent/mod.rs to the sibling src/agent.rs form and add the
trailing comma the perfectionist dylint rules require.

---
Written by an agent (Claude Code, claude-opus-4-8).

Satisfy the perfectionist dylint rule (updated on main) that requires a
single `use` statement per crate root.

---
Written by an agent (Claude Code, claude-opus-4-8).

Port the TypeScript `@pnpm/agent.client` (`fetchFromPnpmRegistry`) plus
the `fetch-and-write-cafs` worker to Rust as a new `pacquet-agent-client`
crate. Given a set of dependencies and the client's content-addressable
store it:

- reads the integrities already in the local store index,
- POSTs them with the dependencies to `/v1/install` and parses the NDJSON
  response (D missing-file digests, I store-index entries, L lockfile +
  stats, E error),
- downloads the missing files from `/v1/files`, decodes the gzip binary
  framing, and writes each file into the local CAFS by digest (no
  re-hashing), rejecting any entry that wasn't requested,
- writes the forwarded store-index entries, skipping keys already present,
- and returns the resolved lockfile for a headless install.

Integration tests drive the real round-trip: a shared TestRegistry serves
the package fixtures, a per-test in-process pnpr hosts the agent endpoints
and resolves from it, and the client materializes a package into a fresh
store. Covers a single-file package, a multi-file package, and warm-store
dedup (second run downloads nothing).

Deferred (matching the server): true streaming and batched /v1/files.

---
Written by an agent (Claude Code, claude-opus-4-8).

…ured

Add an `agent` setting (CLI `--agent`, `agent:` in pnpm-workspace.yaml,
`PNPM_CONFIG_AGENT`) and wire it into the install command, mirroring
pnpm's `install()` delegating to `installFromPnpmRegistry`.

When `agent` is set, `pacquet install` resolves the project server-side
through `pacquet-agent-client` (which populates the local store and
returns the lockfile), writes the lockfile, then runs a frozen install
to link `node_modules` from it — the equivalent of pnpm handing the
agent-produced lockfile to `headlessInstall`. `trustPolicy: no-downgrade`
is refused on this path, matching pnpm's
`TRUST_POLICY_INCOMPATIBLE_WITH_AGENT`.

Adds `Config.agent` plus its yaml/env/CLI wiring and an end-to-end test
that runs the real `pacquet install --agent <url>` binary against an
in-process pnpr agent (resolving from the mocked fixtures registry) and
asserts node_modules is linked from the agent-produced lockfile.

Deferred (matching the client/server): `pacquet add` / `remove` via the
agent, multi-project workspaces, overrides, and per-request
minimumReleaseAge.

---
Written by an agent (Claude Code, claude-opus-4-8).

…add handshake

Rework the fast-path opt-in around how it's actually used:

- Rename the `agent` setting to `pnprServer` (CLI `--pnpr-server`,
  `pnprServer:` in pnpm-workspace.yaml, `PNPM_CONFIG_PNPR_SERVER`). The
  value is a plain URL of a pnpr server, not the registry — the server
  is a resolution/fetch service, not "a registry that resolves from
  itself".

- The client now sends its own resolution config (default `registry`,
  `namedRegistries`, `overrides`, `minimumReleaseAge`) in the
  `/v1/install` request, and the server resolves against *those*
  registries instead of its own uplink. This decouples "who computes"
  from "the source of truth", so the same pnpr server works for any
  client's registry setup. The server interns a `&'static Config` per
  distinct client registry configuration, bounding the leak.

- Add a `GET /-/pnpr` capability handshake advertising supported
  protocol versions. The client probes it before installing and fails
  fast with a clear error if the configured server isn't a pnpr or
  speaks no common version (rather than silently falling back).

Tests: the agent-client + cli e2e tests now leave the pnpr server's own
uplink at the default and rely on the client-supplied registry, proving
resolution uses the forwarded config; plus a handshake-rejection test.

Deferred: auth/credential forwarding so private registries resolve.

---
Written by an agent (Claude Code, claude-opus-4-8).

Complete the move away from "agent" terminology now that the
user-facing surface is `pnprServer`. No behavior change.

- crate `pacquet-agent-client` -> `pacquet-pnpr-client`
  (`AgentClient` -> `PnprClient`, `AgentClientError` -> `PnprClientError`)
- pnpr module `agent` -> `fast_path` (`AgentRuntime` -> `FastPathRuntime`,
  `serve_agent_*` -> `serve_fast_path_*`, `agent_runtime` field, the
  `agent/` source dir and `tests/agent.rs`)
- the CLI's `AgentLink` helper, the `AgentInstallOptions` import alias,
  user-visible error strings, and the server's on-disk `agent-store` /
  `agent-cache` dirs (now `pnpr-store` / `pnpr-cache`)

Upstream citations keep their real names (`@pnpm/agent.client`, the
pnpm-agent proof of concept, pnpm's `TRUST_POLICY_INCOMPATIBLE_WITH_AGENT`
error code).

---
Written by an agent (Claude Code, claude-opus-4-8).

Replace the vague, repetitive "Client for the pnpr fast-path endpoints
exposed by pnpr" with "Client for pnpr's server-accelerated installs":
no doubled `pnpr`, and "server-accelerated" credits the server with the
speedup without claiming the install (linking) runs there.

---
Written by an agent (Claude Code, claude-opus-4-8).

It's the per-server engine that resolves a client's project and serves
the files its store is missing — i.e. what accelerates the install.
"FastPath" was jargon and "Runtime" was vague; the new name matches the
crate's "server-accelerated installs" framing. Field renamed to
`install_accelerator`. No behavior change.

---
Written by an agent (Claude Code, claude-opus-4-8).

Match the `InstallAccelerator` type: `mod fast_path` -> `mod
install_accelerator` (source file, `fast_path/` dir, and the
integration test), the `serve_fast_path_*` route handlers ->
`serve_install` / `serve_files`, and the lingering "fast path" prose.
"fast path" is fully gone from the crate. No behavior change.

---
Written by an agent (Claude Code, claude-opus-4-8).

`pnpr` and `pnpr-fixtures` are licensed under PolyForm Shield (see
`pnpr/LICENSE.md`), not the workspace's MIT, and `[licenses.private]
ignore = false` makes cargo-deny audit first-party crates — so the
license check fails them as "unlicensed" (the LICENSE.md only matches
PolyForm-Noncommercial at 0.74, below the confidence threshold).

Pin the license by file hash via `clarify` and allow it for just those
two crates via `exceptions`. cargo-deny doesn't recognize a
`PolyForm-Shield` identifier, so the closest recognized id
(`PolyForm-Noncommercial-1.0.0`) is used. `cargo deny check` is green.

---
Written by an agent (Claude Code, claude-opus-4-8).