githubnext/chopinPublic

Let's compose rich plans together

Allow guarded CI fixes on stacked PRs #404

MergedMaggieAppletonmerged 1 commit intomainfromrefs/pull/404/head
  1. MA
    MaggieAppleton

    ## Why

    The readiness publisher rejected every proposal on a stacked PR, including a one-commit CI repair that does not rewrite the stack. This left failing CI on stacked children outside the agentic workflow.

    ## Change

    Allow a `fix` proposal on a same-repository stacked PR. Keep the existing parent and child head checks, one-commit validation, protected-path policy, exact review, and head lease. Stacked merge and rebase proposals remain gated on a trusted replay boundary.

    ## Stack and verification

    This change follows #403 in the local preparation stack. It will be restacked onto final `main` when its turn comes. The combined local #402–#404 stack passed 203 maintenance tests, `bun run ci`, `bun run types`, and `bun run build`. CI must run again on the final PR head.

    ## Publication path

    ![Diagram showing a stacked child CI failure, one repair commit, and publisher checks before a leased push](https://github.com/user-attachments/assets/2685fb42-42ae-40bb-9959-fa2dd3edb3f9)

  2. MaggieAppletonreferenced this in Scope PR readiness scans to event-related stacks #402last month on GitHub

  3. MaggieAppletonreferenced this in Clarify source paths in PR readiness hash reviews #403last month on GitHub

  4. MAAllow guarded CI fixes on stacked PRs7713865

  5. MaggieAppletonhead-ref-force-pushed 77138654579clast month on GitHub

  6. MaggieAppletonmerged e0c77056655elast month on GitHub

  7. MaggieAppletonclosedlast month on GitHub

  8. MaggieAppletonhead-ref-deletedlast month on GitHub