ed/manual_slop
Private
Public Access
0
0
Fork 0
Code Activity

docs: fix 4 stale refs (4-thread->8, dispatch line 1341->1322, 7->11 locks)

Browse Source 
Caught these when re-verifying the 4 commits from docs_sync_test_era_20260610.
Not in my track originally (per the prior 'no track boundary' correction),
but they're stale data and easy to fix in one commit:

- docs/Readme.md:41: '4-thread ... 7 lock-protected regions' -> '8-thread
  io_pool ... 11 lock-protected regions' (bumped 4->8 in 4a338486
  on 2026-06-06; 11 locks counted in __init__ at app_controller.py:778-1212)

- docs/reports/session_synthesis_20260608.md:121: same fix, plus a
  note that this report predates the bump

- docs/reports/workflow_markdown_audit_20260608.md:40: same fix
  (the audit report was correct AT TIME OF WRITE but is now stale)

- docs/guide_tools.md:57: 'mcp_client.py:1341' -> 'mcp_client.py:1322'
  (the dispatch function's actual line)

Left unchanged:
- docs/reports/COMPACTION_DIGEST_20260607.md:45 mentions '4 workers are
  stuck' in a specific historical context (2026-06-07 hang investigation
  pre-bump). That '4' was true at the time and is part of the historical
  record; flagging in commit message not text.
This commit is contained in:
Edward R. Gonzalez
2026-06-10 21:25:56 -04:00
parent c730ff8298
commit ea4d3781a6
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reports/session_synthesis_20260608.md
+1 -1
View File
@@ -118,7 +118,7 @@ The user-driven insights from these corrections:
- Debounced change-detection at render frame (`gui_2.py:1140-1170`)
- `_handle_reset_session` (clears 30+ fields, replaces project, preserves `active_project_path` per the 2026-06-08 regression fix)
- `App.__getattr__`/`__setattr__` state delegation to Controller (`gui_2.py:666-675`)
- 4-thread access pattern with 7 lock-protected regions
- 8-thread io_pool with 11 lock-protected regions (bumped 4→8 in 4a338486 on 2026-06-06; this report predates the bump)
- State persistence: in-memory vs project TOML vs config TOML
- Hot-reload integration
- 14 file:line refs into `gui_2.py:735-789`, `history.py`, `app_controller.py:3286-3356`
docs/reports/workflow_markdown_audit_20260608.md
+1 -1
View File
@@ -37,7 +37,7 @@
**Why.** This session produced 3 new deep-dive guides (commits `ba051684`):
- `docs/guide_discussions.md` (353 lines, 23-op matrix A1-A7 + B1-B11 + C1-C5)
- `docs/guide_state_lifecycle.md` (375 lines, UISnapshot + HistoryManager + 4-thread access pattern)
- `docs/guide_state_lifecycle.md` (375 lines, UISnapshot + HistoryManager + 8-thread io_pool access pattern [was 4-thread pre-2026-06-06 bump in 4a338486])
- `docs/guide_context_aggregation.md` (394 lines, aggregate.py + 7 view modes + 3 strategies + FileItem + ContextPreset)
**None of these are in the current architecture-fallback list in `conductor/workflow.md` §"Architecture Documentation Fallback" or in any of the SKILL.md files.** The next Tier 1 orchestrator who loads `mma-tier1-orchestrator` SKILL.md will not see these 3 guides as required reading. The next Tier 2 tech lead who loads `mma-tier2-tech-lead` SKILL.md won't see them either.