[integration][auto-dig] actor failure in run 33094075463 #277
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/prolog-rlm#277
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Auto-Dig integration failure diagnostics
lost-rob0t/starintel-gpt-auto-digaacbe53f9385a2c93c4192e0373cb5524077be687f0050f524db6de5293163241176ac4660f04349Sanitized failure diagnostics
Summary:
phase=planner kind=plan_parse_failed message=planner responses did not contain a valid typed plan model_calls=3 prompt_tokens=8121 completion_tokens=4307 total_tokens=12428 cost_usd=0.00595436Structured Prolog-RLM error
Sanitized traceback / stderr tail (last 160 lines)
Planner-context repair is implemented and pushed on
rage/277-planner-protocol-contextat4d2ab5c.The slice adds exact typed
contextandtoolenvelopes to the mandatory root-planner protocol and makes parse/structural retries receive one bounded latest-error diagnostic. Candidate/provider output is not echoed; capability and budget denials remain non-repairable.Verification on the exact tree:
git diff --check: passKeep #277 open until review/merge and credentialed downstream acceptance. The separate task-framing plus retrieved-evidence composition gap will be tracked independently.
Closing as superseded/completed by merged PR #286, which explicitly consolidated the #277 planner repair and moved the affected workload onto the unified task-first native/direct-or-plan runtime. Historical run-specific duplicates of this old planner failure are being closed in the same audit; any current regression should be represented by a fresh current-head issue.