docs(roadmap): record application actions and rules freshness finding
This commit is contained in:
@@ -1,5 +1,13 @@
|
||||
# Continuing findings list
|
||||
|
||||
## 10 November current additions
|
||||
|
||||
| ID | Finding and evidence | Next action |
|
||||
| --- | --- | --- |
|
||||
| PERF-01-RULES | Independent source review confirmed `RulesController.Update` saves settings without cache invalidation. `JobApplicationsController.GetCachedRuleSettingsAsync` returns detached owner-keyed settings for up to 30 seconds. Lists, board, details, reminders, creation, AI refresh and readiness use that cache, while background workers read settings directly. This is source-confirmed, with no runtime reproducer yet. | Add a shared-cache regression changing follow-up threshold from 30 to one day for a 10-day-old application. Cover owner B, global fallback, failed save and an old in-flight factory after save. Use the narrow existing cache owner, and measure any added DB work. |
|
||||
|
||||
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.
|
||||
|
||||
2026-11-02. Observed defects, source limitations and planning work are separate. This list does not approve implementation, accept risk or close mandatory gates. Exact branch evidence is in WORK_COMPLETED.md.
|
||||
|
||||
| ID | Finding | Evidence / current state | Next action |
|
||||
|
||||
Reference in New Issue
Block a user