AgentDocs

Rewrite the marketplace card around the approved shared-project-context story.
Reuse four AgentDocs launch-film illustrations for the hero and three panels;
retain the existing launch film. Refresh the description, five features and SEO.
No tools, routes, entitlements, dependencies or skill instructions changed.

The marketplace listing shows the launch film. No skill change.

Every AgentDocs route an agent may call is now a method (SP-39): 28 new methods, 46 in all.
Branches (`listBranches`, `createBranch`, `branchDiff`, `mergeBranch`, `closeBranch`), one-call
reads (`projectView`, `pageView`, `searchView`, `pageGraph`), `getRevision`, `listRecentPages`,
templates, members and visibility, and for brand admins webhooks and access tokens. No route
changed. Every brand-admin method's guidance says it needs a brand-admin key. Off the list: the
ZIP export (projectView covers it) and the canvas-position save (a person's layout). The media
upload is `uploadMedia`, a multipart file method (doors gained file parameters with SP-56).

**Fixed — every method takes every field its route accepts** (the review bar). These older
methods sent a field the route never read, so it was dropped without an error:
- `updateTheme` sent `theme`. The route reads `settings`, so every call failed with "No fields to
  update". It now takes `settings` (theme at `settings.theme`) plus name, description and visibility.
  The route **replaces** the whole settings object; the guide no longer claims a merge.
- `pageDiff` `from_rev`/`to_rev` are now `from`/`to`, the names the route reads.
- `pageRollback` `message` is now `commit_message`.
- Added the fields agents could not set: `author_type`/`author_name` and `extra_data`/`agent_context`
  on writes, `page_type` on createPage, `branch` and the per-page item shape on bulkCreatePages,
  `skip`/`limit`/`view` on lists, `settings` on updateProject, and `internal` visibility (createProject
  now defaults to `private`, as the route does).

Republish so agents get what `main` already has: the guide gains the search-boost and tool_help guidance (SP-11). No method or entitlement changes.

Republish so agents are served the **real guide** instead of the root stub (ASP-245 / X.25).

ASP-246 ([#1805]) repointed `docs.skill_guide` from `./SKILL.md` to
`./skills/agentdocs/SKILL.md` and bumped no version. A registry serves one bundle per
version, so the published `1.1.1` still declared the old path and the fix reached nobody —
same version name, different shipped bytes, which is what `scripts/skill-publish-drift.sh`
reports as `IDENTITY`.

**What this changes for an agent.** `registry.py` `_find_skill_root` takes the *directory* of
`docs.skill_guide` as the skill root, and `_extract_skill_guide` lists `layers[]` only from the
`references/` `learnings/` `registry/` `scripts/` dirs directly under it. Rooted at the bundle
root — which has none of those — `GET /api/v1/registry/packages/opvs-ai/agentdocs/skill-guide`,
the read MCP `tool_read` serves, returned the **20-line stub with `layers: []`**, and every
`references/*.md` the guide pointed at answered 404. Measured on the published `1.1.1` bundle
before this release; the real guide is **207 lines**.

Patch, not minor: `methods:` is byte-identical to the previously published bundle. No schema,
API or tool-signature change — only which file the registry hands an agent as the guide.

[#1805]: https://github.com/opvs-ai/OPVS/pull/1805

Republish so one version name denotes one byte-stream again (ASP-245).

- `skills/agentdocs/schema.yaml`: `version` 2.1.0 → 2.2.0, reconciling Tree B to Tree A (ASP-240).
- `CHANGELOG.md`: repaired a dead `docs/planning/opvsHUB/Marketplace/` link left by the 2026-07-20 reorg (baselined debt from 2026-09-10).

No agent-visible change: `methods:` is byte-identical to the previously published bundle, and the
runtime reads only `methods` / `upstream` / `base_url` / `admin` / `name` off a parsed schema.

### Added

- **Initiative A — envelope contract (sei.2.2 / PR #85).** schema.yaml now carries skill-level `intent_aliases`, `pitfalls`, and per-method `guidance` blocks with `next`, `warn`, and `telemetry_signal_default`. Lets the gateway surface OPVS-native guidance inline in every tool description.
- **Initiative B — 4-layer format (s4l.2.2 / PR #88).** Three new directories ship inside `skills/agentdocs/`: `references/` (5 procedure docs — board-synced-pages, bulk-create-pages, create-or-update-page, find-before-creating, revisions-and-rollback), `learnings/` (4 Knowledge Items — asyncpg-jsonb-returns-strings, author-type-resolved-from-context, revisions-immutable-rollback-additive, slug-collision-soft-deleted), and `registry/` (3 typed assets — architecture-decision-record, runbook-page, team-handbook-project, plus the registry.json index).
- Republish on the canonical 4-layer recipe verified 2026-05-25 (see `docs/planning/Marketplace/DEPLOYMENT.md` §"4-layer skill publish"). 4-layer dirs ride along in the signed tarball; no manifest schema changes required.

### Changed

- Skill SKILL.md regrown to carry the new envelope guidance and 4-layer pointers.

### Added

- **Marketing metadata** — `marketing` block now carries a `long_description` (2–4 paragraphs of admin-facing copy), 5–7 `features` bullets with lucide-react icons, and an `author` record ({name: OPVS Team, email: ops@opvs.ai, website: https://opvs.ai}). Drives the Wave 2 Phase B customer detail page at `/dashboard/marketplace/packages/@opvs-ai/<name>`. `media` block intentionally empty for this release — visual assets (hero image, screenshots, demo video) come in a later wave.

### Changed

- `tier: internal` → `tier: beta`. The dashboard customer browse at `/dashboard/marketplace` strips tier=internal by design (per marketplace concept: "internal = no public catalog entry"). Wave 1 is customer-facing — brand admins install `@opvs-ai/platform-skills` to get the OPVS platform. `beta` is the right tier per concept: "published + opted-in per brand, pre-1.0."
- Peer_dependency ranges still `^1.0.0` — matches 1.0.0, 1.0.1, AND 1.0.2 via npm-style.

### Changed

- Republished with `meta_coherence` fix (server-side 979b3b41) — score now 100/100. The 1.0.0 publish scored 95 due to a false-positive `meta.mixed_semantics` warning that penalised every package declaring `@opvs-ai/opvs-foundation` as a peer_dep. The warning has been removed; the BLOCKING `meta.empty_useless` guardrail stays.

### Added

- Initial marketplace release. Packages the in-tree `agentdocs@2.0.0` skill
  verbatim — ~28 methods covering projects, pages, search, history, media.
- Peer dependency on `@opvs-ai/opvs-foundation@^1.0.0`.