fix(plugin): consistent plugin ownership, per-project pools, targeted check/update, and settings directory contract - #39

- Keep one pool per settings view: the process view boot loads, and one per
  project root, created from it on first use and moved only by that project's
  sessions, so the same spec owned by two files can run two builds in one
  process and sessions in different projects never evict each other
- Treat a loaded reference as moved when this view's owner names another
  artifact the store already holds, which is how a project picks up the build
  its own `.npmrc` resolves
- Register event types from the union of every view, one plugin per ID
- Rebuild every view on reload, reporting each distinct failure once
- Extend the two-registry E2E to alternate a project session with one outside
  any project in a single process; its artifact now records both builds

Fixes COD-72. Scoping plugin state per location follows opencode's
plugin supervisor.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

- Accept an optional `spec` on `plugin check` and `plugin update`; without it
  both walk every configured plugin exactly as before
- Match by source identity as the `plugins` array reads: a package by name
  whatever version it was written with, a git spec in full, a path by the
  file it resolves to, and a local package also by its manifest name (read
  without importing, via `Plugin.localName`); a plugin ID matches nothing
- Keep every match, so a spec both layers declare under two registries acts
  on both artifacts; fail an unmatched spec with a pointer to `plugin list`
  before anything is probed
- Name a targeted local plugin instead of skipping it silently, with no
  summary line for a comparison that never happened
- Cover it with one E2E that drives registry, git (`git+file://`) and local
  targets through the real CLI, proves unrelated plugins are never probed,
  runs the result in the runtime, and writes `plugin-targeted.json`

Closes COD-63.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

- Give a project view the host directory its sessions' `hostDir` led to for
  anchoring and parsing, falling back to `hostCwd` only in the process view,
  which has no session; `filed` parses against the reference's own anchor
- Name the CLI plugin commands' host anchor `hostDir` (the linked session's,
  or the directory the command runs in) instead of `cwd`, which is reserved
  for a sandbox's working directory
- Link E2E sessions only through `hostDir`, leave their sandbox directory
  alone, and run the app from a neutral `hostCwd`; the artifacts are
  byte-identical, so settings reach a session through `hostDir` alone

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…ings file

- Read `<--user-config-dir>/settings.jsonc` instead of `<--home>/settings.jsonc`
  rather than as a third layer above the project: the settings layers are
  now user, then project, and the home's file is not opened when the flag
  is given; credentials, cache and data stay in `--home`
- Resolve `--home` and `--user-config-dir` against `hostCwd`, never a
  session's `hostDir`, through one `Settings.userConfigDir`; `Settings.load`
  takes it already absolute and `paths` loses its `from`
- Let the flag choose which user file `plugin add/remove -g` edits instead of
  forcing every edit into it; without `-g` the project file is edited
- Describe `--home` and `--user-config-dir` accordingly in the CLI help
- E2E: CLI list and add plus a server-shaped runtime run (app `hostCwd` apart
  from the session's `hostDir`, with a decoy where a `hostDir`-relative
  resolution would land) write `settings-layers.json`; artifacts collapse
  path-sized column padding so they reproduce on any machine

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

- Rename the `exchange` helper's `cwd` to `hostDir`: it is the host
  directory the session is linked to, which is where its project settings
  come from, not a working directory
- Run the app from `root` beside an outer project while the session is linked
  to a nested one, so the nearest-project test proves discovery follows the
  session's `hostDir` and never the app's `hostCwd`

A local sandbox's `cwd` is a host path by nature, so the other tests that
place a session's sandbox in a temp directory were already right.

Fixes COD-73.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…s choice

- Assert on every attempt that thinking is persisted exactly when thinking
  streamed, which is the harness's contract whatever the provider sends
- Ask for a reasoning summary more firmly (`medium`, `detailed`, a harder
  prompt) and retry in a fresh session, up to three times, until a response
  carries thinking, so the persistence path is exercised rather than skipped
- Scope the durable-event check to the chosen session

Fixes COD-74.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>