[P1][Tier 3] Review-comment to harness loop (recurring comments become durable assets)

Tier 3 — Workflow adoption · Priority: P1

Gap

We have a generic "correct-once loop" in Tier 5 (#3291), but no explicit review-comment → harness workflow step: recurring PR review comments should be converted into durable harness assets (instructions, tests, analyzer rules, or skills) rather than only being fixed in the current PR. dotnet/sdk's epic (#55185) places this in Tier 3 as a distinct workflow step. This is also the manual practice already happening around the Change-Reviewer agent, and it dovetails with the automated-review pipeline (#3282, PR !764574, Automated-PR-Reviewer wrapper).

Investment

• Define a lightweight loop: when a review comment recurs (human or automated review), capture it as an instruction, test, analyzer rule, or skill update — closing the gap in the harness, not just the PR.
• Wire this into the automated-review pipeline so recurring Change-Reviewer findings feed back into skills/instructions.

Acceptance criteria

• A documented review-comment → harness loop (who captures, where it lands: instructions / tests / analyzers / skills).
• At least one recurring review finding converted into a durable harness asset as a worked example.
• Cross-linked with the correct-once loop (#3291) and the automated-review work (#3282).

Reference

• Adopted from dotnet/sdk epic #55185 (Tier 3 → "review-comment-to-harness loop").

Part of epic #3273

Start by reading the linked correct-once loop (#3291), automated-review work (#3282), and the Change-Reviewer workflow described in this issue. Define where recurring findings become instructions, tests, analyzers, or skills, then document the capture loop and add one worked example. Done means the loop is documented, one finding is converted into a durable harness asset, and the related issues are cross-linked.