| P01 Tests & lockfile | BLOCKED — partially implemented; NOT CLOSED | CI-01,02,03,04,05 | 16 P01 allowlisted paths on disposable branch `p01-ci-verification-20261122`; no runtime source changed | Gitea #58 FAIL: Windows and Linux `npm ci` report missing `@tybys/wasm-util@0.10.5`; tests and typecheck NOT EXECUTED | CI snapshot `90fce0629a752dd2916d8d3a2afeaf2c52ed6cbb`; not merged to main or synced |
Historical baseline code stayed frozen through these CI workflow changes. Current HEAD before documentation changes = `d725841ebc828d58cbe90f517da9e600f23c4630` on local/GitHub/GitLab/Gitea.
## Per-phase closure record template — COPY for each P01/P02/P03
- Frozen source baseline remains `d725841ebc828d58cbe90f517da9e600f23c4630`; latest source HEAD before P01 was documentation commit `d8ac96e39dad4ea3b241c1d2f16f959c5215701e` on all three remotes.
- Disposable CI commit `90fce0629a752dd2916d8d3a2afeaf2c52ed6cbb` contains **16 P01-allowed paths**: `bun.lock` deletion, `package-lock.json` optional/native metadata closure (+67 entries, no existing version or root-manifest change), 14 scoped test files, and `.gitea/workflows/datastack-ci.yml` clean-install/phase-filter changes. No application runtime source/UI/SDK/Docker changes.
- Gitea run: https://dev.ivib.cc/vibtools/DataStack/actions/runs/58; overall **FAIL**, terminal. `windows-compatibility`, `node-regression`, `quality`, `production-build` all failed during clean `npm ci`: `Missing: @tybys/wasm-util@0.10.5 from lock file`. The Python and Docker jobs were intentionally skipped for P01. **No current TypeScript test, strict typecheck, ESLint or build PASS may be claimed**.
- Root issue likely parallel incompatible transitive requirement of `@tybys/wasm-util`; inspect `node_modules/@napi-rs/wasm-runtime` vs `node_modules/@tailwindcss/oxide-wasm32-wasi` in lock and install exact requested transitive version under correct nested path without changing existing pinned entries. Then verify npm clean-install on both platforms and rerun focused P01 acceptance once after repair; do not blindly override lock integrity.
- Local original Windows device's VARUA connection reached monthly call quota; local changes were staged via safe squash on `main` but **no P01 main commit/push** occurred. A separate connected desktop did not have this workspace. Do not claim local/3-remote post-P01 sync until verified.
- Completed implementation phases **0/3**, remaining **3**. P01 status BLOCKED, P02 must NOT start until P01 passes and closes. Preserve all working changes; do not force push or deploy.
- OPEN -> IN PROGRESS only with explicit approval and baseline SHA match.
- IN PROGRESS -> CLOSED only after one focused CI and exact diff audit, updated `003` + `005` + relevant `001/004/006`, Git commit, sync, and confirmed remote SHA.
- Failed test -> BLOCKED with log excerpt and scope decision; never log as complete.
- Unexpected file change -> STOP and revert only own documented changes safely; never touch pre-existing work.
- At any time, `actual production deployment status` is a separate tracked dimension (do not infer deployed SHA from Git HEAD).