Publish safe inline findings #17

New issue

Open

opened 2026-07-14 22:32:22 -04:00 by caleb-brown · 0 comments

caleb-brown commented

2026-07-14 22:32:22 -04:00

Owner

What to build

Developers receive a bounded set of actionable inline findings on valid changed lines, while unsafe, excessive, or non-inlineable feedback remains safely represented in the managed summary.

Acceptance criteria

Only findings grounded to an acquired changed line or supported range can become inline comments.
Confidence, severity, actionability, per-review caps, and deduplication rules determine which findings are inline.
Non-inlineable and overflow findings remain visible in the managed summary with their coverage context.
Rendered model output suppresses unsafe HTML, credential-bearing links or images, and unintended user or team mentions.
Retry or reconciliation cannot duplicate an existing inline finding for the same result.
Contract tests cover additions, deletions, renames, ranges, unmappable positions, hostile Markdown, caps, and duplicates.

Blocked by

#16 — Publish advisory status and a managed summary

## What to build Developers receive a bounded set of actionable inline findings on valid changed lines, while unsafe, excessive, or non-inlineable feedback remains safely represented in the managed summary. ## Acceptance criteria - [ ] Only findings grounded to an acquired changed line or supported range can become inline comments. - [ ] Confidence, severity, actionability, per-review caps, and deduplication rules determine which findings are inline. - [ ] Non-inlineable and overflow findings remain visible in the managed summary with their coverage context. - [ ] Rendered model output suppresses unsafe HTML, credential-bearing links or images, and unintended user or team mentions. - [ ] Retry or reconciliation cannot duplicate an existing inline finding for the same result. - [ ] Contract tests cover additions, deletions, renames, ranges, unmappable positions, hostile Markdown, caps, and duplicates. ## Blocked by - [#16](https://git.caleb-brown.dev/caleb-brown/temper/issues/16) — Publish advisory status and a managed summary

caleb-brown added the

ready-for-agent

label

2026-07-14 22:32:22 -04:00

caleb-brown referenced this issue

2026-07-14 22:32:23 -04:00

Keep feedback correct across retries and revisions #18

caleb-brown referenced this issue

2026-07-14 22:32:30 -04:00

Establish Forgejo compatibility and review-quality gates #26

caleb-brown added a new dependency

2026-07-14 22:38:21 -04:00