Skip to content

feat(dashboard): animated, actionable goal-board with PR links via a host open bridge - #18557

Merged
iamwhatever merged 1 commit into
mainfrom
feat/goal-board-motion
Oct 10, 2026
Merged

iamwhatever merged 1 commit into
mainfrom
feat/goal-board-motion

Conversation

@iamwhatever

@iamwhatever iamwhatever commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: The conductor's goal board in the Dashboard tab moves like the old drawer board did, and a person can act on it: answer a task that needs them, and open a task's pull request.

The old right-panel board (agent_panel_templates/kirocrew-conductor.html, #17800) had motion: state pills, pop-in cards, a live shimmer, a done meter and a warm Needs-you band. The new Dashboard tab renders the built-in goal-board template, which has none of that. Its Needs-you items cannot be answered from the page. Neither board can open a task's PR, because both frames are sandbox="allow-scripts" with no allow-popups, so a link is a dead click.

Why it matters

The goal board is what a person watches while a conductor runs. A static list hides what is moving and what waits on them. Without a reply button or a PR link, the reader has to retype the task name into chat and hunt for the PR by hand.

Not a goal

  • No change to either frame's sandbox or CSP. allow-popups stays withheld.
  • No new fold field. The board reads the same work fold paths as before.
  • No change to other built-in templates. This is chenmingwei23's area; the template change is limited to goal-board.
  • The page never sends a message on the person's behalf. It only fills the composer.

What changed (motivation → approach → change)

Motion: goal-board/template.html ports the old drawer's vocabulary using the theme variables the frame already injects. It adds tone-coloured state pills, cards that pop in on first draw only (a host refill does not replay them), and a shimmer plus a blinking dot on open items whose worker last reported progress (keyed on status, because the host masks worker_session_key before any field reaches a page). It also adds a done-of-total line with in-progress and needs-you counts, and a warm band listing open items whose worker reported question or blocked; the band glows three times when drawn, not forever. With nothing waiting, a calm line says "Nothing needs you right now." One prefers-reduced-motion block stops every animation and transition, pseudo-elements included.

Acting on Needs-you: each row in the band gets a ✎ Write a reply button that puts About "<title>" (<id>): in the chat box. When the conductor writes the new optional agentic field asks ({item_id: {options: [string]}}), the row also gets one button per option. Every button posts the existing kirocrew-dashboard:act (as office and project-report do): the host only fills the composer. A row with no asks entry still gets Reply. Option buttons carry the same ✎ mark. Worker status words are translated. An approval-blocked row says to approve on the chat card, not by replying, and the state bar gives needs-you items their own warm segment instead of counting them as open. The band says the buttons only fill the chat box, and each row shows the worker's own reported summary under the task it names. src/kiro_crew/builtin_skills/goal-conductor/SKILL.md tells the conductor how to write asks with dashboard_write.

PR links. Security change: one new frame→host message, kirocrew-dashboard:open {url}, behind a strict allowlist. The new useFrameOpenLink hook (website/src/hooks/useFrameOpenLink.ts) runs in both hosts: website/src/pages/members/CrewDynamicDashboard.tsx (Dashboard tab) and website/src/pages/members/CrewWebview.tsx (the docked frame, the expanded frame, and CrewDashboardFrame). It honours a message only when event.source is one of that host's own frames' contentWindow. The URL must match exactly ^https://github\.com/[A-Za-z0-9_.-]+/[A-Za-z0-9_.-]+/pull/[0-9]+/?$, so no other host, no query and no fragment get through. It also needs a live user gesture in that very frame: the host has a user activation (navigator.userActivation.isActive) and its focused element is that iframe. Activation alone is page-wide, so focus ties the gesture to the frame. Anything else is dropped silently. Both sandbox docstrings now name this one exception. It opens with window.open(url, '_blank', 'noopener,noreferrer'). A linked chip reads PR n on GitHub ↗ (the panel: PR #n on GitHub ↗); a PR with no known repo is a plain grey chip. docs/architecture/dashboard-iframe-hosts.md lists both crew hosts and their two messages out. On the goal board, the PR chip becomes a <button> when the item's acceptance.repo gives a valid URL. On the right-panel board, "PR #n" becomes a <button> when the data carries the new optional top-level repo, which is added to ConductorBoardPanel in src/kiro_crew/conductor_board_contract.py and to the board line in src/kiro_crew/builtin_skills/goal-conductor/SKILL.md. src/kiro_crew/dashboard_templates/builtin/README.md now says goal-board declares asks. With no repo or no PR number, both stay plain text.

Backwards compatibility

Compatible: every new field is optional (asks on the goal-board manifest, repo on ConductorBoardPanel). A board without them renders as before, and both sandboxes are unchanged.

Removes nothing: the templates only add elements, and the hosts only add a listener.

Tests

  • test/test_dashboard_template_goal-board.py (new) pins:
    • the reduced-motion block covers .board *, ::before and ::after, and stops animations and transitions;
    • every animation names a keyframes the page defines;
    • the page posts only kirocrew-dashboard:act and kirocrew-dashboard:open, never a send;
    • a row without an asks entry still gets Reply;
    • a PR chip posts open with the host's allowlist and never uses window.open, href or target;
    • the PR URL is built from the item's own acceptance.repo, with a text fallback.
  • test/test_conductor_board_contract_parity.py: the panel posts open with the same allowlist, builds the URL from repo, and falls back to text. The existing parity test also covers the new repo leaf.
  • website/src/hooks/useFrameOpenLink.test.ts (new): the hook rejects a non-GitHub host and a look-alike host. It rejects non-pull GitHub URLs (repo root, issue, /files, query, fragment, http:, javascript:). It rejects a message from another frame, from the window itself and with a null source, and it ignores the act type. A valid PR URL calls the opener exactly once, and the default opener is window.open(url, '_blank', 'noopener,noreferrer'). A message with no user gesture opens nothing; by default an activation with the composer focused opens nothing, and an activation with the frame focused opens once. The goal-board test pins that live never reads a masked key and that only the shimmer and the dot loop forever.
  • Ran locally: the pytest files above plus test_dashboard_templates_builtin.py and test_dashboard_template_manifest.py (103 passed). Vitest ran useFrameOpenLink, CrewDynamicDashboard, CrewDashboardFrame, CrewDashboardTab, the three CrewWebview* tests, crewDashboardAct and dashboardTemplatesI18n (all pass). tsc, eslint on the touched files, i18n:check, and black, isort and flake8 are clean.

Manual verification

I rendered both templates with scripts/render_dashboard_builtin.py's build_page and a fixture of five items (accepted, live, question with options, blocked without options, rejected without a repo), then drove them in Chromium:

  • Under reducedMotion: 'reduce', the computed animationName is none on every element and pseudo-element.
  • At 320px, scrollWidth is 320 in both themes and no element overflows.
  • Tab reaches the Reply button and shows the focus ring. Enter posts {type: 'kirocrew-dashboard:act', text: 'About "K: crew list density" (it_c): '}, and an option posts the same text plus Ship option B.
  • The goal-board PR chip posts {type: 'kirocrew-dashboard:open', url: 'https://github.com/kirodotdev/KiroCrew/pull/17797'}. The rejected item, whose acceptance has no repo, renders a plain SPAN:PR 18402.
  • The panel with repo posts the same open message. The panel without repo renders 0 PR buttons.

Not checked: the Electron app actually handing window.open to the system browser. That path is the existing one other links use and is unchanged here.

Screenshots / video

Goal board after, dark and light, 760px:

goal-board after dark 760
goal-board after light 760

Needs-you band with keyboard focus on Reply. It says the buttons only fill the chat box and shows each worker's report. K has options, M has none and still gets Reply:

needs-you focus dark
needs-you focus light

Before (main), 320px after, motion frames, reduced motion, right panel

Before, dark and light:

goal-board before dark 760
goal-board before light 760
goal-board before dark 320
goal-board before light 320

After at 320px:

goal-board after dark 320
goal-board after light 320

Motion: a pop-in frame at 140ms, and the live card's shimmer at two instants 500ms apart:

pop-in 140ms
shimmer a
shimmer b

Reduced motion (settled, with no animation running):

reduced motion

Right-panel board with repo (PR chips are buttons) and without (plain text):

panel repo dark
panel repo light
panel no repo dark
panel no repo light

Related Issues

Follows #17800 (the drawer board's motion) and #17507 / #16603 (the Dashboard tab templates). @chenmingwei23, please review: the template change is limited to goal-board, plus the new host open bridge.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (builtin README, conductor board contract, goal-conductor skill line)
  • No secrets, credentials, or internal references in the diff

@iamwhatever
iamwhatever requested review from a team and KiroCrewCaptain as code owners October 9, 2026 18:46
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 9, 2026
@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 3b41e76cef4bf12ede459f62c214811f708156fc — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check before merge: any page a crew publishes can now get a GitHub PR opened by the host when the person clicks inside its frame, not only the conductor templates.

[DESIGN-REVIEWED] 3b41e76

Description read

[DESCRIPTION-READ] d03b21e0f78478438046498480b41c4d7cd778ed1b9ef3debf0ed426ab38a2d3

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — 🟡 CONCERNS

Premise-level review of 3b41e76cef4bf12ede459f62c214811f708156fc — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: CONCERNS

The pop-in, bar-grow and band-glow animations rest only on matching the old drawer, and the template's own comment calls them decoration.

Not justified as shipped

  • Item 1 — inherited: the only support is symmetry ("moves like the old drawer board did"), and the diff's own comment says "Every animation above is decoration: with motion off the page reads the same."
    Subtraction: delete gb-pop, gb-grow and gb-glow, along with the .pop/.grow classes and the seen/data-drawn replay guards that exist only for them. Keep the live shimmer and dot.
    Clears when: someone names a reader who misread the board without these motions, or the three animations are deleted.
  • Item 9 — oversized: the Goal is the "goal board in the Dashboard tab", and ## Not a goal says "No change to other built-in templates". Yet the PR edits agent_panel_templates/kirocrew-conductor.html and adds ConductorBoardPanel.repo.
    Subtraction: revert the kirocrew-conductor.html PR button, the repo field, the CrewWebview.tsx hook wiring and the SKILL.md repo? text.
    Clears when: the mechanism is removed, or a human amends the Goal.

What this change ships

Inventory (10 items) — 8 justified

Intent: let a person watching a conductor see what is moving, answer tasks that wait on them, and open a task's PR. ADDITION.

  1. Goal-board cards pop in, the state bar grows and the needs-you band glows — inherited
  2. Items still in progress show a shimmer and a blinking dot — justified
  3. A done-of-total line with in-progress and needs-you counts — justified
  4. A needs-you band whose Reply button fills the composer — justified
  5. Conductor-offered option buttons through the new agentic asks field, plus SKILL guidance — justified
  6. Needs-you items get their own segment in the state bar — justified
  7. Worker status words are translated — justified
  8. The goal-board PR chip opens GitHub through the new host open bridge — justified
  9. The right-panel conductor board's PR becomes a button through the new repo field — oversized, outside the Goal
  10. Approval-blocked rows say to approve on the chat card — justified

[FIRST-PRINCIPLES-REVIEWED] 3b41e76

Description read

[DESCRIPTION-READ] a460f943c40e6e514b1ffff61ea167f123801814139180e617470568823c7905

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — 🟡 CONCERNS

UX-level review of 3b41e76cef4bf12ede459f62c214811f708156fc — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: CONCERNS

The approval-blocked row offers "✎ Write a reply" right under copy saying a reply won't help, and the card pill says "open" while the bar says "needs you".

Watch

  • Reply on an approval-blocked row contradicts its own hint. Every needs-you row gets Reply, including why === 'approval', where the next line reads "Approve the tool on its approval card in chat. Writing a reply does not approve it." The blind reader (shot-01) said: "I wouldn't click 'Write a reply' here… Then why is the button there? I have never seen an 'approval card'." This hits every approval stall: the user sees a dead-end button and gets no way to reach the card. Severity: medium, because it is frequent for conductor runs and the user stalls on the one item that needs them. Fix: for approval rows, drop Reply or replace it with a control that jumps to the approval card.
  • Two states for one item. The bar counts needs-you items separately ("needs you 2 / open 1"), but chip(stateLabel(state), …) still stamps "open" on cards K and M. The reader said: "the colour key says open 1 and needs you 2, and the list below has 3 cards marked 'open'." The progress summary can't be squared with the cards on every view. Severity: medium (persistent confusion, not task failure). Fix: render the card pill as "needs you", in the same warm tone, whenever needsYou(it) is true.
  • Unlinked PR chip. A plain "PR 18402" chip sits beside linked "PR n on GitHub ↗" chips with nothing to explain the difference ("I can't tell why this one isn't a link"). Severity: low. Fix: set a title such as "No repository recorded, so this PR can't be opened" on the plain chip.

Suggestions

  • option buttons show only clip(o, 40). Tell the conductor in SKILL.md that each option must name its choice ("Ship the compact layout", not "Ship option B"), because shot-11 shows the bare "option B" form confusing the reader.

[UX-REVIEWED] 3b41e76

Description read

[DESCRIPTION-READ] 60ca3e38aba528d3414b10dcb6433fefe563487dd4e26bcb7862dbb7b9326e16

That sha256 names everything this verdict read: the PR description, plus the 21 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 3b41e76cef4bf12ede459f62c214811f708156fc and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 3b41e76

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 3b41e76cef4bf12ede459f62c214811f708156fc: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 3b41e76cef4bf12ede459f62c214811f708156fc — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 3b41e76

Verdict parsed from the review's SHA-scoped output markers for commit 3b41e76cef4bf12ede459f62c214811f708156fc.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 3b41e76cef4bf12ede459f62c214811f708156fc: <one-sentence reason>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 9, 2026
@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Oct 9, 2026
@iamwhatever
iamwhatever force-pushed the feat/goal-board-motion branch from 9b789be to 03a53d9 Compare October 10, 2026 00:03
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: action required A blocking check or review needs attention labels Oct 10, 2026
@iamwhatever
iamwhatever force-pushed the feat/goal-board-motion branch from 03a53d9 to 6315f98 Compare October 10, 2026 00:44
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 10, 2026
@iamwhatever
iamwhatever force-pushed the feat/goal-board-motion branch from 6315f98 to 75cda6d Compare October 10, 2026 01:23
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 10, 2026
@iamwhatever
iamwhatever force-pushed the feat/goal-board-motion branch from 75cda6d to c2e71c0 Compare October 10, 2026 02:01
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 10, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Offered answers (asks) are the user's own ask, not inherited scope span=4fec5ffe22e3

Rebutted. The user asked for this in the dispatch for this item: per Needs-you row, one Reply button plus option buttons when the conductor supplies them, through ONE optional agentic field. The Goal section is frozen and I will not amend it on my own. The field is optional: a page with no asks write renders and works, which is why Reply exists on every row.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • A PR chip with no repo is plain text on purpose span=0ae955853ef5

Kept as is. The link needs a repo, and the user's rule for this item is never to guess or hardcode one. L's acceptance names no repo, so there is no URL to open. A grey chip that is not a button is the honest reading. A link that guesses the repo would open the wrong page. Every conductor-made pr_checks item carries acceptance.repo, so the plain chip is the rare case.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • A blocked row shows what its worker reported, and nothing the board does not know span=c19b0ba51505

Deferred. The board can only show what the record holds: the worker's own summary (shown under the task since the last head) and the reason (approval / needs a person). What to approve is not in the work fold. When the conductor knows, it can offer the answer as an asks option, which the goal-conductor skill now tells it how to write. Adding new fold data is outside this PR's Goal.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Reply buttons sit inside their task's row span=65d9551f8580

Deferred to a follow-up. Each Reply button sits directly under its task's title and report, inside that row, and it fills the chat box with that task's title and id, so a press can only answer the row it is in. The hint line says the buttons only fill the chat box. Scope is frozen after three review rounds on this head series.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Reply to label span=6e34f54db3c5

Deferred to a follow-up together with the item above. The prefill already names the task and id, and scope is frozen after three rounds.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Next step for an approval-blocked row span=a44ea0bda1a6

Deferred. The board does not know which approval timed out or where to re-run it; that is the conductor's to say, as an asks option or in chat. Not in this PR's Goal.

@iamwhatever
iamwhatever force-pushed the feat/goal-board-motion branch from c2e71c0 to 18a7ff4 Compare October 10, 2026 02:41
…host open bridge

Goal-board built-in (the Dashboard tab's conductor template): ports the old drawer's
motion (state pills, pop-in cards on first draw, live shimmer and dot, done-of-total
line with running and needs-you counts, warm needs-you band); all motion stops under
prefers-reduced-motion. Each needs-you row gets a Reply button plus one button per
option from a new optional agentic field, asks ({item_id: {options: [string]}}); every
button posts kirocrew-dashboard:act, so the host only fills the composer.

PR links. SECURITY: adds one new frame-to-host message, kirocrew-dashboard:open
{url}, handled by useFrameOpenLink in both hosts (CrewDynamicDashboard and the
CrewWebview / CrewDashboardFrame panel). The host honours it only from its own
frame's contentWindow and only for a URL matching
^https://github\.com/[A-Za-z0-9_.-]+/[A-Za-z0-9_.-]+/pull/[0-9]+/?$, and opens it with
window.open(url, '_blank', 'noopener,noreferrer'). Both sandboxes are unchanged
(allow-scripts only, no allow-popups). The goal-board PR chip uses the item's
acceptance.repo; the conductor panel takes an optional top-level repo (contract and
goal-conductor skill updated). No repo or no PR number: plain text, no button.
@iamwhatever
iamwhatever force-pushed the feat/goal-board-motion branch from 18a7ff4 to 3b41e76 Compare October 10, 2026 03:18
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • The motion is the user's explicit ask span=c38e6089326f

Rebutted. This item exists because the user asked for the old drawer board's motion in the new Dashboard tab: state pills, pop-in cards, live shimmer, done meter and warm band. The Goal section is frozen and is not mine to amend. The motion carries no data on purpose, so turning it off loses nothing: one prefers-reduced-motion block stops all of it, pinned by a test. The band glow now runs three times, not forever.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • The right-panel PR link is the user's explicit ask span=157c70190848

Rebutted. The user asked for both boards to open a task's PR: the goal-board in the Dashboard tab and agent_panel_templates/kirocrew-conductor.html, the right-panel board the conductor publishes, with an optional top-level repo. The panel board is not a dashboard built-in, so the 'No change to other built-in templates' line still holds. ConductorBoardPanel.repo is optional and a board without it renders as before.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Reply stays on an approval-blocked row span=49f3811b2df6

Kept. Reply still has a use on that row: asking the conductor about the approval, or telling it to skip it. The line above it now says plainly that replying does not approve, and where to approve. Hiding Reply would leave a row the reader cannot answer at all when the approval card is gone.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Card state and bar segment answer two questions span=bfabdca07f29

Kept, by design of the page. The card pill is the ledger's recorded state, which is 'open', and the board never relabels a recorded state; the verdict-vs-state note in the template says why. The bar groups open items waiting on the reader under 'needs you' so they are not hidden as moving work, and those same cards sit in the warm Needs-you band and carry the warm tint. Follow-up candidate: a 'needs you' pill beside 'open' on those cards.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Title on an unlinked PR chip span=c5e4d02b396b

Deferred, low severity per the lane. The chip is plain grey text, not a button, and only appears when the item's acceptance names no repo, which a conductor-made pr_checks item always names. Scope is frozen after five review rounds.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Options must name their choice span=3ff8f9a441bd

Already in this head. src/kiro_crew/builtin_skills/goal-conductor/SKILL.md tells the conductor to write each option as a full answer that reads on its own beside the worker's report, and the evidence fixture now uses 'Ship the compact layout' / 'Ship the roomy layout'.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 10, 2026

@CrysisDeu CrysisDeu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Reviewed the diff with the security change in focus: both sandboxes stay as they are; the new kirocrew-dashboard:open bridge accepts only an exact GitHub PR URL, only from one of the host's own frames (event.source match), and only with a live user activation while that iframe is the focused element; the open is noopener,noreferrer. The template builds every node with createElement/textContent, no innerHTML. Reduced-motion block covers pseudo-elements. All checks green.

@iamwhatever
iamwhatever merged commit afb24ab into main Oct 10, 2026
102 checks passed
@iamwhatever
iamwhatever deleted the feat/goal-board-motion branch October 10, 2026 07:52
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants