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

docs(roadmap): record legacy rollback guidance finding

Browse Source
This commit is contained in:
cesnimda
2026-11-11 07:32:28 +01:00
parent f7ca1f6948
commit 4e98b2d9e0
2 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/direct-roadmap/FINDINGS.md
+1
View File
@@ -5,6 +5,7 @@
| ID | Finding and evidence | Next action |
| --- | --- | --- |
| PERF-01-RULES | RESOLVED in A3 `e286be48`, published through `1d733675`. Seven red SQLite cases reproduced stale settings after save. Direct owner/global settings reads replace the 30-second controller cache. The 35-case final and integration runs include owner isolation, fallback and overlapping old/new responses. Native receipts retained. | Measure MariaDB/load tradeoff and inject a failed save in later qualification. Existing-setting reads add one indexed lookup, or two with global fallback. No latency gain claimed. |
| RR-14 | Current use of the July first-deploy runbook could inherit its historical no-op migration rollback rationale. Source review confirmed current Up methods add application Version and operation-event schema. Guidance clarified and published at release `3cca4418`. | Rehearse the exact old/new image pair after migration and representative writes with ownership/revision/document checks. Historical scope clarification is complete; runtime compatibility remains open. |
Earlier rows below retain historical dates. The current TODO and checkpoints supersede their old execution status, including the fixed backup parser and completed 188 dynamic-call reviews.