Create a new feedback item in the Loopback bus.

Use this to file any observation about a running product: a UI defect, a backend error, a usage insight, or a UX papercut. Every item is tagged to a project so the right agent picks it up later.

Args: project (slug), type (ui|backend|usage|ux), title, and optionally body, severity (p0-p3, default p2), source, reporter, route, url, dom_selector, screenshot_path, replay_url, console[], network[], repro_steps[].

Returns the created item as JSON, including its generated id (fb_...). New items start with status 'open'.

Example: file "Pay button dead on iOS Safari" with project='shop-web', type='ui', severity='p1', route='/checkout'.

List feedback items, filtered and paginated. This is the entry point for "work the queue".

Args (all optional): project, status (open|triaged|in_progress|fixed|verified|wontfix), type (ui|backend|usage|ux), severity (p0-p3), source, assignee_agent, limit (default 20), offset (default 0), response_format (markdown|json).

Returns items ordered most-severe first, then newest. Pagination metadata: total, count, offset, has_more, next_offset.

Typical agent flow: loopback_list_feedback(project='X', status='open') → loopback_claim_feedback → fix → loopback_link_change → loopback_update_status(status='fixed').

Fetch one feedback item with full context: description, repro steps, console lines, network entries, screenshot/replay links, linked change (commit/PR), and the complete comment trail.

Args: id (fb_...), response_format (markdown|json).

Read this before starting a fix — it contains everything captured at report time.

Atomically claim a feedback item for an agent before working on it. Prevents two agents from fixing the same thing.

Args: id, agent (your name, e.g. 'claude-code', 'codex', 'gemini'), force (default false).

On success the item's assignee_agent is set and status moves to 'in_progress' (from open/triaged). If another agent already holds the claim, this fails with a message naming the holder — pass force=true only if you intend to take over.

Move a feedback item through the workflow: open → triaged → in_progress → fixed → verified | wontfix.

Args: id, status, note (optional — recorded as a comment for the audit trail), author (default 'agent').

Use 'fixed' after making the change; use loopback_resolve_feedback for final verified/wontfix closure.

Append a comment to a feedback item's discussion trail. Use for investigation notes, questions back to the reporter, or reasoning worth preserving.

Args: id, author, body (markdown ok).

Attach the fix to a feedback item so the loop is auditable: which repo/branch/commit/PR addressed it and a one-paragraph diff summary.

Args: id, plus any of repo, branch, commit, pr_url, diff_summary. Provided fields merge into existing links.

Call this right after committing the fix, before updating status to 'fixed'.

Close a feedback item with a final outcome.

Args: id, resolution ('verified' = the fix was confirmed against the running app, tests, or the relevant metric/replay; 'wontfix' = intentionally not addressing), note (optional closing comment), agent (YOUR name — this is the write that turns the reporter's pin full green, and omitting it records the generic default instead of you).

Prefer verifying before resolving: re-check the UI via your browser tools, or confirm the error/metric cleared, then call this.

Correct an item after it was filed: title, body, severity, type, project, or route.

Feedback is filed fast and imprecisely on purpose — that is what makes people file it at all. Use this to re-rank a severity you now understand, fix a mis-guessed type, correct a typo, or move an item to the right project.

Args: id, plus any of title, body, severity (p0-p3), type (ui|backend|usage|ux), project, route. Also author (default 'human') — use your agent name so the trail says who re-triaged it.

Every change is recorded as a comment naming the old and new value; nothing is silently rewritten. Fields you omit are left alone.

This is for correcting the REPORT. To record progress use loopback_update_status, and to record the fix use loopback_link_change.

Overview of the feedback queue: counts by project and status. Use to orient before picking work, or to report queue health.

Args: project (optional — omit for all projects).

Returns { total, projects: [{ project, by_status, total }] }.