You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Follow up generated Harness boundary hardening from #562 #603
Follow-up items explicitly reviewed as nonblocking on PR #562. Keeping them together avoids expanding the already-reviewed generated Harness wiring while preserving each concrete observation.\n\n- [ ] Avoid duplicate instruction injection when brief is empty.\n- [ ] Fail closed or emit a strong diagnostic when capability.tools is present across catalogue skew.\n- [ ] Serialize proposed tool calls as JSON-like objects for generated participants.\n- [ ] Skip StepView payload construction when the generated verb is absent.\n- [ ] Document the fail-fast policy for a missing capability catalogue.\n- [ ] Clarify that checksImpl is a reserved, disabled validation gate until wired.\n- [ ] Normalize misshapen catalogue errors to the loader RuntimeError.\n- [ ] Make capability-catalogue setup failure visible beyond a warning or validate at startup.\n- [ ] Include generated functions in Charter boundary logs.\n- [ ] Feed generated functions the authored task rather than the Charter-prefixed task.\n- [ ] Make advise guidance single-use and keep it out of tool messages.\n\nSource review: #562.
Activity
feat(playbook): wire generated participant functions (#562)
feat(playbook): wire generated participant functions (#562)
fix(agent): name the file when a catalogue section is misshapen (#1298)
fix(subagent): read a brief-less charter's addendum once
fix(agent): preserve structured tool calls for generated participants (…
fix(agent): deliver generated advice once and never inside a tool res…