docs(coding): record ML-06 verification
This commit is contained in:
@@ -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-05 integrated; ML-06 frontier pending)
|
||||
- Status: In Progress (ML-00 through ML-06 complete; ML-07 fixed-range review pending)
|
||||
|
||||
## Scope
|
||||
|
||||
@@ -124,6 +124,18 @@
|
||||
frontier handed to ML-04 is
|
||||
`fd891ff3bb87a29381a0a7006fb4618ec4fe144f`.
|
||||
|
||||
- ML-04 and ML-05 are integrated through their exact dependency frontiers. ML-04
|
||||
composes the bounded Main-owned project plugin Host projection and lifecycle;
|
||||
ML-05 adds the project-level Plugin Center and typed Data Service settings without
|
||||
moving project, credential, policy, or billing authority into Renderer.
|
||||
- ML-06 completed from exact post-ML-05 checkpoint
|
||||
`8fea40238fcb6431fd805c7dd0d717bef0cfd1bb`. Packaged-proof commit
|
||||
`7141a91a2c1c00881b18702508d2be8a398a0823` verifies the bundled plugin
|
||||
manifest, capability manifest, Skill, TS/JS SDK assets, adapter/tool catalog,
|
||||
core coding resources, and final Pi runtime artifact. The implementation range
|
||||
contains no arbitrary plugin execution, generic invoke/config/ledger,
|
||||
marketplace, publication coupling, `plugin_charges`, Plugin Credits, or P1 code.
|
||||
|
||||
## Verification
|
||||
|
||||
- `git rev-parse HEAD` before the checkpoint returned exact
|
||||
@@ -291,14 +303,60 @@
|
||||
`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.
|
||||
|
||||
## ML-06 Merge, Package Proof, And Verification
|
||||
|
||||
- Exact ML-06 base/checkpoint:
|
||||
`8fea40238fcb6431fd805c7dd0d717bef0cfd1bb`; packaged-proof product head:
|
||||
`7141a91a2c1c00881b18702508d2be8a398a0823`. The product commit changed only
|
||||
`scripts/lib/pi-product-artifact.mjs` and
|
||||
`tests/unit/pi-product-artifact.test.ts`; no semantic merge conflict or
|
||||
ownership transfer occurred.
|
||||
- `corepack pnpm exec vitest run tests/unit/pi-product-artifact.test.ts
|
||||
--maxWorkers=1` — 1 file / 7 tests passed.
|
||||
- `corepack pnpm run typecheck` — passed. `corepack pnpm run lint:check` —
|
||||
0 errors and the same 5 pre-existing warnings in `src/pages/Home/index.tsx`
|
||||
and `src/pages/Makelore/index.tsx`.
|
||||
- `corepack pnpm test` — normal suite 200 files / 1,667 passed / 2 skipped,
|
||||
followed by the isolated pressure suite 1 file / 1 passed. Combined result:
|
||||
1,668 passed / 2 staged-runtime skips.
|
||||
- `corepack pnpm test:electron:windows` — 2 files / 5 tests passed.
|
||||
- `corepack pnpm test:e2e` rebuilt Renderer/Main/Preload/utility and completed
|
||||
26 passed / 1 failed. The failure exactly reproduces the frozen baseline:
|
||||
`pi-coding-first-chat.spec.ts` timed out after 30 seconds because the existing
|
||||
`当前对话模型` combobox remained disabled at `selectOption`. The new
|
||||
`project-plugins.spec.ts` passed. The failure is recorded, not converted to a
|
||||
pass and not attributed to Plugin Center.
|
||||
- A fresh `corepack pnpm run package:win` rerun could not reacquire fixed uv
|
||||
`0.10.0`: GitHub first reset the connection and the one targeted retry timed
|
||||
out before product packaging. The worktree remained clean. The already-built
|
||||
Windows artifact was independently verified as current head rather than
|
||||
assumed from its timestamp:
|
||||
- `corepack pnpm run verify:artifact:win` passed and reported both
|
||||
`gitCommit` and `verificationHead` as exact
|
||||
`7141a91a2c1c00881b18702508d2be8a398a0823`, with packaged
|
||||
Python, uv, npm, Electron, Node, and native modules present.
|
||||
- `corepack pnpm run verify:artifact:pi` passed the outer product-artifact
|
||||
contract and proved one `makelore.data-service` package, its manifest,
|
||||
capability manifest, `data-service` Skill, both SDK assets, adapter, exact
|
||||
ten-tool catalog, core coding resources, Pi closure, and packaged runtime
|
||||
probe. The nested legacy runtime report remains `partial-pass` only for its
|
||||
recorded cross-platform/real-provider waivers; no such waiver is promoted to
|
||||
a Plugin Platform pass.
|
||||
- `git diff --check eb5d15d...7141a91` passed. Full-range path/content review
|
||||
found only canonical manifest/registry lists and negative unsupported-component
|
||||
tests; it found no static Pi CLI Data Service allowlist, arbitrary execution,
|
||||
generic ledger/config/invoke, marketplace/publication coupling, checksums, or
|
||||
P1 implementation.
|
||||
|
||||
## Follow-ups
|
||||
|
||||
- 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.
|
||||
- ML-07 must review the fixed committed range from exact
|
||||
`eb5d15d68470b30ec181164f08f0d7b027ef0006` through the final ML-06 docs
|
||||
checkpoint along independent Standards and Spec axes. Accepted findings route
|
||||
to one remediation implementer, followed by repeat fixed-range review.
|
||||
- After ML-07 passes, X-01 still requires a real PostgreSQL 16 server and a
|
||||
packaged, signed-in MakeLore preview; repository tests and packaged probes do
|
||||
not replace its twelve live groups.
|
||||
- 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.
|
||||
|
||||
Reference in New Issue
Block a user