feat(isac): add oversight proposal corrections

docs/architecture.md

@@ -113,7 +113,7 @@ mutation rather than deletion or modification of the original event:
 ISAC data access is split into `data.view`, `data.propose`, `data.manage`, and
 `data.approve`. Data Viewers can inspect registries. Data Contributors can submit
 the same editor forms, but the request is serialized into `data_change_proposals`
-instead of mutating canonical tables. Data Approvers review the queue and must
+instead of mutating canonical tables. Data Oversight reviews the queue and must
 explicitly confirm approval or rejection.
 
 Approval replays the stored form through its original SvelteKit server action.
@@ -124,8 +124,8 @@ proposal as failed without changing live data. Pending counts appear alongside
 each data registry in ISAC so collaborators can see concurrent suggestions.
 
 The protected seeded roles are Data Viewer, Data Contributor, Data Editor, and
-Data Approver. Data Editor retains direct-write access for trusted operators;
-Data Approver combines direct-write access with queue review. New ISAC data
+Data Oversight. Data Editor retains direct-write access for trusted operators;
+Data Oversight combines direct-write access with queue review. New ISAC data
 modules must use the shared moderation interception path and audit both the final
 mutation and proposal lifecycle.