feat(plugins): grant conversation access through the capability review (#200961)

## What Problem This Solves

A third-party plugin that reads conversations (conversation hooks, or a session fork such as a `/better` helper) needed a separate manual step after install: set `plugins.entries.<id>.hooks.allowConversationAccess: true` in config. The install already shows a capability review, but conversation access was not part of it: the manifest had no way to request it, so the review could only display it as denied. Installing such a plugin meant: install, approve, then go find a config setting.

## User Impact

- A plugin can declare `contracts.conversationAccess: ["read"]`. The install/enable capability review lists it with the plugin's other capabilities, and approving that review grants it. No config change, no restart.
- An explicit `allowConversationAccess` value still wins: `false` denies even after approval, `true` allows as before.
- Plugins that do not declare it behave exactly as before.

## Why This Change Was Made

- **One review, one decision.** `conversationAccess` is a manifest contract family, so it flows through the existing declared-surface review: shown as `conversationAccess: read`, covered by the review hash, and re-prompted when a later version adds it. Approval is stored in the existing install record (`acceptedSurface.contracts`); nothing new is persisted and no schema changes.
- **One grant rule.** `resolveConversationAccessAllowed` now takes the approval as an input: explicit config wins; otherwise bundled plugins, or an installed plugin whose approved review included the contract. All readers use it: typed-hook registration, plugin session forks, and the capability summary shown by inspect and the review.
- **Bound to the approved install.** The approval is computed with the existing install trust decision (`resolvePluginTrust`) and carried on `PluginTrust`. It counts only when the loaded code is the recorded install (unambiguous owner, install path matches, not a workspace plugin) and the stored acceptance hash matches its surface. A `plugins.load.paths` entry that points at the recorded install keeps the grant; a workspace plugin or an untracked load path still needs the config setting.
- **Previews show what approval grants.** The consent review, Template plans and catalog inspect all project the grant that approving the declared surface produces (`conversationAccessAccepted` in `buildPluginCapabilitySummary`). Approval covers the package's merged surface, so in a multi-entry package every entry gets the grant when any sibling declares it; Template plans read that same merged surface. Template apply requires the reviewed grants to equal the planned grants, so without one projection a Template dependency that declares conversation access could never install.

Accepted edge case: an approval is checked when the install is loaded. Editing a linked install's manifest on disk without reinstalling keeps the earlier approval until the next managed reload re-runs the review, which is the same rule every other declared capability follows.

## Evidence

- **Red on `main`, green here:** `src/plugins/loader.conversation-access-consent.test.ts`. An installed plugin whose approved review includes `conversationAccess: read` registers its conversation hook with no config (fails on `main`); an approval without the contract, a forged acceptance hash, and an explicit `false` stay blocked (pass on both).
- **Template plan matches the review:** `template-managed-capability-consent.integration.test.ts` plans a plugin that declares conversation access, then installs it while asserting the reviewed grants equal the plan (red before the projection fix: planned `effective: false`, reviewed `true`). The plan and the review now read the same merged package surface (`inspectPluginCapabilityArtifact().declared`), so they cannot disagree for multi-entry packages either.
- **Suites:** `capability-consent`, `loader` (193, including conversation-hook diagnostics), `loader.trust-diagnostics`, `server-plugins`, fork transport, management-service inspect/install/capability-consent, catalog discovery, Template packages; `tsgo:core`, `tsgo:core:test`, oxlint, both import-cycle checks, all baseline ratchets.
- **Live, source Gateway, real Anthropic:** `openclaw plugins install <better-prompt> --link --accept-capabilities` with no conversation-access config.

| Check | Result |
|---|---|
| Plugin config after install | `{ "enabled": true }` only |
| `plugins.inspect` | declares `conversationAccess: read`; conversation access `effective: true`, nothing configured |
| `/better` (a session fork reading the chat) | ran; 5 model requests |
| Then `allowConversationAccess: false`, `/better` again | 0 model requests in 20 s |

**SDK impact.** Additive manifest contract family. No plugin can already declare it, so no existing grant changes; config `true`/`false` and the bundled default keep their meaning.

Co-authored-by: Ayaan Zaidi <hi@obviy.us>