feat(pr-pipeline): restore Refine as its own stage that tidies every PR before review #9306

Activity

1. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 23, 2026
2. github-actions commented on Oct 23, 2026

   

   github-actionsBot

   on Oct 23, 2026 – with GitHub Actions

   Last edited by melodic-automation-lanes

   Contributor

   More actions

   Proposed work class: work-class: structural
   Basis: automated intake triage; the lanes App applied this class.

   Size: Large
   Complexity: High
   Uncertainty: Knowable
   Flags: none

   Decision recorded. Cost: accepted.

   Question (Q50, owner interview round 11, 2026-10-23): Accept the cost entries for #9306 (Refine restore, PR #9332), #9276, and #9215 (refine-issue funding, PR #9310)? [...]

   [quote truncated; the full decision is at the link]
   #9306 (comment)

   The decision settles the cost question. I understood the request as restoring Refine as its own dispatched stage (pr-refine.yml) that runs fix-docs on every eligible PR before review.

   The work spans the workflow, the broker allow-list in azure-iac (a separate repository and a trust boundary), skip rules and de-duplication. The canary check needs a live run. A person needs to handle the broker change and the canary.

   Cost: Refine runs key-first, then the subscription, within the accepted Q46 bounds; the owner decision is recorded above.

   _{Automated triage, applied by the lanes App.}
3. github-actions

   added

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   and removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 23, 2026
4. github-actions

   added the

   Feature

   issue type on Oct 23, 2026
5. melodic-automation-lanes

   added

   status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

   on Oct 23, 2026
6. kyle-sexton commented on Oct 23, 2026

   

   kyle-sexton

   on Oct 23, 2026

   MemberAuthor

   More actions

   Decision recorded. Cost: accepted.

   Question (Q50, owner interview round 11, 2026-10-23): Accept the cost entries for #9306 (Refine restore, PR #9332), #9276, and #9215 (refine-issue funding, PR #9310)? #9310's refine-issue entry runs only on AUTOMATIONS_CLAUDE_CODE_OAUTH_TOKEN (no bill); #9332 runs Refine key-first then subscription, within Q46 (each prepaid $200 lasts about 2-3 days a month, then the subscription carries it); Actions minutes on this public repo are free.

   Answer (owner, 2026-10-23): "Yes that all sound logical and within the bounds/instructions I've been repeating here, lets go with those"
7. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   and removed

   status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 23, 2026
8. melodic-automation-lanes

   added

   status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

   work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.Refactors, migrations, contract changes; cross-cutting and hard to reverse.

   on Oct 23, 2026
9. kyle-sexton

   added a commit that references this issue on Oct 23, 2026

   fix(ci): read cost holds from the lanes' check-run notices

   ...

   f3eb71b
10. kyle-sexton commented on Oct 23, 2026

    

    kyle-sexton

    on Oct 23, 2026

    MemberAuthor

    More actions

    The Refine canary passed, so this issue is done.

    • #9332 restored pr-refine.yml. It merged at 14:59 UTC.
    • Canary PR #9431 is a person's ready PR that adds one Markdown file with em dashes and a chatbot phrase.
    • A hand dispatch of pr-unblock-dispatch.yml on main, run 39975582718, logged dispatched fix-docs #9431 head fc76d0e7 workflow_run_id=39975673209.
    • The same run skipped feat(pr-pipeline): arm native auto-merge for lane pull requests #9399: "an earlier commit already has a pr-refine / fix-docs check run".
    • In pr-refine run 39975673209, every job passed:
      • fix-docs / broker-check passed, so the broker accepted the dispatched run.
      • fix-docs / run ran 16 turns.
      • fix-docs-handoff passed and fix-docs-subscription was skipped, as it should be.
      • apply-docs-patch / run pushed c520415e.
    • That commit is signed and verified, authored by melodic-automation-lanes[bot], and carries the trailer Lane-Activity: pr-refine/fix-docs. It removed the em dashes and the chatbot phrase.
    • docs(pr-pipeline): canary for the refine stage #9431 was closed unmerged and its branch deleted.

    Not exercised live: skipping Dependabot, release and standards-sync PRs by account id, and the pr-unblock / fix-docs already-ran path. Those rest on #9332's tests.
11. kyle-sexton

    closed this as completedon Oct 23, 2026