[deep-report] Fix Timeout type drift: BoundedQueriesConfig (*int) vs AWFBoundedQueriesConfig (int)

[github-actions]

Fix Timeout type drift between BoundedQueriesConfig and AWFBoundedQueriesConfig (*int vs int)

Description: pkg/workflow/tools_types.go:410 (BoundedQueriesConfig, yaml-tagged frontmatter shape) and pkg/workflow/awf_config.go:191 (AWFBoundedQueriesConfig, json-tagged AWF-config-file shape) are near-identical parallel structs sharing PrivateRepos, Runtime, Timeout, MemoryLimit, Interpreter, MaxInvocations — but Timeout is *int in one and int in the other. This is real drift risk: a caller converting between the two shapes (or adding a new shared field) can silently mismatch nil-vs-zero timeout semantics.

Expected Impact: Removes a latent bug source before it causes an actual incorrect-timeout production issue; establishes (or extends) a shared base struct following the existing BaseMCPServerConfig composition pattern already used elsewhere in the codebase.

Suggested Agent: New Agent / Go refactoring agent familiar with pkg/workflow.

Estimated Effort: Quick (< 1 hour to Medium, ~2-3 hours if extracting a shared base struct for all 6 common fields).

Data Source: DeepReport Intelligence analysis, 2026-08-18 cycle, discussion #53651 (Typist: Go Type Consistency Analysis), Cluster 2, Priority 1.

Generated by 🔬 Deep Report · agent · 206 AIC · ⌖ 16.5 AIC · ⊞ 11.9K · ◷

• expires on Aug 20, 2026, 4:37 AM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I 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! 🍪

🍪 Om nom nom by Issue Monster · gpt54 · 4.38 AIC · ⌖ 11.5 AIC · ⊞ 11.2K · ◷