Skip to content

✨ dashboard: 12px text floor for the Activity monitor on phones - #17180

Merged
kubestellar-prow[bot] merged 11 commits into
v5from
scanner/fix-17164
Nov 8, 2026
Merged

kubestellar-prow[bot] merged 11 commits into
v5from
scanner/fix-17164

Conversation

@hivecommons-hive

Copy link
Copy Markdown
Contributor

At 390×844 the Activity monitor rendered 240 text nodes below 11px (--fs-xs / --fs-2xs on chips, since, stage, column headers).
In the existing phone tier, #activity-monitor-section now remaps --fs-2xs and --fs-xs to --fs-sm (12px). Inputs stay at --fs-touch; desktop is unchanged.
Adds a Go guard test, a 390×844 tracker-text-floor probe in dashboard-mobile-shots (text size + no horizontal overflow), design-system docs, and a changelog fragment. static/index.html is updated to match the generated output.

Closes #17164

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

@kubestellar-prow kubestellar-prow Bot added dco-signoff: yes Indicates the PR's author has signed the DCO. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Nov 8, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor Author

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

hive/awaiting-ci: CI pending — sweep will merge when green.


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

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

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

Read this against the v5 tree rather than just the diff; it looks correct to me.

What I verified

  • responsive.css:44 adds the remap inside the existing phone tier (media (max-width: 640px), ((pointer: coarse) and (max-width: 820px))), and the generated static/index.html:5965 carries the same line inside the same tier block, so TestActivityMonitorPhoneTextFloor actually exercises the shipped output.
  • Every font-size in tracker.css / responsive.css goes through a --fs-* token — there are no literal px/rem sizes to slip under the floor. The only indirections are --ham-odo-digit (tracker.css:684, resolved at :root from --fs-xs, so the section-level remap alone would not reach it — the PR correctly re-pins it), --cue-flight-size (--fs-3xl) and --tap-glyph (16px), both already ≥ 12px.
  • --fs-xs/--fs-2xs are used for nothing but font-size inside the tracker CSS, so the remap cannot change layout geometry.
  • TRUSTED_SCRIPTS_TREE → c0197bc4… matches git rev-parse <head>:src/scripts for this branch, and src/scripts has not moved on v5 since the merge-base, so the pin stays valid on a merge of this PR as it stands.

Red mobile-shots is not this PR. The job log fails only on 390x844@3 light/dark tracker-phone-ergonomics; the new tracker-text-floor probe passed. That ergonomics probe was fixed on v5 by #17199 (7f604c2), which landed after this branch's merge-base — a rebase would clear it. The workflow is continue-on-error and not required anyway.

Sequencing note for whoever merges: #17198 also edits src/scripts/dashboard-mobile-shots.mjs and re-pins TRUSTED_SCRIPTS_TREE (to a different hash, since its tree differs). Whichever of the two lands second will need a fresh git rev-parse HEAD:src/scripts re-pin or integration-governance.cjs:102 will reject the merged tree.

Minor: #17164's acceptance text says #stage-tracker-section; the tree only has #activity-monitor-section (static-src/html/tracker.html:5), so the PR's selector is the right one.

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

