feat(my-pr-monitor): redirect Phase 1 — disabled discovery task#406
Closed
johnjansen wants to merge 1 commit into
Closed
feat(my-pr-monitor): redirect Phase 1 — disabled discovery task#406johnjansen wants to merge 1 commit into
johnjansen wants to merge 1 commit into
Conversation
… Phase 1)
Lands `.anvil/todos/p2/my-pr-monitor-discover.md` per the redirect plan
(`dw/ideas/2026-05-29-my-pr-monitor-redirect.md` §9.4). The new task
coexists with the existing `my-pr-monitor.md` until plan step 9.6
validates ≥ 5 cycles with no recall keyspace conflict; the existing task
is not edited.
The new task is **discover + diff + notify**, full stop:
- reads `gh search prs author:@me` + `gh pr view` + GraphQL review
threads (read-only on the repo)
- diffs against recall and emits four event kinds keyed by
`<kind>:<head_sha>:<discriminator>`: `new_review_comment`,
`ci_failure`, `merge_conflict`, `ready_to_merge`
- resolves the originating workspace via cached
`origin_workspace_ref`, falling back to branch-prefix lookup against
`cmux list --json`, then to a `parking:pr-triage` synthetic ref
- delivers events through three layered channels: recall (truth),
`cmux color/progress/status` paint of the target workspace
(visible projection), and `terminal-notifier` for `ready_to_merge`
only (gated by the existing `notifications/ready-to-merge` key for
cross-task idempotency)
- re-paints stale `delivered` events idempotently but never re-fires
`terminal-notifier`
- supersedes events / comments / checks on `head_sha` rollover
Hard rules preserved from the sibling task and sharpened for the
redirect: no `git`, no worktrees, no `yarn`, no PR comments, no review
replies, no `gh pr ready`, no `update-branch`, no `requested_reviewers`,
no force-push, no API merge. PrimerAI org filter retained. Anvil never
escalates — the cmux pill staying Rose and the Phase 4 stdout report are
the escalation surface.
Ships `disabled: true` so it never runs until plan step 9.6 explicitly
enables it. Recall keyspace `events` is disjoint from the existing
task's `comments` / `checks` / `notifications` writes, so the two tasks
can run side-by-side during the validation window without collision.
Refs: dw/ideas/2026-05-29-my-pr-monitor-redirect.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lands Phase 1 of the my-pr-monitor redirect (
dw/ideas/2026-05-29-my-pr-monitor-redirect.md§9.4): a new discover + diff + notify task that ships disabled alongside the existingmy-pr-monitor.md. The existing task is not edited.When eventually enabled (plan step 9.6, behind a separate brief that ships the workspace-side responder), this task replaces JJ-Monitor's triage loop with a routing model — anvil sees, the originating workspace acts.
.anvil/todos/p2/my-pr-monitor-discover.md,disabled: true, schedule*/15ready for activationBash(git:*),Edit,Write; plusBash(cmux:*)eventscollection (pending/delivered/acked/superseded), keyed<kind>:<head_sha>:<discriminator>; disjoint from the existing task'scomments/checks/notificationswrites so the two coexist without collision during the validation windownew_review_comment,ci_failure,merge_conflict,ready_to_mergeorigin_workspace_ref→ branch-prefix lookup againstcmux list --json→parking:pr-triagesynthetic refcolor/progress/status, idempotent re-paint on staledelivered) +terminal-notifierforready_to_mergeonly (gated by the existingnotifications/ready-to-mergekey)head_sharollover supersedesevents/comments/checkscleanlyHard rules preserved + sharpened
git, no worktrees, noyarn, no typecheck (workspace concerns now)gh pr ready, noupdate-branch, norequested_reviewers, no force-push, no API merge — this task is silent on GitHubterminal-notifieronly forready_to_merge; never re-fired for the samehead_shaOut of scope (separate briefs)
gh pr createorigin_workspace_reffor currently-open PRsschedule: ''on the existing task)Test plan
.anvil/todos/p2/my-pr-monitor-discover.mddisabled: truegit check-ignorereports the new file as not ignored; runtime state under.anvil/runs/,.anvil/git-state/, etc. remains ignored.anvil/todos/p2/my-pr-monitor.mdunchanged (zero diff)