Updated the Code Path Audit entry in the tracks.md registry to accurately
describe the MVP state after the code_path_audit_polish_20260622 follow-up:
REMOVED:
- '4 renderers (to_dsl_v2 flat-section, to_markdown 10-section, to_tree
box-drawing, parse_dsl_v2 round-trip)' -> '2 renderers (to_markdown
10-section, to_tree box-drawing)'
- '14-tagged-word v2 postfix DSL' claim (the DSL parser was deprecated)
ADDED:
- 'MVP output is a single AUDIT_REPORT.md (6797 lines, 311KB) + per-aggregate
markdowns + summary.md as a TOC pointer'
- '127 tests passing after the polish follow-up (was 131 pre-polish; -4 DSL
tests removed)' (was previously 131)
- Note about DSL deprecation referencing code_path_audit_polish_20260622
No other track entries were modified.
Per the 3-step archiving convention:
1. Move the folders (done in 964d7edd)
2. Update tracks.md (this commit)
The 22 video_analysis tracks are now registered in the Archived section at the bottom of tracks.md. The Active Tracks table (rows 1-30) remains unchanged for the ongoing tracks (qwen_llama_grok, data_oriented_error_handling, mcp_architecture_refactor, etc.).
The 3-pass video analysis research campaign is officially CLOSED as of 2026-06-23. The campaign closeout report is at docs/reports/CAMPAIGN_CLOSE_OUT_video_analysis_20260621.md.
- tracks.md: new row 29 for the de-obfuscation campaign (priority A, research, awaits user samples)
- Pass 1 spec §11.1: superseded 2026-06-21; now points to the dedicated Pass 2 umbrella spec for the full handoff contract. The 'user must rediscover math encoding' action item is replaced by 'user provides 3-10 samples of past de-obfuscation notes; warmup derives the lexicon'
Updates:
- conductor/tracks.md: entry #27 marked SHIPPED 2026-06-21; BLOCKER
removed for code_path_audit_20260607 (broadcast() TypeError fixed)
- state.toml: status=completed, current_phase=6, all 4 phases marked
completed with checkpoint SHAs, all verification booleans true
NOT shipped (per user instruction):
- The git mv to conductor/tracks/archive/ is the USER's responsibility
- Track directory stays at conductor/tracks/phase2_4_5_call_site_completion_20260621/
- tier2/any_type_componentization_20260621 branch NOT merged (reconnaissance framing)
The follow-up track now includes Phase 6e: Tier 2 produces the authoritative
Phase 3 cost analysis as part of the follow-up work. Tier 2 is in
src/ai_client.py doing Phase 6b/6d anyway; they have full context to produce
the refined cost hypothesis that Tier 1's draft at PHASE3_HYPOTHETICAL_PROMOTION.md
could not (Tier 1 worked without the 6b/6d ground-truth context).
Tier 1's draft STAYS as the hypothesis doc. Tier 2's PHASE3_TIER2_ANALYSIS.md
is the refined version (per-sender cost summary + hidden call sites table
+ recommendations for the future Phase 3 track + cross-reference to Tier 1
explicit).
Phase 6e tasks (5 total, ~2 commits):
- t6e_1: Profile the 6 senders (codepath catalog + hidden cross-refs)
- t6e_2: Qualitative cost estimation per sender
- t6e_3: Identify hot iteration sites needing 'with h.lock:' pattern
- t6e_4: Author PHASE3_TIER2_ANALYSIS.md
- t6e_5: Phase 6e checkpoint commit + git note
Total estimated commits: 16 -> 18 (still within Tier 2 1-4 hour budget).
Files updated:
- conductor/tracks/phase2_4_5_call_site_completion_20260621/spec.md (+50 lines)
- conductor/tracks/phase2_4_5_call_site_completion_20260621/plan.md (+146 lines)
- conductor/tracks/phase2_4_5_call_site_completion_20260621/metadata.json (+13 lines)
- conductor/tracks/phase2_4_5_call_site_completion_20260621/state.toml (+9 lines)
- conductor/tracks.md (track 27 entry expanded with Phase 6e details)
Phase 9 final checkpoint per Tier 1's spec.md §12:
- tracks.md row 6d-6 updated with Phase 9 patch status
- campaign is now LEGITIMATELY closed at 100% (not the false claim
from Phase 8 commit d7242953)
- the 3 wrappers Tier 1 said were remaining are verified gone via
4 new Phase 9 invariant tests (commit 84af01a7)
- the 7 failing tests are verified passing (31/31 baseline tests)
- the campaign status report is updated (commit 2939bea9)
- the corrected TRACK_COMPLETION doc is in place (commit 06c3b9f4)
Final state:
- 0 legacy wrappers in src/ (scripts/audit_legacy_wrappers.py)
- 31/31 baseline tests pass (pytest tests/test_baseline_result.py)
- 127/127 unit tests pass across 5 test files
- 9/11 batched tiers PASS (2 pre-existing flaky)
- Campaign 100% complete (5 sub-tracks + 1 close-out track)
Phase 0 task 0.1: register the new track in the Active Tracks table.
The campaign-close-out track is added as row 6d-6 (after sub-track 5 which
shipped 2026-06-20). The dependency links to sub-track 5 (which is the
data-plane source: 91 _result helpers, but the legacy wrappers that
defeat error propagation are still in place).
Per user directive 2026-06-20: OBLITERATE every legacy wrapper; no
pass-throughs; no backward compat.
Adds the end-of-track artifacts for the tier2_leak_prevention_20260620
fix track:
- docs/reports/TRACK_COMPLETION_tier2_leak_prevention_20260620.md:
Full track completion report following the precedent set by
TRACK_COMPLETION_tier2_autonomous_sandbox_20260616.md. Documents
the 4 atomic commits, the 25 default-on tests, the manual
end-to-end verification, the key design decisions (auto-unstage
not exit 1, git rm --cached --force, CRLF handling, specific not
prefix patterns), the known limitations, and the next steps for
the user (push to origin, rebase stale tier-2 branches, re-run
setup on the existing clone, optional CI wiring).
- conductor/tracks/tier2_leak_prevention_20260620/metadata.json:
Track metadata (status=shipped, scope: 5 new files + 1 modified,
25 default-on tests, 5 verification criteria, 5 risk-register
entries, 2 deferred follow-up tracks).
- conductor/tracks/tier2_leak_prevention_20260620/spec.md:
Track spec (background on the 00e5a3f2 offender commit, design
with the 3-layer defense-in-depth, forbidden patterns, tests,
out-of-scope items).
- conductor/tracks/tier2_leak_prevention_20260620/plan.md:
Track plan (4 phases: revert + hook + audit + install; tasks
recorded retroactively per workflow.md "Plan is the source of
truth").
- conductor/tracks/tier2_leak_prevention_20260620/state.toml:
Track state (status=completed, current_phase=complete, 4 phases
with checkpoint SHAs, 16 tasks all completed with commit SHAs).
- conductor/tracks.md: registered as track 6f in the Active
Tracks table; added a "Recently Completed" entry with the
commit-history summary.
Per conductor/workflow.md "End-of-track report" protocol. The
report includes a "Mistake to flag" section about the
`Remove-Item -Recurse -Force` accident during verification, per
the AGENTS.md "Hard ban on destructive commands" rule (which is
specifically about `git restore`/`git checkout`/`git reset`/`git
push` but the lesson generalizes: destructive PowerShell commands
on directories with tracked files require explicit verification
before running).
TIER-2 READ conductor/code_styleguides/error_handling.md end-to-end before Phase 13.
Final state:
- All 13 phases completed (checksha recorded)
- All verification flags = true (audit_strict_exits_0,
site_inventory_has_42_rows, drain_plane_render_functions_exist,
silent_swallow_count_zero, rethrow_count_zero, unclear_count_zero,
broad_catch_count_zero)
- batched_suite_11_of_11_pass = false (Tier 3 has 1 known issue:
test_gui2_performance.py measures FPS 28.46 vs 30 threshold; documented
in TRACK_COMPLETION report as a known issue for user review)
- tracks.md updated: sub-track 4 row -> 'shipped 2026-06-20'
Track shipped on the success path. All 42 migration-target sites in
src/gui_2.py resolved.
TIER-2 READ conductor/code_styleguides/error_handling.md end-to-end before Phase 0.
Updates the sub-track 4 row from 'ready to start' to 'active 2026-06-19'.
Anti-sliming protocol (13 phases, per-site audit, per-phase invariant test)
is in effect for the migration of 42 sites in src/gui_2.py.
Sub-track 4 of the 5-sub-track result_migration_20260616 umbrella.
Migrates src/gui_2.py (the largest source file at 260KB / 7282 lines;
the immediate-mode ImGui rendering layer) to the data-oriented
Result[T] convention.
Scope: 42 migration-target sites (38 V + 2 S + 2 UNCLEAR) + 6 infra
sites for the drain plane. Per the user's directive (2026-06-19),
the phase structure is EXTRA LONG (13 phases instead of the umbrella's
1-2) to give Tier 2 well-defined narrow scope per phase. No phase has
more than 10 migration sites. This is the anti-sliming protocol:
previous sub-tracks slimed when scope felt tight (sub-track 2 Phase 10
slimed 21/26 sites via 5 laundering heuristics; sub-track 3 Phase 3
slimed 8 sites via logging.debug bodies). The 13-phase structure with
per-phase audit gates prevents sliming.
The 13 phases:
0. Setup + styleguide re-read (Tier 2 reads error_handling.md)
1. Site inventory + classification (42 sites in PHASE1_SITE_INVENTORY.md)
2. Drain plane wiring (3 new render functions: render_controller_error_modal,
_render_worker_error_indicator, _render_last_request_errors_modal)
3. INTERNAL_BROAD_CATCH Batch A (render-loop, <=10 sites)
4. INTERNAL_BROAD_CATCH Batch B (modal/dialog, <=10 sites)
5. INTERNAL_BROAD_CATCH Batch C (event handlers, <=10 sites)
6. Signal handler sites (<=5 sites; Pattern 3 drain: sys.exit)
7. Worker/background sites (<=5 sites; thread-safety via app._worker_errors_lock)
8. Property setter/state sites (<=5 sites)
9. Helper/utility sites (<=5 sites)
10. INTERNAL_SILENT_SWALLOW (<=13 sites; CRITICAL anti-sliming phase;
per user principle 'logging is NOT a drain')
11. INTERNAL_RETHROW classification (<=2 sites; Pattern 1/2/3)
12. UNCLEAR classification (<=2 sites)
13. Audit gate + end-of-track report (--strict exits 0; 11/11 tiers PASS)
Anti-sliming protocol per phase:
- Styleguide re-read at start of each phase (commit msg acknowledgment)
- Per-site audit pre/post check (capture before + after in commit body)
- Per-phase invariant test (test_phase_N_invariant_count_dropped)
- Per-file atomic commits (1 site = 1 commit)
- 'If a site resists migration: DO NOT invent a heuristic. Report.'
The data plane (8 controller state attributes added by sub-track 3
Phase 6: _last_request_errors, _worker_errors + lock,
_startup_timeline_errors, _signal_handler_error, _inject_preview_error,
_mcp_config_parse_error, _save_project_error, _model_fetch_errors) is
the source of truth. Sub-track 4 adds the drain plane (3 new render
functions in Phase 2) and migrates the 42 sites to feed their errors
into the data plane.
Files:
- spec.md (323 lines, 11 sections)
- plan.md (938 lines, 13 phases, 60+ atomic commits, anti-sliming protocol)
- metadata.json (14 VCs, 8 risks, scope)
- state.toml (14 phases, 102 tasks, 22 verification entries)
- tracks.md (new row 6d-4 in Active Tracks table)
Total: 5 files, 1327 lines added (excluding tracks.md).
Next: Tier 2 picks up Phase 0 (setup + styleguide re-read).
Adds track 16 (priority A) to Active Tracks table:
- 5-part fix for test data loss outside ./tests/
- 9-phase TDD plan with 30 tasks
- Root cause: src/paths.py:get_config_path() silent fallback via SLOP_CONFIG env var
- Per user directive: NO ENV VARS, --config CLI flag, config_overrides.toml naming
- Baseline: 1288 + 4 + 0 (no regression allowed per VC8)
Co-Authored-By: Claude <noreply@anthropic.com>
Added a new Track section for live_gui_test_fixes_20260618 documenting:
- The 2 fixes (Issue 1: GUI subprocess crash; Issue 2: xdist race)
- The 8 commits in this track (1 setup + 2 TDD red + 2 TDD green + 2 audit + 1 docs)
- The 11/11 tier pass result
- The blocks relationship: unblocks sub-track 2 of result_migration_20260616
- Out of scope: the 4 Gemini 503 skip markers (deferred to follow-up track)
Added the new track entry to conductor/tracks.md following the
tier2_autonomous_sandbox_20260616 and send_result_to_send_20260616
precedents. Includes the link, spec, plan, metadata, status, scope,
goal, deliverables, and test inventory.
Refs: conductor/tracks/tier2_no_appdata_20260618
Phase 13 is the ACTUAL completion of sub-track 2. Phase 12 was rejected
for the false test claim; Phase 13 fixed the script crash, investigated
the 3 failures on parent commit, and verified 11/11 tiers actually run.
Updated:
- state.toml: status=completed, current_phase=complete, phase_13.checkpointsha=0e3dc484
- metadata.json: phase_13_outcome block added
- tracks.md: 6d-2 row updated to reflect Phase 13 completion + 2 reported issues
Final state:
- 9/11 tiers PASS clean
- 2/11 tiers PASS with documented issues (reported for diff tracks)
- 4 tests documented with @pytest.mark.skip (Gemini 503 pre-existing)
- Test count is 11. NOT 10. NOT 9.
2 issues reported for diff tracks:
1. test_execution_sim_live: GUI subprocess crashes mid-test on port 8999.
Same failure with gemini_cli and gemini providers. NOT Phase 12 regression.
2. test_live_gui_workspace_exists: xdist race condition (passes in isolation).
Sub-track 2 is READY FOR MERGE.
Phase 11 (REJECT Phase 10's sliming). The full Result[T] migration for
the 21 slimed sites has been completed:
- 5 full Result migrations in warmup.py (on_complete, _record_success,
_record_failure, _log_canary, _log_summary now return Result[T])
- 2 helper extracts: startup_profiler._log_phase_output and
file_cache._get_mtime_safe (Result-returning helpers)
- 14 sites documented as already compliant (Result/BOUNDARY_CONVERSION/
Heuristic #19 - not sliming, valid existing pattern)
- 1 known limitation: warmup._warmup_one L185 (indirect Result return
via delegation; convention followed; audit has known limitation)
5 LAUNDERING HEURISTICS (#22-#26) REVERTED in commit 37872544.
Heuristic A (Result-returning recovery) ADDED in commit 3c839c91.
Test count corrected: Phase 10 wrongly claimed '10 tiers'; the 11th tier
is tier-1-unit-comms. Phase 11 ran ALL 11 tiers and 10 PASS; tier-3
fails on the pre-existing test_execution_sim_live flake (unrelated).
Updated:
- conductor/tracks/result_migration_small_files_20260617/state.toml
- conductor/tracks/result_migration_small_files_20260617/metadata.json
- conductor/tracks.md (sub-track 6d-2 row)
- conductor/tracks/result_migration_20260616/spec.md (umbrella)
- docs/reports/RESULT_MIGRATION_SMALL_FILES_20260617.md (Phase 11 addendum)
- docs/reports/TRACK_COMPLETION_result_migration_small_files_20260617.md
(Phase 11 addendum with corrected test count)
Phase 11 is the actual completion. Phase 10 was rejected for sliming.
Sub-track 1 of the 5-sub-track result_migration_20260616 campaign.
Audit-driven research task: classify 43 ambiguous exception-handling sites
(24 UNCLEAR + 19 INTERNAL_RETHROW across 11 files) and update the
audit script's heuristics. No production code change.
Scope: 11 files, 43 sites, T-shirt S. The per-site decisions feed
sub-tracks 2-4 (small_files, app_controller, gui_2) as their starting
migration scope.
Files: spec.md, plan.md, metadata.json, state.toml under
conductor/tracks/result_migration_review_pass_20260617/. Row added
to conductor/tracks.md.
Per user feedback 2026-06-17:
- T-shirt size is not an acceptable sizing metric. Remove it from
conductor/workflow.md (the policy file), conductor/tracks.md (the
registry), and docs/reports/NEGATIVE_FLOWS_INVESTIGATION_20260617.md.
- Regenerate manualslop_layout.ini to remove 83 stale window references
that pointed to deleted/renamed windows (Projects, Files, Screenshots,
Provider, System Prompts, Discussion History, Comms History, etc.).
Layout now matches the windows registered in src/app_controller.py
_default_windows (lines 1862-1886). Stale window count: 10 -> 3.
T-shirt size removal details:
- conductor/workflow.md: Removed the S/M/L/XL table, the replacement
pattern row, and the 'reasonable effort' guard's reference. Scope
(N files, M sites, N tasks) is the only effort dimension.
- conductor/tracks.md: Removed the T-shirt column from the table header
and removed T-shirt size mentions from the Fable track entry.
- docs/reports/NEGATIVE_FLOWS_INVESTIGATION_20260617.md: Removed the
T-shirt size mention in the follow-up track suggestion.
Layout fix:
- manualslop_layout.ini went from 17,360 bytes (102 windows, 83 stale)
to 3,361 bytes (23 windows, all matching _default_windows). The
stale window warning dropped from 10 windows to 3 (Message, Tool
Calls, Response - these are in _default_windows but reference
separate panels in the layout).
Verification: layout fix did NOT fix the underlying stack overflow crash.
After layout fix, the test still dies with rc=3221225725 (0xC00000FD).
The user noted 'Something more fundamental is wrong.' Investigation
continues; this commit only addresses the explicit ask (remove T-shirt,
fix layout).
New research track for critical analysis of Anthropic's Claude Fable 5 system prompt. Added as row 25 in the Active Tracks table (Priority B research) and as a section in the new 'Active Research Tracks (2026-06+)' grouping. The companion spec + metadata + state.toml are committed in 058e2c93 and a6114ef9.
ed