Visual Intent Layer 0.3.2

The published package now carries the front door and the manual.

The npm page is a front door, and the manual ships with it

The README was both the front door and the whole product manual — 337 lines, where
someone registering the server read four paragraphs of interaction design first. It
is now 109 lines: what the product is, the install line per Harness with the pi
entry written out in full, update, uninstall, and the by-hand command that separates
Node and npm from your Harness.

Everything else moved to docs/guide.md — the Review Surface, the Annotation model,
target resolution, Check-In, the four MCP tools, environment and data, the envelope
schema, develop and layout. It ships inside the package, so the README's link
resolves for someone reading the installed tarball, not only on GitHub.

Two claims were wrong, and one act was missing

• @latest does not always mean the newest release: pi-mcp-adapter caches a
  resolved command for 24 hours, so the README now says what forces a fresh fetch.
• Uninstalling was never documented. It is now — including the fact that it deletes
  none of your reviews: Annotations, sessions and attachments stay in
  ~/.visual-intent-layer/data until you remove that directory.

Repository

Conventional commits are enforced by a commit-msg hook and re-checked in CI. The
registry listing retries the window where npm has not yet served the released
version, which is what required a hand dispatch for 0.3.1.