You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Repository Quality Improvement Report (2026-08-24) flagged pkg/workflow/awf_config.go at 1,090 lines (verified via wc -l) as mixing three separable concerns across its 19 top-level functions: schema validation (validateAWFConfigJSON), config construction (BuildAWFConfigJSON), and policy/domain resolution (resolveModelPolicyForAWFConfig, intersectModelPolicyRules). This is the repo's 2nd-largest non-test Go file and, like the handler registry (see companion issue), was actively edited on the same day it was flagged — decomposition debt accumulating in high-churn code.
Split along the three natural seams (schema validation / config building / policy resolution) into separate files, consistent with the "one file per functionality" pattern used elsewhere in pkg/workflow.
Expected Impact
Improves reviewability and reduces merge-conflict surface for a file under active development; makes the three concerns independently testable/navigable.
Suggested Agent
New Agent / general coding agent — mechanical extraction along the documented function groupings, verify via existing config tests after the split.
Activity
github-actions commentedon Aug 24, 2026
🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