docs(redesign): freeze WAL successor and reconcile acceptance evidence

This commit is contained in:
cesnimda
2026-10-21 08:09:51 +02:00
parent 2f772e1322
commit 32e464f612
9 changed files with 1059 additions and 6 deletions
+4
View File
@@ -2,6 +2,10 @@
## Continuation — 21 October
Latest source is clean/directly synchronized development `2f772e132274e75a05deb0a0dd363dadebc9175a`, verified06:05:08UTC. [WAL successor identity](evidence/wal-entry.json) freezes792runtime inputs and rebuilt API/test assemblies before the new complete run06:05:40UTC. This supersedes the earlier791-input snapshots. The [SQLite concurrency repair](SQLITE_CONCURRENCY.md) reproduces the same write stack deterministically, enables WAL before SQLite reconciliation and passes1060backend cases,6focused cases and17affected native cases. The [pagination fixture](USERS_PAGINATION.md) navigates the actual populated desktop grid. Both are separately committed/pushed; no product assertion or timeout is weakened. Full351-case browser and separate lanes remain in progress, with no final acceptance claim.
The prior patched-source attempt was explicitly stopped05:55:08UTC after144passing and3failing logged cases. [Failure observations](CURRENT_FAILURES.md) and [raw hashes](evidence/lock-observation.json) retain both SQLite client failures and the first-page fixture assumption. Release838 independently failed with matching Node/Jest SIGSEGV cores and deployment skipped; main5f835e5/live/model qualification remains separate and production NO-GO. Older observations below remain chronological.
Latest source continuation is normally pushed development `9b17b04d61513b8e3c909e4da74998d4cadb1e83`, verified05:30:49UTC. The fixture repair `b39a5af4dec0c0e7d471fea5122b41095ff21453` was pushed/verified05:21:31UTC; [protected-action help](ADMIN_HELP.md) `44458f4f3a1ba218a309aa74351b02a04f042d00` was pushed/verified clean05:23:06UTC. Its10component/3native cases and fresh build/types/lint pass; no case is added. A fresh899/101frontend,1057backend and56sidecar run also passes21October; whole browser/separate lanes remain required.
The pre-security source snapshot [final-entry.json](evidence/final-entry.json) is **superseded**, not final acceptance. That candidate browser run was interrupted after22passing cases when the fresh registry audit introduced two production-classified high findings in follow-redirects1.16.0. [The bounded1.16.1patch](../../../infrastructure/2026-10-21-follow-redirects-patch.md) changes one lock entry, passes two loopback credential-stripping contracts and returns production audit to0vulnerabilities; full audit policy retains only the approved dev-only high exception plus recorded moderate development findings. Patched build/types/lint pass. Security repair9bb8b1a is pushed; equivalent main5f835e5 is normally pushed/directly verified05:30:46UTC. A fresh patched-source snapshot and complete run follow, with the partial pre-patch log retained.