Repository navigation
Conversation
Load automation lists across accessible organizations, preserve partial results, and support confirmed deletion and readable target-chat links behind the chat-automations experiment. Keep unsupported management actions disabled, cover interaction and visual states, and retain the backend parent dependency resolution after rebasing.
jakehwll
force-pushed
the
jakehwll/automations-list-page
branch
from
November 19, 2026 06:33
af3121e to
e420ee6
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Depends on #32079 (
tk/automations-api-read).Connects the automations list page to the organization-scoped API behind the
chat-automationsexperiment. It lists readable automations across accessible organizations, preserves usable results during partial failures, and supports filtering, confirmed deletion, and readable target-chat links.Creation, editing, manual runs, and enabling or disabling automations remain unavailable until the corresponding backend APIs land.
Implementation decisions and verification
The read API branch is the smallest backend dependency for this slice. The frontend uses generated types and per-organization React Query entries, invalidates only the owning list after either deletion outcome, and handles redacted owners and target chats. No backend, generated-type, or dependency changes are included relative to the parent; production placeholder data is replaced by shared test fixtures.
The row menu releases focus before opening deletion confirmation. Closing restores focus to the trigger, or to a stable page region after deletion. Status labels use the primary text color for light-theme contrast while retaining colored status dots.
Local validation passed: 95 unit tests, 53 Storybook tests,
pnpm format,pnpm check,pnpm lint, andmake lint/emdash. Frontend, test-value, and documentation self-reviews are complete. Storybook checks covered keyboard interaction, dialog focus, light/dark themes, and 320px reflow. Screenshots were returned in the task chat rather than uploaded to GitHub. Live-backend UAT was not run.Existing shared-component accessibility issues remain in filter combobox ARIA references and popup naming, empty-state heading order, and pending-delete focus/Escape behavior. Some offscreen contrast checks were inconclusive; status-label contrast was verified at 19.9:1 in both themes. Public documentation is deferred while
chat-automationsis an unsafe experiment.