Greptile Summary

Fixes duplicate ## 💚 Sponsor fnox sections in release notes by (1) adding a system_extra directive in communique.toml telling the LLM not to emit a sponsor block, and (2) making the workflow's append step idempotent with an awk filter that strips any pre-existing sponsor heading before appending the canonical block.

The awk pattern /^## .*Sponsor fnox[[:space:]]*$/ correctly matches both ## Sponsor fnox and ## 💚 Sponsor fnox, and YAML block-scalar processing strips the common indentation before the shell runs, so the regex anchors work as expected against the previously appended block. Both changes together are a solid belt-and-suspenders approach.

Confidence Score: 5/5

Safe to merge — targeted fix with correct logic and no regressions introduced.

Both changes are small, well-scoped, and correct. The awk filter handles all known sponsor heading formats, YAML indentation stripping ensures the regex anchors work against the workflow's own previously-appended block, and the communique directive provides the primary prevention layer. No functional regressions found.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant CQ as communique (LLM)
    participant GH as GitHub Release API
    participant AWK as awk filter
    participant TMP as /tmp/release-notes.md
    participant GHE as gh release edit

    Note over CQ: system_extra: do NOT add sponsor section
    CQ->>GH: generate release notes (no sponsor section)
    GH-->>GH: release body stored

    Note over GH,AWK: "Append en.dev sponsor blurb" step
    GH->>AWK: gh release view --json body --jq .body
    AWK->>AWK: strip any ## .*Sponsor fnox section
    AWK->>TMP: write cleaned body
    TMP->>TMP: cat >> canonical sponsor block
    TMP->>GHE: gh release edit --notes-file
    GHE-->>GH: exactly one sponsor section published

_{Reviews (1): Last reviewed commit: "fix(ci): de-duplicate sponsor section in..." | Re-trigger Greptile}