stale-pr: resolve code#5164 — feat(pm-stack): project spend attribution facts (#4822) #6912

Activity

1. developing-today commented on Nov 7, 2026

   

   developing-todayBot

   on Nov 7, 2026 – with developing.today

   Contributor

   More actions

   CODE-2171
2. dezren39

   added

   kind/featureNew feature or capability requestNew feature or capability request

   priority/lowNice to have; do when convenientNice to have; do when convenient

   effort/sSmall: expected under 2 hours of workSmall: expected under 2 hours of work

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   on Nov 7, 2026
3. dezren39 commented on Nov 7, 2026

   

   dezren39

   on Nov 7, 2026

   MemberAuthor

   More actions

   Intake review

   Fleet monitor intake (2026-11-07). Verified still live this run: PR #5164 is OPEN (last activity 2026-11-07T16:20Z, the warden scan touch; idle ~90h before that, no failing checks at scan).

   • Related: PR feat(pm-stack): project spend attribution facts (#4822) #5164 (the stale PR this issue owns) and its origin issue impl(pm-stack): spend attribution projection — session to issue/epic resolution, unattributed shown (#1259 slice 1) #4822.
   • Notes: This is a stale-PR warden issue: the PR has had no owner for ~3.8 days. The warden note says a resolution task naming this issue is already enqueued in repo-health-code-pilot, so no new task was created by intake.
   • Risks: merging a 3-day-idle branch without re-checking drift against current main; conversely, closing a still-valid fix and losing the work.
   • Suggested approach: the resolution task reviews the diff against current main, confirms checks, then merges if clean — or closes the PR with the reason recorded — and posts the outcome here.