[deep-report] Split 2 over-length functions in compiler_orchestrator_tools.go and compiler_safe_outputs_job.go #55691

Description

The Daily Compiler Code Quality Report (discussion #55585, 2026-08-25) flagged two functions over the review's line-count guidance during its rotation over the orchestrator/safe-outputs compiler files, both otherwise scoring "Good" (85/100 and 80/100):

• processToolsAndMarkdown in pkg/workflow/compiler_orchestrator_tools.go — 86 lines.
• buildSafeOutputsSetupAndDownloadSteps in pkg/workflow/compiler_safe_outputs_job.go — 91 lines. The report also notes this file is 793 lines total and suggests splitting it into two focused files.

Both are isolated, mechanical extractions (pull out sub-steps into named helpers) with no behavior change, and the report notes strong existing test coverage for this area (ratios 1.6-21.8x), so regression risk is low.

Expected Impact

Keeps two actively-changing compiler files under the project's function-length linter threshold (see LintMonster's 735-item largefunc backlog, discussion #55584) before they get flagged there too, and improves readability of the safe-outputs step-generation code.

Suggested Agent

General-purpose refactoring agent, or whichever agent handles LintMonster's largefunc backlog.

Estimated Effort

Quick (<1 hour) per function — mechanical helper extraction.

Data Source

DeepReport Intelligence analysis, 2026-08-25 06:25Z cycle, based on discussion #55585 (Daily Compiler Code Quality Report).

Generated by 🔬 Deep Report · claude · agent · 137.5 AIC · ⌖ 8.95 AIC · ⊞ 12.4K · ◷

• expires on Aug 26, 2026, 10:33 PM UTC-08:00