docs(p02): record guarded ACK and replay patch plus HTTP scope blocker [skip ci]

This commit is contained in:
victorsteele428 committed 2026-11-22 16:58:00 +06:00
1 parent 5c88088537
commit 6a873cb04f
6 files changed
+70

No files matched your search

+10
View File
@@ -107,3 +107,13 @@ Historical baseline code stayed frozen through these CI workflow changes. Curren
### Verification environment blocker — local dependency install
The authorized Windows PC attempted a **local disposable** `npm.cmd ci --ignore-scripts --no-audit --no-fund --prefer-offline` in the isolated P02 worktree only; it failed with `npm ERR! ETARGET No matching version found for yaml@2.9.1` plus cleanup EPERM warnings in the temp worktree's `node_modules`. Exact output captured in `%TEMP%\DataStack-P02-npm-ci.log` on the authorized PC. This is **not a passed code test nor proof of a repository package defect**, and `package-lock.json` / `package.json` cannot be edited under P02 scope. Gitea MCP remained UNAVAILABLE and the Git remote/HTTP service was not responding when CI was attempted, so the mandatory P02 focused CI was **not dispatched**. Phase remains BLOCKED pending actual CI evidence; no runtime change was pushed to production/main.
## P02-RUNTIME-REMEDIATION-02 — Post-patch evidence/status (2026-11-22)
- **P02 current status: BLOCKED / NOT CLOSED** by a separate Port 3000 HTTP RAM-ACK path (and until terminal CI evidence). Completed implementation phases remain **1/3** (P01 only); P03 not authorized.
- Baseline `fd57a3518d14bcb8367ce9ab9c3ec306bcfc9898`; isolated Gitea branch `p02-runtime-remediation-20261122`; inspected code commit `5c880885378ae0f4fa8dd3a145f9c7055dada635`. Original PC root `main` at earlier docs SHA with 16 user-staged P01 paths remains untouched. No force-reset, stash, production write or deployment.
- **Verified earlier focused CI #66:** 24/24 TS suites, strict TypeScript, ESLint, Windows/npm SDK and Next.js standalone production build success; Python/Docker jobs skipped as separate P03 work.
- **CI #68:** new same-ID retry test failed because an unproven duplicate had left a local claim set; this was corrected in handlers on the subsequent scoped code commit. #68 was cancelled after failure (logs preserved). **CI #70:** revised focused acceptance and added HTTP failure diagnostic; confirm actual terminal job conclusions before claiming PASS. The HTTP diagnostic is intentionally expected to expose an unresolved behavior, not fix it.
- P02 code changes confined to `server/index.js` selected ACK/buffer/flush methods, `server/socket/handlers.js` persistence ACK/duplicate proof methods, `core/data/buffer.ts` flush, and three approved test files; notes/001–006 only. R-03 public health unchanged. All other app/UI/auth/SDK/CI workflow/lockfile/Docker/runtime source unchanged.
- **Residual blocking source evidence:** `app/api/events/route.ts:744-754` returns success following `core/data/buffer.ts:412-442` silent Redis-error RAM fallback; Node SDK may switch to HTTP after negative WS ACK. A separate exact scope exception is required for end-to-end no-positive-ACK-on-volatile-data acceptance. Do not merge the blocked candidate into three `main` refs or assert P02 production ready.
- Performance boundary: replay checking can stream entire CSV partitions per flush (not throughput benchmarked); duplicate proof is capped at last 512 Redis queue items and 256 MiB/1.8s CSV proof (negative ACK on uncertainty). This is safer than a false positive, but compatibility under heavy ingestion must be reviewed before release.