download_media now shells out to gallery-dl (handles X.com auth/403/video->mp4) instead of urllib, returns the downloaded files, + media_files_for_post glob helper + --cookies CLI. render_markdown embeds images with  and videos with an HTML <video controls> tag (were plain links). extract_corpus uses the package download_media (one download path). Tests rewritten for the gallery-dl API. Corpus: 4 threads, 33 media (32 img embeds + 1 video), 0 missing.
fetch_thread_from_url now passes -o conversations=true (full threads, not single tweets), sorts posts chronologically, and sets root_post_id to the URL's target tweet. render_markdown builds front-matter from the target (root_post_id) post, not the earliest conversation tweet (fixes wrong @handle). Added dedupe_corpus.py: keeps deepest thread per conversation, deletes duplicates, keeps+marks unique branches (branch_of) + writes threads_index.json. 33 tests pass.
thread_from_dict (JSON wire boundary) round-trips thread_data.json; download_media/render_markdown gain argparse main() + __main__ so the plan Task 5.3 pipeline runs via -m; dual-import added so all modules run standalone or via -m (G5). Pipeline integration test (html->names->render) + CLI tests cover the glue without network. TDD: red -> green (4 pipeline + 29 regression = 33 passed).
Added standalone Result[T] (frozen+slots, ok/err classmethods, is_ok) to error_types.py per canonical AND-over-OR error_handling.md (not the video_analysis _Ok|_Err sum type). render_markdown renders YAML front-matter from root post, per-post ## sections with reply markers, quote blockquotes, and ./media/<name> links; media_names mapping keeps render decoupled from download_media. TDD: red (no Result) -> green (7 render + 9 types passed).
The original build_track_index spawned 5+ git subprocesses per track
folder (244 tracks * 5 calls = 1200+ subprocesses). That exceeded the
120s NFR1 budget. Replaced with a single 'git log --all --name-only'
pass + a mutable _TrackAccumulator; reduces git subprocess count from
1200+ to 1.
Also adds 3 smoke tests for build_subagent_task_index,
build_session_index, build_track_index (covering previously untested
pure-function indexers). 23 tests pass; coverage up from 39% to 61%.
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.
Adds a new MCP tool that exposes scripts/aggregate_directives.py as an
LLM-callable endpoint. The tool reads a presets markdown file, resolves
each directive's v1.md, and returns the concatenated clean directive
bodies. metadata (meta.md) is never read.
Tool contract:
name: aggregate_directives
params: preset_path (string, default current_baseline.md), max_chars (int, default 0)
result: text content (clean bodies) or 'ERROR: ...' string on failure
Dispatch runs the impl in asyncio.to_thread so the 66+ v1.md reads do not
block the MCP stdio loop. Errors from aggregate_directives are caught and
formatted as 'ERROR: aggregate_directives(<path>) failed: <type>: <msg>' so
the LLM can read the failure mode inline. Tool count: 45 (MCP_TOOL_SPECS)
+ 2 (run_powershell, aggregate_directives) = 47.
Added scripts/ to sys.path so 'from aggregate_directives import ...' works
inside the MCP server process; idempotent with existing project_root and src
path inserts.
Wraps the body-building core in a public aggregate_directives() function that
returns the rendered string and raises FileNotFoundError/ValueError on errors.
The existing aggregate() CLI wrapper catches those and preserves the prior
stdout/file output behavior. parse_preset now accepts an optional root param so
directive paths inside the preset resolve against a caller-supplied
project_root instead of always REPO_ROOT. No behavior change for the CLI; the
new function is the API surface used by the upcoming MCP server tool.
Aggregates v1.md bodies from a preset markdown into a single output stream.
NEVER reads meta.md (pollution fix). Stdlib-only; supports stdout and -o.
5 tests in tests/test_aggregate_directives.py cover: success path,
no-meta-md pollution, missing-file error, -o flag, no provenance leakage.
The previous write_registry wiped existing .md files first, then wrote
new ones. When multiple xdist workers ran the script concurrently, they
would clobber each other mid-write, causing intermittent test failures
(test_generate_type_registry.py would see missing or stale files).
Fix: generate to a sibling staging directory (PID+timestamp suffix)
first, then use os.replace() to atomically swap into place. No observer
can see the registry in a partial state.
The staging dir is built manually (not via tempfile) because
scripts/audit_no_temp_writes.py forbids tempfile imports in scripts/.
Verified: 6/6 tests in test_generate_type_registry.py PASS in isolation
and in tier-1-unit-core batch (was: 2 failed due to race); audit CLEAN.
These scripts were created during the search for the "Missing End()" imgui error
that the user reported on 2026-06-29. They are throwaway diagnostic tools;
their purpose was to find the orphan imgui.end_child() call in
render_tier_stream_panel (commit c2155593) and verify the fix worked.
No production code depends on these. They are kept for archival purposes
only so future debugging of similar imbalanced-begin/end issues has a
reference.
Scripts included:
- apply_fix.py : the actual applied fix to src/gui_2.py
- fix_orphan.py/fix_orphan2.py : iterative attempts at removing the orphan
- fix_indent.py : was used to attempt an indent fix; superseded
- remove_orphan.py : rejected because pattern didn't match
- find_imbalance.py : the canonical begin/end imbalance detector
- find_extras.py : finds orphan imgui.end() (window-level)
- find_ends.py : dumps all imgui.end() lines with context
- peek*.py (8 files) : various context-dump helpers used during
investigation
- check_dynamic.py : dynamic-control-flow imbalanced tracker
- check_indents.py : indent diagnostic for L7086
- diag_install_heuristic.py : earlier diagnostic for install heuristic
- inspect_imgui_apis.py : dumps imgui-bundle API surface
- search_indent*.py (3) : indent search helpers
- window_balance.py : dedicated imgui.begin/imgui.end balance check
- apply_fix.py/remove_orphan2.py : final iterations that succeeded
None of these are imported by src/ or tests/. The fix commit c2155593 is
the actual production change; these scripts are just the trail of breadcrumbs
left during the investigation.
Self-documents that subdirectories (existing week folders + category
folders like code_path_audit/ and license_cve_audit/) are skipped
non-recursively. Surfaces in both human-readable and --json output.
organize_reports.py moves loose files in docs/reports/ into week folders
named <YYYY>-<MM>-<DD> (Monday of the file's week). Old weeks only; current
week's files stay put. Non-recursive: subdirectories like code_path_audit/
and license_cve_audit/ are skipped. Dry-run by default; --apply to move.
MCP_BUGFIX.md had no date in the filename; renamed to MCP_BUGFIX_20260306.md
so the organizer's filename-date heuristic picks it up correctly.
Sequel to commit de9dd3c1. The de-cruft track's Phase 2.3 removed
the __getattr__ lazy-load entries from models.py. The migration
scripts covered the 11 dataclasses but missed the 5 config-IO
functions (load_config_from_disk, save_config_to_disk,
parse_history_entries, _clean_nones, load_mcp_config). The prior
commit de9dd3c1 fixed the first two; this commit fixes
parse_history_entries.
6 reference sites updated:
- src/app_controller.py line 7: added 'parse_history_entries'
to the existing 'from src.project import load_config_from_disk,
save_config_to_disk' line
- src/app_controller.py 5 call sites: models.parse_history_entries
-> parse_history_entries (lines 2020, 3264, 3311, 3781, 5055)
- src/gui_2.py: added 'from src.project import parse_history_entries'
(gui_2.py didn't import from src.project before)
- src/gui_2.py 1 call site: models.parse_history_entries ->
parse_history_entries (line 5492)
The fix was performed by the one-time script
scripts/tier2/artifacts/post_module_taxonomy_de_cruft_20260627/fix_parse_history_entries.py
which does an in-place re.sub on the 2 affected files. The script
is idempotent (re-running does the same work).
Verification:
- 'from src.app_controller import AppController' works
- 'from src.gui_2 import App' works
- 'uv run sloppy.py' should now pass the 'load_active_project'
phase of init_state
Discovered by user: running 'uv run sloppy.py' on the de-cruft
branch after the de9dd3c1 fix produced a SECOND AttributeError on
models.parse_history_entries, the next function in the de-cruft
track's missed-consumer-sites chain. The user is iterating through
sloppy.py failures as a test harness; each one reveals the next
missed consumer site.
Still pending (potential):
- models._clean_nones (3 sites in test_thinking_persistence.py)
- models.load_mcp_config (1 site in app_controller.py)
These are likely to surface in the next sloppy.py run. The fix
pattern is the same: add to the from src.X import line + replace
the models.X call sites with the bare name.
The 2 config-IO functions NOT in models.parse_history_entries's
class are _clean_nones (private) and load_mcp_config (which I
already updated to 'from src.mcp_client import load_mcp_config').
Wait, that's not right. Let me re-grep.
Per Tier 1 review of post_module_taxonomy_de_cruft_20260627 (the
commit 6b0668f1 + aa80bc13 work moved GenerateRequest +
ConfirmRequest to src.api_hooks.py and removed the lazy __getattr__
proxy for them in src/models.py). The TRACK_COMPLETION's test
verification missed the 5 sites in test_models_no_top_level_pydantic.py
+ 1 site in test_project_switch_persona_preset.py that still did
'from src.models import GenerateRequest/ConfirmRequest' after the
move.
This commit:
- tests/test_models_no_top_level_pydantic.py: 5 sites updated
(lines 49, 60, 74, 88, 99) from
'from src.models import GenerateRequest/ConfirmRequest'
to
'from src.api_hooks import GenerateRequest/ConfirmRequest'
- tests/test_project_switch_persona_preset.py: 1 site updated
(line 299) same change
After this commit:
- All 'from src.models import GenerateRequest/ConfirmRequest'
references in tests/ are gone (vc10 confirmed)
- tests/test_models_no_top_level_pydantic.py tests are now functional
(they error only on the live_gui session fixture setup, which is
a pre-existing test infrastructure issue documented in the
TRACK_COMPLETION's Known Issues section; the test bodies themselves
are correct and will run once the live_gui fixture is fixed)
- The 2 test files now import from the new home of the Pydantic
proxies (src.api_hooks)
A direct subprocess verification (bypassing the live_gui fixture)
confirms the imports work:
uv run python scripts/tier2/artifacts/post_module_taxonomy_de_cruft_20260627/verify_pydantic_test.py
# Output:
# pydantic in sys.modules: False
# src.models imported OK
# GenerateRequest: <class 'src.api_hooks.GenerateRequest'>
# ConfirmRequest: <class 'src.api_hooks.ConfirmRequest'>
Per post_module_taxonomy_de_cruft_20260627 Phase 0a (FR1). The audit
script's find_violations() function iterated over 'LEGACY_NAMES' but
only LEGACY_PRIVATE_NAMES + LEGACY_PUBLIC_NAMES were defined (the
single LEGACY_NAMES was split into two in module_taxonomy_refactor
Phase 3b but the function reference wasn't updated). This caused a
NameError that crashed the audit with --strict mode.
The spec claimed the bug was in scripts/generate_type_registry.py but
that was a misdiagnosis. generate_type_registry.py works correctly
(verified: 'Registry in sync (29 files checked)'). The actual bug was
in audit_no_models_config_io.py.
This commit:
- Updates line 95: 'for pattern, name in LEGACY_NAMES:' ->
'for pattern, name in LEGACY_PRIVATE_NAMES + LEGACY_PUBLIC_NAMES:'
- The function now iterates over both legacy name lists (private +
public), matching the actual variables defined in the file.
Verification: VC3 (audit_no_models_config_io passes --strict)
uv run python scripts/audit_no_models_config_io.py --strict
# Output: 'OK - no violations found.'
Per post_module_taxonomy_de_cruft_20260627 Phase 3 (FR6). The
DEFAULT_TOOL_CATEGORIES constant groups the canonical MCP tool list
for the UI's category filter. The AI client is the natural owner
(it owns the tool spec registry via src.mcp_tool_specs); models.py
is a data-class shim, not a UI-config registry.
This commit:
1. Adds DEFAULT_TOOL_CATEGORIES (the 7-category dict) to src/ai_client.py
after the PROVIDERS constant. The dict is identical to the one that
was in models.py.
2. Updates src/gui_2.py (the single consumer) to:
- Add 'from src.ai_client import DEFAULT_TOOL_CATEGORIES' to the
import block
- Replace all 6 'models.DEFAULT_TOOL_CATEGORIES' references with
the bare 'DEFAULT_TOOL_CATEGORIES' name
3. Removes the DEFAULT_TOOL_CATEGORIES dict from src/models.py
(it was already removed as a side effect of the Phase 2.3
__getattr__ removal commit; the file is now 70 lines).
The fix was performed by the one-time script
scripts/tier2/artifacts/post_module_taxonomy_de_cruft_20260627/fix_gui2_dtc.py
which does an in-place re.sub on src/gui_2.py.
Verification:
- 'from src.ai_client import DEFAULT_TOOL_CATEGORIES' works
- 'from src.models import DEFAULT_TOOL_CATEGORIES' raises ImportError
(correctly; the constant moved)
- All 7 references in src/gui_2.py resolve to the ai_client version
- 'from src.models import Metadata' still returns TrackMetadata
(the legacy alias is preserved)
Per post_module_taxonomy_de_cruft_20260627 Phase 2 (FR7 continued).
The previous migration commit (8f11340b) handled the
'from src.models import X' pattern (85 sites). This commit handles
the 'models.<moved_class>' attribute access pattern (44 sites in 20
files), which the __getattr__ shim previously supported.
The migration was performed by the one-time script
scripts/tier2/artifacts/post_module_taxonomy_de_cruft_20260627/migrate_models_attr.py
which:
1. For each 'models.<moved_class>' reference, replaces it with the
bare class name (e.g., 'models.MCPConfiguration' -> 'MCPConfiguration')
2. Adds the import 'from src.<destination> import <moved_class>' at
the top of the file (deduplicated if the import already exists)
3. Skips moved classes that the file already imports directly
The migration script inserts the import after the 'from __future__
import annotations' line if present; otherwise it adds the import
to the destination module's existing import block. Two files
required manual fixes because the script's regex didn't handle them:
- src/rag_engine.py: uses 'from src import models' (not 'from
src.models import X'); the class is accessed
via 'models.RAGConfig'. Replaced with a
direct 'from src.mcp_client import RAGConfig'
import and removed the 'from src import models'.
- tests/test_project_context_20260627.py: uses the parens-style
multi-line 'from src.models import (X, Y, Z)'.
Replaced with the parens-style direct import.
After this commit:
- 'models.MCPConfiguration', 'models.FileItem', 'models.Ticket', etc.
no longer work in src/ and tests/ (the AttributeError raises
because models.py no longer has the __getattr__ entries for
moved classes)
- All consumer files have direct imports of the moved classes
Total: 44 'models.<moved_class>' references rewritten across 20 files.
Per post_module_taxonomy_de_cruft_20260627 Phase 0 prerequisite.
Master is at 6344b49f (pre-merge of v2 SHIPPED). This merge brings in
the 18 v2 SHIPPED commits that define the destination modules
(src.mma, src/project.py, src/project_files.py, src.tool_presets,
src.tool_bias, src.external_editor, src.personas,
src.workspace_manager, src.mcp_client) needed by the Phase 2
consumer migration in commit 8f11340b.
Conflicts resolved (all were import-block re-orderings between my
migration's update and v2 SHIPPED's update of the same files):
- src/external_editor.py: took v2 SHIPPED version (class definitions
+ the no-alias import pattern)
- src/personas.py: took v2 SHIPPED version
- src/tool_bias.py: took v2 SHIPPED version
- src/tool_presets.py: took v2 SHIPPED version
- src/workspace_manager.py: took v2 SHIPPED version
- src/ai_client.py: took v2 SHIPPED version (removes the 'as _FIC'
alias; uses 'from src.project_files import
FileItem' directly per the v2 SHIPPED style)
- conductor/tracks/module_taxonomy_refactor_20260627/spec.md: took
HEAD version (my Phase 1 VC2 + VC10
corrections; the v2 SHIPPED version was
the pre-correction spec)
The migration commit (8f11340b) replaced 'from src.models import X'
with 'from src.<destination> import X' in EVERY file including the
destination files themselves. This created self-imports like
'from src.external_editor import ExternalEditorConfig' in
src/external_editor.py (which defines ExternalEditorConfig locally).
This fix removes the spurious self-imports from the 5 destination
files that were affected:
- src/external_editor.py (3 lines removed: 1 top-level + 2 in
function bodies that my migration
missed on the first pass)
- src/personas.py (1 line removed)
- src/tool_bias.py (1 line removed)
- src/tool_presets.py (1 line removed)
- src/workspace_manager.py (1 line removed)
The migration in non-destination files is correct and unchanged.
After this fix, the next merge of origin/tier2/module_taxonomy_refactor_20260627
(bringing in the v2 SHIPPED work) will not conflict on these files
because the self-imports are gone; the merge will apply v2's class
definitions cleanly.
The fix was performed by
scripts/tier2/artifacts/post_module_taxonomy_de_cruft_20260627/fix_self_imports.py
which removes 'from src.<module> import X' lines from files where
<module> matches the file's destination module name.
Per post_module_taxonomy_de_cruft_20260627 Phase 2 (FR7). Each
'from src.models import X' for a moved class is rewritten to
'from src.<destination> import X':
Ticket, Track, WorkerContext, TrackState, TrackMetadata,
ThinkingSegment, EMPTY_TRACK_STATE -> src.mma
ProjectContext, ProjectMeta, ProjectOutput, ProjectFiles,
ProjectScreenshots, ProjectDiscussion, EMPTY_PROJECT_CONTEXT -> src.project
FileItem, Preset, ContextPreset, ContextFileEntry,
NamedViewPreset -> src.project_files
Tool, ToolPreset -> src.tool_presets
BiasProfile -> src.tool_bias
TextEditorConfig, ExternalEditorConfig,
EMPTY_TEXT_EDITOR_CONFIG -> src.external_editor
Persona -> src.personas
WorkspaceProfile -> src.workspace_manager
MCPServerConfig, MCPConfiguration, VectorStoreConfig,
RAGConfig, load_mcp_config -> src.mcp_client
NOT touched (kept on src.models; Phase 3 or Phase 4 will move them):
GenerateRequest, ConfirmRequest, DEFAULT_TOOL_CATEGORIES, Metadata, PROVIDERS
Migration was performed by the one-time script
scripts/tier2/artifacts/post_module_taxonomy_de_cruft_20260627/migrate_imports.py
which uses a class-to-module map and re.sub() to rewrite each
'from src.models import X' line.
Total: 85 import lines rewritten across 71 files.
Note: this commit depends on the v2 SHIPPED work
(origin/tier2/module_taxonomy_refactor_20260627) being merged into
this branch NEXT. On master (without the v2 SHIPPED commits), the
destination modules do not exist and these imports would fail.
TIER-2 READ AGENTS.md, conductor/workflow.md, conductor/edit_workflow.md,
conductor/tier2/githooks/forbidden-files.txt,
conductor/tracks/tier2_leak_prevention_20260620/spec.md,
conductor/code_styleguides/data_oriented_design.md,
conductor/code_styleguides/error_handling.md,
conductor/code_styleguides/type_aliases.md,
conductor/product-guidelines.md, conductor/code_styleguides/python.md,
docs/guide_meta_boundary.md before post_module_taxonomy_de_cruft_20260627/Phase0b.
The audit_code_path_audit_coverage.py script expects an
--input-dir pointing to the most recent code_path_audit output.
The spec suggested creating a 'latest' symlink at
docs/reports/code_path_audit/latest -> 2026-06-24.
On Windows (Tier 2 sandbox), symlinks to the audit output directory
fail with PermissionError when Python's pathlib.Path.exists() calls
os.stat(follow_symlinks=True) on the target. Per the spec's R2 risk
mitigation: 'Use a .latest marker file instead of a symlink; update the
audit script to read the marker.'
This commit:
1. Creates docs/reports/code_path_audit/.latest containing '2026-06-24'
(the most recent audit output directory name).
2. Updates scripts/audit_code_path_audit_coverage.py to:
- Detect when --input-dir ends in 'latest'
- Read the sibling .latest file to resolve the actual directory name
- Fall through to the symlink behavior if the .latest marker is absent
(preserves Linux/macOS behavior)
Verification:
uv run python scripts/audit_code_path_audit_coverage.py \\
--input-dir docs/reports/code_path_audit/latest --strict
# Output: 'Meta-audit: 0 violations (10 real profiles checked)'
# Exit code: 0
Note on LEGACY_NAMES: the spec claimed generate_type_registry.py
referenced an undefined LEGACY_NAMES. Verified: generate_type_registry.py
at master 6344b49f (the spec's baseline) does NOT reference LEGACY_NAMES;
the audit passes ('Registry in sync (23 files checked)'). The
LEGACY_NAMES constant IS defined in scripts/audit_no_models_config_io.py
(verified via git grep). This bug does not exist; no fix needed for
Phase 0a. Documented here to avoid confusion in future audits.
Per the 4-criteria decision rule (C1=cross-system, C3=tests, C4=size);
ProjectContext is the typed return of project_manager.flat_config();
the 5 sub-dataclasses model the actual nested dict structure of
flat_config()'s return; load_config_from_disk / save_config_to_disk
are the canonical config I/O primitives (renamed from the private
_load_config_from_disk / _save_config_to_disk).
This commit:
1. Creates src/project.py with ProjectContext + 5 sub (ProjectMeta,
ProjectOutput, ProjectFiles, ProjectScreenshots, ProjectDiscussion)
+ EMPTY_PROJECT_CONTEXT + _clean_nones + load_config_from_disk +
save_config_to_disk + parse_history_entries.
2. Removes the original class + function definitions from src/models.py.
3. Adds backward-compat re-exports in src/models.py (the same pattern
used by Phase 3a mma.py and Phase 3g personas.py).
4. Updates src/app_controller.py to use the new public function names
(load_config_from_disk / save_config_to_disk).
5. Updates tests/test_models_no_top_level_tomli_w.py to use the new
public name (the test still asserts lazy-loading; the lazy load
happens in the new project.py module).
6. Updates scripts/audit_no_models_config_io.py FORBIDDEN_PATTERNS to
reference the new public names (models.load_config_from_disk /
models.save_config_to_disk) + the new src.project path.
Verification: VC6
uv run python -c 'from src.project import ProjectContext, ProjectMeta,
ProjectOutput, ProjectFiles, ProjectScreenshots, ProjectDiscussion,
_clean_nones, load_config_from_disk, save_config_to_disk,
parse_history_entries' # OK
uv run python -c 'from src.models import ProjectContext, ...' # OK
(re-exports work)
Pre-existing test regression (NOT caused by this commit):
tests/test_models_no_top_level_tomli_w.py::test_models_does_not_import_tomli_w_at_module_level
was already failing because the Phase 3g 'from src.personas import Persona'
re-export in src/models.py loads src.personas at module level, which
loads tomli_w. The Phase 5 reduce-models.py pass moves the persona
import into __getattr__ (lazy), which will make this test pass again.
Tests verified: tests/test_project_context_20260627.py (10/10 PASS),
tests/test_project_serialization.py (2/2 PASS), tests/test_thinking_persistence.py
(4/4 PASS), tests/test_presets.py (3/3 PASS), tests/test_persona_models.py
(2/2 PASS), tests/test_ticket_queue.py (PASS), tests/test_dag_engine.py
(PASS), tests/test_orchestration_logic.py (PASS).
Implements the 7th audit script referenced in python.md §17.8. Scans
src/*.py for local imports (§17.9a), _PREFIX aliasing (§17.9b), and
repeated .from_dict() in the same expression (§17.9c, info-only).
Three changes in this commit:
1. scripts/audit_imports.py: AST-based scanner; exits 1 in --strict on
LOCAL_IMPORT or PREFIX_ALIAS. Whitelist-aware via
scripts/audit_imports_whitelist.toml (load with --show-whitelist;
disable with --no-whitelist).
2. scripts/audit_imports_whitelist.toml: 21 files whitelisted with per-file
reason (vendor SDK warmup, hot-reload re-imports, circular-dep avoidance).
Suppresses 187 LOCAL_IMPORT sites; 0 strict violations remain.
3. conductor/code_styleguides/python.md: updated §17.8 (4th audit entry)
and §17.9a (3 documented exceptions + whitelist mechanism).
Tests: tests/test_audit_imports.py (7 tests, all passing).
ed