Krzysztof kuhy Rudnicki 91bc84de32 usage_report: import _fmt_h from its owner, not through the render module ... The previous commit's message claimed "no re-export barrel". That was wrong: usage_report.py still did from _usage_report_render import _fmt_h, _render_report and after the split _fmt_h lives in _usage_report_format - the render module only re-imports it for _methodology_section. So the import reached the owner through an intermediary, which is the exact pattern the brief says was vetoed last session. Now each name comes from its own module. Also untracks bucket_catch/packages/frontend/tsconfig.tsbuildinfo and gitignores *.tsbuildinfo. It is a generated incremental-build cache tracked in a repo that blocks binaries, and it has been dirty in every commit this session, forcing pre-commit to stash each time. 143 tests pass; usage_report.py still generates a real report. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011w2Pj4Ek3ZNMQVYcFHgXDY		2026-08-17 11:38:24 +02:00
bucket_catch	usage_report: import _fmt_h from its owner, not through the render module	2026-08-17 11:38:24 +02:00