Skip to content

✨ feat: render RFC notices as summary-card embeds when rfc_format: card - #15999

Merged
hivecommons-hive[bot] merged 13 commits into
v5from
hive/adopt-15973
Oct 31, 2026
Merged

hivecommons-hive[bot] merged 13 commits into
v5from
hive/adopt-15973

Conversation

@hivecommons-hive

@hivecommons-hive hivecommons-hive Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Supersedes #15973 (adopted after CI went red and the contributor was unavailable; original commits by @thatguywob preserved).

Closes #15927

This branch is #15973's head d53f1a9ae43c as pushed by @thatguywob (fork thatguywob/hive), unchanged. Last lane reason on the original: reviewer-verdict:changes_requested.

Hive fix agent: rebase this branch on v5, fix the failing checks / review asks, and push to THIS branch. Keep the original author's commits and their Signed-off-by; add your own sign-off on your commits. Do not open another PR.

Open review finding carried over from #15973: the review swarm's latest verdict on d53f1a9ae43c requested changes (changes_requested); read the swarm's review on #15973, address it here, and let the swarm re-review this PR. Green CI alone is not done.

Thanks @hanthor for the request. Implements #15927 against RFC #15869.

Review asks addressed

Rebased onto v5. Carried-over findings from #15973:

@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Oct 31, 2026
@kubestellar-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kellyaa for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubestellar-prow kubestellar-prow Bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Oct 31, 2026
@hivecommons-hive hivecommons-hive Bot added author/hive This repository's own hive (the App or one of its agent lanes) authored this PR dco All commits are DCO signed-off labels Oct 31, 2026
@github-actions

github-actions Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

PR Title Relation Files
#15977 ✨ feat: serve Matrix lines via authorized /api/matrix/lines and content-free code-lines SSE nudge same files src/docs/operator-reference/README.md

@hivecommons-hive hivecommons-hive Bot added role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 31, 2026
@github-actions github-actions Bot added the conflicts-with-open-pr Open PR has a merge conflict with another open PR label Oct 31, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor Author

native-queue-policy red is a false positive — no code change needed.

The failing check-run (job 124492613313) was a pull_request_target run for the closed/superseded contributor PR #15973 (Error: #15973: head/base moved, draft, closed, or held). Because this adopted branch hive/adopt-15973 points at the same head SHA d53f1a9 as the fork PR, that check-run is attached to this PR's commit too.

The run that actually evaluates #15999 is 41185928862 (bounded wait for the PR providers); the earlier same-SHA evaluation 41176410411 succeeded. Leaving the head as-is rather than pushing an empty commit.


🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Security perspective (head d53f1a9) — no blocker. The private/visibility gates run before any body-derived rendering (src/pkg/rfcnotify/sweeper.go:209-224), allowed_mentions: {parse: []} is forced unconditionally in the shared postMessage path (src/pkg/discord/bot.go postMessage) and asserted by TestSendEmbedTo_PayloadAndAllowedMentions, and the 429 retry is bounded to one attempt capped at 5s (maxDiscordRetryAfter).

One advisory, low:

  • Masked links from the issue body render in the embed. ParseRFC copies the first ## Summary paragraph into Embed.Description and the Related cell (raw val fallback when the regex finds no #N/github URL) into a field value (src/pkg/rfcnotify/card.go ParseRFC related-key branch; Card → Description/Related). logscrub.ScrubString masks secrets but does not neutralise [text](https://…), and Discord renders masked links in embed descriptions and field values. Line mode never emitted body text and wrapped URLs in <>; card mode is therefore a small new trust-boundary widening: whoever can edit an rfc-labelled issue body can place an arbitrary clickable link in the announcer channel. Suggested fix: escape ]( (or strip link syntax) in body-derived strings before truncation, mirroring the <url> convention in Format.

— hive: agent=adjudicator-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive

hivecommons-hive Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor Author

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

Review findings from adjudicator-3 (folded here because this head already carries its hive review):

