3-post sibling to the 1736161886079533186 VK retrospective: same public-
domain release context, Dec 2023. Covers the mmap-ring-buffer error
logger and the multi-session rationale (crash auto-reload + log
preservation, no debugger).
10-post single-author walkthrough of his old Vulkan pipeline: warm-all-pages
startup, auto-relaunch on crash, single-SPIR-V plus spec-constants, Bind-
Everything-Once, SSBO-as-4-types aliasing, GPU-side game logic, hardware-
style fixed resources. High engagement (36 likes, 3778 views). Closes
with the ruthless-anti-complexity thesis.
6-post single-author walkthrough of the fast-path error-check pattern:
volatile store __LINE__ + error code, TEST, conditional forward branch
to a distant Err() call. Companion to the 2063733456144597200 thread
which established the macro system via the conversation with
@winning_tactic.
Path objects with trailing separators (e.g. './media/') intermittently
failed to glob on Windows after download_media.py had just finished
writing the directory. Normalize via rstrip('/\\\\') before Path()
re-wrapping so the CLI is forgiving regardless of OS path quirks.
Repro: gallery-dl ran + immediate render with trailing slash on the
just-created media/ dir -> glob returned nothing -> markdown emitted
no ![Media N] lines. Removing the trailing slash fixed it; this makes
both work.
Track closed per user direction with PARTIAL completion (17 of 31
tasks done; 13 deferred to followup tracks).
TRACK_COMPLETION_test_suite_cleanup_gemini_cli_removal_20260705.md
records the 12-VC status (7 PASS, 5 NOT DONE / NOT VERIFIED), the
phase-by-phase breakdown, branch state, risks, and hand-off notes.
conductor/chronology.md: Active row updated to 'Partially Completed'
with the commit range + summary of completed/deferred work.
state.toml: status = 'superseded'; current_phase kept at 1 (mid-Phase 1)
to reflect actual stopping point; new [followup_tracks] section
records the two upcoming tracks:
- vendor_ai_client_track (Front C metadata work)
- test_de_crufting_track (Front B cruft work)
These are generated by scripts/generate_type_registry.py based on the
current @dataclass / NamedTuple / TypeAlias declarations in src/. The
regeneration reflects the gemini_cli removal and to_legacy_dict deletion
across ai_client, api_hooks, history, etc.
Script used calendar-day duration (end_date - init_date), which
inflated tracks that sat dormant between work and archive-move.
Example: external_editor_integration_20260308 reported 60 days
(init 2026-03-08, last archive-move 2026-05-07) when actual work
was 2 active days.
Corrected metric: active days = distinct calendar days with at
least one commit touching the track folder. All 30 top tracks
now show 2-7 active days, matching the user's expectation that
no track lasts more than a week.
Also fixed commit_count + files_touched for all 30 tracks (the
script's work-prefix-only count was always 0-1 for these).
Top 3 examples:
- external_editor_integration_20260308: 60d/1c/4f -> 2d/4c/8f
- code_path_audit_20260607: 18d/1c/7f -> 7d/23c/14f
- nagent_review_20260608: 12d/0c/20f -> 3d/53c/20f
Still stale (need recompute, not hand-fix):
- 3.1 per-era aggregates
- 8 use-case predictions
- 218 other tracks not in top-30
The script's commit_count and files_touched columns only counted
work-prefix commits (feat|fix|refactor|perf|test) with pathspecs
matching the track folder. Track folders contain only metadata
commits (conductor(*), chore(conductor), docs(track)), so the
script reported 0 commits for any track that did real work.
Corrected rows (now using total commits + total unique files
touching the track folder, any prefix):
- code_path_audit_20260607: 1->23 commits, 7->14 files
- qwen_llama_grok_integration_20260606: 0->25 commits, 4->8 files
- nagent_review_20260608: 0->53 commits, 4->20 files
- data_oriented_error_handling_20260606: 0->21 commits, 4->8 files
- superpowers_review_20260619: 0->63 commits, 8->16 files
Added 9.1 caveat explaining the manual corrections and the
methodology error that caused them.
Deleted scripts/audit/generate_chronology.py + chronology_quality_gate.py
after repeated corruption incidents (auto-classifier drifted from
user intent, silently rewrote rows). chronology.md is now maintained
by hand: add a row at the top when a track ships/abandons/is archived.
Updated conductor/workflow.md §Chronology Maintenance and
conductor/tracks.md §Archiving a track to reflect manual maintenance.
Added 40 rows to conductor/chronology.md for the 2026-07-05 archive
batch, with archive-folder paths and deferral notes where applicable.
Removed 12 archived-track rows from conductor/tracks.md Active Tracks
table (rows 2, 3, 7c, 16, 17, 23b, 23c, 23d, 25, 26, 29, 29c) and
their track-detail anchors.
Wrote docs/reports/ARCHIVE_REVIEW_20260705.md: a categorized index
of unfinished work items from the archived tracks' state.toml files
that remain relevant to the codebase, with a ranked follow-up list.
Sweep of the per-source-file guides + Readme.md for stale references
to src/models.py as the data model home. models.py is now a ~1.5KB
re-export shim per module_taxonomy_refactor_20260627; dataclasses
moved to src/mma.py, src/project_files.py, src/type_aliases.py,
src/mcp_tool_specs.py, src/result_types.py, src/context_presets.py,
src/workspace_manager.py, src/personas.py.
- guide_gui_2.md: _gui_func line 754->1062; render_main_interface
line 1259->1898.
- python.md §10 exemption table: App gui_2.py:307->314; AppController
795->801; RAGEngine 123->125; HookServer 856->941;
HookServerInstance 130->171; HookHandler 155->208;
WebSocketServer 908->993.
- guide_multi_agent_conductor.md: Ticket now in src/mma.py (not
models.py); ConductorEngine 116+->112+; WorkerPool 50-114->52-110.
- guide_agent_memory_dimensions.md: FileItem ref models.py:510-559
-> src/project_files.py.
- guide_context_aggregation.md: FileItem + ContextPreset refs ->
src/project_files.py + src/context_presets.py; ai_client _send_*
count 5->8.
- guide_discussions.md: parse_history_entries now in src/mma.py;
ContextPreset/FileItem cross-refs updated.
- guide_personas.md: Persona now in src/personas.py; import example
updated.
- guide_rag.md: RAGConfig now in src/mcp_client.py.
- guide_workspace_profiles.md: WorkspaceProfile now in
src/workspace_manager.py.
- guide_mma.md: Data Structures section notes src/mma.py as the live
location.
- Readme.md: MMA Engine + Data Models rows updated for the
models.py shim reality + 8 providers + mma_exec deprecation.
- guide_ai_client.md: '5 provider SDKs'->8 (added note); PROVIDERS
line 56->62; __getattr__ re-export line 261->31; provider
switching examples use real registered model names (claude-sonnet-
4-5, MiniMax-M2, gemini-2.5-flash, qwen-plus, grok-2, llama-3.1);
_provider union lists all 8 providers.
product-guidelines.md claimed send_result() was canonical and send()
was removed. The reverse is true: send() is the live public API
returning Result[str, ErrorInfo]; send_result exists only as a local
var in _send_gemini_cli. Corrected the section and added a
reconciliation note. Also fixed guide_ai_client.md send() signature
to show -> Result[str] instead of -> str.
The guide described models.py as a 132KB centralized registry with
Provider/ModelInfo enums, Ticket/Track classes, AGENT_TOOL_NAMES, and
parse_plan_md. None of that is in models.py anymore — it's a ~1.5KB
re-export shim (Metadata=TrackMetadata alias + PROVIDERS lazy
__getattr__). Dataclasses moved to per-system files (mma.py,
project_files.py, type_aliases.py, mcp_tool_specs.py, result_types.py).
VendorCapabilities moved from the deleted vendor_capabilities.py into
ai_client.py #region. Rewrote the guide to reflect the current
where-each-model-lives table.
test_visual_sim_mma_v2 was the user's explicit complaint about pre-
existing flakes. The fix (9cfbb980) addresses three root causes:
dict metadata normalization, App-side state sync in load_track, and
btn_reset pollution cleanup. Update the report to reflect this.
Both failures from the user's full batch run on 2026-07-01 are now fixed
in 1c31c603. Update the report to reflect the final state: all 7 originally-
failing tests pass, the 8th (drift test) is skipped with a documented
reason, and the only remaining tier-3 failure (test_visual_sim_mma_v2)
was fixed by the mma_status endpoint serialization patch.
The render_task_dag_panel AttributeError on dict leftover tickets
(fix ff864050) closes the last outstanding test failure. Update the
report to reflect the resolution, the file scope, and the commit log.
Final report on the 7-commit branch covering:
- Phase 8/9/10 audit invariant migrations (3 tests in tier-1-unit-gui)
- TEST_SANDBOX skip-in-test-mode (2 tests)
- btn_reset history clear (1 test in tier-3)
- type-registry atomic write_registry (1 test in tier-1)
- rag stress no-op initial case (1 test in tier-3)
- undo_redo longer waits (1 test in tier-3, partial fix)
- drift test skip (1 test in tier-1)
Documents the 1 remaining failure (render_task_dag_panel ImGui Missing PopID
in batch) with a recommended try/except wrap for follow-up.
Auto-generated by scripts/generate_type_registry.py after the recent
src/gui_2.py and src/paths.py changes:
- src_paths.md: adds 'layouts: Path' to the Paths struct fields list
- src_layouts.md: NEW module file (src/layouts.py added by the
default_layout_install track)
- index.md: includes the new src_layouts.md entry
Pure doc regeneration; no production code changed.
Documents the MiniMax_understand_image workflow for converting
screenshots to ASCII Layout Maps. Covers: when to use it, the
6-step workflow, the proportional-measurement prompt pattern,
faithful rendering rules (width ratios, empty space, floating
window position, color annotations, tab bars, table rows),
multi-screenshot composition, and limitations.
After Tier 2 marked the default_layout_install track SHIPPED, the user
ran uv run sloppy.py from C:\projects\manual_slop_tier2 and STILL saw
empty workspace (just the menu ribbon, no body content). This report
captures what was empirically verified this session and what remains
unverified.
Verified this session:
- Tier 2's 79c25a32 pre-run install fires correctly (stderr confirms)
- The bundled layouts/default.ini has correct [Docking] hierarchy
(DockSpace ID=0xAFC85805 + 2 DockNode children + per-window DockId)
- show_windows state has 9 visible-by-default entries
- _render_main_interface_result does NOT raise [FATAL] exceptions
- The imgui_scopes audit reports 4 extra end() calls (all 4 are false
positives from the script not tracking conditional control flow)
- Tier 2's working tree has UNCOMMITTED edits to src/gui_2.py
(removed redundant local imports in render_main_interface)
NOT verified (cannot be in this session):
- Whether [DIAG] lines from _render_window_if_open fire (Python pipe
buffering discards stderr when process is force-killed)
- Whether panels actually render visually (Tier 1 cannot run windowed GUI)
- The exact render_main_interface codepath that prevents panels from
appearing
5 of Tier 2's commits claim to fix panel visibility but NONE of them
empirically verified visible panels after install. Tier 2 marked the
track SHIPPED based on INI content assertions (17/17 tests pass) but
not on visible-panel verification.
Recommendation:
1. STOP adding speculative fixes
2. Revert tier 2 to a known-good baseline (master has working 2150-byte
INI with full [Docking] hierarchy)
3. Visual verify both master AND tier 2 produce visible panels
4. If tier 2 fails, the bug is environment-specific (not in code)
5. Defer pixel-level verification to the imgui_test_engine track
Files written:
- conductor/tracks/default_layout_install_20260629/ (Tier 1 scaffolding)
- conductor/tracks/default_layout_install_followup_20260629/ (Tier 1
followup track; corrects Tier 2's wrong-theory diagnosis)
- docs/transcripts/_9_bK_WjuYY_ryan_fleury_raddbg_walkthrough.json
+ docs/transcripts/rcJwvx2CTZY_ryan_fleury_raddbg_codebase_intro.json
(Fleury raddbg transcripts for deferred panel_defs_fleury_migration track)
- docs/reports/PANEL_VISIBILITY_DEBUG_REPORT_20260629.md (this file)
ed