cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(redesign): reconcile integration failures and release qualifications

Browse Source
This commit is contained in:
cesnimda
2026-10-21 07:32:45 +02:00
parent 9b17b04d61
commit 59ac1b5049
7 changed files with 952 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-7/p7-12/README.md
+6
View File
@@ -2,6 +2,12 @@
## Continuation — 21 October
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.
Production observations05:22:25UTC show health/ready/root HTTP200and healthy core containers, but source checkout remains7d641ed and backend version metadata contains literal unevaluated shell expressions. This does not verify the requested release identity. AI still runsqwen2.5:7b; model activation remains pending the live-release priority. CI837's matching Python/.NET native-crash evidence and the earlier production F04/restore/configuration/rollback gates remain open; no production GO is inferred.
The first complete successor run failed103/351, with248unexpected failures and zero skips/flaky/retries; it is not accepted. [Fixture investigation](FIXTURE_ISOLATION.md) and [portable evidence](evidence/fixture-repair.json) separate administrative role/language contamination from an unresolved isolated Audit500. The corrected shared-fixture composition passes16/16. Existing409/403/503, ownership, source/save and route assertions remain; no test is removed or relaxed. The final whole run and separate lanes still follow. The earlier18:52:58UTC clean publication of entry evidence `ddb9c3da4ff31447fa6bd579002f32199052937d` remains historical, not final acceptance.
Separately, parser native-exit diagnostics `dda16873455259bce23a744bd838c3e3e0fc6ee8` are pushed on development and equivalent main8699ae4 is normally pushed/directly verified21October05:13:39UTC. Release837 remains unqualified: it subsequently failed in native MSBuild/.NET test compilation after the parser process succeeded. No deployment/model activation is claimed. The [parser report](../../../infrastructure/2026-10-21-parser-native-exit.md) preserves the earlier distinct SIGSEGV and diagnostic-only scope.