Task: Inspect MakeLore Web Search Plugin seams

Identity

Inspect the exact MakeLore Main, Marketplace Package Store, effective plugin resolver, capability registry, Pi worker, conversation-envelope, and Renderer seams needed by a future makelore.web-search hosted Plugin.
Record client ownership and acceptance requirements in the server-side task-owned Web Search design/spec. Do not implement product code in this client root.

The installed schema-2 package remains declarative; only a code-owned Main adapter may call the fixed Works Square typed route. Pi and Renderer never receive Provider secrets or arbitrary endpoints.
A tool is materialized only for an acquired, installed, compatible, project-enabled, Agent-assigned, admitted and currently supported Release, parent worker only. Existing account/project/logout/worker invalidation and stable logical-operation identity apply.
Preserve the generic Marketplace/My Plugins surfaces and makelore-capability.v1 conversation parser. P0 needs no plugin-specific Renderer panel.
Concurrent Task Gate: PASS. This clean root was claimed at exact base bf32fecd6013101485434b1977a73beb8b6a1fe3; no other active writer owns this semantic slice and only this task record is changed.
Planning Gate: PASS after loading AGENTS, project memory, current plugin source and tests. The project-positioning document is still a template and is therefore recorded as stale context; AGENTS, current-state, exact source, and tests are the implementation authority for this inspection.

Completed a read-only client seam inspection and fed exact ownership/acceptance requirements into the server task's detailed design and implementation Spec.
Confirmed Web Search can remain a signed schema-2 platform_hosted package with one code-owned Main adapter; no static Pi allowlist, third-party executable, Provider secret/model, generic invoke route, or Plugin-specific results page is required.
Identified one necessary generic UI change: the conversation timeline may render the closed billing union, while web-search.v1 answer/sources remain tool payload used by the Agent and preserved by conversation details.
No client product file was changed.

Inspected current Package Store, Marketplace client, effective resolver, capability registry, Game Resource hosted adapter, Pi worker materialization, conversation parser, timeline, composition and their focused tests at exact base bf32fecd6013101485434b1977a73beb8b6a1fe3.
Confirmed CapabilityBillingReceiptV1 currently has no Main transport-ambiguity variant and the generic timeline currently shows only operation/outcome; both changes are explicitly owned by MLW-02/MLW-03 rather than silently assumed.
Final check_project_docs and task-aware check_doc_drift pass.

Start client implementation only after the server WSW-03 typed DTO is frozen, then follow MLW-01 -> MLW-02 -> MLW-03 and fixed-range review from the current integrated client frontier.