docs(coding): record ML-07 R3 remediation

This commit is contained in:
2026-08-27 21:47:02 +08:00
parent e3e34d3803
commit 07ea9da858
2 changed files with 27 additions and 64 deletions

View File

@@ -409,6 +409,33 @@
## Follow-ups
## ML-07 R3 Review And Remediation
- The third fixed-range Standards and Spec reviews over exact
`eb5d15d68470b30ec181164f08f0d7b027ef0006...405b9f64fd6872f6b4bd4c4429e6aaff2fa0b84a`
agreed on one remaining medium-severity root cause: a same-project manual refresh
could race enable/configure/reset/removal mutations, allowing an old GET to
overwrite a successful mutation or causing the successful mutation and its
authoritative reload to be discarded.
- The same sole remediation implementer returned source commit
`92bce15a7e70440e78b2ff8d90b2e57470d14d77` with exact parent
`405b9f64fd6872f6b4bd4c4429e6aaff2fa0b84a`; it integrated without conflict as
coordinator commit `e3e34d3`. The foreign source task record is removed here and
remains in its isolated source worktree.
- A per-project operation epoch now separates internal load flights by project and
epoch. Successful mutations advance the epoch before committing, so reads begun
before or during the mutation cannot win and post-mutation authoritative reloads
cannot coalesce with stale flights. The existing stable public pending key and the
latest-requested-project A-to-B guard remain intact.
- Source verification recorded the expected red failures for all supported race
orderings, then 13/13 store tests and 4 files / 22 expanded focused tests passed;
typecheck, scoped ESLint, full lint, diff, documentation drift, and task completion
gates passed. No UI, Main, Preload, package, or asset ownership was used.
- After integration, coordinator `corepack pnpm test` passed 201 normal files /
1,692 tests with 2 staged-runtime skips, followed by the isolated pressure file
1/1 (202 files / 1,693 passed / 2 skipped total). Coordinator typecheck passed;
full lint reported 0 errors and the unchanged 5 warnings in Home and Makelore.
- 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