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

docs(redesign): record saved-search repair acceptance

Browse Source
This commit is contained in:
cesnimda
2026-10-09 15:30:16 +02:00
parent 2753d03db6
commit c8e32238ef
15 changed files with 1594 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-5/p5-15/p5-15-01/DEFECTS.md
+5 -3
View File
@@ -1,12 +1,14 @@
# P5-15-01 functional defect register
**R-01 current disposition:** DISCOVERY-01 is **CLOSED for the verified SQLite listing/error/recovery defect** by the [bounded repair](saved-search-repair/README.md). Live deployed-provider qualification and complete PRES-J02 delivery/device acceptance remain open. AUTH-01 and SETTINGS-01 remain P2/OPEN; current reproduced open counts areP0=0/P1=0/P2=2/P3=0. Original reproduction/severity/evidence below remain historical; closing this defect does not erase release blockers or grant full-group PASS.
Audit source `932b962b9038ddb5ad59b982c0199475bfb50454`. Findings use synthetic accounts and disposable local data; no production account, provider or infrastructure is exercised. An audit finding is not automatically a regression introduced by Phase 5. Application source is unchanged here; neither source inspection nor an InMemory pass can override a native failure.
P0 means serious security/data loss; P1 an important broken workflow; P2 limited/recoverable functional failure; P3 minor inconsistency. Missing evidence is a gap, not a defect. The original [debt register](../READINESS_DEBT.md) remains authoritative for separately carried items. This register assigns concrete remediation; it does not authorize or perform it.
## P5-15-01-DISCOVERY-01 — Saved-search listing fails on SQLite
**Confirmed P1 / OPEN.** PRES-J02; `/discover`; `GET /api/job-discovery/saved-searches`. Current local SQLite workflow is NO-GO. Production release remains blocked until the supported/provider-specific path is verified and repaired as appropriate; a SQLite exception is not proof of the deployed MariaDB result.
**Confirmed P1 at audit / CLOSED by R-01 for the verified SQLite defect.** PRES-J02; `/discover`; `GET /api/job-discovery/saved-searches`. The original local SQLite workflow was NO-GO; see the successor native proof. Production release remains blocked by its separate readiness/provider verification obligations; a SQLite exception is not proof of the deployed MariaDB result.
| Field | Evidence-based finding |
|---|---|
@@ -72,6 +74,6 @@ The two standalone [preference diagnostics](diagnostics/README.md) assert intend
| P5-13 and `followMode` compose UI | Approved deferrals, not accidental dead controls. P5-13 remains unqualified/Production-withheld; metadata-only followMode survives the current route contract |
| F04, current backup/restore, production config/schema/keys and rollback | Existing release blockers remain NOT VERIFIED. No deployment/production checks or `main` push are performed here |
**No P0 is demonstrated by the collected evidence.** That is a bounded finding, not an exhaustive security certification. P1 saved-search verification/acceptance and dependent activity remain blocked pending a separate repair; independent audit evidence can still be collected safely.
**No P0 is demonstrated by the collected evidence.** That is a bounded finding, not an exhaustive security certification. At the original audit, P1 saved-search verification and dependent activity were blocked; R-01 now supplies the scoped repair proof; independent audit evidence can still be collected safely.
Confirmed finding totals: **P0 0 / P1 1 / P2 2 / P3 0**. These are three distinct failures, not the same count as failing browser cases: normal/admin cases share DISCOVERY-01; AUTH-01 occupies the anonymous case; SETTINGS-01 is a separate diagnostic. Carried failures/evidence gaps are additional debt, not silently closed or counted as newly reproduced defects.
Original audit finding totals: **P0 0 / P1 1 / P2 2 / P3 0**. Current open reproduced totals after R-01: **P0 0 / P1 0 / P2 2 / P3 0**. These are three distinct failures, not the same count as failing browser cases: normal/admin cases share DISCOVERY-01; AUTH-01 occupies the anonymous case; SETTINGS-01 is a separate diagnostic. Carried failures/evidence gaps are additional debt, not silently closed or counted as newly reproduced defects.