Changelog

Changed

• Suggested Agents now return a typed result for each stage, like the Islo tenant’s own Lines, and define evidence and redaction rules. Ship and plan Lines bound review/fix retries and separate product failures from unavailable checks. Verification checks the PR revision running in the Machine app.
• Suggested QA stores cross-run findings in a Factory Knowledge item. Each full report stays on its Line run; no external report delivery is added. A memory problem is reported on a Memory: line and does not change the QA result.
• Suggested build checks read the repository’s own CI results for the exact pull request head. They run PR scripts locally only inside an isolated offline executor without gateway credentials, and only for checks CI did not cover. Without one, those checks return untested.
• Suggested reviewers and verifiers now post their findings and verification report on pull requests themselves, signed Islo Reviewer or Islo Verifier like the implementer’s Islo Implementer.
• Suggested Lines route on those typed results, with a head_moved value for a moved pull request head. Bug triage now has its own Suggested Agent, bug-confirmer, with reproduced, not_reproduced and blocked results. It replaces the verifier in the Triage a bug Line, so a new suggestion appears in Agent suggestions.

Deployment note

Existing deployments keep their saved prompts and continue running unchanged. After a catalog prompt update, redeploying an existing suggestion returns agent_name_conflict until you rename or delete the existing Agent. A changed saved Line manifest can separately return line_name_conflict. Catalog updates do not upgrade existing deployments in place. The Triage a bug Line now uses the new bug-confirmer Agent in place of verifier. Redeploying it also needs the existing Line renamed or deleted, and a verifier Agent that no other Line uses stays behind and can be deleted.