chore(coding): record ML-04 integration

.project-docs/30-worklog/tasks/20260826-makelore-data-service-client-b72e4c19.md

@@ -105,6 +105,20 @@
   client now rejects known error codes paired with undocumented HTTP statuses
   as `upstream_invalid_response`, with one focused regression test. The ML-04
   frontier is `6b36753` plus this coordinator record commit.
+- Integrated ML-04 from source commits
+  `e4fdeaea02cab216f4e7ff4543d57ca9e2aab33b` and
+  `93609d5890b6be4c51c083125d3d8ab7ebd3d02d` in the requested order as
+  coordinator commits `1d63233cd03425e9158b9c4868b3cfc0e508bc6f` and
+  `f61990f3a7f5ea417ca3eecc6702e71398f77d7f`. Git auto-merged the known
+  `data-service-client.ts` overlap without a conflict; the ML-03
+  `ERROR_STATUS_BY_CODE` ↔ HTTP-status validation remains alongside the ML-04
+  trusted `projectPath` authority seam. The ten parent-only underscore tools,
+  closed inputs, shared in-process `DataServiceOperations`, safe details and
+  literal confirmation behavior are retained. The foreign ML-04 task record
+  was removed from this coordinator after both cherry-picks; the source record
+  remains in `D:\Datas\OthersProjects\makelore-ml04-pi-data-tools-8d3c91a7`.
+  The ML-04 frontier is `f61990f3a7f5ea417ca3eecc6702e71398f77d7f` plus this
+  coordinator cleanup/record commit.
 
 ## Verification
 
@@ -169,13 +183,36 @@
 - Correction cherry-pick was applied from the exact `e15d8b7` coordinator
   frontier; only the expected foreign task-record modify/delete conflict
   occurred, and the source record remains in the source worktree.
+- The coordinator already had this task's Git-common ownership in feature mode
+  under `codex-root`; the required integration-mode resume was rejected by the
+  task gate, so the same task was resumed in its existing feature mode without
+  changing ownership, branch, or worktree.
+- ML-04 Pi focused suite: `pnpm exec vitest run
+  tests/unit/pi-product-tools.test.ts tests/unit/pi-extension-bundle.test.ts
+  tests/unit/pi-extension-host.test.ts --maxWorkers=1` — 3 files / 23 tests
+  passed.
+- ML-04 Data Service/projector + Pi focused suite:
+  `pnpm exec vitest run tests/unit/data-service-client.test.ts
+  tests/unit/data-service-routes.test.ts
+  tests/unit/data-service-server-registration.test.ts
+  tests/unit/coding-conversation-contracts.test.ts
+  tests/unit/coding-conversation-timeline.test.tsx
+  tests/unit/coding-product-tools-facade.test.ts
+  tests/unit/pi-extension-ui-projector.test.ts
+  tests/unit/pi-product-tools.test.ts tests/unit/pi-extension-bundle.test.ts
+  tests/unit/pi-extension-host.test.ts --maxWorkers=1` — 10 files / 62 tests
+  passed.
+- ML-04 `pnpm typecheck`: passed.
+- ML-04 `pnpm 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`.
+- ML-04 `git diff --check`: passed after the foreign task-record cleanup.
 
 ## Follow-ups
 
 - ML-02 identity choice and legacy/independent-copy UX plus ML-03 Main Data
-  Service are integrated. ML-04 must consume the `DataServiceOperations` seam
-  from the recorded ML-03 frontier and preserve its active-project identity
-  and trusted project-path constraints.
+  Service and ML-04 Pi Data Service tools are integrated. ML-04 consumed the
+  `DataServiceOperations` seam from the recorded ML-03 frontier and preserves
+  its active-project identity and trusted project-path constraints.
 - The broader ML-00 through ML-09 coordinator task remains in progress; this
   record does not claim full client-suite, build, review, or release proof.