6 Commits

Include renames

Author	SHA1	Message	Date
steveandClaude Opus 4.8	9922166d7a	review(agent): address gadfly on progress-aware guard ... Merge the parallel callCounts/lastResults maps into one repeatState struct map (removes the "two maps in sync" smell + double lookup), drop the dead i<len(results) bounds branch that contradicted the documented index invariant, and note in-code that exact-string result equality is a deliberate err-toward- not-tripping choice (a hung job whose poll reports a ticking field is left to MaxRuntime / the job ceiling rather than risking a false kill of real progress). No behavior change; guard tests still green. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01HgEuVfZJN9mhRhzEsMEVog	2026-07-18 19:11:30 -04:00
steveandClaude Opus 4.8	68bf7157d3	fix(agent): make same-call repeat guard progress-aware ... The maxSameCallRepeats guard counted identical (name+arguments) tool calls across a run and tripped ErrToolLoop past the ceiling — regardless of whether each call made progress. This killed legitimate polling of long-running background jobs: code_exec_poll must be called with identical args (same job_id), so a render/encode that needs more than N polls was guillotined mid-flight even as each poll returned an advancing result (elapsed/status moving forward). Only count an identical call toward the trip when its RESULT is unchanged from the previous identical call. A call whose result keeps changing is progress and resets its count; a genuinely stuck call returning the same output still trips. This can never trip more than before, only less, and covers every idempotent poller with no per-tool configuration — matching the progress-over-usage thesis behind the stall-detection work. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01HgEuVfZJN9mhRhzEsMEVog	2026-07-18 18:56:56 -04:00
steveandClaude Opus 4.8	6abb399f5b	fix(agent): recover front-loaded answer past a citations-only terminal turn (#11) ... finalOutput now recovers the front-loaded answer when the terminal turn is a sources/citations-only addendum ("Sources: [x](url), ..."), not just when it is empty or a back-reference. It recovers the prior substantive answer and appends the (real) citations below it. Guards: citation-DOMINANCE (a prose answer that merely opens with "Source: ... http://..." is left as the answer), ^-anchored heading, citations recovery decoupled from the terminal-length ratio (concise answers recover too), preamble filter applied only in the borderline band (long answers opening with "Sure,"/"Let me" are not vetoed), and a dedup that ignores <url> angle-bracket wrappers. Healthy terminal answers unchanged; zero extra model calls. Fixes mort #1418. Gadfly-reviewed (6 reviewers) + adversarially pre-verified; all findings graded, real ones addressed. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>	2026-07-10 16:47:32 +00:00
steveandClaude Opus 4.8	1fd7109a42	fix(agent): recover front-loaded answer when terminal turn is degenerate ... The agent loop took the final answer only from the terminal (no-tool-call) turn. Models that "front-load" their answer into an earlier turn that also calls a tool — then close with a trivial pointer like "(Already answered above.)" — had their real answer discarded and the pointer delivered. This recurs across several open-weight models (glm-5.2, etc.); well-behaved models (Claude/GPT) defer their answer to the terminal turn and are unaffected. finalOutput() now falls back to the last substantive assistant content in the transcript when the terminal text is weak (empty, or a short back-reference). The predicate is narrow and back-reference-gated so short-but-correct answers ("42", "It's down, restarting now.") are never overridden; recovery only picks a prior turn that reads like a real answer, not a preamble. Zero extra model calls. Terminal-answer behavior for normal runs is unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>	2026-06-26 18:37:38 -04:00
steveandClaude Fable 5	0147a79d18	feat: conversion-driven extensions — resolvers, DefineTool, hooks, ops controls ... Phase 9a (ADR-0014): Registry.RegisterResolver for dynamic tiers; DefineTool[Args] typed tools; Usage cache/reasoning detail fields wired through anthropic/openai/google; WithPromptCaching (Anthropic cache_control); agent supervision hooks (WithMaxStepsFunc, WithSteer, WithCompactor, WithToolErrorLimits + ErrToolLoop); health Bench/Unbench/Snapshot; ChainConfig.Observer failover events. Co-Authored-By: Claude Fable 5 <[email protected]>	2026-06-10 13:30:06 +02:00
steveandClaude Fable 5	7dab4112ff	feat: agent run loop, Generate[T], reflect-derived schemas ... Phase 5: - agent/: model + system prompt + toolboxes composition; bounded tool-dispatch loop (default 10 steps); panic-proof tool execution; unknown-tool and duplicate-name handling; history continuation; step observers; partial results on ErrMaxSteps/errors (ADR-0012) - llm.SchemaFor[T]: strict-compatible JSON schemas from Go types (nullable pointers, description/enum tags, recursion rejected) - majordomo.Generate[T]: typed structured output with fence-stripping decode and model-naming errors - README agents/structured-output sections + matrix synced Co-Authored-By: Claude Fable 5 <[email protected]>	2026-06-10 13:10:18 +02:00