From 3a47dede4bc178018781bbac8af377d3806dc6ad Mon Sep 17 00:00:00 2001 From: Ed_ Date: Sun, 5 Jul 2026 15:18:01 -0400 Subject: [PATCH] =?UTF-8?q?refactor(conductor/edit=5Fworkflow.md):=20thin-?= =?UTF-8?q?pointer=20=C2=A79=20to=20conductor/code=5Fstyleguides/python.md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per agent_directives_consolidation_20260705 §3.3. The 9-line §9 'No Diagnostic Noise in Production Code' section is replaced with a 1-line pointer to the canonical home in conductor/code_styleguides/python.md §AI-Agent Specific Conventions. Net: 9 lines reduced to 1 line. Duplicate content removed; the canonical styleguide remains the source of truth. --- conductor/edit_workflow.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/conductor/edit_workflow.md b/conductor/edit_workflow.md index 24e5667a..896ab411 100644 --- a/conductor/edit_workflow.md +++ b/conductor/edit_workflow.md @@ -109,13 +109,7 @@ If you mismatch any of these, the file will fail to parse. Run `py_check_syntax` ### 9. No Diagnostic Noise in Production Code (Added 2026-06-09) -`sys.stderr.write(f"[XYZ_DIAG] ...")` lines added to `src/*.py` for debugging are technical debt the moment they ship. If you need to instrument for a one-time investigation: - -- Write the diag output to a log file: `tests/artifacts/.diag.log` -- Or to a standalone diagnostic script under `/tmp/diag_.py` that imports the production module and exercises it -- Or read the production source with `get_file_slice` and reason about it directly - -Do NOT add diag lines to `src/*.py` "temporarily." If you must add them for a single test run, they are part of the same atomic commit as the fix — they do not live uncommitted in the working tree. If you "revert everything," that means the diag lines are also reverted. +See `conductor/code_styleguides/python.md` §"AI-Agent Specific Conventions" (the canonical home for this rule). ## Step-by-Step Workflow for gui_2.py