Document RuntimeState concurrency model and mark task 5 complete
This commit is contained in:
@@ -98,6 +98,8 @@ Reference: `Docs/Refactoring.md` for full analysis of each issue.
|
||||
|
||||
**Why this is needed:** The safety of `RuntimeState` depends on an implicit assumption (single-worker, no `await` between read and write) that is not written down anywhere. If the deployment model changes or a developer modifies state-mutating functions, silent data races could appear with no warning. Explicit documentation prevents this.
|
||||
|
||||
**Status:** Completed.
|
||||
|
||||
---
|
||||
|
||||
### 6. `geo_service` Calls `db.commit()` Directly Instead of Deferring to Repository
|
||||
|
||||
Reference in New Issue
Block a user