Two findings-presentation items from the cold-reviewer audits.
Paste-able guard.write(...) fix-diffs
Each real flow finding should generate a concrete, paste-able diff anchored to the finding's file:line and the sink call, instead of a generic snippet.
Partially addressed: #75 made flow fixes tailored — they now rewrite the actual sink call by node identity (e.g. store.put(ns, 'user_preferences', verdict.content)) rather than boilerplate. Remaining work: emit a true unified diff anchored at file:line, not just a corrected code block.
Stop labeling suggested_policies.yml as "derived" when flows == 0
The policy block is a fixed opinionated default (aegis_memory/inspect/policies.py). When no flows are found it should be labeled a default template, not "generated from findings", until it is actually derived from real flows.
Source: docs/issues/inspect-followups.md (Findings UX)
Two findings-presentation items from the cold-reviewer audits.
Paste-able
guard.write(...)fix-diffsEach real flow finding should generate a concrete, paste-able diff anchored to the finding's
file:lineand the sink call, instead of a generic snippet.Partially addressed: #75 made flow fixes tailored — they now rewrite the actual sink call by node identity (e.g.
store.put(ns, 'user_preferences', verdict.content)) rather than boilerplate. Remaining work: emit a true unified diff anchored atfile:line, not just a corrected code block.Stop labeling
suggested_policies.ymlas "derived" whenflows == 0The policy block is a fixed opinionated default (
aegis_memory/inspect/policies.py). When no flows are found it should be labeled a default template, not "generated from findings", until it is actually derived from real flows.Source:
docs/issues/inspect-followups.md(Findings UX)