Commit graph

3 commits

Author SHA1 Message Date
Ouroboros
520a6f2e32 fix(tools): a filled optional argument that asks for nothing is not a refusal
Models fill every key of a tool schema. Five handlers refused the empty or
mode-irrelevant form of an optional argument with a text that restated the
rule, the retry kept the same key set, and several of those refusals were
recorded as successful calls, so neither the task nor its reflection could
locate the fault.

- escalate: a wait bound on a quiz that does not wait, or 0 on one that does,
  takes the omitted path and the receipt says so; a bound past the task ceiling
  is lowered to it; the ignored bound is never persisted with the quiz.
- knowledge_read: an end past the note is lowered to it, 0..0 reads the whole
  note, one bound alone is allowed; the returned range is the range delivered.
- delegate_wait: the empty pair (0, "") asks for no checkpoint and the wake
  says so; a half-filled pair is refused naming the missing half.
- schedule_followup: a zone beside an absolute run_at is ignored, disclosed
  and not stored.
- get_task_result source ranges: an invalid range still returns no text, now
  with the complete length and the range received, published as an argument
  error instead of ok.

The remaining refusals at these sites are published typed and name the value
received (tools/arg_feedback). The typed-refusal source lint now counts
interpolated marker returns per file, growth-only.
2026-09-19 10:42:28 +03:00
Ouroboros
bff9f321a4 fix(results): retain review and completion sources through shared handles 2026-09-06 18:15:05 +00:00
Ouroboros
7577b5ff2c fix(tasks): expose canonical completion sources to native readers 2026-09-06 11:59:55 +00:00