:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
feat(signals): add wrong assignee dismissal reason (#121800)
Dylan Martincd4cc94facad
diff --git a/packages/agent/packages/agent-contracts/src/dismissal-reasons.ts b/packages/agent/packages/agent-contracts/src/dismissal-reasons.tsindex 849e9d6ca56e..4fa948e2c9f9 100644--- a/packages/agent/packages/agent-contracts/src/dismissal-reasons.ts+++ b/packages/agent/packages/agent-contracts/src/dismissal-reasons.ts@@ -16,13 +16,17 @@ export const DISMISSAL_REASON_OPTIONS = [value: "analysis_wrong",label: "Agent's analysis is wrong",},+ {+ value: "wrong_assignee",+ label: "Wrong assignee",+ },{value: "wontfix_intentional",label: "Won't fix - intentional behavior",},{value: "wontfix_irrelevant",- label: "Won't fix - issue is real but insignificant",+ label: "Not relevant to this project",},{ value: "other", label: "Something else…" },] as const;diff --git a/products/desktop/docs/INBOX-REPORT-STATES.md b/products/desktop/docs/INBOX-REPORT-STATES.mdindex 2ae446ddd5c0..48a518764624 100644--- a/products/desktop/docs/INBOX-REPORT-STATES.md+++ b/products/desktop/docs/INBOX-REPORT-STATES.md@@ -14,6 +14,10 @@ Choosing **Already fixed** in the Dismiss dialog pauses the report. It returns taction does not start an investigation. Other dismissal reasons archive thereport with status `suppressed`.+**Wrong assignee** records a routing mistake without treating the report as+incorrect. **Not relevant to this project** records that the report itself is+not useful to the project.+**Already fixed** is available for `in_progress`, `pending_input`, `ready`, and`failed` reports. It is disabled for `potential` and `candidate` reports. Thesereports can still be archived with another dismissal reason.diff --git a/products/desktop/packages/ui/src/features/inbox/components/DismissReportDialog.test.tsx b/products/desktop/packages/ui/src/features/inbox/components/DismissReportDialog.test.tsxindex b170f3941786..c46456de0de2 100644--- a/products/desktop/packages/ui/src/features/inbox/components/DismissReportDialog.test.tsx+++ b/products/desktop/packages/ui/src/features/inbox/components/DismissReportDialog.test.tsx@@ -39,7 +39,12 @@ describe("DismissReportDialog", () => {).toContainElement(screen.getByRole("radio", { name: "Already fixed" }));expect(screen.getByRole("group", { name: "Don't surface again" }),- ).toContainElement(screen.getByRole("radio", { name: "Something else…" }));+ ).toContainElement(screen.getByRole("radio", { name: "Wrong assignee" }));+ expect(+ screen.getByRole("group", { name: "Don't surface again" }),+ ).toContainElement(+ screen.getByRole("radio", { name: "Not relevant to this project" }),+ );await user.click(screen.getByRole("radio", { name: "Already fixed" }));expect(description).toHaveTextContent(/dismisses the report for everyone/);diff --git a/products/signals/ARCHITECTURE.md b/products/signals/ARCHITECTURE.mdindex f8c90a4ba7ff..e9b738ba5475 100644--- a/products/signals/ARCHITECTURE.md+++ b/products/signals/ARCHITECTURE.md@@ -1054,6 +1054,7 @@ So with `ordering=status`, **`failed` sorts after actionable `ready`**. With `orDefault ordering is **`-is_suggested_reviewer,status,-updated_at,id`**.**Dismissal feedback.** `dismissal_reason` / `dismissal_note` on the state and bulk-state bodies persist as a stacking `dismissal` artefact on the report, which stays the record of truth.+`wrong_assignee` records a routing error, while `wontfix_irrelevant` records that the report is not useful to the project; neither says the report analysis is incorrect.When the caller typed a note, that feedback is _also_ forwarded to a `SignalScoutNote` (`dismissal_notes.forward_dismissal_note`).The artefact alone only reaches a scout if some later run happens to search the inbox and land on that report; notes are read by name at the start of every run, which is where a "this was noise, and here is why" verdict belongs."Forward" rather than "promote" because promotion in this product means the pipeline moving a report up the status ladder to `candidate` (`promoted_at`, `signals_at_run`, re-promotion), and nothing here changes a report's standing.diff --git a/products/signals/backend/artefact_schemas.py b/products/signals/backend/artefact_schemas.pyindex 9fdbd03c8b9f..cb2872589344 100644--- a/products/signals/backend/artefact_schemas.py+++ b/products/signals/backend/artefact_schemas.py@@ -509,8 +509,9 @@ class RankingScore(BaseModel):return self-# Reason code shared by the dismissal writer (the state API) and the corrections reader-# (`repo_corrections`), defined here so the two cannot drift apart.+# Reason-only routing feedback still needs to reach the authoring scout.+DISMISSAL_REASON_WRONG_ASSIGNEE = "wrong_assignee"+# Shared by the dismissal writer and repository-corrections reader so they cannot drift apart.DISMISSAL_REASON_WRONG_REPO = "wrong_repo"# Reason codes that claim the issue is fixed, rather than stating a preference about the report.# A later matching signal contradicts the claim, so the grouping stage treats these dismissals thediff --git a/products/signals/backend/dismissal_notes.py b/products/signals/backend/dismissal_notes.pyindex 4149c92e764a..89ddab813d2f 100644--- a/products/signals/backend/dismissal_notes.py+++ b/products/signals/backend/dismissal_notes.py@@ -8,7 +8,7 @@ the feedback as a `SignalScoutNote`, which every run reads by name at cold start(`scout-notes-list`, see the run prompt's *Notes left for you* section).Dismissing, snoozing, and restoring forward; resolving does not, see `_FORWARDED_OUTCOMES`.-A `wrong_repo` dismissal forwards even with no note: the repositories it names are the feedback.+`wrong_assignee` and `wrong_repo` dismissals forward even with no note because the reason itself is feedback.Forwarding, not promotion: promotion here is the pipeline moving a report up to `candidate`, andnothing in this path changes a report's standing.@@ -40,7 +40,11 @@ from posthog.models import Team, Userfrom posthog.permissions import get_authenticator_scoped_team_idsfrom products.access_control.backend.facade.user_access_control import UserAccessControl-from products.signals.backend.artefact_schemas import DISMISSAL_REASON_WRONG_REPO, Dismissal+from products.signals.backend.artefact_schemas import (+ DISMISSAL_REASON_WRONG_ASSIGNEE,+ DISMISSAL_REASON_WRONG_REPO,+ Dismissal,+)from products.signals.backend.models import SignalReport, SignalReportArtefact, SignalScoutNotefrom products.signals.backend.repo_corrections import sanitized_repositoryfrom products.signals.backend.scout_authorship import resolve_authoring_skill_names@@ -110,9 +114,7 @@ def forward_dismissal_note(read the database."""text = (note or "").strip()- # A wrong-repo verdict carries its feedback in the repositories it names, so it forwards with no- # prose. Every other reason has nothing to tell a scout without the note.- if not reports or (not text and reason != DISMISSAL_REASON_WRONG_REPO):+ if not reports or (not text and reason not in {DISMISSAL_REASON_WRONG_ASSIGNEE, DISMISSAL_REASON_WRONG_REPO}):return []try:return _forward(team=team, reports=reports, reason=reason, note=text, request=request)diff --git a/products/signals/backend/scout_harness/prompt.py b/products/signals/backend/scout_harness/prompt.pyindex a27dfdcf102b..e35a1d25ecac 100644--- a/products/signals/backend/scout_harness/prompt.py+++ b/products/signals/backend/scout_harness/prompt.py@@ -257,7 +257,7 @@ Notes are the team's cheapest steering lever: feedback on what you've surfaced (Each note's `origin` says how to read it, and each names the report ids it concerns, so `inbox-reports-retrieve` gets you the full context:- `human`: steering someone wrote for you directly.-- `report_dismissal`: a reviewer's verdict on one or more of your reports, forwarded so it reaches you without you re-finding them. One note covers one verdict, so when a reviewer acted on several reports at once read it as their view of that batch, never as a fleet-wide rule. **Dismissed** is the only kind that should make you stop filing something, and the reason code decides whether it even means that: `analysis_wrong`, `report_unclear`, and `wontfix_*` speak to your precision, so fold a reason that generalizes into a `noise:`/`pattern:` entry; `wrong_repo` says the report targeted the wrong repository, not that the finding was wrong — keep watching the topic, record the repository the note says was wrong so you do not pick it again for that kind of work, and record the corrected repository when the note names one; `already_fixed` means the issue was real and someone fixed it, so record that a fix shipped and keep watching for a recurrence. **Snoozed or restored** is about timing, not correctness: the report is still live, so keep watching what it describes.+- `report_dismissal`: a reviewer's verdict on one or more of your reports, forwarded so it reaches you without you re-finding them. One note covers one verdict, so when a reviewer acted on several reports at once read it as their view of that batch, never as a fleet-wide rule. **Dismissed** is the only kind that should make you stop filing something, and the reason code decides whether it even means that: `analysis_wrong` and `report_unclear` speak to your precision, while `wontfix_*` say the report was not useful in this project's context, so fold a reason that generalizes into a `noise:`/`pattern:` entry; `wrong_assignee` says the report reached the wrong owner, not that the finding was wrong, so correct the matching `reviewer:` memory and keep watching the topic; `wrong_repo` says the report targeted the wrong repository, not that the finding was wrong — keep watching the topic, record the repository the note says was wrong so you do not pick it again for that kind of work, and record the corrected repository when the note names one; `already_fixed` means the issue was real and someone fixed it, so record that a fix shipped and keep watching for a recurrence. **Snoozed or restored** is about timing, not correctness: the report is still live, so keep watching what it describes.- `report_discussion`: a question a user asked when they opened a discussion on one of your reports. Not a verdict and not a directive, but often carrying a preference, a correction, or context you couldn't have known ("this is expected, it's the approval flow"): fold the durable part into a `noise:`/`pattern:`/`watch:` entry, and leave one-off asks and unrelated chatter be.- `report_reviewer_correction`: someone added or removed a suggested reviewer on a report. This is the strongest ownership evidence there is, and the note reaches you because you either filed the report, edited it, or hold a `reviewer:` memory naming the login. An added login is a positive ownership fact, so record it with the report id and the date. A removal is weaker on its own (someone away, a duplicate reviewer, noise the editor trimmed), and weaker still when the editor removed their own login, but repeated removals of the same login on the same surface say the memory you route on is stale. Search your `reviewer:` keys for the login and condense rather than delete: fold in that a teammate removed it, on how many reports and when, and keep the ownership evidence that still stands. Do not put a removed login back on a report about the same topic without new evidence.diff --git a/products/signals/backend/test/test_dismissal_scout_notes.py b/products/signals/backend/test/test_dismissal_scout_notes.pyindex 94d318d8ddd7..ec37c4b67f6f 100644--- a/products/signals/backend/test/test_dismissal_scout_notes.py+++ b/products/signals/backend/test/test_dismissal_scout_notes.py@@ -190,6 +190,18 @@ class TestDismissalScoutNotes(APIBaseTest):assert self._notes() == []+ def test_wrong_assignee_dismissal_forwards_without_prose(self) -> None:+ self._create_scout_skill()+ report = self._create_report()+ self._create_run(emitted_report_ids=[str(report.id)])++ self._dismiss(report, dismissal_reason="wrong_assignee")++ note = self._notes()[0]+ assert note.skill_name == SCOUT_SKILL+ assert "wrong_assignee" in note.content+ assert "The note left with it" not in note.content+@parameterized.expand([("with_correction", {"corrected_repository": "acme/right"}, True),diff --git a/products/signals/backend/test/test_signal_report_api.py b/products/signals/backend/test/test_signal_report_api.pyindex 89706e764869..9d86c594bb7a 100644--- a/products/signals/backend/test/test_signal_report_api.py+++ b/products/signals/backend/test/test_signal_report_api.py@@ -3044,6 +3044,13 @@ class TestSignalReportSuppressionAPI(APIBaseTest):"other","edge case",),+ (+ "suppress_with_wrong_assignee",+ {"state": "suppressed", "dismissal_reason": "wrong_assignee"},+ SignalReport.Status.SUPPRESSED,+ "wrong_assignee",+ None,+ ),("snooze_with_reason_and_note",{diff --git a/products/signals/backend/views.py b/products/signals/backend/views.pyindex febc31f255e0..5f876840a466 100644--- a/products/signals/backend/views.py+++ b/products/signals/backend/views.py@@ -700,9 +700,10 @@ SIGNAL_REPORT_DISMISSAL_REASON_CHOICES = [("already_fixed", "Already fixed"),("report_unclear", "Report is unclear to me"),("analysis_wrong", "Agent's analysis is wrong"),+ ("wrong_assignee", "Wrong assignee"),("wrong_repo", "Agent picked the wrong repository"),("wontfix_intentional", "Won't fix - intentional behavior"),- ("wontfix_irrelevant", "Won't fix - issue is real but insignificant"),+ ("wontfix_irrelevant", "Not relevant to this project"),("fixed_outside_posthog", "Fixed outside PostHog"),("no_action_needed", "No action needed"),("pr_merged", "PR was merged"),@@ -711,7 +712,7 @@ SIGNAL_REPORT_DISMISSAL_REASON_CHOICES = [_DISMISSAL_REASON_HELP_TEXT = ("Optional canonical reason code recorded with the transition. Must be one of: already_fixed, "- "report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, "+ "report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, ""fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a ""labelled chip rather than a raw code. When the work this report asked for is done, the honest ""transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), "@@ -721,8 +722,9 @@ _DISMISSAL_REASON_HELP_TEXT = ("resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three ""codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked ""to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. "- "The dismissal codes (report_unclear, analysis_wrong, "+ "The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, ""wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use "+ "'wrong_assignee' when the report was routed to the wrong person or team. ""'wrong_repo' when the agent picked the wrong repository for this report, ideally with ""corrected_repository naming the right one. ""Use 'other' together with a dismissal_note for anything that doesn't fit a code."diff --git a/products/signals/dags/inbox_ranking/common.py b/products/signals/dags/inbox_ranking/common.pyindex 5334b9fa00d2..05200c6295d3 100644--- a/products/signals/dags/inbox_ranking/common.py+++ b/products/signals/dags/inbox_ranking/common.py@@ -45,6 +45,7 @@ NOT_FIXED_RESOLUTION_REASONS = ("wontfix_intentional","wontfix_irrelevant","report_unclear",+ "wrong_assignee","wrong_repo",)# A dismissal that says the problem was real and is fixed somewhere.diff --git a/products/signals/dags/inbox_ranking/tests/test_dataset.py b/products/signals/dags/inbox_ranking/tests/test_dataset.pyindex 6e0b7ca91451..9cd8e2503854 100644--- a/products/signals/dags/inbox_ranking/tests/test_dataset.py+++ b/products/signals/dags/inbox_ranking/tests/test_dataset.py@@ -886,6 +886,7 @@ class TestStatusStream(ClickhouseTestMixin, BaseTest):("reasonless_resolve", "ready", "resolved", None, 1),("already_fixed_dismissal", "ready", "suppressed", "already_fixed", 1),("analysis_wrong_resolve", "ready", "resolved", "analysis_wrong", 0),+ ("wrong_assignee_resolve", "ready", "resolved", "wrong_assignee", 0),("no_action_needed_resolve", "ready", "resolved", "no_action_needed", 0),("manual_fix_resolve", "ready", "resolved", "fixed_outside_posthog", 1),("other_dismissal", "ready", "suppressed", "other", 0),diff --git a/products/signals/frontend/generated/api.schemas.ts b/products/signals/frontend/generated/api.schemas.tsindex 990d4dda193f..251b2d9353f0 100644--- a/products/signals/frontend/generated/api.schemas.ts+++ b/products/signals/frontend/generated/api.schemas.ts@@ -4300,9 +4300,10 @@ export const SignalReportStateEnumApi = {* * `already_fixed` - Already fixed* * `report_unclear` - Report is unclear to me* * `analysis_wrong` - Agent's analysis is wrong+ * * `wrong_assignee` - Wrong assignee* * `wrong_repo` - Agent picked the wrong repository* * `wontfix_intentional` - Won't fix - intentional behavior- * * `wontfix_irrelevant` - Won't fix - issue is real but insignificant+ * * `wontfix_irrelevant` - Not relevant to this project* * `fixed_outside_posthog` - Fixed outside PostHog* * `no_action_needed` - No action needed* * `pr_merged` - PR was merged@@ -4314,6 +4315,7 @@ export const DismissalReasonEnumApi = {AlreadyFixed: 'already_fixed',ReportUnclear: 'report_unclear',AnalysisWrong: 'analysis_wrong',+ WrongAssignee: 'wrong_assignee',WrongRepo: 'wrong_repo',WontfixIntentional: 'wontfix_intentional',WontfixIrrelevant: 'wontfix_irrelevant',@@ -4330,14 +4332,15 @@ export interface SignalReportStateRequestApi {* * `potential` - potential* * `resolved` - resolved */state: SignalReportStateEnumApi- /** Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.+ /** Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.** * `already_fixed` - Already fixed* * `report_unclear` - Report is unclear to me* * `analysis_wrong` - Agent's analysis is wrong+ * * `wrong_assignee` - Wrong assignee* * `wrong_repo` - Agent picked the wrong repository* * `wontfix_intentional` - Won't fix - intentional behavior- * * `wontfix_irrelevant` - Won't fix - issue is real but insignificant+ * * `wontfix_irrelevant` - Not relevant to this project* * `fixed_outside_posthog` - Fixed outside PostHog* * `no_action_needed` - No action needed* * `pr_merged` - PR was merged@@ -4962,14 +4965,15 @@ export interface SignalReportBulkStateRequestApi {* * `potential` - potential* * `resolved` - resolved */state: SignalReportStateEnumApi- /** Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.+ /** Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.** * `already_fixed` - Already fixed* * `report_unclear` - Report is unclear to me* * `analysis_wrong` - Agent's analysis is wrong+ * * `wrong_assignee` - Wrong assignee* * `wrong_repo` - Agent picked the wrong repository* * `wontfix_intentional` - Won't fix - intentional behavior- * * `wontfix_irrelevant` - Won't fix - issue is real but insignificant+ * * `wontfix_irrelevant` - Not relevant to this project* * `fixed_outside_posthog` - Fixed outside PostHog* * `no_action_needed` - No action needed* * `pr_merged` - PR was mergeddiff --git a/products/signals/frontend/generated/api.zod.ts b/products/signals/frontend/generated/api.zod.tsindex 74d8fd021442..4a00ee0838a5 100644--- a/products/signals/frontend/generated/api.zod.ts+++ b/products/signals/frontend/generated/api.zod.ts@@ -1020,6 +1020,7 @@ export const SignalsReportsStateCreateBody = /* @__PURE__ */ zod.object({'already_fixed','report_unclear','analysis_wrong',+ 'wrong_assignee','wrong_repo','wontfix_intentional','wontfix_irrelevant',@@ -1029,11 +1030,11 @@ export const SignalsReportsStateCreateBody = /* @__PURE__ */ zod.object({'other',]).describe(- "\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"+ "\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_assignee` - Wrong assignee\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Not relevant to this project\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…").optional().describe(- "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_\*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"+ "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_\*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_assignee` - Wrong assignee\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Not relevant to this project\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"),dismissal_note: zod.string()@@ -1293,6 +1294,7 @@ export const SignalsReportsBulkStateCreateBody = /* @__PURE__ */ zod.object({'already_fixed','report_unclear','analysis_wrong',+ 'wrong_assignee','wrong_repo','wontfix_intentional','wontfix_irrelevant',@@ -1302,11 +1304,11 @@ export const SignalsReportsBulkStateCreateBody = /* @__PURE__ */ zod.object({'other',]).describe(- "\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"+ "\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_assignee` - Wrong assignee\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Not relevant to this project\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…").optional().describe(- "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_\*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"+ "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_\*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_assignee` - Wrong assignee\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Not relevant to this project\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"),dismissal_note: zod.string()diff --git a/products/signals/frontend/inbox/inboxTaskKickoffLogic.ts b/products/signals/frontend/inbox/inboxTaskKickoffLogic.tsindex 0abf6d8f3f66..35ddf398705d 100644--- a/products/signals/frontend/inbox/inboxTaskKickoffLogic.ts+++ b/products/signals/frontend/inbox/inboxTaskKickoffLogic.ts@@ -136,7 +136,7 @@ const REPORT_STATE_INSTRUCTIONS = `Keep the report's own state honest while you- Read the report before you start. This run took the report when its task was created, but a rerun of a run that released it starts unclaimed: claim it again first, so the work you are about to do is visible to everyone else.- Opening the PR is enough by itself. The PR is linked to the report for you, and merging it resolves the report. Do NOT set the state to resolved because you opened a PR: that closes the PR you just opened.- If the work is finished without a PR, set the state to resolved with the reason that fits (\`fixed_outside_posthog\`, \`pr_merged\`, or \`already_fixed\`) and a short note that says what you did.-- If the report holds no work to do, set the state to suppressed with the reason that says why (\`report_unclear\`, \`analysis_wrong\`, \`wrong_repo\` with \`corrected_repository\`, \`wontfix_intentional\`, \`wontfix_irrelevant\`, or \`other\`) and a short note, then release your claim: suppressing does not release it for you.+- If the report holds no work to do, set the state to suppressed with the reason that says why (\`report_unclear\`, \`analysis_wrong\`, \`wrong_assignee\`, \`wrong_repo\` with \`corrected_repository\`, \`wontfix_intentional\`, \`wontfix_irrelevant\`, or \`other\`) and a short note, then release your claim: suppressing does not release it for you.- If you stop for any other reason, release your claim on the report, so it does not look like work is still in flight.`export function buildCreatePrReportPrompt(report: SignalReport, feedback?: string): string {diff --git a/products/signals/frontend/inbox/utils/dismissalReasons.ts b/products/signals/frontend/inbox/utils/dismissalReasons.tsindex a53c3c72d293..52a11b639cf7 100644--- a/products/signals/frontend/inbox/utils/dismissalReasons.ts+++ b/products/signals/frontend/inbox/utils/dismissalReasons.ts@@ -9,9 +9,10 @@ export const DISMISSAL_REASON_OPTIONS = [{ value: 'already_fixed', label: 'Already fixed' },{ value: 'report_unclear', label: 'Report is unclear to me' },{ value: 'analysis_wrong', label: "Agent's analysis is wrong" },+ { value: 'wrong_assignee', label: 'Wrong assignee' },{ value: 'wrong_repo', label: 'Agent picked the wrong repository' },{ value: 'wontfix_intentional', label: "Won't fix - intentional behavior" },- { value: 'wontfix_irrelevant', label: "Won't fix - issue is real but insignificant" },+ { value: 'wontfix_irrelevant', label: 'Not relevant to this project' },{ value: 'other', label: 'Something else…' },] as constdiff --git a/products/signals/mcp/tools.yaml b/products/signals/mcp/tools.yamlindex 2e24f8885a55..d3b96c999ad5 100644--- a/products/signals/mcp/tools.yaml+++ b/products/signals/mcp/tools.yaml@@ -271,12 +271,12 @@ tools:for clearing, snoozing, or resolving a batch of inbox reports without one request per report. Pass `ids`(1–100 report ids) and a `state` ('resolved' when the requested work is done, 'suppressed' to dismiss,'potential' to snooze/restore); the optional `dismissal_reason` (same canonical codes as the single-report- tool, including `wrong_repo`), `dismissal_note`, `corrected_repository` (only with `wrong_repo`), and- `snooze_for` apply to every id. Dismissing or resolving closes each report's open implementation PR, if it- has one. Each id is processed independently, so the whole call returns 200 even on partial failure: inspect- `results` (one entry per id, in request order) and the `transitioned_count` / `skipped_count` /- `failed_count` / `not_found_count` summary. An id whose transition isn't allowed from its current status- comes back as `skipped` (the single-report 409) while the rest still go through.+ tool, including `wrong_assignee` and `wrong_repo`), `dismissal_note`, `corrected_repository` (only with+ `wrong_repo`), and `snooze_for` apply to every id. Dismissing or resolving closes each report's open+ implementation PR, if it has one. Each id is processed independently, so the whole call returns 200 even on+ partial failure: inspect `results` (one entry per id, in request order) and the `transitioned_count` /+ `skipped_count` / `failed_count` / `not_found_count` summary. An id whose transition isn't allowed from its+ current status comes back as `skipped` (the single-report 409) while the rest still go through.inbox-reports-claim:operation: signals_reports_claimenabled: true@@ -529,17 +529,18 @@ tools:Dismissing or resolving closes the report's open implementation PR, if it has one; a resolved report neverreopens, and a recurrence starts a fresh report linked to it. Optionally include a `dismissal_reason` — acanonical code from the inbox UI (`fixed_outside_posthog`, `pr_merged`, `already_fixed`, `report_unclear`,- `analysis_wrong`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`, `other`), so it renders as a- labelled chip rather than a raw string. With state='resolved' use `fixed_outside_posthog` when the fix- landed without a pull request, `pr_merged` when a pull request with the fix was merged but did not resolve- the report on its own, or `already_fixed` when it was fixed before the report was filed; the other codes- describe a dismissal. Use `wrong_repo` when the agent picked the wrong repository for this report, and pass- `corrected_repository` (an 'owner/repo' string, only allowed with `wrong_repo`) to name the one it should- have used — the correction is recorded and fed into future repository selection for this project. Use- `other` plus a `dismissal_note` (free-form text, up to 4000 chars) for anything that doesn't fit a code.- Both are persisted as a DISMISSAL artefact on the report so the rationale survives later transitions.- Returns 409 if the transition is not allowed from the report's current status. To transition several reports- at once, use `inbox-reports-bulk-set-state` instead of calling this per report.+ `analysis_wrong`, `wrong_assignee`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`, `other`), so+ it renders as a labelled chip rather than a raw string. With state='resolved' use `fixed_outside_posthog`+ when the fix landed without a pull request, `pr_merged` when a pull request with the fix was merged but did+ not resolve the report on its own, or `already_fixed` when it was fixed before the report was filed; the+ other codes describe a dismissal. Use `wrong_assignee` when the report reached the wrong person or team. Use+ `wrong_repo` when the agent picked the wrong repository for this report, and pass `corrected_repository` (an+ 'owner/repo' string, only allowed with `wrong_repo`) to name the one it should have used — the correction is+ recorded and fed into future repository selection for this project. Use `other` plus a `dismissal_note`+ (free-form text, up to 4000 chars) for anything that doesn't fit a code. Both are persisted as a DISMISSAL+ artefact on the report so the rationale survives later transitions. Returns 409 if the transition is not+ allowed from the report's current status. To transition several reports at once, use+ `inbox-reports-bulk-set-state` instead of calling this per report.inbox-reports-update:operation: signals_reports_partial_updateenabled: truediff --git a/products/signals/skills/inbox-exploration/SKILL.md b/products/signals/skills/inbox-exploration/SKILL.mdindex 1e90575cf47e..b05f797b463a 100644--- a/products/signals/skills/inbox-exploration/SKILL.md+++ b/products/signals/skills/inbox-exploration/SKILL.md@@ -528,9 +528,10 @@ inbox-reports-set-statethat pairing means "fixed by something else, might recur", so the report comes back.- `state: "suppressed"` dismisses the report from the inbox; `state: "potential"` snoozes it backinto the pipeline. When snoozing, `snooze_for: <N>` holds it until it accumulates N more signals.-- `dismissal_reason` must be one of nine server-validated canonical codes — `already_fixed`,- `report_unclear`, `analysis_wrong`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`,- `fixed_outside_posthog`, `pr_merged`, `other` — an unlisted value returns `400`. Reach for `other` plus a+- `dismissal_reason` must be one of the server-validated canonical codes — `already_fixed`,+ `report_unclear`, `analysis_wrong`, `wrong_assignee`, `wrong_repo`, `wontfix_intentional`,+ `wontfix_irrelevant`, `fixed_outside_posthog`, `no_action_needed`, `pr_merged`, `other` — an+ unlisted value returns `400`. Reach for `other` plus a`dismissal_note` for anything that doesn't fit a specific code. `dismissal_note` is free-form(≤ 4000 chars). Both persist as a DISMISSALartefact, so the rationale survives later transitions — **always include them**, on a resolve too,@@ -541,6 +542,8 @@ inbox-reports-set-stateselection for the project, and when the named repository is connected to the project it alsobecomes this report's own next selection. Without a usable correction the report's selection iscleared instead, so a restored report re-selects rather than reusing the rejected repository.+- `wrong_assignee` means the report reached the wrong person or team. It is routing feedback, not a+ verdict that the report itself was wrong.- On a dismiss, snooze, or restore, the `dismissal_note` is also forwarded as a steering note to thescout that filed the report, which every scout run reads at cold start, so what you write there iswhat stops the same report being filed again. Write it for that reader: name the evidence thatdiff --git a/products/signals/skills/working-with-scouts/SKILL.md b/products/signals/skills/working-with-scouts/SKILL.mdindex e33bf368a32c..eef989ed4fdf 100644--- a/products/signals/skills/working-with-scouts/SKILL.md+++ b/products/signals/skills/working-with-scouts/SKILL.md@@ -90,7 +90,7 @@ Report triage mechanics live in `inbox-exploration`; what matters here is how ac- **Verify before implementing.** A scout report is an LLM diagnosis, not ground truth — confirm the cited entities and behavior against the live data or code before fixing.A report that doesn't hold up is a dismissal candidate, and dismissing it _well_ is valuable work (see below).- **Close every report with the honest state**: `resolved` when the work landed (PR-backed fixes resolve themselves on merge — don't resolve at PR-open time), `suppressed` (dismissed) when it's not real or not worth fixing, `potential` (snoozed) when it's real but deferred.-- **The dismissal note is a steering message.** On a dismiss, snooze, or restore, the `dismissal_note` is forwarded to the scout that filed the report, and every future run reads it as prior context (a `wrong_repo` dismissal forwards even without a note, since the repositories it names are the feedback).+- **The dismissal note is a steering message.** On a dismiss, snooze, or restore, the `dismissal_note` is forwarded to the scout that filed the report, and every future run reads it as prior context. A `wrong_assignee` or `wrong_repo` dismissal forwards even without a note because the reason itself is routing feedback.Write it for that reader: name the evidence that settles it ("staging traffic — hosts match `*.dev.example.com`, ignore this pattern"), not just the verdict.A well-written dismissal is the cheapest scout edit you will ever make; a bare dismissal teaches nothing and the report comes back.Two caveats: forwarding is best-effort and requires the dismisser to hold scout-steering (skill-editor) access on the canonical project, and a dismissal made on a child environment's report never forwards at all; in both cases the note still lands on the report but never reaches the scout, so for a steer that must stick, confirm it arrived (`posthog:scout-notes-list`, with a credential that also holds `task:read`, since derived notes are hidden without it) or have someone authorized leave a note directly.diff --git a/services/mcp/schema/generated-tool-definitions.json b/services/mcp/schema/generated-tool-definitions.jsonindex 230799c47cc9..b69568198692 100644--- a/services/mcp/schema/generated-tool-definitions.json+++ b/services/mcp/schema/generated-tool-definitions.json@@ -7652,7 +7652,7 @@}},"inbox-reports-bulk-set-state": {- "description": "Transition many signal reports to the same state in one call — the bulk form of `inbox-reports-set-state`, for clearing, snoozing, or resolving a batch of inbox reports without one request per report. Pass `ids` (1–100 report ids) and a `state` ('resolved' when the requested work is done, 'suppressed' to dismiss, 'potential' to snooze/restore); the optional `dismissal_reason` (same canonical codes as the single-report tool, including `wrong_repo`), `dismissal_note`, `corrected_repository` (only with `wrong_repo`), and `snooze_for` apply to every id. Dismissing or resolving closes each report's open implementation PR, if it has one. Each id is processed independently, so the whole call returns 200 even on partial failure: inspect `results` (one entry per id, in request order) and the `transitioned_count` / `skipped_count` / `failed_count` / `not_found_count` summary. An id whose transition isn't allowed from its current status comes back as `skipped` (the single-report 409) while the rest still go through.",+ "description": "Transition many signal reports to the same state in one call — the bulk form of `inbox-reports-set-state`, for clearing, snoozing, or resolving a batch of inbox reports without one request per report. Pass `ids` (1–100 report ids) and a `state` ('resolved' when the requested work is done, 'suppressed' to dismiss, 'potential' to snooze/restore); the optional `dismissal_reason` (same canonical codes as the single-report tool, including `wrong_assignee` and `wrong_repo`), `dismissal_note`, `corrected_repository` (only with `wrong_repo`), and `snooze_for` apply to every id. Dismissing or resolving closes each report's open implementation PR, if it has one. Each id is processed independently, so the whole call returns 200 even on partial failure: inspect `results` (one entry per id, in request order) and the `transitioned_count` / `skipped_count` / `failed_count` / `not_found_count` summary. An id whose transition isn't allowed from its current status comes back as `skipped` (the single-report 409) while the rest still go through.","category": "Signals","feature": "signals","summary": "Dismiss or snooze signal reports in bulk",@@ -7757,7 +7757,7 @@}},"inbox-reports-set-state": {- "description": "Transition a single signal report to a new state. Use 'resolved' when the work this report asked for has been done (e.g. you fixed the issue it describes), 'suppressed' to dismiss the report from the inbox (the user has reviewed it and decided no action is needed), or 'potential' to snooze/restore it back into the pipeline for later review. Resolving is allowed from ready, pending_input, or failed, or from a suppressed report whose previous status was ready, pending_input, failed, or resolved. Repeat resolution succeeds. Other statuses return 409. Fixed reasons require state='suppressed' or state='resolved', not 'potential'. Dismissing or resolving closes the report's open implementation PR, if it has one; a resolved report never reopens, and a recurrence starts a fresh report linked to it. Optionally include a `dismissal_reason` — a canonical code from the inbox UI (`fixed_outside_posthog`, `pr_merged`, `already_fixed`, `report_unclear`, `analysis_wrong`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`, `other`), so it renders as a labelled chip rather than a raw string. With state='resolved' use `fixed_outside_posthog` when the fix landed without a pull request, `pr_merged` when a pull request with the fix was merged but did not resolve the report on its own, or `already_fixed` when it was fixed before the report was filed; the other codes describe a dismissal. Use `wrong_repo` when the agent picked the wrong repository for this report, and pass `corrected_repository` (an 'owner/repo' string, only allowed with `wrong_repo`) to name the one it should have used — the correction is recorded and fed into future repository selection for this project. Use `other` plus a `dismissal_note` (free-form text, up to 4000 chars) for anything that doesn't fit a code. Both are persisted as a DISMISSAL artefact on the report so the rationale survives later transitions. Returns 409 if the transition is not allowed from the report's current status. To transition several reports at once, use `inbox-reports-bulk-set-state` instead of calling this per report.",+ "description": "Transition a single signal report to a new state. Use 'resolved' when the work this report asked for has been done (e.g. you fixed the issue it describes), 'suppressed' to dismiss the report from the inbox (the user has reviewed it and decided no action is needed), or 'potential' to snooze/restore it back into the pipeline for later review. Resolving is allowed from ready, pending_input, or failed, or from a suppressed report whose previous status was ready, pending_input, failed, or resolved. Repeat resolution succeeds. Other statuses return 409. Fixed reasons require state='suppressed' or state='resolved', not 'potential'. Dismissing or resolving closes the report's open implementation PR, if it has one; a resolved report never reopens, and a recurrence starts a fresh report linked to it. Optionally include a `dismissal_reason` — a canonical code from the inbox UI (`fixed_outside_posthog`, `pr_merged`, `already_fixed`, `report_unclear`, `analysis_wrong`, `wrong_assignee`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`, `other`), so it renders as a labelled chip rather than a raw string. With state='resolved' use `fixed_outside_posthog` when the fix landed without a pull request, `pr_merged` when a pull request with the fix was merged but did not resolve the report on its own, or `already_fixed` when it was fixed before the report was filed; the other codes describe a dismissal. Use `wrong_assignee` when the report reached the wrong person or team. Use `wrong_repo` when the agent picked the wrong repository for this report, and pass `corrected_repository` (an 'owner/repo' string, only allowed with `wrong_repo`) to name the one it should have used — the correction is recorded and fed into future repository selection for this project. Use `other` plus a `dismissal_note` (free-form text, up to 4000 chars) for anything that doesn't fit a code. Both are persisted as a DISMISSAL artefact on the report so the rationale survives later transitions. Returns 409 if the transition is not allowed from the report's current status. To transition several reports at once, use `inbox-reports-bulk-set-state` instead of calling this per report.","category": "Signals","feature": "signals","summary": "Dismiss or snooze a signal report",diff --git a/services/mcp/schema/tool-definitions-all.json b/services/mcp/schema/tool-definitions-all.jsonindex 294a8f3bbb7d..d8efd4c46e39 100644--- a/services/mcp/schema/tool-definitions-all.json+++ b/services/mcp/schema/tool-definitions-all.json@@ -7854,7 +7854,7 @@}},"inbox-reports-bulk-set-state": {- "description": "Transition many signal reports to the same state in one call — the bulk form of `inbox-reports-set-state`, for clearing, snoozing, or resolving a batch of inbox reports without one request per report. Pass `ids` (1–100 report ids) and a `state` ('resolved' when the requested work is done, 'suppressed' to dismiss, 'potential' to snooze/restore); the optional `dismissal_reason` (same canonical codes as the single-report tool, including `wrong_repo`), `dismissal_note`, `corrected_repository` (only with `wrong_repo`), and `snooze_for` apply to every id. Dismissing or resolving closes each report's open implementation PR, if it has one. Each id is processed independently, so the whole call returns 200 even on partial failure: inspect `results` (one entry per id, in request order) and the `transitioned_count` / `skipped_count` / `failed_count` / `not_found_count` summary. An id whose transition isn't allowed from its current status comes back as `skipped` (the single-report 409) while the rest still go through.",+ "description": "Transition many signal reports to the same state in one call — the bulk form of `inbox-reports-set-state`, for clearing, snoozing, or resolving a batch of inbox reports without one request per report. Pass `ids` (1–100 report ids) and a `state` ('resolved' when the requested work is done, 'suppressed' to dismiss, 'potential' to snooze/restore); the optional `dismissal_reason` (same canonical codes as the single-report tool, including `wrong_assignee` and `wrong_repo`), `dismissal_note`, `corrected_repository` (only with `wrong_repo`), and `snooze_for` apply to every id. Dismissing or resolving closes each report's open implementation PR, if it has one. Each id is processed independently, so the whole call returns 200 even on partial failure: inspect `results` (one entry per id, in request order) and the `transitioned_count` / `skipped_count` / `failed_count` / `not_found_count` summary. An id whose transition isn't allowed from its current status comes back as `skipped` (the single-report 409) while the rest still go through.","category": "Signals","feature": "signals","summary": "Dismiss or snooze signal reports in bulk",@@ -7959,7 +7959,7 @@}},"inbox-reports-set-state": {- "description": "Transition a single signal report to a new state. Use 'resolved' when the work this report asked for has been done (e.g. you fixed the issue it describes), 'suppressed' to dismiss the report from the inbox (the user has reviewed it and decided no action is needed), or 'potential' to snooze/restore it back into the pipeline for later review. Resolving is allowed from ready, pending_input, or failed, or from a suppressed report whose previous status was ready, pending_input, failed, or resolved. Repeat resolution succeeds. Other statuses return 409. Fixed reasons require state='suppressed' or state='resolved', not 'potential'. Dismissing or resolving closes the report's open implementation PR, if it has one; a resolved report never reopens, and a recurrence starts a fresh report linked to it. Optionally include a `dismissal_reason` — a canonical code from the inbox UI (`fixed_outside_posthog`, `pr_merged`, `already_fixed`, `report_unclear`, `analysis_wrong`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`, `other`), so it renders as a labelled chip rather than a raw string. With state='resolved' use `fixed_outside_posthog` when the fix landed without a pull request, `pr_merged` when a pull request with the fix was merged but did not resolve the report on its own, or `already_fixed` when it was fixed before the report was filed; the other codes describe a dismissal. Use `wrong_repo` when the agent picked the wrong repository for this report, and pass `corrected_repository` (an 'owner/repo' string, only allowed with `wrong_repo`) to name the one it should have used — the correction is recorded and fed into future repository selection for this project. Use `other` plus a `dismissal_note` (free-form text, up to 4000 chars) for anything that doesn't fit a code. Both are persisted as a DISMISSAL artefact on the report so the rationale survives later transitions. Returns 409 if the transition is not allowed from the report's current status. To transition several reports at once, use `inbox-reports-bulk-set-state` instead of calling this per report.",+ "description": "Transition a single signal report to a new state. Use 'resolved' when the work this report asked for has been done (e.g. you fixed the issue it describes), 'suppressed' to dismiss the report from the inbox (the user has reviewed it and decided no action is needed), or 'potential' to snooze/restore it back into the pipeline for later review. Resolving is allowed from ready, pending_input, or failed, or from a suppressed report whose previous status was ready, pending_input, failed, or resolved. Repeat resolution succeeds. Other statuses return 409. Fixed reasons require state='suppressed' or state='resolved', not 'potential'. Dismissing or resolving closes the report's open implementation PR, if it has one; a resolved report never reopens, and a recurrence starts a fresh report linked to it. Optionally include a `dismissal_reason` — a canonical code from the inbox UI (`fixed_outside_posthog`, `pr_merged`, `already_fixed`, `report_unclear`, `analysis_wrong`, `wrong_assignee`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`, `other`), so it renders as a labelled chip rather than a raw string. With state='resolved' use `fixed_outside_posthog` when the fix landed without a pull request, `pr_merged` when a pull request with the fix was merged but did not resolve the report on its own, or `already_fixed` when it was fixed before the report was filed; the other codes describe a dismissal. Use `wrong_assignee` when the report reached the wrong person or team. Use `wrong_repo` when the agent picked the wrong repository for this report, and pass `corrected_repository` (an 'owner/repo' string, only allowed with `wrong_repo`) to name the one it should have used — the correction is recorded and fed into future repository selection for this project. Use `other` plus a `dismissal_note` (free-form text, up to 4000 chars) for anything that doesn't fit a code. Both are persisted as a DISMISSAL artefact on the report so the rationale survives later transitions. Returns 409 if the transition is not allowed from the report's current status. To transition several reports at once, use `inbox-reports-bulk-set-state` instead of calling this per report.","category": "Signals","feature": "signals","summary": "Dismiss or snooze a signal report",diff --git a/services/mcp/src/api/generated.ts b/services/mcp/src/api/generated.tsindex 59111863ad20..28e1a63704c1 100644--- a/services/mcp/src/api/generated.ts+++ b/services/mcp/src/api/generated.ts@@ -38576,9 +38576,10 @@ export namespace Schemas {* * `already_fixed` - Already fixed* * `report_unclear` - Report is unclear to me* * `analysis_wrong` - Agent's analysis is wrong+ * * `wrong_assignee` - Wrong assignee* * `wrong_repo` - Agent picked the wrong repository* * `wontfix_intentional` - Won't fix - intentional behavior- * * `wontfix_irrelevant` - Won't fix - issue is real but insignificant+ * * `wontfix_irrelevant` - Not relevant to this project* * `fixed_outside_posthog` - Fixed outside PostHog* * `no_action_needed` - No action needed* * `pr_merged` - PR was merged@@ -38591,6 +38592,7 @@ export namespace Schemas {AlreadyFixed: 'already_fixed',ReportUnclear: 'report_unclear',AnalysisWrong: 'analysis_wrong',+ WrongAssignee: 'wrong_assignee',WrongRepo: 'wrong_repo',WontfixIntentional: 'wontfix_intentional',WontfixIrrelevant: 'wontfix_irrelevant',@@ -106561,14 +106563,15 @@ export namespace Schemas {* * `potential` - potential* * `resolved` - resolved */state: SignalReportStateEnum;- /** Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.+ /** Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.** * `already_fixed` - Already fixed* * `report_unclear` - Report is unclear to me* * `analysis_wrong` - Agent's analysis is wrong+ * * `wrong_assignee` - Wrong assignee* * `wrong_repo` - Agent picked the wrong repository* * `wontfix_intentional` - Won't fix - intentional behavior- * * `wontfix_irrelevant` - Won't fix - issue is real but insignificant+ * * `wontfix_irrelevant` - Not relevant to this project* * `fixed_outside_posthog` - Fixed outside PostHog* * `no_action_needed` - No action needed* * `pr_merged` - PR was merged@@ -106911,14 +106914,15 @@ export namespace Schemas {* * `potential` - potential* * `resolved` - resolved */state: SignalReportStateEnum;- /** Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.+ /** Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.** * `already_fixed` - Already fixed* * `report_unclear` - Report is unclear to me* * `analysis_wrong` - Agent's analysis is wrong+ * * `wrong_assignee` - Wrong assignee* * `wrong_repo` - Agent picked the wrong repository* * `wontfix_intentional` - Won't fix - intentional behavior- * * `wontfix_irrelevant` - Won't fix - issue is real but insignificant+ * * `wontfix_irrelevant` - Not relevant to this project* * `fixed_outside_posthog` - Fixed outside PostHog* * `no_action_needed` - No action needed* * `pr_merged` - PR was mergeddiff --git a/services/mcp/src/generated/signals/api.ts b/services/mcp/src/generated/signals/api.tsindex 820e4ce98acd..86ab142113c7 100644--- a/services/mcp/src/generated/signals/api.ts+++ b/services/mcp/src/generated/signals/api.ts@@ -616,6 +616,7 @@ export const SignalsReportsStateCreateBody = () => zod.object({'already_fixed','report_unclear','analysis_wrong',+ 'wrong_assignee','wrong_repo','wontfix_intentional','wontfix_irrelevant',@@ -625,11 +626,11 @@ export const SignalsReportsStateCreateBody = () => zod.object({'other',]).describe(- "\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"+ "\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_assignee` - Wrong assignee\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Not relevant to this project\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…").optional().describe(- "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_\*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"+ "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_\*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_assignee` - Wrong assignee\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Not relevant to this project\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"),dismissal_note: zod.string()@@ -1051,6 +1052,7 @@ export const SignalsReportsBulkStateCreateBody = () => zod.object({'already_fixed','report_unclear','analysis_wrong',+ 'wrong_assignee','wrong_repo','wontfix_intentional','wontfix_irrelevant',@@ -1060,11 +1062,11 @@ export const SignalsReportsBulkStateCreateBody = () => zod.object({'other',]).describe(- "\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"+ "\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_assignee` - Wrong assignee\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Not relevant to this project\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…").optional().describe(- "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_\*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"+ "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_\*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n\* `already_fixed` - Already fixed\n\* `report_unclear` - Report is unclear to me\n\* `analysis_wrong` - Agent's analysis is wrong\n\* `wrong_assignee` - Wrong assignee\n\* `wrong_repo` - Agent picked the wrong repository\n\* `wontfix_intentional` - Won't fix - intentional behavior\n\* `wontfix_irrelevant` - Not relevant to this project\n\* `fixed_outside_posthog` - Fixed outside PostHog\n\* `no_action_needed` - No action needed\n\* `pr_merged` - PR was merged\n\* `other` - Something else…"),dismissal_note: zod.string()diff --git a/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-reports-bulk-set-state.json b/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-reports-bulk-set-state.jsonindex 960e8471ef20..2ad6a06af93f 100644--- a/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-reports-bulk-set-state.json+++ b/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-reports-bulk-set-state.json@@ -13,11 +13,12 @@"type": "string"},"dismissal_reason": {- "description": "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n* `already_fixed` - Already fixed\n* `report_unclear` - Report is unclear to me\n* `analysis_wrong` - Agent's analysis is wrong\n* `wrong_repo` - Agent picked the wrong repository\n* `wontfix_intentional` - Won't fix - intentional behavior\n* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n* `fixed_outside_posthog` - Fixed outside PostHog\n* `no_action_needed` - No action needed\n* `pr_merged` - PR was merged\n* `other` - Something else…",+ "description": "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n* `already_fixed` - Already fixed\n* `report_unclear` - Report is unclear to me\n* `analysis_wrong` - Agent's analysis is wrong\n* `wrong_assignee` - Wrong assignee\n* `wrong_repo` - Agent picked the wrong repository\n* `wontfix_intentional` - Won't fix - intentional behavior\n* `wontfix_irrelevant` - Not relevant to this project\n* `fixed_outside_posthog` - Fixed outside PostHog\n* `no_action_needed` - No action needed\n* `pr_merged` - PR was merged\n* `other` - Something else…","enum": ["already_fixed","report_unclear","analysis_wrong",+ "wrong_assignee","wrong_repo","wontfix_intentional","wontfix_irrelevant",diff --git a/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-reports-set-state.json b/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-reports-set-state.jsonindex 6a0eaa80a55b..6e3e685321a4 100644--- a/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-reports-set-state.json+++ b/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-reports-set-state.json@@ -13,11 +13,12 @@"type": "string"},"dismissal_reason": {- "description": "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n* `already_fixed` - Already fixed\n* `report_unclear` - Report is unclear to me\n* `analysis_wrong` - Agent's analysis is wrong\n* `wrong_repo` - Agent picked the wrong repository\n* `wontfix_intentional` - Won't fix - intentional behavior\n* `wontfix_irrelevant` - Won't fix - issue is real but insignificant\n* `fixed_outside_posthog` - Fixed outside PostHog\n* `no_action_needed` - No action needed\n* `pr_merged` - PR was merged\n* `other` - Something else…",+ "description": "Optional canonical reason code recorded with the transition. Must be one of: already_fixed, report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_intentional, wontfix_irrelevant, fixed_outside_posthog, no_action_needed, pr_merged, other — these match the inbox UI so the rationale renders as a labelled chip rather than a raw code. When the work this report asked for is done, the honest transition is state='resolved' with 'fixed_outside_posthog' (the fix landed without a pull request), 'pr_merged' (a pull request with the fix was merged but did not resolve the report on its own), or 'already_fixed' (it was fixed before the report was filed). Use 'no_action_needed' with state='resolved' when the report was useful but needs no implementation. A report that failed in processing resolves too, so a fix that landed is recorded as a fix rather than as a dismissal. These three codes claim the issue is gone, so a later signal about the same issue starts a fresh report linked to this one. Fixed reason codes require state='suppressed' or state='resolved', not 'potential'. The dismissal codes (report_unclear, analysis_wrong, wrong_assignee, wrong_repo, wontfix_*) go with state='suppressed' and absorb later signals silently. Use 'wrong_assignee' when the report was routed to the wrong person or team. 'wrong_repo' when the agent picked the wrong repository for this report, ideally with corrected_repository naming the right one. Use 'other' together with a dismissal_note for anything that doesn't fit a code.\n\n* `already_fixed` - Already fixed\n* `report_unclear` - Report is unclear to me\n* `analysis_wrong` - Agent's analysis is wrong\n* `wrong_assignee` - Wrong assignee\n* `wrong_repo` - Agent picked the wrong repository\n* `wontfix_intentional` - Won't fix - intentional behavior\n* `wontfix_irrelevant` - Not relevant to this project\n* `fixed_outside_posthog` - Fixed outside PostHog\n* `no_action_needed` - No action needed\n* `pr_merged` - PR was merged\n* `other` - Something else…","enum": ["already_fixed","report_unclear","analysis_wrong",+ "wrong_assignee","wrong_repo","wontfix_intentional","wontfix_irrelevant",