docs-currency review at head 92bff15f.

  1. Design-system doc states a rule the PR itself had to break — :root aliases do not inherit the floor. src/docs/dashboard-design-system.md:333-337 says the phone tier "remaps --fs-2xs and --fs-xs to --fs-sm" and that new tracker CSS sizing "through --fs-2xs/--fs-xs/--fs-sm" gets "the floor applies automatically". But tracker.css:684 declares :root { --ham-odo-digit: var(--fs-xs); }, which resolves at :root before the section-scoped remap, so the floor did not apply and responsive.css:44 had to add a third override --ham-odo-digit: var(--fs-sm) (also pinned by activity_monitor_phone_text_floor_test.go:17). The doc omits --ham-odo-digit and the trap. Since ✨ dashboard: Activity monitor 12px text floor on phones #17164 asks for the doc "so later tracker CSS respects it", please add one sentence: any --fs-* alias declared on :root (not on .ham-*/the section) must be remapped explicitly in the phone tier, as --ham-odo-digit is, and list it alongside the two tokens.

  2. PR body/changelog omit a visible phone layout change. tracker.css:992 adds #activity-monitor-section .ham-row { padding-block: var(--sp-3); } in the phone tier, tightening card rows from --sp-4 (tracker.css:105). Commits 30554b21/92bff15f explain it (96px card median cap after ✨ dashboard: card-per-row Activity monitor layout on phones #17198), but the PR body and changelog.d/changed-activity-monitor-phone-12px-text-floor.md only describe the text floor. Please mention the row-padding trim in the body (and ideally the changelog bullet).

Advisory (not blocking): #17164 asks for 390×844 + 1280 screenshots in the PR; none are attached (body/comments), though tracker-text-floor.js covers the 390×844 acceptance checks. The TRUSTED_SCRIPTS_TREE re-pin (integration-governance.cjs:12) is explained only in a PR comment, not the body.

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

Intent alignment (#17164) — reviewed head 92bff15. The core change matches the issue: the phone tier remaps --fs-2xs/--fs-xs (plus --ham-odo-digit, which :root resolves from --fs-xs before the section override) to --fs-sm inside #activity-monitor-section (static-src/css/responsive.css:44), scoped to the .modal-sheet tier, so 1280 is unchanged by construction. Two advisory notes, neither blocking:

  1. Undocumented visual change — static-src/css/tracker.css:992 adds #activity-monitor-section .ham-row { padding-block: var(--sp-3); }, tightening phone row padding from the base --sp-4 (.ham-row at static/index.html:1448). Neither the PR body nor ✨ dashboard: Activity monitor 12px text floor on phones #17164 mentions it; it looks like compensation for the card median-row-height probe (dashboard-mobile-shots.mjs:525-528) once text grows to 12px. Worth a line in the PR body/changelog so the next card-layout PR knows why it is there.
  2. Ratchet baseline edit is unrelated drift — webstatic/style_ratchet_test.go:30 lowers rawColors 135→134, but the index.html diff adds only two lines with no colour literals. Running the test's own counting logic gives 134 at both merge-base 4e65421 and head, so the baseline was already stale on v5; this PR just absorbs the fix. Fine to land, but it is not a consequence of this change.

Also noted: the tracker-text-floor probe only asserts when innerWidth <= 640 (testdata/tracker-text-floor.js:7), so the coarse-pointer ≤820px half of the tier (768×1024, landscape phones) is covered by the CSS but not asserted. Acceptable for the 390×844 criterion in the issue.

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

Style/maintainability review at 92bff15 — two small in-scope fixes, one advisory.

  1. tracker-text-floor probe detects the phone tier differently from every sibling probe and the runner. src/pkg/dashboard/webstatic/testdata/tracker-text-floor.js:7 uses const phone = innerWidth <= 640;, while tracker-phone-card.js:21, tracker-phone-pill.js:14 and the runner itself (src/scripts/dashboard-mobile-shots.mjs:276,504) use matchMedia('(max-width: 640px), ((pointer: coarse) and (max-width: 820px))'). The CSS floor (responsive.css:44) is scoped to that full query, so on a coarse-pointer viewport between 641 and 820px wide (the shots matrix includes 740×360 landscape, dashboard-mobile-shots.mjs:9-10) the floor is active but the probe skips all three assertions and reports ok. Requested: use the same matchMedia(...) expression as the siblings.

  2. Design-system doc omits the gotcha this PR itself hit. src/docs/dashboard-design-system.md:335-337 says new tracker CSS that sizes text through --fs-2xs/--fs-xs/--fs-sm gets the floor "automatically". That is not true for tokens derived at :root — tracker.css:684 declares :root { --ham-odo-digit: var(--fs-xs) }, which resolves before the section-scoped remap, which is why responsive.css:44 has to override --ham-odo-digit separately (the Go test comment at activity_monitor_phone_text_floor_test.go:9-11 explains this; the doc does not). Requested: add one sentence to the doc — any :root token derived from --fs-* must be added to the phone-tier override on #activity-monitor-section (as --ham-odo-digit is) or declared on the section instead.

Advisory (no change needed): the PR body and changelog describe only the text remap, but the diff also adds #activity-monitor-section .ham-row { padding-block: var(--sp-3); } (tracker.css:992) to keep the card-row median under 96px once text grew (commit 30554b2). Worth a line in the body so the padding change is not read as unrelated. The rawColors baseline 135→134 in style_ratchet_test.go:30 corrects a count that was already 134 at merge-base (I recounted both blobs); it is unrelated to this diff but harmless.

Could not run go test in this environment; CI is green at head.

@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 stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) labels Nov 8, 2026
@kubestellar-prow kubestellar-prow Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 8, 2026
@github-actions

github-actions Bot commented Nov 8, 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
#17179 ✨ dashboard: attention-first Activity monitor ordering and count line on phones same files src/pkg/dashboard/static-src/css/tracker.css
src/pkg/dashboard/static/index.html
#17171 🐛 fix: unclaimed proposal / kind/design issues derive stage/018-open-for-discussion same files src/pkg/dashboard/static/index.html

@hivecommons-hive

Copy link
Copy Markdown
Contributor Author

hive/ci-triage: the tide error webhook was transient — tide now reports pending: Not mergeable. Needs approved, lgtm labels for head 2d5810e4. PR is MERGEABLE against v5 with no conflicts; no code change needed. Awaiting lgtm/approved — sweep will merge when green. DEFER.


🐝 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 added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 8, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor Author

runtime-tests failure root-caused: this PR adds the tracker-text-floor probe to src/scripts/dashboard-mobile-shots.mjs, which changes the src/scripts tree hash and invalidated the pinned TRUSTED_SCRIPTS_TREE in .github/scripts/integration-governance.cjs (test 5 of integration-governance.test.cjs). Re-pinned to 4b2b0585… (same pattern as #17176) in b1bdf2b.


🐝 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

@github-actions github-actions Bot added the conflicts-with-open-pr Open PR has a merge conflict with another open PR label Nov 8, 2026
@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 Nov 8, 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 Nov 8, 2026
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 8, 2026
@github-actions github-actions Bot removed the conflicts-with-open-pr Open PR has a merge conflict with another open PR label Nov 8, 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/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) labels Nov 8, 2026
…text-floor probes, re-pin TRUSTED_SCRIPTS_TREE

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 stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 8, 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 at head 514371b against v5 (merge-base 8e55232). The CSS itself is still correct, but this head's red mobile-shots is caused by this PR, not by v5: the 12px floor pushes the card-per-row layout from #17198 over its height budget.

Evidence

  • mobile-shots run 42447214267 fails only tracker-phone-card: "card rows must have median height ≤ 96px with ≥ 6 rows in view at 390x844", on every phone viewport (390×844, 375×667, 430×932, light and dark). The new tracker-text-floor probe passes.
  • #17198 (which added that probe and the card layout) passed mobile-shots at its own head 6532b1c — run 42446431101.
  • Between 6532b1c/v5 and this head, the only change inside #activity-monitor-section is responsive.css:44: #activity-monitor-section { --fs-2xs: var(--fs-sm); --fs-xs: var(--fs-sm); --ham-odo-digit: var(--fs-sm); }. Row text that goes through those tokens — .ham-chip (tracker.css:31), .ham-meta (:84), .ham-since (:164) — grows from ~10.9px to 12px per line, and the card probe (tracker-phone-card.js:12, MAX_MEDIAN_ROW_HEIGHT = 96) measures .ham-row height.

