Repository navigation
feat: deliver the command palette operating surface - #441
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Too many files changed for review (870 files, 100 file limit). |
Contributor
|
Important Review skippedToo many files! This PR contains 753 files, which is 453 over the limit of 300. To get a review, reduce the PR to 300 files or fewer by splitting it into smaller PRs or changing its base branch. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (117)
📒 Files selected for processing (753)
You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
|
React Doctor found 4 issues in 4 files · 2 errors & 2 warnings · score 81 / 100 (Needs work) · vs Errors
2 warnings
|
Checkpoint via cy-loop-tasks (iteration 3, phase B mode=tasks). Registry-driven web projection, unified dispatch, cache/stream hydration, and core surface absorption. E2E execution and visual evidence remain deferred to the QA tail by the accepted workflow policy. Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 8, phase B mode=tasks). Validated by current full gate fingerprint 9fcaeb530163cd8196e0704079dd398bf8469b69; visual and scenario QA remain assigned to task_12. Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 14, phase B mode=tasks). Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 16, phase B mode=tasks). Co-Authored-By: Codex <[email protected]>
pedronauck
force-pushed
the
cmd-palette
branch
from
August 21, 2026 00:44
08da5af to
0131342
Compare
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| } | ||
| setSubmitting(true); | ||
| setSubmitError(""); | ||
| try { |
Contributor
There was a problem hiding this comment.
React Doctor · react-hooks-js/todo (error)
This component misses React Compiler's automatic memoization & re-renders more than it should. Rewrite the flagged code so the compiler can optimize it.
Fix → Todo: (BuildHIR::lowerStatement) Handle TryStatement with a finalizer ('finally') clause
| const tiles = visibleGridTiles(grid, query, filterLocally); | ||
| const rows = virtualGridRows(grid.sections, columns, tiles); | ||
| // oxlint-disable-next-line react/incompatible-library -- virtualizer state is isolated inside this compiler boundary. | ||
| const virtualizer = useVirtualizer<HTMLDivElement, HTMLDivElement>({ |
Contributor
There was a problem hiding this comment.
React Doctor · react-hooks-js/incompatible-library (error)
This component misses React Compiler's automatic memoization & re-renders more than it should: Compilation Skipped: Use of incompatible library. It's how the library works, not a bug in your code. Memoize values you pass from it into other memoized components, or suppress it with // react-doctor-disable-next-line react-hooks-js/incompatible-library.
Fix → This API returns functions which cannot be memoized without leading to stale UI. To prevent this, by default React Compiler will skip memoizing this component/hook. However, you may see issues if values from this API are passed to other components/hooks that are memoized.
| } | ||
| const nextQuery = searchText ?? ""; | ||
| store.trigger.searchEchoed({ query: nextQuery }); | ||
| onQueryChange(nextQuery); |
Contributor
There was a problem hiding this comment.
React Doctor · react-doctor/no-pass-data-to-parent (warning)
Handing data back to a parent from a useEffect costs your users an extra render.
Fix → Fetch the data in the parent and pass it down as a prop (or return it from the hook), instead of handing it back up through a prop callback in a useEffect. See https://react.dev/learn/you-might-not-need-an-effect#passing-data-to-the-parent
| setLocalValue(current => { | ||
| const resolved = | ||
| typeof nextValue === "function" ? (nextValue as (current: T) => T)(current) : nextValue; | ||
| cachedState.set(key, resolved); |
Contributor
There was a problem hiding this comment.
React Doctor · react-doctor/no-side-effect-in-state-updater-function (warning)
This side-effecting call runs inside a state updater, which React may invoke more than once. Move it outside the setter after computing the next state.
Fix → React may replay a state updater, so callbacks, analytics, and persistence inside it can run more than once. Compute state purely, then perform the side effect outside the setter.
This was referenced Aug 21, 2026
Merged
Merged
Merged
Merged
This was referenced Sep 10, 2026
Merged
Merged
Merged
Merged
This was referenced Sep 27, 2026
Merged
Merged
This was referenced Oct 6, 2026
Merged
Merged
Merged
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
1 participant
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.
What & why
This delivers the command palette as an end-to-end CompozyOS operating surface owned by the daemon instead of a web-only launcher.
How you verified it
Verification completed before the operator deferred the final QA round:
make codegen-checkpassed.The final
make gate,make gate-full, real-user QA walks, and screenshot evidence were not run for the final tree by operator request. They are intentionally deferred to a follow-up QA round after this PR is open.The attempted isolated QA kickoff activated all 11 scenario tasks, but runtime-owned journey logging made no progress during the 300-second observation window. The strict audit was deferred. The lab was torn down successfully with
teardown.jsonreporting"clean": trueand no surviving processes.Impact
Compozy Impact Audit:
internal/tools/builtin, OpenAPI, CLI, and transport parity.internal/extension,sdk/*, desktop, web, and site docs.skills/compozy/references/configuration.mdwas updated for the public configuration behavior.Release notes
Features
Fixes
Testing and documentation
QA
Final status: Deferred by operator to a post-PR QA round.
Coverage: 0 of 9 real-user charters completed. One isolated kickoff activated 11 tasks; observation then stalled without journey-log progress.
Issues: Not assessed by the deferred real-user QA round.
Follow-up: Run the full scenario suite, capture visual evidence, repair any findings, then run one final
make gate-full.Full report:
docs/qa/reports/2026-08-20-command-palette.mdChecklist
make gatepasses locally with no errors or warnings — deferred by operator.