docs: checkpoint ML-05 integration

This commit is contained in:
2026-08-27 18:45:42 +08:00
parent cb1fd2629c
commit 8fea40238f
2 changed files with 37 additions and 63 deletions

View File

@@ -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-04 integrated; ML-05 frontier pending)
- Status: In Progress (ML-00 through ML-05 integrated; ML-06 frontier pending)
## Scope
@@ -261,12 +261,44 @@
utility bundles; only existing dynamic-import/chunk-size warnings were
emitted. `git diff --check` passed.
## ML-05 Integration
- Integrated ML-05 from source task
`20260827-plugin-ml05-plugin-center-6c1e9a42` and sole source commit
`379e575efba8cecb17b10e5e195f05924b827782`, whose exact parent was the
coordinator frontier `b6d9e6156fdc98aa792045692cc25fdce993a531`.
The cherry-pick produced coordinator product commit
`cb1fd2629ce861f72eada35a83e730986fb1c3d1` without conflict. The source
commit contained its source task record plus fourteen Renderer/product-test
files; the foreign task record was deleted from this coordinator in this
checkpoint while the source record remains in
`D:\Datas\OthersProjects\makelore-plugin-ml05-plugin-center-6c1e9a42`.
ML-05 adds the project-scoped Plugin Center, typed project-plugin client/store,
Data Service settings surface, and project navigation. It does not add Main
authority, worker, preview, policy, marketplace, or P1 behavior. The exact
downstream product frontier handed to ML-06 is the post-merge docs checkpoint
recorded below.
- ML-05 focused regression command (using the repository's actual singular
`coding-plugin-routes.test.ts` filename) passed 13 files / 75 tests in 8.64s
with one worker. `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 with only existing dynamic-import/chunk-size warnings. After this
required build, `corepack pnpm exec playwright test
tests/e2e/project-plugins.spec.ts --config=playwright.config.ts` passed 1/1
test in 1.7s. A preliminary direct Playwright invocation against stale
`dist-electron` timed out waiting for the new navigation test id; it is not
counted as a product failure because the repository E2E contract builds first.
## Follow-ups
- 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.
- ML-06 is the coordinator-owned packaged-proof frontier from the exact
post-ML-05 product/docs checkpoint; it may edit only the Pi artifact proof
library, verifier, and focused test named by the ticket. It must prove the
bundled plugin manifest, Skill, SDK assets, adapter/tool catalog, and core
resources without restoring a static Data Service list or adding checksums,
arbitrary execution, generic config/ledger/invoke, publication, or P1 scope.
- 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.