Skip to content

Follow up generated Harness boundary hardening from #562 #603

Open

Description

@ypflll

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions