copilotkit 4.9.50 → 4.10.0

package/onboarding/prompts/feature/open-generative-ui/start.md

@@ -3,10 +3,20 @@
 Treat this as a focused OSS enhancement. Orchestrate the work with separate read-only,
 implementation, and proof subagents, all restricted to the target project directory.
 
+Before any subagent or project process runs, capture the developer's existing work:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect
+```
+
+Keep the exact protected path list it prints and give that list to every subagent. No
+subagent may write a protected path or an overlapping path unless this run records the
+approved authorization before implementation.
+
 Before edits, have a research subagent identify the current CopilotKit runtime route,
 provider/chat component, agent id, package versions, existing middleware, sandbox/CSP
 constraints, and normal test/dev commands. Prove the existing app first with `/info`,
-`npx --yes copilotkit@4.9.50 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --yes copilotkit@4.10.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and a real frontend request when browser control is available. If the app is not an existing
 OSS CopilotKit app with a proven round trip, change nothing and direct the developer to the
 generic onboarding path first.
@@ -14,7 +24,7 @@ generic onboarding path first.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -24,7 +34,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.10.0 onboard read feature/stop
 ```
 
 Do not sign in, select an Intelligence project, create credentials, change the existing
@@ -38,10 +48,23 @@ Retry through a second retrieval method if needed. Setup is the documented
 Show a small plan covering that runtime option, the existing provider's renderer path,
 likely CSP/sandbox implications, tests, and a user-visible generated UI proof. Ask for approval separately.
 
-After approval, report the plan this run is about to implement:
+The plan must list every protected path it needs to change under `Authorization requested`,
+with one sentence explaining why. Write `None` when it needs none.
+
+After approval, record each approved path before implementation:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+```
+
+If an approved path changed after capture and no implementation step has run, add
+`--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
+authorize a path the approved plan did not list.
+
+Then report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.9.50 onboard read feature/open-generative-ui/implement`.
+Then run `npx --yes copilotkit@4.10.0 onboard read feature/open-generative-ui/implement`.

package/onboarding/prompts/feature/realtime-sync/implement.md

@@ -17,22 +17,51 @@ non-zero on an app that is working. Pass what `identifyUser` reads with a repeat
 It is not a defect to repair.
 
 Run focused tests and
-`npx --yes copilotkit@4.9.50 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --yes copilotkit@4.10.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 Repair changed-file failures and record changed paths and secret-safe validation
 evidence.
 
-When implementation validation passes, report it:
+After validation and each repair, run:
+
+```text
+npx --yes copilotkit@4.10.0 onboard audit
+```
+
+Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
+not a finding. Carry it into the final summary with its reason.
+
+If the audit fails, never repair, reset, or revert a protected path. Compare each named path
+with the implementation subagent's `Files changed` section. If that section does not name
+the path, accept the developer's external change:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --accept-external --path <path>
+```
+
+For an env file where the developer placed a requested credential, use
+`onboard protect --accept-credential --path <path>` instead. If the subagent names the path,
+or its report does not settle who changed it, ask the developer to allow the unplanned
+change. Only after they agree, record their answer:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+```
+
+Run the audit again after each accepted or authorized change. If it still fails, or starts
+with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.10.0 onboard read feature/stop
 ```
 
-If validation cannot pass, or this intent needs a prerequisite the app does not have, stop
-without further changes:
+When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase build-validated
 ```
 
+If validation cannot pass, or this intent needs a prerequisite the app does not have, use
+the feature stop route above without further changes.
+
 Otherwise run
-`npx --yes copilotkit@4.9.50 onboard read feature/realtime-sync/proof`.
+`npx --yes copilotkit@4.10.0 onboard read feature/realtime-sync/proof`.

package/onboarding/prompts/feature/realtime-sync/proof.md

@@ -14,15 +14,39 @@ the missing proof rather than claiming realtime works.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
-Run
-`npx --yes copilotkit@4.9.50 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
-with the actual outcome.
+After the final attempt, report the gate exactly once:
+
+```text
+npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+```
+
+Use `passed` only for proved two-client sync, `failed` for an attempted proof that failed,
+and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.10.0 onboard audit`.
+Continue only when it starts with `Status: passed`.
+
+If the audit fails, never repair, reset, or revert a protected path. Compare each named path
+with the proof subagent's `Files changed` section. If that section does not name the path,
+run `onboard protect --accept-external --path <path>`, or
+`onboard protect --accept-credential --path <path>` for an env file where the developer
+placed a requested credential. If the subagent names the path, or its report does not settle
+who changed it, ask the developer to allow it. Only after they agree, run
+`onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`.
+Run the audit again after each accepted or authorized change.
+
+If the audit still fails, or starts with `Status: blocked`, route out and stop:
+
+```text
+npx --yes copilotkit@4.10.0 onboard read feature/stop
+```
+
+When the audit passes, run
+`npx --yes copilotkit@4.10.0 onboard read feature/complete` with the actual outcome.

package/onboarding/prompts/feature/realtime-sync/start.md

@@ -4,6 +4,16 @@ Treat realtime sync as the Intelligence thread-realtime plane, not as a generic
 exercise. Act as the orchestrator and delegate read-only inspection, implementation, and
 two-context proof to subagents within the target project.
 
+Before any subagent or project process runs, capture the developer's existing work:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect
+```
+
+Keep the exact protected path list it prints and give that list to every subagent. No
+subagent may write a protected path or an overlapping path unless this run records the
+approved authorization before implementation.
+
 Before edits, inspect the current runtime, provider/chat, agent id, authenticated stable user
 identity, thread routes, existing Intelligence configuration (presence only), current websocket
 configuration, and normal test/dev commands. Prove the current frontend-to-runtime-to-agent
@@ -13,7 +23,7 @@ unchanged and direct the developer to generic onboarding first.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -23,7 +33,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.10.0 onboard read feature/stop
 ```
 
 Fetch the current official guides before planning:
@@ -41,10 +51,23 @@ from explicit developer-owned values; never derive one from the other. The clien
 `/api` itself, so an `apiUrl` that already ends in `/api` produces `/api/api/...`. Hosted setup may not
 need a `wsUrl`. Ask for approval separately.
 
-After approval, report the plan this run is about to implement:
+The plan must list every protected path it needs to change under `Authorization requested`,
+with one sentence explaining why. Write `None` when it needs none.
+
+After approval, record each approved path before implementation:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+```
+
+If an approved path changed after capture and no implementation step has run, add
+`--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
+authorize a path the approved plan did not list.
+
+Then report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.9.50 onboard read feature/realtime-sync/implement`.
+Then run `npx --yes copilotkit@4.10.0 onboard read feature/realtime-sync/implement`.

package/onboarding/prompts/feature/rich-threads/implement.md

@@ -2,7 +2,7 @@
 
 Delegate implementation to one subagent with the approved plan and fetched official guides.
 If repository evidence does not prove an existing valid Intelligence selection, run
-`npx --yes copilotkit@4.9.50 login --json` and follow its single streaming session. Then
+`npx --yes copilotkit@4.10.0 login --json` and follow its single streaming session. Then
 list projects, show the developer the current/recent choices, and select or create one only
 after they choose. Require the secret-safe selection summary to confirm the project file,
 environment file, and key provisioning; never display a key. If existing configuration is
@@ -20,22 +20,51 @@ non-zero on an app that is working. Pass what `identifyUser` reads with a repeat
 It is not a defect to repair.
 
 Run focused type/test commands, then start the app and run
-`npx --yes copilotkit@4.9.50 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --yes copilotkit@4.10.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 Repair changed-file failures before continuing. Record changed paths and secret-safe
 validation evidence.
 
-When implementation validation passes, report it:
+After validation and each repair, run:
+
+```text
+npx --yes copilotkit@4.10.0 onboard audit
+```
+
+Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
+not a finding. Carry it into the final summary with its reason.
+
+If the audit fails, never repair, reset, or revert a protected path. Compare each named path
+with the implementation subagent's `Files changed` section. If that section does not name
+the path, accept the developer's external change:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --accept-external --path <path>
+```
+
+For an env file where the developer placed a requested credential, use
+`onboard protect --accept-credential --path <path>` instead. If the subagent names the path,
+or its report does not settle who changed it, ask the developer to allow the unplanned
+change. Only after they agree, record their answer:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+```
+
+Run the audit again after each accepted or authorized change. If it still fails, or starts
+with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.10.0 onboard read feature/stop
 ```
 
-If validation cannot pass, or this intent needs a prerequisite the app does not have, stop
-without further changes:
+When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase build-validated
 ```
 
+If validation cannot pass, or this intent needs a prerequisite the app does not have, use
+the feature stop route above without further changes.
+
 Otherwise run
-`npx --yes copilotkit@4.9.50 onboard read feature/rich-threads/proof`.
+`npx --yes copilotkit@4.10.0 onboard read feature/rich-threads/proof`.

package/onboarding/prompts/feature/rich-threads/proof.md

@@ -13,15 +13,41 @@ running.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
-Then run
-`npx --yes copilotkit@4.9.50 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
-with the actual browser outcome.
+After the final attempt, report the gate exactly once:
+
+```text
+npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+```
+
+Use `passed` only for proved persistence and reopen, `failed` for an attempted proof that
+failed, and `skipped` when the proof could not run. Then run
+`npx --yes copilotkit@4.10.0 onboard audit`. Continue only when it starts with
+`Status: passed`.
+
+If the audit fails, never repair, reset, or revert a protected path. Compare each named path
+with the proof subagent's `Files changed` section. If that section does not name the path,
+run `onboard protect --accept-external --path <path>`, or
+`onboard protect --accept-credential --path <path>` for an env file where the developer
+placed a requested credential. If the subagent names the path, or its report does not settle
+who changed it, ask the developer to allow it. Only after they agree, run
+`onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`.
+Run the audit again after each accepted or authorized change.
+
+If the audit still fails, or starts with `Status: blocked`, route out and stop:
+
+```text
+npx --yes copilotkit@4.10.0 onboard read feature/stop
+```
+
+When the audit passes, run
+`npx --yes copilotkit@4.10.0 onboard read feature/complete` with the actual browser
+outcome.

