Skip to content

fix(fleet): show measured status, asks and problems - #663

Merged
BastiHu merged 19 commits into
fix/fleet-read-factsfrom
fix/fleet-facts-ui
Oct 29, 2026
Merged

BastiHu merged 19 commits into
fix/fleet-read-factsfrom
fix/fleet-facts-ui

Conversation

@BastiHu

@BastiHu BastiHu commented Oct 19, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

Fleet rows need consistent measured status, Exchange details, activity and problems. Inline full dates also make the table hard to scan, and the details need a keyboard path.

What changed

Render the shared measured facts in Fleet rows, Crew summaries and command-palette navigation. A sibling Facts disclosure outside the row-navigation button makes unknown reasons, counterparty/intent/age and full timestamps available with Tab, Enter and Space, including threadless rows.

Inline runtime, activity, problems, ask-opened and environment-read times use relative duration labels on the existing minute tick. Clock subscriptions stay in leaves so sections do not rebuild each minute. Stale runtime/activity/problem labels remain absolute; stale ask ages stay fixed at the recorded read. Absolute times follow the client's 12/24-hour preference and remain visible in the disclosure; the source readout shows its exact timestamp inline. Ask tooltips render plain text without nested tooltip triggers.

The page merges receiver-side remote delivery alarms from #662, marks unavailable delivery coverage explicitly, and keeps measured failures visible beside an incomplete-coverage explanation. A current row with incomplete delivery facts keeps the incomplete-coverage explanation.

Stack: #662 → #663 → #664. Land #663 and #664 together; the intermediate layer retains the old rail badge. No early closure of #360.

UI changes

Refreshed screenshots supplied by Jackson on 27 October: capture report. Before is j5/main; after is the stack tip (#664), with matched fixture data and dark theme. The report used a 1280×800 browser viewport; these captures show its cropped 1024×800 main panel. This is an integrated stack comparison. Each image is clickable at its original size. Videos are omitted as requested.

Populated Fleet table

Main already showed relative Last activity. The stack adds measured runtime, ask and problem details.

Before — main: populated Fleet table · Open full-size screenshot

Before — main: populated Fleet table

After — stack tip: populated Fleet table · Open full-size screenshot

After — stack tip: populated Fleet table

Disconnected environment

Before — main: saved rows while disconnected · Open full-size screenshot

Before — main: saved rows while disconnected

After — stack tip: stale absolute times and incomplete coverage · Open full-size screenshot

After — stack tip: stale absolute times and incomplete coverage

Exact-time tooltip

After — relative label with absolute-time tooltip open · Open full-size screenshot

After — relative label with absolute-time tooltip open

Keyboard Facts disclosure

After — Facts open with ask counterparty, intent, age and exact timestamps · Open full-size screenshot

After — Facts open with ask counterparty, intent, age and exact timestamps

The capture report records Tab to Facts, Enter to open and Space to close.

Remote-sender alarm

After — receiving server alarm attached to sender row · Open full-size screenshot

After — receiving server alarm attached to sender row

The remote alarm is a database fixture on two connected test servers, not a real peer delivery failure. #664 evidence shows the numeric alarm badge and incomplete-coverage page/badge. No loading, empty-state or screen-reader evidence is claimed.

Validation

The integrated predecessor 30e4f70da passed 117 tests across 12 focused files, scoped server/web/client-runtime/contracts typechecks, targeted lint (27 changed code files), formatting (32 changed files), and whitespace checks. Dependencies were installed from the pinned lockfile; no repo-wide local checks were run.

The current follow-up fixes CodeRabbit r4376419909: frozen rows always mark problem coverage incomplete while preserving their measured runtime, activity, asks and problems. Already-incomplete cached objects keep their identity. The strengthened regression reproduced the old failure, then passed after the fix; it verifies frozen references, stable identity across unrelated updates and reconnection recovery. The base layer passes 18 shared tests. The integrated predecessor 7d442e446 passed 67 relevant tests across 5 files, client-runtime/web typechecks, targeted lint, formatting and whitespace checks. Server/contracts code is unchanged by this follow-up.

Claude Opus 5.5 approved the full predecessor stack with no Critical, High or Medium findings, then independently approved this two-file follow-up after rerunning the same 23 shared + 44 web tests. Repeated runs are not added together. Its optional performance observation remains: the remote merge currently reruns on thread-shell changes; no measured regression was reported.

GitHub J5 CI passed on #662’s current head and the prior #663/#664 heads: #662, #663, #664, including all three server shards and each aggregate check; infrastructure timeouts required reruns without changing the code or the workflow timeout. The earlier #662 run passed format/lint/typecheck, unit/web tests and server shards 1/2; shard 3 exceeded its 15-minute budget while downloading Chromium dependencies, before tests began. The CI-timeout increase remains outside this stack.

The latest change fixes the timezone-dependent keyboard assertions reported in the maintainer review on #663. Expected absolute times now use the local timestamp formatter and current 12/24-hour setting. The original failure reproduced in America/New_York. All nine keyboard tests pass in UTC, America/New_York and Pacific/Auckland; an independent Claude Opus 5.5 review approved the test-only change and repeated the same nine tests successfully in six zones, including UTC+14 and UTC−11. Targeted lint, formatting and whitespace checks pass. Product code is unchanged. Fresh J5 CI passed on the corrected UI and integrated heads: #663 a0e89707f and #664 3d4bba413, including format/lint/typecheck, unit/web tests, all three server shards and each aggregate check. The earlier links above predate the test-only correction.

Current layer heads: #662 87ed2dd73f8412a1a3f2abaaa89beecc84845cfc; #663 a0e89707ffc832c37319e69bb9ef609df9364998; #664 3d4bba4134d408418a80bda8ddf54577764c9da9. All include j5/main at 882256d0915b4bb639c236506ec66a2a7a0975d9.

Live testing

Fresh fixture-based browser screenshots are available in the #663 capture report and #664 capture report. They show the table and exact-time tooltip, keyboard-open Facts, stale absolute times, a remote-sender alarm, and incomplete coverage on the page and rail badge. Remote alarms were seeded in disposable test databases; these captures do not prove a real-network delivery failure or provider run.

The initial J5 Browser attempt failed because AppArmor blocks its sandbox. The user-authorized standalone Chrome fallback works and has captured additional #663/#662 fixture screenshots; the isolated tester is finishing the bounded comparison and live-turn work. No host security setting or live database was changed. The earlier blocked-attempt artifact is historical, not the current evidence status. No new real provider turn, screen-reader pass or real-network peer failure has yet been verified in this follow-up. Automated push/poll and DOM tests cover modeled behavior separately. Disposable databases that applied the removed branch migration 44 must be recreated before testing against main's migration 44.

Upstream impact

apps/web/src/components/CommandPalette.tsx delegates to the J5 Fleet palette module. apps/web/package.json and its lock importer add the test-only user-event dependency. These edits are recorded in FORK.md case 34. Web and desktop share this surface; native mobile has no Fleet entry.

Checklist

  • One concern: measured Fleet facts and their presentation
  • Focused tests cover the changed behavior
  • UI evidence: refreshed fixture screenshots and limitations are linked above
  • Live testing: exercised and unexercised paths are stated above
  • Upstream-owned edits are recorded in FORK.md
  • Upstream product behavior is unchanged
  • Surfaces: shared contracts/derivation, web and desktop, provider-independent facts, connected environments and stale recovery; native mobile has no Fleet page
  • Affected J5 definitions are updated

Implementation and integration: GPT-6.1-Sol through Codex. Independent review: Claude Opus 5.5 through Claude.

BastiHu and others added 2 commits October 19, 2026 16:17
Use the existing live shell and ledger facts for Fleet rows, with explicit unknown reasons, per-environment read times and frozen stale measurements. Add the Fleet command-palette delegate and keep section and Crew summaries aligned with those measurements.

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
AI-Model: gpt-6.1-sol
AI-Harness: Codex
Use the existing absolute timestamp formatter for every Fleet time, including the date and year, so stale measurements never depend on midnight clocks. Omit the empty problems line while preserving unknowns and actual problems.

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
AI-Model: gpt-6.1-sol
AI-Harness: Codex
@BastiHu BastiHu self-assigned this Oct 19, 2026
@vercel

vercel Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
j5-code Ready Ready Preview Oct 27, 2026 1:56pm UTC

Request Review

@github-actions github-actions Bot added the vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. label Oct 19, 2026
@github-actions github-actions Bot added the size:XL 500-999 effective changed lines (test files excluded in mixed PRs). label Oct 19, 2026
BastiHu added a commit that referenced this pull request Oct 20, 2026
BastiHu added a commit that referenced this pull request Oct 20, 2026
BastiHu added a commit that referenced this pull request Oct 20, 2026
@BastiHu
BastiHu marked this pull request as ready for review October 21, 2026 09:17

@bryantderosier bryantderosier left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Reviewed the incremental UI layer 65ee343 -> c1cfbf4; PR head and stack base rechecked before submission.

No additional verified actionable defects found in this layer. Checked measured status/activity presentation, owed/awaited details, missing/stale facts, Active/Settled classification, Crew summaries, command-palette navigation, and environment-qualified lookups.

The stack remains blocked by the P1 integration issue reported on #662: its Fleet read imports a human-name helper removed from current main, preventing server startup after the proposed merge. This is a nonblocking review of the incremental UI changes, not approval to land the current stack. Recheck this layer after updating its base, and preserve the requirement to land the UI and badge layers together.

Validation: 60 existing focused tests passed across six files (server Fleet facts, read-change feeds, Fleet projection, shared runtime facts, Fleet logic, and Fleet presentation) on the integrated stack head 9bf180e. Whitespace checks passed for all three incremental diffs. These branch-only results do not establish compatibility with current j5/main. No live server/provider turns or browser testing were performed; no repository source files were changed.

Reviewed with GPT-6.1-Sol through the Codex harness.

@bryantderosier bryantderosier left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Review: measured Fleet presentation

M1 needs a keyboard-accessible path to the new fact details. The page, Crew summaries and section classification now consume the same measured states, and the inherited People-lookup fix is present.

Severity Open Fixed Accepted
🔴 Critical 0 — —
🟠 High 0 — —
🟡 Medium 1 — —
🔵 Low 0 — —
⚪ Info 1 — —

There were no prior incremental findings; the inherited #662 blocker is fixed. Historical dependency findings are not counted again here.

🟡 M1 · New fact details are unavailable from the keyboard Risk 💬 inline

Owes/Awaiting details and unknown reasons use non-focusable span tooltip triggers inside the row's navigation button. Keyboard focus lands on that outer button, so it cannot open those tooltips; the new counterparty/intent/age and reason details have no keyboard path.
Ask: expose the details with an accessible description or keyboard-operated disclosure outside the navigation button, and add an interaction regression.

Evidence
  • Ask trigger; unknown-reason trigger; containing row button.
  • The pinned tooltip wrapper adds no focusability. Lockfile-matching Base UI 1.5.0 attaches focus handlers to the rendered span without adding tabIndex. Source-confirmed; no browser interaction run.
  • The PR's known-limit prose is not an approved waiver.
Layer safety and validation

Keep #663 and #664 together: this intermediate layer retains the old owed-ask badge, so it does not alone complete #360/AC23. Preserve that dependency when retargeting/merging, and avoid closing #360 before its badge layer lands. #662's remote-alarm/activity gaps are inherited.
Both reviewers independently ran the same 3 focused client files / 40 passing tests at this head; those are repeated runs, not 80 unique tests. Whitespace passed. Palette/readout rendered behavior and positive-alarm visuals remain coverage gaps.
Two independent reviewers (GPT-6.1-Sol and Claude Opus 5.5), each with separate Standards, Spec and Risk children; Captain reconciled findings against pinned source. Focused tests used existing mirrored dependencies: Effect was relinked to pinned 4.0.5, but other dependency versions may drift. No lint/typecheck, browser/accessibility interaction, live server/provider or real cross-environment execution was run.

⚪ Info (1): stale comments

The comments at FleetPage.tsx:349-356 still describe the old status pills. Refresh them. Stop availability intentionally asks whether there is a turn to interrupt; a different classifier from presentation is not by itself a demonstrated defect.

Reviewed base 45a5db8145af → head dcdee0b922f7. Ordinary COMMENT review.

Comment thread apps/web/src/j5/fleet/FleetFacts.tsx Outdated
</FleetFactHint>
) : (
<Tooltip>
<TooltipTrigger render={<span className="text-right text-xs tabular-nums" />}>

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

M1 · Make the fact details available from the keyboard
This span and FleetFactHint's span are not focusable; the outer Fleet row button gets keyboard focus instead, so users cannot reveal the new ask details or unknown reasons.
Ask: expose an accessible description or a keyboard-operated disclosure outside the navigation button, without nesting another control in it, and cover keyboard access with an interaction test.

@BastiHu BastiHu Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Fixed in cb5ea76, included in #663 head 2ef5350 and propagated to #664. Each row now has a sibling Facts disclosure outside its navigation button, with a specific accessible name, aria-expanded and aria-controls. Keyboard users can read counterparty/intent/age and runtime/activity/provenance unknown or stale reasons. It remains reachable when threadless navigation is disabled, and detail subscriptions mount only while open. Existing mouse tooltips remain.

Three real DOM user-event tests cover Tab, Enter, Space, disclosure without navigation, retained Enter navigation, threadless access and frozen stale ages. Focused web tests, scoped web typecheck and targeted lint/format passed; The pushed-head CI results are recorded below. No browser or screen-reader pass was claimed; the PR body marks existing screenshots as historical and not evidence of this new disclosure.

Final CI verification: all three code heads before the documentation-only follow-up passed J5 CI: #662 CI at b25b43c62; #663 CI at dd2b237db; #664 CI at 8c99b6217. The only subsequent code change raised the server-job timeout to accommodate cold Chromium setup; no test or required check was removed.

Subsequent docs-only follow-up 19dde72 folds AC12 into one sentence for CodeRabbit r4360611828; no runtime behavior changed. New-head CI has now passed, as linked below.

Current-head CI verified after the documentation follow-up: #662 CI at 19dde72bf; #663 CI at 664e98908; #664 CI at 7c2b2bf25. All three passed; #663 required rerunning the server shard after slow Ubuntu dependency downloads exhausted its job budget.

@Jacksondr5 Jacksondr5 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

UI review (Jackson): please show row timestamps as relative time.

fleetTime() (apps/web/src/j5/fleet/fleetPresentation.ts:38) uses formatChatTimestampTooltip, a tooltip formatter. It puts a full date with the year inline in every row, for example "3:14 PM, 24th October 2026". The Fleet table on j5/main shows Last activity as relative time using formatElapsedDurationLabel (FleetPage.tsx:687), and so do the Inbox, Playbooks and spawned children.

Please:

  1. Use formatElapsedDurationLabel for the inline labels: Last activity, "Idle since", the problem labels, the ask's "opened" time and the environment read time. Keep the absolute time in the tooltip or title. This also removes the known limit about ignoring the 12/24-hour preference.
  2. Re-render the new labels on the existing minute tick, so a relative label doesn't stop moving.
  3. On frozen or stale rows, show the absolute time or "as of read" instead of a relative time that keeps counting, the same way ask ages already freeze.

Posted by Claude Opus 5.5 on Jackson's behalf.

@Jacksondr5 Jacksondr5 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Review panel: Claude Opus 5.5 + GPT-6-Astra (re-review at e2be84730d)

The maintainer's timestamp comment is applied in the code. Live labels use formatElapsedDurationLabel on the shared minute tick, absolute times are in the tooltip and the disclosure, and frozen rows keep absolute times. We found one test defect in this layer.

Two keyboard tests fail outside UTC

apps/web/src/j5/fleet/FleetFacts.keyboard.test.tsx expects local wall-clock strings, such as 12:00, 23rd October 2026 at lines 285–289 and 348–350, from UTC ISO fixtures (…T12:00:00Z). The product formats those in the machine's local time zone, which is correct, so the expected strings only match when the test runs in UTC.

  • Failure: on a machine in America/New_York, vp test run apps/web/src/j5/fleet/FleetFacts.keyboard.test.tsx fails 2 of 9 tests. "refreshes live row, expanded facts, asks and environment times on the shared minute tick" gets 08:00, 23rd October 2026 where it expects 12:00. "advances waiting-to-start ages and freezes their absolute request time" gets since 08:00. With TZ=UTC all 9 pass, which is likely why CI is green. Both panel members reproduced this by running it on separate worktrees.
  • Fix: build the expected strings from the fixture ISO times with the same formatter the component uses (formatChatTimestampTooltip(iso, format)), or pin this suite's time zone. The 12-hour assertions at lines 293–295 need the same treatment.

This is a test-portability defect, not a product timestamp defect.

Verified by running: the rest of the focused Fleet suites at this head pass (shared and server Fleet facts, ReadChangeFeeds, peer round trips, fleetState, fleetPresentation, fleet.logic).

@Jacksondr5

Copy link
Copy Markdown
Owner

Thanks for applying the timestamp change. With the panel's time-zone test fix, please also refresh this PR's UI evidence. The current images and videos predate the rework, so they can't be used for the UI review. Please capture base and head with the same fixture, viewport and theme:

  • the Fleet table with relative row times, with the absolute time showing in a tooltip;
  • the keyboard Facts disclosure open, showing an ask's counterparty, intent and age;
  • a frozen or stale row showing absolute times;
  • a remote-sender alarm chip, and the incomplete-coverage note on the page and the badge.

If a state is impractical to reach, say so in the PR body. Videos should be uploaded to GitHub, so they play inline, rather than linked as raw files.

Posted by Claude Opus 5.5 for Jackson.

@BastiHu

BastiHu commented Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator Author

@Jacksondr5 @bryantderosier Following up on the timezone review and refreshed UI evidence request: please re-review #663 at a0e89707f.

The absolute-time expectations now use the local formatter and selected 12/24-hour preference. All nine keyboard tests passed in six time zones in independent Opus 5.5 review, including UTC+14 and UTC−11. The keyboard Facts disclosure, leaf minute updates, stale absolute times and accessible exact timestamps remain covered. Latest-head J5 CI passed.

Update, 27 October: the PR bodies now include Jackson's refreshed #663 screenshots and #664 screenshots. I visually checked the table, exact-time tooltip, Facts disclosure, stale rows, remote alarm and incomplete page/badge. The comparison is main → stack tip; the remote alarm is a database fixture, not a real peer delivery failure. The user-requested Chrome fallback works despite the J5 Browser AppArmor restriction. Videos are omitted from the bodies as requested. The previous blanket evidence-blocked statement is superseded; the bounded isolated tester is finishing its remaining work.

@Jacksondr5

Copy link
Copy Markdown
Owner

UI evidence (captured for review)

Before is j5/main and after is the stack tip (#664). Both use the same fixture data, 1280×800 and the dark theme.

Before After
Populated Fleet table. Before already showed Last activity as relative time. before after
A disconnected environment's saved rows before after

After only:

State Screenshot
Hovering a relative time shows the absolute time tooltip
Facts opened from the keyboard: counterparty, intent and age facts
A receiving server's alarm on the local sender's row, with both environments connected remote alarm

Keyboard: Tab to Facts, Enter opens it, Space closes it.

fleet-keyboard-facts.mp4

Not shown: the remote alarm is a database fixture on two connected test servers. It is not a real peer delivery failure. There are no loading or empty states.

Captured by GPT-6-Astra; posted by Claude Opus 5.5 for Jackson.

* fix(fleet): badge counts agents with measured problems

Count live agents with failed runs, overdue dispatch or open-Exchange delivery failures once per environment and participant. Keep source gaps and unmeasured agents explicit, and preserve facts across duplicate project placements.

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
AI-Model: gpt-6.1-sol
AI-Harness: Codex

* fix(fleet): omit counts when every source is unavailable

* test(fleet): verify cross-environment badge coverage and recovery

---------

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Codex <codex@openai.com>
@github-actions github-actions Bot added size:XXL 1,000+ effective changed lines (test files excluded in mixed PRs). and removed size:XL 500-999 effective changed lines (test files excluded in mixed PRs). labels Oct 27, 2026

@Jacksondr5 Jacksondr5 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Approving on 0e7b6f6, including the problem badge merged in from #664. The UI is reviewed from the evidence screenshots and video, and the relative timestamps fix my earlier comment.

@BastiHu
BastiHu merged commit 7026b32 into fix/fleet-read-facts Oct 29, 2026
33 of 35 checks passed
@BastiHu
BastiHu deleted the fix/fleet-facts-ui branch October 29, 2026 11:53
Jacksondr5 pushed a commit that referenced this pull request Oct 29, 2026
* fix(fleet): expose measured ledger and runtime facts

Read owed and awaited Exchanges and sender delivery alarms with the Fleet snapshot. Derive runtime, dispatch problems and labeled activity from the existing live raw shell, with one shared local threshold deadline and explicit missing-fact reasons.

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
AI-Model: gpt-6.1-sol
AI-Harness: Codex

* fix(fleet): measure received messages and bound ask summaries

* fix(fleet): leave partial ledger activity unknown

* fix(fleet): return peer thread-delivery alarms to origin

* fix(fleet): keep polling past early alarm facts

* ci(j5): allow cold Chromium setup before server shards

* docs(a2a): keep delivery criterion in one sentence

* fix(fleet): read remote delivery alarms through client sources

* fix(fleet): track remote coverage from open Exchanges

* fix(fleet): qualify frozen rows as incomplete

* fix(fleet): show measured status, asks and problems (#663)

* fix(fleet): show measured status, asks and problems

Use the existing live shell and ledger facts for Fleet rows, with explicit unknown reasons, per-environment read times and frozen stale measurements. Add the Fleet command-palette delegate and keep section and Crew summaries aligned with those measurements.

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
AI-Model: gpt-6.1-sol
AI-Harness: Codex

* fix(fleet): keep dates explicit in measured timestamps

Use the existing absolute timestamp formatter for every Fleet time, including the date and year, so stale measurements never depend on midnight clocks. Omit the empty problems line while preserving unknowns and actual problems.

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
AI-Model: gpt-6.1-sol
AI-Harness: Codex

* fix(fleet): make row fact details keyboard accessible

* docs(fleet): record keyboard test dependency seam

* fix(fleet): refresh relative timestamps while live

* fix(fleet): keep exact times accessible and relative labels clear

* fix(fleet): merge receiver facts and qualify incomplete coverage

* test(fleet): respect local timezone in keyboard assertions

* fix(fleet): badge counts agents with measured problems (#664)

* fix(fleet): badge counts agents with measured problems

Count live agents with failed runs, overdue dispatch or open-Exchange delivery failures once per environment and participant. Keep source gaps and unmeasured agents explicit, and preserve facts across duplicate project placements.

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
AI-Model: gpt-6.1-sol
AI-Harness: Codex

* fix(fleet): omit counts when every source is unavailable

* test(fleet): verify cross-environment badge coverage and recovery

---------

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Codex <codex@openai.com>

---------

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Codex <codex@openai.com>

---------

Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Codex <codex@openai.com>

This branch was successfully deployed

1 active deployment
Preview — 0e7b6f61 Deployed Oct 27, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XXL 1,000+ effective changed lines (test files excluded in mixed PRs). vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants