chore(coding): record ML-01 package 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
+- Status: In Progress (ML-00/ML-01 integrated; ML-02 frontier pending)
 
 ## Scope
 
@@ -71,8 +71,19 @@
 - ML-00 completed: the client coordination unit is isolated from exact accepted
   Data Service evidence head, ownership/planning gates passed, and no product file
   changed before the first implementation frontier.
-- Current frontier after this checkpoint: ML-01. WS-01 proceeds independently on
-  the server branch.
+- Integrated ML-01 from replacement source commit
+  `c092863ee600808e8a7c15440b3c370fd649a885` at the exact ML-00 frontier
+  `2ab1c51a2404086cbd688ac80154765d7c5d4662` as coordinator product commit
+  `422150d4fabdcc703952797875f88f239ca1e37a`, with no cherry-pick conflict.
+  The superseded `f83038d371888cca87f0f04d0e61906d499668eb` was not
+  cherry-picked. ML-01 adds the fixed bundled Data Service plugin manifest and
+  capability projection, atomic project plugin selection service, package-owned
+  Skill/SDK resource move, and core Skill registry projection. The coordinator
+  foreign ML-01 task record is removed in the docs checkpoint while its source
+  record remains in
+  `D:\Datas\OthersProjects\makelore-plugin-ml01-package-selection-8d3c7a21`.
+  The exact downstream product frontier handed to ML-02 is
+  `422150d4fabdcc703952797875f88f239ca1e37a`.
 
 ## Verification
 
@@ -93,10 +104,40 @@
   initial task-context claim selected the clean root despite isolation arguments;
   the generated record/claim were removed through the normal release path before
   the successful isolated start from `eb5d15d...`.
+- ML-01 precondition and merge: coordinator was clean at exact frontier
+  `2ab1c51a2404086cbd688ac80154765d7c5d4662`; replacement source parent matched
+  exactly; cherry-pick produced `422150d4fabdcc703952797875f88f239ca1e37a`
+  without conflict.
+- ML-01 focused verification:
+  `corepack pnpm exec vitest run tests/unit/data-service-sdk-assets.test.ts
+  tests/unit/coding-plugin-manifest.test.ts tests/unit/project-plugin-service.test.ts
+  tests/unit/skill-display.test.ts tests/unit/pi-product-tools.test.ts
+  --maxWorkers=1` — 5 files / 45 tests passed (Vitest 3.15s).
+- ML-01 `corepack pnpm run typecheck` — passed.
+- ML-01 `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`.
+- Scoped ESLint over ML-01-owned source/tests — passed with no output.
+- The Skill and SDK resource move is byte-for-byte (`R100`). The ML-01-owned
+  `tests/unit/data-service-sdk-assets.test.ts` assertion now targets the
+  canonical package path and passed; this merger did not edit unrelated tests.
+  Any remaining consumer of the removed legacy
+  `resources/coding-skills/data-service` path must migrate under its owning
+  ticket, not this merger.
+- ML-01 path/scope audit matched the source change set: package manifest/service,
+  existing Skill registry/shared definitions, plugin resources, and focused tests
+  only. No P1 policy/capability-invoke, Pi runtime, Host, Renderer,
+  marketplace/download/update, generic execution, pricing, or billing paths were
+  added. `git diff --check` passed.
 
 ## Follow-ups
 
-- None recorded.
+- ML-02 may consume the exported bundled-plugin definitions and
+  `ProjectPluginService` callback interfaces from exact product frontier
+  `422150d4fabdcc703952797875f88f239ca1e37a`.
+- 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.
 
 ## Promotion Candidates