package/onboarding/prompts/feature/rich-threads/start.md

@@ -4,6 +4,16 @@ Treat Rich Threads as a managed Intelligence feature layered onto the existing a
 reason to replace its agent or chat. Act as the orchestrator and delegate inspection,
 implementation, and proof to separate subagents within the target project.
 
+Before any subagent or project process runs, capture the developer's existing work:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect
+```
+
+Keep the exact protected path list it prints and give that list to every subagent. No
+subagent may write a protected path or an overlapping path unless this run records the
+approved authorization before implementation.
+
 Before edits, have a read-only subagent locate the runtime route, CopilotKit provider/chat,
 agent id, current thread UI or headless API, authentication boundary, stable server-side user
 identity source, current project configuration (presence only), and test/dev commands. Prove
@@ -13,7 +23,7 @@ an existing CopilotKit app, leave it unchanged and direct the developer to gener
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -23,7 +33,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.10.0 onboard read feature/stop
 ```
 
 Fetch the current official guides before planning:
@@ -43,10 +53,23 @@ The plan must name the documented Intelligence runtime wiring, server-side `iden
 catch-all thread routes, the selected UI (drawer or existing headless UI), preserved behavior,
 tests, and a reload/reopen proof. Ask for approval separately.
 
-After approval, report the plan this run is about to implement:
+The plan must list every protected path it needs to change under `Authorization requested`,
+with one sentence explaining why. Write `None` when it needs none.
+
+After approval, record each approved path before implementation:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+```
+
+If an approved path changed after capture and no implementation step has run, add
+`--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
+authorize a path the approved plan did not list.
+
+Then report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.9.50 onboard read feature/rich-threads/implement`.
+Then run `npx --yes copilotkit@4.10.0 onboard read feature/rich-threads/implement`.

package/onboarding/prompts/feature/stop.md

@@ -14,7 +14,7 @@ a `start` with no `--run` reprints the id this stopped run already holds, and on
 covering both reads as one run that did two different things.
 
 ```text
-npx --yes copilotkit@4.9.50 onboard start --run <new-12-character-id>
+npx --yes copilotkit@4.10.0 onboard start --run <new-12-character-id>
 ```
 
 Do not read a generic onboarding node from this run. A feature run and a generic run are
@@ -25,17 +25,20 @@ Do not run `onboard complete`. This run did not complete.
 If this run changed files before it stopped, list every path it changed and say whether it
 reverted them. A report that says only that the run stopped cannot be acted on.
 
-Send one short report. Run the feedback command without another developer question. The
+Send one short report. Run the friction command without another developer question. The
 CLI telemetry gate decides whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.50 onboard feedback
+npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
 ```
 
-Write the feedback message to the command's standard input, in at most four lines. Send no
+Write one or two sentences to standard input: the step you stopped at and what stopped it.
+Pick the category that fits from docs-missing, docs-wrong, docs-sequential, cli-gap,
+sdk-gap, environment, port-collision, credential, validation-loop, and other. Leave
+--cost-seconds off. A run that stopped cannot separate one papercut's cost from the cost
+of the whole run, so the estimate is optional on a stop report and only there. Send no
 secrets, source code, logs, or command output. The command refuses a report that carries
 any of those, prints the reason, and exits zero. A refused report is not a failed step.
 Reword it and send it again, or stop without a report. The command prints what it sent.
-This is the channel for a stop. Report friction only from a run that finished, never from
-here. If the CLI says that telemetry is disabled or unavailable, state that the report was
-not sent and stop without another question.
+This is the channel for a stop. If the CLI says the report was not sent, state what it said and
+stop without another question.

package/onboarding/prompts/feature/voice/implement.md

@@ -11,18 +11,47 @@ type/test command and start the app. Confirm `/info` reports
 `audioFileTranscriptionEnabled`, but treat it as capability evidence rather than completed
 voice proof. Record changed paths and validation results.
 
-When implementation validation passes, report it:
+After validation and each repair, run:
+
+```text
+npx --yes copilotkit@4.10.0 onboard audit
+```
+
+Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
+not a finding. Carry it into the final summary with its reason.
+
+If the audit fails, never repair, reset, or revert a protected path. Compare each named path
+with the implementation subagent's `Files changed` section. If that section does not name
+the path, accept the developer's external change:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --accept-external --path <path>
+```
+
+For an env file where the developer placed a requested credential, use
+`onboard protect --accept-credential --path <path>` instead. If the subagent names the path,
+or its report does not settle who changed it, ask the developer to allow the unplanned
+change. Only after they agree, record their answer:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+```
+
+Run the audit again after each accepted or authorized change. If it still fails, or starts
+with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.10.0 onboard read feature/stop
 ```
 
-If validation cannot pass, or this intent needs a prerequisite the app does not have, stop
-without further changes:
+When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase build-validated
 ```
 
+If validation cannot pass, or this intent needs a prerequisite the app does not have, use
+the feature stop route above without further changes.
+
 Otherwise run
-`npx --yes copilotkit@4.9.50 onboard read feature/voice/proof`.
+`npx --yes copilotkit@4.10.0 onboard read feature/voice/proof`.

package/onboarding/prompts/feature/voice/proof.md

@@ -13,15 +13,40 @@ path, agent response, app URL, and process IDs. Fix changed-file defects and rep
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
-Then run
-`npx --yes copilotkit@4.9.50 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
-with the actual surface outcome.
+After the final attempt, report the gate exactly once:
+
+```text
+npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+```
+
+Use `passed` only for proved voice input, `failed` for an attempted proof that failed, and
+`skipped` when the proof could not run. Then run `npx --yes copilotkit@4.10.0 onboard audit`.
+Continue only when it starts with `Status: passed`.
+
+If the audit fails, never repair, reset, or revert a protected path. Compare each named path
+with the proof subagent's `Files changed` section. If that section does not name the path,
+run `onboard protect --accept-external --path <path>`, or
+`onboard protect --accept-credential --path <path>` for an env file where the developer
+placed a requested credential. If the subagent names the path, or its report does not settle
+who changed it, ask the developer to allow it. Only after they agree, run
+`onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`.
+Run the audit again after each accepted or authorized change.
+
+If the audit still fails, or starts with `Status: blocked`, route out and stop:
+
+```text
+npx --yes copilotkit@4.10.0 onboard read feature/stop
+```
+
+When the audit passes, run
+`npx --yes copilotkit@4.10.0 onboard read feature/complete` with the actual surface
+outcome.

package/onboarding/prompts/feature/voice/start.md

@@ -3,17 +3,27 @@
 Treat voice as an OSS enhancement to an existing CopilotKit chat. Orchestrate with separate
 read-only, implementation, and proof subagents, each restricted to the target project.
 
+Before any subagent or project process runs, capture the developer's existing work:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect
+```
+
+Keep the exact protected path list it prints and give that list to every subagent. No
+subagent may write a protected path or an overlapping path unless this run records the
+approved authorization before implementation.
+
 Before edits, inspect the runtime route, CopilotKit provider/chat composer, current agent,
 existing provider credential variable names (presence only), package versions, browser
 permissions approach, and test/dev commands. Prove the existing OSS baseline with `/info`,
-`npx --yes copilotkit@4.9.50 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --yes copilotkit@4.10.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and a real UI request when a browser is available. If that baseline is absent, change nothing
 and direct the developer to generic onboarding first.
 
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -23,7 +33,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.10.0 onboard read feature/stop
 ```
 
 Do not run login, select Intelligence, create a credential, read a credential value, or
@@ -36,10 +46,23 @@ stop rather than writing a placeholder.
 Show a small plan for the documented transcription service, the existing composer, focused
 tests, and a microphone/canned-transcript proof. Ask for approval separately.
 
-After approval, report the plan this run is about to implement:
+The plan must list every protected path it needs to change under `Authorization requested`,
+with one sentence explaining why. Write `None` when it needs none.
+
+After approval, record each approved path before implementation:
+
+```text
+npx --yes copilotkit@4.10.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+```
+
+If an approved path changed after capture and no implementation step has run, add
+`--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
+authorize a path the approved plan did not list.
+
+Then report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.9.50 onboard read feature/voice/implement`.
+Then run `npx --yes copilotkit@4.10.0 onboard read feature/voice/implement`.

package/onboarding/prompts/framework/ag2.md

@@ -31,7 +31,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the A2UI documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/agno.md

@@ -34,7 +34,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, the documented dependencies and adapter, and the context documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/built-in.md

@@ -27,7 +27,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.