Repository navigation
[P2 docs] Refresh compiler-architecture target registry and capability evidence for Amp #755
Description
Activity
Closed by #758, squash-merged as
0ef0436ef79737485b9f8698d246edc5c6fb115a.Ask Where it landed ampin the built-in adapter/planner table, naming its module and pinned capability JSONguide/concepts/architecture.mdx(en + zh):ampAdapter.planinadapters/amp.ts,adapters/capabilities/amp-0.0.0-20260907001852-gf348fed.jsonRegistry prose includes Amp, without implying order is author-facing precedence The createDefaultRegistryparagraph now ends withampand saysplanCompositesorts the selection (sortedProjections) before planning, with the composite identity the sorted name joinAmp's architectural difference, briefly, linking the generated matrix rather than copying it One paragraph: a generated index.jsPluginAPI factory under.amp/plugins/{plugin}/, Skills and callbacks registered through the API, skill-scoped MCP (exactly one Amp Skill for a canonical server; a compiler-owned local server refused for want of a documented plugin-root placeholder). Links the generated Hosts page and the capability map from #754Keep portablethe default andplugina non-targetBoth sentences kept verbatim Remove stale wording implying four built-in adapters "Four planners, one merge" → five, including ampAdapter.plan;BundleIdentityHostcorrected toamp | claude | codex | cursorwith the note thatDoctorHostexcludes AmpAcceptance:
pnpm docs:site:buildgreen (locale drift, diagnostics coverage, language parity,
0 broken links over 30105 anchors), pluspnpm build,pnpm typecheck,pnpm lint, and
pnpm test:unit(4480 tests, 0 failures). The built site was searched for stale
"complete built-in registry" enumerations; the only remaining four-host list is the host-scoped
config keys inreference/configuration.mdx, which is correct — the Amp adapter declares no
configExtension.Review caught one real error in the first draft: the composite-root paragraph had been extended
to claim Amp reads the artifact directory as its plugin root and sharesskills/,hooks/,
mcp/,scripts/,bin/, andINSTALL.md. Amp's root is the nested.amp/plugins/<plugin>/
directory, self-contained down to its ownskills/andhooks/, andinstall ampcopies only
that subdirectory. The merged text states the exception.
Documentation drift
Audited docsite against main
14c9822bc6c01d8ff2788454d0e1dc7861bc3816while expanding #754.website/docs/{en,zh}/guide/concepts/architecture.mdxstill describes the pre-Amp target registry:claude,codex,cursor, andportable;createDefaultRegistryregistersportable, thencodex,claude, andcursor;ampadapter and its pinnedamp-0.0.0-20260907001852-gf348fed.jsoncapability evidence.Current production registry/tests include Amp as a built-in target. The convention-first/capability pages in #754 already present all five targets correctly, so the architecture page should not contradict them.
Required correction
Update both locales together:
ampto the built-in adapter/planner table, namingadapters/amp.tsand the pinned capability JSON..amp/plugins/<name>/, API-registered callbacks/Skills, and skill-scoped MCP constraints. Link to the generated Hosts matrix instead of copying its detailed evidence.portableas the default target and keep the statement thatpluginis not a target.Acceptance
Run the docsite locale-drift/link/anchor gates and search the built site for stale statements equivalent to “portable, codex, claude, and cursor” where the text is claiming the complete built-in registry. The generated
hosts.md/events.md/notices.mdremain authoritative for detailed capability states; do not hand-copy those matrices into architecture.This is documentation only. It does not request another adapter, target registry, capability system, or changes to Amp runtime behavior.