docs(coding): record ML-04 host merge

.project-docs/30-worklog/tasks/20260827-makelore-plugin-client-7d3a91c4.md

@@ -8,7 +8,7 @@
 - Worktree: D:\Datas\OthersProjects\makelore-plugin-client-7d3a91c4
 - Base commit: eb5d15d68470b30ec181164f08f0d7b027ef0006
 - Owner: codex-root
-- Status: In Progress (ML-00 through ML-03 integrated; ML-04 frontier pending)
+- Status: In Progress (ML-00 through ML-04 integrated; ML-05 frontier pending)
 
 ## Scope
 
@@ -226,13 +226,47 @@
   dynamic declarations, bridge allowlisting, CLI agreement, child-empty
   exposure, disabled/re-enabled assignment, and old-worker behavior are
   covered by the owned focused suite. `git diff --check` passed.
+- ML-04 precondition and merge: coordinator was clean at exact frontier
+  `a92cd904d33d4fa0b7c2413188186852a39eb6d4`; source commit
+  `1e925bc10ade8aed1a580362dfa65223993e3a24` had that exact parent and
+  cherry-picked without conflict as
+  `a18727ecf8f40c1d85e2d40922bcf3bc8d1a0ed3`. The product change set contains
+  four Main API files (`coding-composition`, `coding-product-services`,
+  `route-handlers`, and `routes/coding-plugins`), three new focused tests, and
+  one existing Data Service server-registration test update. There are no
+  changes to `project-service`, preview, Renderer, P1, `electron/api/context.ts`,
+  `electron/api/server.ts`, or `electron/main/index.ts`; the source task record
+  remains in its worktree.
+- ML-04 focused verification:
+  `corepack pnpm exec vitest run tests/unit/coding-plugin-routes.test.ts
+  tests/unit/coding-plugin-composition.test.ts tests/unit/coding-plugin-lifecycle.test.ts
+  tests/unit/coding-product-services.test.ts tests/unit/data-service-server-registration.test.ts
+  tests/unit/coding-core-routes.test.ts tests/unit/coding-project-identity.test.ts
+  tests/unit/main-quit-lifecycle.test.ts --maxWorkers=1` — 8 files / 47 tests
+  passed (Vitest 4.73s). The route tests confirm exact GET
+  `/api/coding/plugins?projectId=...` and PUT `/api/coding/plugins/{plugin_id}`
+  bodies with Main-only authority; composition/lifecycle tests cover bounded
+  projection and `list`/`setEnabled`/`deactivate` wiring.
+- ML-04 adjacent policy/capability/Data Service/Pi/preview regressions:
+  `coding-capability-registry`, `plugin-policy-client`,
+  `data-service-plugin-adapter`, `coding-conversation-contracts`,
+  `pi-product-tools`, `data-service-routes`, `data-service-sdk-assets`,
+  `pi-extension-bundle`, `pi-extension-host`, `pi-resource-loader`,
+  `preview-data-session`, and `pi-worker-process-real` — 12 files / 86 passed /
+  2 skipped (Vitest 8.37s, one worker; skips are staged-runtime gated).
+- `corepack pnpm run typecheck` — passed. `corepack pnpm run lint:check` —
+  passed with 0 errors and the same 5 pre-existing warnings in
+  `src/pages/Home/index.tsx` and `src/pages/Makelore/index.tsx`.
+- `corepack pnpm run build:vite` — passed for Renderer, Main, Preload, and
+  utility bundles; only existing dynamic-import/chunk-size warnings were
+  emitted. `git diff --check` passed.
 
 ## Follow-ups
 
-- ML-04 may consume the effective plugin worker-resource snapshot, dynamic Pi
-  declarations/bridge/CLI materialization, and child-empty behavior from exact
-  product frontier `fd891ff3bb87a29381a0a7006fb4618ec4fe144f`; ML-04 owns its
-  Host/Renderer composition changes.
+- ML-05 may consume the bounded project-plugin projection and exact Main Host
+  routes from exact product frontier
+  `a18727ecf8f40c1d85e2d40922bcf3bc8d1a0ed3`; it owns the Renderer Plugin
+  Center surface and must keep Data Service configuration on its typed routes.
 - The legacy `resources/coding-skills/data-service` path is intentionally removed
   by ML-01; any unowned downstream reference must be migrated by its owning
   ticket. This merger made no such downstream edit.