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

conductor: register exception_handling_audit_20260616 in tracks.md

Browse Source
This commit is contained in:
ed
2026-06-16 09:09:34 -04:00
parent 3c59e24162
commit 4b8363bd71
1 changed files with 31 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
conductor/tracks.md
+31 -1
View File
@@ -22,7 +22,8 @@ Tracks that are unblocked and ready to start. Ordered by **dependency** (blocked
| 5 | A | [MCP Architecture Refactor (Sub-MCP Extraction)](#track-mcp-architecture-refactor-sub-mcp-extraction) | spec ✓, plan pending | test_infrastructure_hardening_20260609 (merged), data_oriented_error_handling, data_structure_strengthening |
| 6 | D | [Public API Result Migration](#track-public-api-result-migration-followup) | placeholder; not yet specced | data_oriented_error_handling (deprecated `send()`) |
| 6a | A | [Public API Migration + UI Polish Test Cleanup](#track-public-api-migration--ui-polish-test-cleanup) | spec ✓, plan ✓, shipped 2026-06-15 (13 pre-existing failures fixed; 3 RAG failures deferred to `rag_test_failures_20260615`) | (none — independent; **NEW 2026-06-15**; combined stability track) |
| 6b | A | [RAG Test Failures Fix](#track-rag-test-failures-fix-new-2026-06-15) | spec ✓, plan ✓, ready to start | (none — independent; **NEW 2026-06-15**; small bug-fix track; 3 RAG tests fail with same NoneType.get error; first fully green baseline since 2026-06-12) |
| 6b | A | [RAG Test Failures Fix](#track-rag-test-failures-fix-new-2026-06-15) | spec ✓, plan ✓, shipped 2026-06-15 (3 RAG tests fixed; first fully green baseline 1288 + 4 + 0) | (none — independent; **NEW 2026-06-15**; small bug-fix track) |
| 6c | B | [Exception Handling Audit (Convention Compliance + Doc Clarification)](#track-exception-handling-audit-convention-compliance--doc-clarification) | spec ✓, plan ✓, shipped 2026-06-16 (211 violations identified across 42 files; 5 doc gaps closed) | (none — independent; **NEW 2026-06-16**; audit + doc track; identifies the migration target for `data_structure_strengthening_20260606` and the user's `send_result` → `send` rename) |
| 7 | — | [UI Polish (Five Issues)](#track-ui-polish-five-issues) | spec ✓, plan ✓, ready to start (Phases 1/4/5 shipped; Phases 2/3 code shipped but tests broken — fixed by track 6a) | (none — independent) |
| 7a | B | [SQLite-Granularity Inline Docs for gui_2.py](#track-sqlite-granularity-inline-docs-for-gui_2py) | spec ✓, plan ✓, complete | (none — independent) |
| 7b | B | [Continued SQLite-Granularity Inline Docs for gui_2.py](#track-continued-sqlite-granularity-inline-docs-for-gui_2py) | spec ✓, plan ✓, complete | (none — independent) |
@@ -667,6 +668,35 @@ Lightweight chronology; full spec/plan/state per track is in the linked folder.
*Out of scope (deferred to separate tracks): the `send_result` → `send` mass rename (user's stated manual refactor), 23 lower-impact weak-type files (`data_structure_strengthening_20260606`), `live_gui_mock_injection_20260615` infrastructure (separate track), RAG test quality cleanup (poll loops, etc.; separate track).*
#### Track: Exception Handling Audit (Convention Compliance + Doc Clarification) `[track-created: 2026-06-16]`
*Link: [./tracks/exception_handling_audit_20260616/](./tracks/exception_handling_audit_20260616/), Spec: [./tracks/exception_handling_audit_20260616/spec.md](./tracks/exception_handling_audit_20260616/spec.md), Plan: [./tracks/exception_handling_audit_20260616/plan.md](./tracks/exception_handling_audit_20260616/plan.md), Metadata: [./tracks/exception_handling_audit_20260616/metadata.json](./tracks/exception_handling_audit_20260616/metadata.json), Report: [../../docs/reports/EXCEPTION_HANDLING_AUDIT_20260616.md](../../docs/reports/EXCEPTION_HANDLING_AUDIT_20260616.md)*
*Status: 2026-06-16 — Active, completed (5/5 phases, ~12 tasks). An AUDIT + DOC track (no production code change). The deliverable is the audit script + the report + 3 doc/codestyle updates that close 5 gaps in the convention's documentation.*
*Goal: produce a static analyzer that classifies every `try/except/finally/raise` site in the codebase against the data-oriented error handling convention established by `data_oriented_error_handling_20260606` (shipped 2026-06-12). The audit's value is in the report + the doc clarification, not in a refactor.*
*Deliverables:*
- *`scripts/audit_exception_handling.py` — 792-line AST-based static analyzer; 10-category classification taxonomy (5 compliant + 3 violation + 1 suspicious + 1 unclear); `--json`, `--top`, `--verbose`, `--strict`, `--include-tests` modes; "delete to turn off" per `feature_flags.md`*
- *`conductor/code_styleguides/error_handling.md` — 5 new sections (Boundary Types, The Broad-Except Distinction, Constructors Can Raise, Re-Raise Patterns, Audit Script) closing 5 gaps the audit revealed*
- *`docs/guide_app_controller.md` — new "Exception Handling" section explaining the 13 FastAPI boundary sites + the 40 migration-target sites*
- *`conductor/product-guidelines.md` — cross-reference to the audit script*
- *`docs/reports/EXCEPTION_HANDLING_AUDIT_20260616.md` — 9-section report (370 lines) for the user to decide the next track*
*Headline numbers: 348 total sites across 65 files. 80 compliant (23%) + 25 suspicious (7%) + 211 violation (61%) + 32 unclear (9%). The 3 refactored baseline files (mcp_client, ai_client, rag_engine) have 112 sites / 77 violations (the convention reference; remaining violations are mostly broad-catches without ErrorInfo conversion). The 62 migration-target files have 236 sites / 134 violations (the work for future refactor tracks).*
*5 gaps the audit revealed + closed:*
- *G1: FastAPI `HTTPException` in `_api_*` handlers not explicitly documented as a legitimate boundary (closed in styleguide + app_controller doc)*
- *G2: The "broad except Exception" rule doesn't distinguish between "swallow" and "convert to ErrorInfo" (closed in styleguide)*
- *G3: The "constructors can raise" rule is brief; needs elaboration (closed in styleguide)*
- *G4: The "re-raise" pattern is not in the styleguide at all (closed in styleguide)*
- *G5: The new audit script is not referenced from the styleguide (closed in styleguide + product-guidelines.md)*
*Critical audit findings (2026-06-16): The convention is applied to 3 of 65 src/ files (mcp_client.py, ai_client.py, rag_engine.py — the "baseline"). The remaining ~10 files in src/ are in the "migration-target" state. The top 3 candidates by violation count: `src/gui_2.py` (37 violations, 260KB), `src/app_controller.py` (35 violations + 13 FastAPI boundary = 48 sites, 166KB), `src/session_logger.py` (8 violations, 16KB). The user decides which is the next refactor track.*
*`blocks: app_controller_result_migration_20260616` (recommended next track; 22 migration-target sites in app_controller.py after excluding the 13 FastAPI boundary sites; 2-3 days Tier 2), `gui_2_result_migration` (37 violations; 2-3 days Tier 2), `session_logger_result_migration` (8 violations; 0.5 day Tier 2). Also unblocks the user's stated `send_result` → `send` mass rename and the planned `data_structure_strengthening_20260606` track.*
*Out of scope (deferred to separate tracks): the `send_result` → `send` mass rename (user's stated manual refactor), 23 lower-impact weak-type files (`data_structure_strengthening_20260606`), `live_gui_mock_injection_20260615` infrastructure (separate track), RAG test quality cleanup (poll loops; separate track), and — most importantly — **any production code refactor** (this track is informational; the user decides what to migrate).*
---
## Phase 9: Chore Tracks