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

docs: publish Phase 9 requalification decisions and evidence
MariaDB persistence qualification / mariadb (push) Failing after 7s
Details

Browse Source
This commit is contained in:
cesnimda
2026-10-24 18:32:24 +02:00
parent 7092697cb3
commit 3727a723e8
22 changed files with 53642 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-9/p9-requal-01/FINDINGS.md
+22 -1
View File
@@ -1,6 +1,6 @@
# P9-REQUAL-01 findings and independent gate register
Source review dated 24 October 2026 on `fix/p9-ci-and-requalification`, baseline `549b2cba5a791862ba3f854312ea819a86dc42a0`. This register covers RD01–RD28, every retained P9 finding, and M09-01–10. [Machine-readable register](findings.json) contains source, evidence, impact, dependency, owner, status and required closure for each entry. Fresh execution is pending the root-owned validation ledger; every result referenced below is historical unless explicitly updated there.
Source review dated 24 October 2026 on `fix/p9-ci-and-requalification`, baseline `549b2cba5a791862ba3f854312ea819a86dc42a0`. This register covers RD01–RD28, every retained P9 finding, and M09-01–10. [Machine-readable register](findings.json) contains source, evidence, impact, dependency, owner, status and required closure for each entry. Final fresh results are in validation.json and the dated addendum. Historical rows below retain their original observations; the final disposition table supersedes pending execution wording without rewriting historical reports.
The original [REQUEST §§6,13,18](../REQUEST.md) distinguishes completed assessment from acceptance and explicitly says “Carry uncompleted checks into the release gates.” It permits transparent human-check carry-forward; it does not invent human PASS results. Production-only storage/backup/deployment conditions do not automatically veto isolated functional QA. Each unmet functional criterion still needs a specific disposition. The [master cleanup criterion](../../IMPLEMENTATION_PLAN.md#phase-10--cleanup) requires proof that no route still uses removed code, tests pass and the functionality inventory is satisfied. Neither conditional Phase9 acceptance nor an open manual checklist satisfies these deletion criteria by itself. No Phase10 implementation is authorized.
@@ -94,3 +94,24 @@ No current final verdict is locked by this source register. Root must reconcile
## Additional verified provider defect
P9-REQUAL-DB01: actual MariaDB Documents UNION failed on mixed startup name collations. [Repair and real RED/GREEN evidence](DOCUMENTS_PROVIDER_REPAIR.md) records the narrow read-only fix, three new cases and full35/35 MariaDB plus1123/1123 backend successors. Broad final-source qualification remains separate. The register now contains58 unique findings.
## Final source-bound dispositions
This section and findings.json supersede provisional/pending wording above. There are59 unique findings. Complete automation is **not passing**: Linux PDF fidelity fails and Python advisory disposition remains open.
| Finding | Final bounded disposition |
| --- | --- |
| RD03 | Fresh MariaDB12.2.2:35 integration cases,1 native recovery,2 HTTP cases and15-minute workload PASS; broader deployed parity remains PARTIAL. |
| RD05 | Hosted MariaDB BLOCKED: inspected847/849 fail first isolation gate; no database tests. Existing host network/socket binding is not safe service isolation. |
| RD10 | Windows24 fixtures/60 pages PASS; Linux13/24 fixtures PASS,65 exported versus60 expected pages: P9-REQUAL-PDF01 OPEN; physical printing NOT TESTED. |
| RD17 | Finite exclusive MariaDB workload PASS:250 applications,2 readers,900006ms,3382 reads,20 navigations,zero failures and selected exact-state checks; no capacity SLA. |
| RD21 | RESOLVED within original six save/concurrency clauses and tested scope; fresh source-bound provider/browser/regression evidence. Creation-intent idempotency remains separate OPEN debt. |
| P9-SEC-01 | Compatible NuGet/npm repairs and fresh regression PASS; Python P9-REQUAL-SEC04 OPEN, coverage INCOMPLETE. No blanket security PASS. |
| P9-PUB-01 | Normal checkpoint pushes verified through7092697; final publication follows ledger and direct remote receipt. No force-push or main change. |
| P9-REQUAL-DB01 | LOCALLY REPAIRED at2b26953; three real RED/GREEN cases, full35 MariaDB/1123 backend and complete successor browser/workload PASS. |
| P9-REQUAL-SEC01 | LOCALLY REMEDIATED; post-pin audits zero and complete affected frozen-source successors PASS; production NOT DEPLOYED. |
| P9-REQUAL-SEC02 | LOCALLY REMEDIATED; post-pin audits zero and complete affected frozen-source successors PASS; production NOT DEPLOYED. |
| P9-REQUAL-SEC03 | LOCALLY REMEDIATED; post-pin audits zero and complete affected frozen-source successors PASS; production NOT DEPLOYED. |
| P9-REQUAL-PDF01 | OPEN: Linux producer5/5 PASS but fidelity9/16 and settings4/8 PASS;65 exported versus60 expected pages. Root cause not yet isolated. |
P9-T01/L01/V01/V02/T02/T03 have passing mapped fresh automated successors; no human row is promoted. The authoritative five decisions are in [the final addendum](ACCEPTANCE_ADDENDUM_2026-10-24.md). Hosted infrastructure, Linux output and Python risk require distinct owners and closure evidence.