Repository navigation
feat: extensions improvements - #278
Merged
Merged
Conversation
Checkpoint via cy-loop-tasks (iteration 2, phase B mode=tasks). Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 3, phase B mode=tasks). Focused Phase B gates passed; full make verify remains reserved for final program completion. Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 4, phase B mode=tasks). Scoped Phase C gates passed; the single monorepo make verify remains reserved for final program completion. Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 5, phase B mode=tasks). Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 6, phase B mode=tasks). Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 7, phase B mode=tasks). Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 8, phase B mode=tasks). Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 9, phase B mode=tasks). Visual recapture was explicitly waived by the operator; functional browser and focused gates passed. Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 10, phase B mode=tasks). Co-Authored-By: Codex <[email protected]>
Checkpoint via cy-loop-tasks (iteration 11, phase B mode=tasks). QA planning checkpoint: six targeted extension charters, one Marketplace/Skills canary, 676 materialized scenarios, and explicit coverage of Safety Invariants 1-17 plus ADRs 001-008. Co-Authored-By: Codex <[email protected]>
|
Too many files changed for review. ( |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Review skippedToo many files! This PR contains 492 files, which is 192 over the limit of 300. To get a review, narrow the scope: 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 (171)
📒 Files selected for processing (502)
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 new issues in 1 file · 4 warnings · score 89 / 100 (Great) · 0 fixed · vs 4 warnings
Reviewed by React Doctor for commit |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| useEffect(() => { | ||
| cursorRef.current = 0; | ||
| setStreamed({ entries: [], instance }); |
Contributor
There was a problem hiding this comment.
React Doctor · react-doctor/no-derived-state (warning)
Storing "streamed" in state when you can derive it from other values costs an extra render.
Fix → Work out the value while rendering (or with useMemo if it's expensive) instead of copying it into state and synchronizing it during render or through an effect. See https://react.dev/learn/you-might-not-need-an-effect#updating-state-based-on-props-or-state
|
|
||
| useEffect(() => { | ||
| cursorRef.current = 0; | ||
| setStreamed({ entries: [], instance }); |
Contributor
There was a problem hiding this comment.
React Doctor · react-hooks-js/set-state-in-effect (warning)
This synchronous effect update causes an extra render: Calling setState synchronously within an effect can trigger cascading renders. Prefer deriving or initializing the value before render. If the effect must read a browser API after mount, treat this as advisory or suppress it with // react-doctor-disable-next-line react-hooks-js/set-state-in-effect.
Fix → Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
- Update external systems with the latest state from React.
- Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
|
|
||
| useEffect(() => { | ||
| if (!enabled || name === "" || !follow) { | ||
| setStatus(follow ? "idle" : "paused"); |
Contributor
There was a problem hiding this comment.
React Doctor · react-doctor/no-derived-state (warning)
Storing "status" in state when you can derive it from other values costs an extra render.
Fix → Work out the value while rendering (or with useMemo if it's expensive) instead of copying it into state and synchronizing it during render or through an effect. See https://react.dev/learn/you-might-not-need-an-effect#updating-state-based-on-props-or-state
|
|
||
| useEffect(() => { | ||
| if (!enabled || name === "" || !follow) { | ||
| setStatus(follow ? "idle" : "paused"); |
Contributor
There was a problem hiding this comment.
React Doctor · react-hooks-js/set-state-in-effect (warning)
This synchronous effect update causes an extra render: Calling setState synchronously within an effect can trigger cascading renders. Prefer deriving or initializing the value before render. If the effect must read a browser API after mount, treat this as advisory or suppress it with // react-doctor-disable-next-line react-hooks-js/set-state-in-effect.
Fix → Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
- Update external systems with the latest state from React.
- Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
This was referenced Jul 30, 2026
Merged
Merged
Merged
Merged
This was referenced Aug 7, 2026
Merged
Merged
Merged
This was referenced Aug 9, 2026
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
This was referenced Aug 18, 2026
Merged
Merged
Merged
Merged
Merged
This was referenced Aug 27, 2026
Merged
Merged
This was referenced Sep 7, 2026
Merged
Merged
Merged
This was referenced Sep 15, 2026
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.
Summary
Completes the greenfield Extension DX overhaul across the daemon, public SDKs, CLI, HTTP/UDS APIs, native tools, Web, documentation, release automation, and living QA system. The branch implements the full Phase A–G MVP plus its QA planning/execution pair as one hard-cut contract, with no compatibility layer for the replaced extension model.
What shipped
SDK contracts and manifest v2
permissions.requiresandprovidescontracts, derived consent areas, deterministic__describeoutput, schema digests, minimum SDK versions, and rejection of legacy manifest fields.HookSourceExtensionwith explicit hook ordering and complete dispatch coverage.extensions.trust,extensions.sources,extensions.dev, and resource policy, including live config lifecycle metadata and precise diagnostics for removedextensions.marketplace.*keys.Code-first authoring and local development
compozy extension init,build, andvalidateflows with five embedded templates for Go and TypeScript extensions.dist/gen-<hash>publications, overlap protection, and release compatibility checks.Distribution, provenance, and contributed commands
Operability, Web, docs, and official skill
compozyskill, importable examples, release workflow, and migration guidance to the new hard-cut model.QA and review outcomes
Compozy Impact Audit
compozy__extensions_*authoring, development, distribution, provenance, publish, update, and removal toolset; command execution remains governed by the canonical tool dispatcher and approval policy.