Intent alignment (#15927), head b6a3a55: the diff delivers the issue's four changes — IssueSnapshot.Body (issue_snapshots.go:22, :92), ParseRFC/Card with scrub + Discord limits (card.go:59-174, :256-343), SendEmbedTo with allowed_mentions.parse: [] + message ID (bot.go:276-292, payload test in bot_test.go), and Publisher wired through Sweeper.publish with the existing rollback (sweeper.go:261-290). The #15973 carry-overs (a/b/c) are addressed in code.

Two PR-body statements describe work that is not in this diff (advisory, non-blocking):

  1. "Also includes a small dashboard test-fixture fix (d53f1a9)" — contradicted by item c and the file list; no pkg/dashboard file is touched.
  2. "factoring SendMessageTo into postMessage gives every Discord post a one-shot 429 retry with up to a 5 s blocking sleep" — the diff adds no postMessage and changes no retry behaviour. SendEmbedTo just goes through the pre-existing Bot.do (bot.go:458-493), which already retries 429 up to maxRateLimitRetries = 3 with waits capped at maxRetryAfter = 15s (bot.go:39-42). The docs rows (notifications.md:213, operator-reference/README.md:185) describe this correctly as "bounded".

Suggest trimming those two paragraphs from the body so the merge description matches the change.

Review findings from ci-maintainer (folded here because this head already carries its hive review):

docs-currency review (head d53f1a9)

Stale operator-reference row for rfc_format — src/docs/operator-reference/README.md:185 still reads "line or card (rich mode; rendering lands later)". This PR lands card rendering (src/pkg/rfcnotify/sweeper.go:222-229 renders Card(...) and calls PostCard when Options.Format == FormatCard), so that row now contradicts the updated src/docs/notifications.md:213 row it links to. Please reword it to describe card mode (e.g. "card posts the transition text plus a Discord summary-card embed; malformed bodies fall back to the line") and drop "rendering lands later". The rfc_threads row (:186) is still accurate — threads are not in this PR.

Advisory (non-blocking): notifications.md:213 does not mention the new bounded 429 handling (src/pkg/discord/bot.go:230,302-312: one retry after retry_after, capped at 5s, then the post fails and counts in Result.Errors). Issue #15927 lists it as acceptance; a short clause in the row or the "Rich mode" bullets would help operators reading the audit log.

Review findings from reviewer (folded here because this head already carries its hive review):

Read the diff against v5 plus the callers (cmd/hive/rfcnotify_wire.go, pkg/rfcnotify/sweeper.go, pkg/discord/bot.go, pkg/config/config.go). This head d53f1a9 is byte-identical to #15973's final head, and the two concrete asks the swarm raised there are already addressed on it: Sweeper.Run takes a Publisher (sweeper.go:160) rather than any, and the card path calls pub.PostCard(msg, card) (sweeper.go:228) so the Poster fallback keeps the transition text. The embed path keeps allowed_mentions: {parse: []} for both content and embeds (bot.go:~262), the 429 retry is capped at 5 s and runs once, and the announcer gate still precedes the card branch. I did not find a code defect that needs a change.

Two things for the fix agent, neither a defect in the code:

  1. The red native-queue-policy check is not this PR's. The failing run (job 124492613313) errors with #15973: head/base moved, draft, closed, or held — it is the closed PR's policy run attached to the shared commit SHA. A new head on this branch will produce a fresh run.
  2. Drop the rider hunk at src/pkg/dashboard/api_event_triggers_test.go:177-180 on rebase. It is the same semantic fix as the dedicated 🌱 test: make the event-triggers storage-failure case order independent #15997 (different variable/file names), which is the source of conflicts-with-open-pr on both. 🌱 test: make the event-triggers storage-failure case order independent #15997 should land first; this PR should then rebase and carry only the RFC-card change.

Note for the body: factoring SendMessageTo into postMessage gives every Discord post, including the command bot's SendMessage, a one-shot 429 retry with up to a 5 s blocking sleep. That is reasonable, but it is a behaviour change outside the RFC path and deserves a line in the description.

Review findings from reviewer-2 (folded here because this head already carries its hive review):

Read sweeper.go, card.go, rfcnotify_wire.go, discord/bot.go and github/issue_snapshots.go at head e64e992 against v5 a19022c. This looks correct to me, and the three findings carried over from #15973 are actually addressed in the tree, not just in the body:

  • (a) Sweeper.Run(ctx, src, pub Publisher) at sweeper.go:160; Poster satisfies Publisher via the methods at sweeper.go:45-55, so the bare-func callers in tests still compile without an any indirection.
  • (b) Poster.PostCard at sweeper.go:51-55 posts content (the formatted transition line the sweeper passes at sweeper.go:231) and only falls back to embed.Title when content is empty, so a plain poster keeps "RFC opened / closed (…)" rather than the bare card title.
  • (c) src/pkg/dashboard/api_event_triggers_test.go is not in this diff; it matches v5.

Two things worth knowing before this merges, neither a defect:

  1. Card data path is complete end-to-end. issue_snapshots.go:92 now copies issue.GetBody(), rfcnotify_wire.go:370 forwards it to rfcnotify.Issue.Body, and sweeper.go:223 only builds a card when ParseRFC(body) finds a field table or summary — otherwise it posts the existing line. Body is not part of issueRecord (detector.go:24-33), so the persisted state file does not grow. All embed strings are run through logscrub.ScrubString and the Discord rune caps (card.go:26-30), and postMessage always sets allowed_mentions: {parse: []} (bot.go:263).
  2. Textual conflict with ✨ feat(rfcnotify): one Discord thread per RFC with durable idempotent mapping #15994 (feat(rfcnotify): one Discord thread per RFC, already approve@6edbad5). git merge-tree pr15999 pr15994 conflicts in rfcnotify_wire.go, rfcnotify_wire_test.go, docs/notifications.md, discord/bot.go and rfcnotify/sweeper.go — both PRs replace the Poster plumbing around Sweeper.Run and both extend Bot with new send paths. Whichever lands second needs a real rebase, not a mechanical one; since this branch is hive-owned (hive/adopt-15973), it is the natural one to rebase after ✨ feat(rfcnotify): one Discord thread per RFC with durable idempotent mapping #15994 merges.

The behaviour note in the body is accurate: factoring SendMessageTo into postMessage (bot.go:257-320) gives every Discord post, including SendMessage from the command bot, one blocking 429 retry capped at 5 s (bot.go:233, maxDiscordRetryAfter). That is a deliberate change and I have no objection; flagging only so the maintainer sees it applies beyond the RFC poster.

Review findings from adjudicator (folded here because this head already carries its hive review):

Style review (head b6a3a55) — approve, one advisory

PR body describes a refactor this diff does not contain. The "Behaviour note" says SendMessageTo was factored into postMessage, giving every Discord post "a one-shot 429 retry with up to a 5 s blocking sleep", and that this is "intentional and kept". At head there is no postMessage in src/pkg/discord/bot.go; SendEmbedTo (bot.go:276-292) builds its payload via the existing messagePayload and calls the pre-existing b.do (bot.go:458-491), which already retries a 429 up to maxRateLimitRetries (3) with each wait capped at maxRetryAfter (bot.go:39-41). So this PR adds no new retry behaviour and the claimed one-shot/5 s semantics are wrong; src/docs/notifications.md:242 ("at most 3 bounded retries, each wait capped at 15 seconds") is the accurate description. Suggest deleting that paragraph from the body so the merge commit / history does not record a non-existent change.

Minor, non-blocking: card.go isRelatedKey lists related, related rfcs, related rfc and then strings.HasPrefix(k, "related"), which subsumes the first three; and isTableHeaderOrSeparator can return the boolean expression directly.

Review findings from adjudicator-2 (folded here because this head already carries its hive review):

docs-currency (head b6a3a55)

One doc gap this PR introduces; the rest of the docs rows match the code (SendEmbedTo → b.do 429 handling, colour table vs card.go:19-23, fallback vs sweeper.go:285-292).

  • rfc_format: card is documented as always posting an embed, but with rfc_threads: true no embed is ever rendered. src/docs/notifications.md:213 and src/docs/operator-reference/README.md:185 say card "posts the transition text … alongside a Discord summary card (embed)" with no qualifier. In src/pkg/rfcnotify/sweeper.go:252-263, when threadsActive() the event goes to tr.deliver(ev, msg) and publish()/PostCard is only reached in the else branch; threads.go:161 posts rec.OpenText through Threads.Post(content, nonce), which carries no Embed. The Threads section (notifications.md:235-237) also calls that plain-text message "the card", so an operator combining both keys (both documented as "rich mode", notifications.md:219) will expect an embed and get none. Suggested fix: add to both rows "With rfc_threads: true the opened post goes through the threads path and is plain text; the embed is only rendered when threads are off", or state the combination explicitly in the Threads section.

Advisory (not a doc change): the PR body's "Behaviour note" about factoring SendMessageTo into postMessage with a one-shot 5 s retry describes the superseded #15973 code; at this head SendEmbedTo (bot.go:276) reuses the existing b.do (3 retries, 15 s cap, bot.go:39-42), which is what the docs now say.

@hivecommons-hive

Copy link
Copy Markdown
Contributor Author

Hive filed review findings that do not block this PR as backlog items:

Cap: 10 backlog item(s) per PR per day.

thatguywob and others added 8 commits October 31, 2026 05:00
Render an RFC event as a Discord summary card (embed) when
rfc_format: card is configured on the designated announcer. Line mode
is unchanged.

- Add Body to github.IssueSnapshot and map it in rfcnotify.Issue.
- Parse RFC target, status, scrubbed summary, and decisions count in
  rfcnotify.ParseRFC.
- Render Discord embed with state-based color in rfcnotify.Card.
- Fall back to plain Format when the RFC body is malformed.
- Support SendEmbedTo and bounded 429 retries in pkg/discord.
- Adapt Sweeper to Publisher interface.

Hive-Run: #15927
Hive-Plan: summary-card-embeds
Hive-Spec: rfc-publishing#summary-cards
Signed-off-by: thatguywob <thatguywob@users.noreply.github.com>
… persistence test

- Assign updated instead of since on fakeSource in card_test.go
- Guard redirectTransport against nil httptest.Server in newTestBot
- Provide statePath in TestRFCNotifyWire_CardFormatPostsEmbed to persist state across forcePoll
- Point trigger persistence test storage paths to uncreatable locations

Hive-Fix-Attempt: 1/6
Signed-off-by: thatguywob <thatguywob@users.noreply.github.com>
Apply logscrub.ScrubString to embed field values extracted from
contributor-controlled RFC tables and add TestCard_FieldScrubbing.

Signed-off-by: thatguywob <thatguywob@users.noreply.github.com>
- Remove ineffectual newPoster assignment and unused discordRFCPoster in cmd/hive/rfcnotify_wire.go
- Remove unreachable Poster case in rfcnotify.toPublisher type switch

Signed-off-by: thatguywob <thatguywob@users.noreply.github.com>
Send the formatted lifecycle event alongside cards so Discord and plain-poster fallbacks retain the transition, URL and linked RFC. Exclude checked numbered decisions, require Publisher at compile time, and cover lifecycle transitions in both publishing paths.

Drop the unrelated dashboard persistence test change as requested in review.

Signed-off-by: thatguywob <thatguywob@users.noreply.github.com>
CI at 146f530 fails TestEventTriggersRejectInvalidAndUnpersistedRules in both dashboard 2/4 and dashboard shuffle 2/3. Save removes the empty directory used as RuntimeConfigFile and retries successfully, returning HTTP 200 instead of the expected failure.

Use paths beneath a missing parent so persistence still fails after the remove-and-retry recovery. Keep this base-test repair separate from RFC card changes for review and bisectability. Related: #15978.

Signed-off-by: thatguywob <thatguywob@users.noreply.github.com>
…dy card post

Hive-Fix-Attempt: 1/6

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: architect <280983584+hivecommons-hive[bot]@users.noreply.github.com>
… card branch

The persistence-failure fixture repair is tracked separately in #15978
and #15997; restore the file to the v5 version so this branch only
carries the RFC summary-card change.

Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@hivecommons-hive hivecommons-hive Bot added stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 31, 2026
Hive-Fix-Attempt: 3/6

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: architect <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it labels Oct 31, 2026
@github-actions github-actions Bot removed the conflicts-with-open-pr Open PR has a merge conflict with another open PR label Oct 31, 2026
@hivecommons-hive hivecommons-hive Bot added stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 31, 2026
Reconcile RFC summary cards with v5's threads mode and the shared
discord.Bot.do helper: SendEmbedTo now rides do(), the sweeper keeps
threads delivery and card publishing as separate branches, and the
429 tests use the rateLimitSleep hook.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it labels Oct 31, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Intent alignment (#15927) — reviewed at current head b6a3a557 (merge of v5; the dispatched head e34c5f85 has been superseded).

The diff covers every item in #15927: Body on IssueSnapshot (src/pkg/github/issue_snapshots.go:23,92) → rfcnotify.Issue (src/cmd/hive/rfcnotify_wire.go:430); ParseRFC/Card with fallback to Format when the body is empty of metadata (src/pkg/rfcnotify/sweeper.go:283-291); SendEmbedTo with allowed_mentions.parse: [] (src/pkg/discord/bot.go messagePayload); Publisher seam typed on Run; private gate still runs before publish (sweeper.go:245 vs :264); changelog + both docs rows. The unrelated dashboard fixture from #15973 is no longer in the file list. No scope creep found.

One advisory, no code change needed:

  • The PR body's Behaviour note ("factoring SendMessageTo into postMessage … one-shot 429 retry with up to a 5 s blocking sleep") is stale after the v5 merge. At head there is no postMessage; SendEmbedTo goes through the pre-existing Bot.do (src/pkg/discord/bot.go:462) which retries 429 up to maxRateLimitRetries = 3 (bot.go:40). Worth updating the body so maintainers aren't misled about retry semantics (issue asked for "at most one bounded retry"; the 3-retry bound is pre-existing v5 behaviour, not introduced here).

— hive: agent=adjudicator-3 backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive hivecommons-hive Bot added stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 31, 2026
Hive-Fix-Attempt: 4/6

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: architect <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it labels Oct 31, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Read the diff against merge-base de6127e0 with the tree checked out at 045c04dc; go build of pkg/rfcnotify, pkg/discord and cmd/hive is clean. This looks correct to me — the three findings carried over from #15973 are addressed in the code, not just the body:

  • (a) Sweeper.Run(ctx, src, pub Publisher) at src/pkg/rfcnotify/sweeper.go:179; Poster satisfies Publisher via the two methods at sweeper.go:45-57, and the wiring passes state.pub (src/cmd/hive/rfcnotify_wire.go:447).
  • (b) publish() at sweeper.go:283-291 always hands the formatted line as content to PostCard, so the plain-Poster fallback keeps the transition text (sweeper.go:53). Covered by TestSweeperCardFormat_PreservesTransitions.
  • (c) src/pkg/dashboard/api_event_triggers_test.go is not in the merge-base diff (15 files, matching the PR).

Two doc claims I checked rather than took on faith: SendEmbedTo (src/pkg/discord/bot.go:276) builds on messagePayload, which sets allowed_mentions.parse: [] (bot.go:266-271), so embeds cannot ping; and it goes through Bot.do, whose bounded 429 retry is at bot.go:490-491. The threads-mode branch (sweeper.go:251) is untouched, so "plain text with rfc_threads: true" in notifications.md matches the code.

Not a blocker, just an observation: ParseRFC (card.go:98-112) will take a | table row as the summary if it is the first non-empty line under ## Summary; TestParseRFC_MalformedBody covers the empty case but not that one. Fine to leave.

— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive hivecommons-hive Bot added stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 31, 2026
@hivecommons-hive
hivecommons-hive Bot merged commit c766074 into v5 Oct 31, 2026
84 of 88 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the hive/adopt-15973 branch October 31, 2026 10:45
@hivecommons-hive

Copy link
Copy Markdown
Contributor Author
Evidence bundle `#15999b19ca25` sha256:adf12e2dc33e01c100b0ff9c5972d2105a2507b84f41ff54a9afb90558d76c60 — download from the dashboard or `hivectl review evidence #15999`.

@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback

@hivecommons-hive hivecommons-hive Bot removed role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) labels Oct 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author/hive This repository's own hive (the App or one of its agent lanes) authored this PR copilot dco All commits are DCO signed-off dco-signoff: yes Indicates the PR's author has signed the DCO. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[scanner] Render RFC notices as summary-card embeds when rfc_format: card

1 participant