docs: fix 4 stale refs (4-thread->8, dispatch line 1341->1322, 7->11 locks)
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:
+1
-1
@@ -38,7 +38,7 @@ This documentation suite provides comprehensive technical reference for the Manu
|
||||
| [MMA Engine](guide_multi_agent_conductor.md) | `src/multi_agent_conductor.py` + `src/dag_engine.py` reference: TrackDAG with cycle detection (iterative DFS) and topological sort (Kahn's variant), ExecutionEngine with Auto-Queue / Step Mode state machine, MultiAgentConductor with WorkerPool (configurable concurrency, default 4), mma_exec.py sub-agent invocation for Token Firewall, parse_plan_md utility, Beads mode delegation |
|
||||
| [Data Models](guide_models.md) | `src/models.py` reference: centralized data model registry using pydantic + dataclasses, model categories (Core, AI, Preset, Persona, Context, MMA, UI State, Logging, Hook, Workspace, RAG), `AGENT_TOOL_NAMES` canonical 45-tool list, `PROVIDERS` constant, `parse_plan_md` utility, validation patterns, SDM tags, serialization strategies (TOML, JSON-L) |
|
||||
| [Discussions](guide_discussions.md) | The Discussion system: 23-operation matrix A1-A7 (per-entry) + B1-B11 (discussion-level) + C1-C5 (undo/redo), Take naming convention (`<base>_take_<n>`), branching at any entry (`project_manager.branch_discussion`), promotion to top-level (`project_manager.promote_take`), user-managed role list (`app.disc_roles`), per-role filter linked to MMA persona focus, `_disc_entries_lock` thread-safety contract, Hook API session endpoints |
|
||||
| [State Lifecycle](guide_state_lifecycle.md) | Undo/redo via `HistoryManager` + `UISnapshot` (13 captured fields, 100-snapshot capacity, debounced change detection at render frame), reset flow (`_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, 4-thread access pattern with 7 lock-protected regions, hot-reload integration |
|
||||
| [State Lifecycle](guide_state_lifecycle.md) | Undo/redo via `HistoryManager` + `UISnapshot` (13 captured fields, 100-snapshot capacity, debounced change detection at render frame), reset flow (`_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, 8-thread io_pool with 11 lock-protected regions (per `IO_POOL_MAX_WORKERS = 8` in `src/io_pool.py:20`; bumped 4→8 in 4a338486 on 2026-06-06), hot-reload integration |
|
||||
| [Context Aggregation](guide_context_aggregation.md) | The `aggregate.py` (518-line) pipeline: 3 aggregation strategies (`auto`/`summarize`/`full`), 7 per-file view modes (`full`/`summary`/`skeleton`/`outline`/`masked`/`custom`/`none`), full `FileItem` schema (9 fields + `__post_init__` normalizer), `ContextPreset` schema and `ContextPresetManager`, Tier 3 worker variant (`build_tier3_context` with FuzzyAnchor re-resolution and focus-file handling), `force_full`/`auto_aggregate` short-circuits, output file numbering, cache strategy (static prefix + dynamic history) |
|
||||
|
||||
---
|
||||
|
||||
+1
-1
@@ -54,7 +54,7 @@ The error message includes the full list of allowed base directories for debuggi
|
||||
|
||||
## Native Tool Inventory
|
||||
|
||||
The `dispatch` function (`mcp_client.py:1341`) is a flat if/elif chain mapping 45 tool names to implementations. All tools are categorized below with their parameters and behavior. The count grew from the original 26 as Python structural tools (Phase 6) and C/C++ AST tools (Phase 6.5) were added; Beads tools (4) were added for the Beads mode integration.
|
||||
The `dispatch` function (`mcp_client.py:1322`) is a flat if/elif chain mapping 45 tool names to implementations. All tools are categorized below with their parameters and behavior. The count grew from the original 26 as Python structural tools (Phase 6) and C/C++ AST tools (Phase 6.5) were added; Beads tools (4) were added for the Beads mode integration.
|
||||
|
||||
### File I/O Tools
|
||||
|
||||
|
||||
@@ -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`
|
||||
|
||||
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user