sumo_qa_capture_review_feedback

Manage an EXPLICIT, user-confirmed review-feedback memory of recurring QA findings.

Promotes a recurring review lesson (e.g. "we always miss timezone boundaries in billing") into a local, inspectable, reversible memory that future planning/review skills consult as an ADVISORY hint — NOT automatic learning. action selects the operation:

• 'capture' — add a new lesson (or replace one with the same id). Requires entry with scope, trigger_signal, recommended_probe, source_note, and optional last_reviewed (ISO-8601; defaults to now).

• 'update' — replace the fields of an existing lesson; needs entry_id plus entry.

• 'delete' — remove a lesson by entry_id.

• 'list' (default) — return stored lessons, advisory-flagged. The scope default is the literal 'project', so it lists the current repo; pass scope='global' for the cross-repo set. An unrecognised scope returns an error envelope (it is never coerced to project).

NEVER persist without explicit user confirmation, and NEVER auto-capture from a review/prompt/trace. That confirmation gate is the HOST/skill's responsibility, not enforced by a tool parameter — the deliberate writer-local data-ownership model shared with the risk-ledger and AC tools; the sumo-qa-feedback CLI correspondingly exposes only list/delete, so a capture can never be a fire-and-forget flag. Sensitive input — a raw diff hunk, a secret, a code snippet, or a pasted full issue/PR body — is REJECTED; only the user's own summary is stored, and a rejected entry is never echoed to the debug-capture sink either. Storage reuses the #92 user-writable pack location (project = /.sumo-qa, global = the user data dir) under a feedback/ subdir, so it is NOT a second hidden tree. Memory-derived probes are ADVISORY: cite them SEPARATELY from bundled ISTQB/rules content; they never override canonical classifications or change-rules.

Common natural-language phrasings that map to this tool: "remember that we always miss X in Y", "save this review lesson", "promote this recurring finding to team memory", "what review lessons have we saved?", "forget the timezone-billing lesson".