So the two requirements now conflict on the same rows: 12px text (this PR / #17164) and ≤ 96px median card height (#17198). Merging as-is would leave v5's mobile-shots red. The fix belongs here: either tighten the card's vertical spacing/wrapping so 12px text fits in 96px, or raise MAX_MEDIAN_ROW_HEIGHT with the rationale in #17198's terms (≥ 6 rows in view at 390×844 is the real constraint). I could not read the exact medians — gh run download is not permitted from this lane — so the *-activity-probes.json artifact on that run is the place to confirm the numbers.

Unchanged from earlier reviews: the TRUSTED_SCRIPTS_TREE re-pin at integration-governance.cjs:12 (066d4e1e → 75a61a7a) equals git rev-parse 514371b:src/scripts, which is what the guard's own error text (:103) prescribes, and the only src/scripts delta is the probe name at dashboard-mobile-shots.mjs:270. That is still a .github/scripts edit for @clubanderson to confirm, as the previous rounds said.

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

hivecommons-hive Bot and others added 2 commits November 7, 2026 23:48
…ext floor

After #17198 (card-per-row Activity monitor layout) merged into v5, the tracker-phone-card probe measured a median .ham-row height of 97px against the 96px cap once combined with this PR's 12px text floor. Trim the phone-tier .ham-row vertical padding by 1px top and bottom (2px per card); every phone font-size stays at or above 12px. Regenerated static/index.html.

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 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.

Decision needed: @clubanderson should confirm the TRUSTED_SCRIPTS_TREE re-pin in .github/scripts/integration-governance.cjs:12 (066d4e1e → 75a61a7a) is acceptable; it equals this head's src/scripts tree and the only src/scripts change is one probe name at dashboard-mobile-shots.mjs:270.

Read at head 30554b2 against v5. mobile-shots is now green at this head (all phone probes including tracker-phone-card and tracker-text-floor pass), but the commit that fixed it — 30554b2, "keep phone card rows at the 96px median" — introduces a raw 1px literal into the phone card tier and that breaks two existing guards. This is the PR's own change, not v5 drift.

What fails and why

  • src/pkg/dashboard/static-src/css/tracker.css:992 (and the generated static/index.html:2335): #activity-monitor-section .ham-row { padding-block: calc(var(--sp-4) - 1px); }.
  • src/pkg/dashboard/stage_tracker_activity.test.js:682 asserts doesNotMatch(card…, /#[0-9a-fA-F]{3,8}\b|\d+px/, 'card tier uses tokens only') over the whole phone-card media block — the 1px matches \d+px. That is the not ok 123 — phone card per row … failure in runtime-tests, and TestStageTrackerActivityJavaScript (dashboard 2/4, dashboard shuffle 3/3) is the Go wrapper over the same JS suite.
  • src/pkg/dashboard/webstatic/style_ratchet_test.go:237 counts the new padding-block: declaration via paddingRE (line 63): operator static/index.html is now at 205 raw padding declarations against the 204 baseline (line 32). The same run also reports raw colors at 134, below the 135 baseline (line 30) — so the baseline needs editing to 134 at this head regardless.

Suggested fix: express the row padding through tokens the card tier already uses (e.g. a --sp-* value or a new --ham-row-pad-phone token declared in tokens.css, rather than - 1px inline), then regenerate static/index.html; update styleRatchetBaselines["operator static/index.html"].rawColors to 134 in the same PR. If the padding tweak genuinely needs a non-token value, the guard at stage_tracker_activity.test.js:682 is deliberate (#17161), so that is a conversation to have rather than a regex to widen.

Trust-surface note (.github/scripts/integration-governance.cjs:12): TRUSTED_SCRIPTS_TREE moves 066d4e1e → 75a61a7a. I checked: 75a61a7a… is exactly src/scripts at this head, and the only src/scripts change in the diff is the added 'tracker-text-floor' probe name at dashboard-mobile-shots.mjs:270. Mechanical, but it is a verifier pin, so it stays a maintainer's call.

Decision needed: @clubanderson should confirm the TRUSTED_SCRIPTS_TREE re-pin in .github/scripts/integration-governance.cjs:12 (066d4e1e → 75a61a7a) is acceptable; it equals this head's src/scripts tree and the only src/scripts change is one probe name at dashboard-mobile-shots.mjs:270.

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

…rs 134

The 1px trim landed as calc(var(--sp-4) - 1px), which carries a raw px literal: the card-tier tokens-only assertion in stage_tracker_activity.test.js and TestStyleRatchet's raw-padding count both rejected it. --sp-3 (6px) keeps every card at or under the 96px median cap without a literal. The ratchet also reports this branch at 134 raw colors, one below the operator baseline, so the baseline follows it down.

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 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 at head 30554b2 against v5. The 12px remap itself is still correct and mobile-shots is now green, but the line added at this head to fix the card-height conflict is what turns v2 Tests red — two separate guards reject it.

Finding (high) — src/pkg/dashboard/static-src/css/tracker.css:992 (mirrored at static/index.html:2335)

#activity-monitor-section .ham-row { padding-block: calc(var(--sp-4) - 1px); }
  1. stage_tracker_activity.test.js:682 asserts the phone card tier contains no \d+px literal after its first { ('card tier uses tokens only'). The - 1px fails it, so TestStageTrackerActivityJavaScript (stage_tracker_activity_test.go:200) fails in test (dashboard 2/4) and test (dashboard shuffle 3/3), on all re-runs — run 42448342897, subtest not ok 26 - phone card per row ….
  2. style_ratchet_test.go:88: operator static/index.html raw padding went 204 → 205, above the baseline, so TestStyleRatchet fails in test (rest 3/4). That is the same declaration.

Consequence: merging as-is leaves v5 red on the dashboard and rest lanes. Fix: express the row padding through tokens only (e.g. a --sp-* step, or a new token in tokens.css if the card budget genuinely needs the odd pixel) and regenerate static/index.html.

Open question (not a defect from this diff): the same TestStyleRatchet run also reports raw colors at 134, below the 135 baseline. This PR touches no color literal, so that likely rode in with the v5 merge; whoever lands first should lower styleRatchetBaselines["operator static/index.html"].rawColors to 134.

Also verified

  • .github/scripts/integration-governance.cjs:12 — TRUSTED_SCRIPTS_TREE 75a61a7a… equals git rev-parse 30554b2:src/scripts; the only src/scripts change is the probe name at dashboard-mobile-shots.mjs:270. Same re-pin mechanism the earlier reviews routed to @clubanderson; nothing new there.
  • responsive.css:44 remap and activity_monitor_phone_text_floor_test.go:17 guard are unchanged from the previously reviewed heads.
  • The .ham-row padding change is not mentioned in the PR body or in the dashboard-design-system.md section this PR adds; worth a sentence once it is reworked, since it is the one line that interacts with #17198's ≤96px card budget.

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

@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 8, 2026
@clubanderson
clubanderson dismissed their stale review November 8, 2026 05:33

Stale: the tracker-text-floor probe passes on 92bff15 (mobile-shots green); the 10.88px ham-merged-n came from the earlier b1bdf2b run.

@clubanderson clubanderson left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Owner review: scoped token remap (--fs-2xs/--fs-xs/--ham-odo-digit → --fs-sm) inside #activity-monitor-section in the existing phone tier only; desktop untouched; ratchet count adjusted; probe + Go guard added. mobile-shots green on 92bff15.

/approve
/lgtm

@kubestellar-prow kubestellar-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Nov 8, 2026
@kubestellar-prow

Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 9aa15ed62f9077dacac593f9ac4fbfa638a0f520

@kubestellar-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: clubanderson

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

The pull request process is described 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

@github-actions

github-actions Bot commented Nov 8, 2026

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

✨ dashboard: Activity monitor 12px text floor on phones

1 participant