@vypdev/copilot 3.10.5 → 3.10.7

package/README.md

@@ -31,6 +31,11 @@ flowchart LR
 
 AI capabilities require a configured agent runtime, an allowed model, and working authentication on the selected runner. Code-changing requests require repository write authority and run configured verification before commit/push. Release promotion follows the repository's merge policy. Installing Copilot does not grant permission to merge or deploy.
 
+On shared runners, the runtime verifies the executing workflow's native PR or
+branch concurrency before setup, so unrelated PRs can proceed independently.
+Custom and legacy workflows retain the conservative predecessor queue. See
+[workflow coordination and recovery](https://docs.page/vypdev/copilot/features#workflow-concurrency-and-sequential-execution).
+
 ## Start with the web assistant
 
 Use **Node.js 24 or newer**, `pnpm`, and a working checkout of the repository you want to configure:
@@ -69,6 +74,15 @@ Setup installs the selected workflows, Issue Forms, labels, issue types, Variabl
 
 Release templates are registry-neutral. Publishing your application or package requires your own build, validation, and deployment steps. This repository's npm publishing workflow is an example, not something setup installs into every consumer repository.
 
+## Browser extension development
+
+The private browser runtime is being built as a complete Chrome/Firefox/Safari
+product. H2 adds scoped runtime services and protected read sessions; the full
+feature inventory and local setup/control center remain required milestones.
+See the [runtime preview](docs/browser-extension/runtime.mdx) and
+[build, browser evidence and architecture guide](docs/development/browser-extension.mdx).
+No browser-store availability or complete-product acceptance is implied.
+
 ## Advanced integrations and contributing
 
 For a manually maintained workflow, use `vypdev/copilot@v3` and supply `token: ${{ secrets.PAT }}`. Follow the [manual integration instructions](https://docs.page/vypdev/copilot/how-to-use#manual-workflow-integration-advanced) to install the supporting resources and event workflows.

package/action.yml

@@ -35,6 +35,21 @@ inputs:
   single-action-operation-id:
     description: "Expected durable deployment operation ID for trusted continuation actions."
     default: ""
+  single-action-expected-revision:
+    description: "Exact current durable revision for replace_deployment_action."
+    default: ""
+  single-action-candidate-sha:
+    description: "Freshly validated full candidate SHA for replace_deployment_action."
+    default: ""
+  single-action-reviewed-source-sha:
+    description: "Exact corrected source reviewed before fresh replacement preparation. Separate from generated validated candidate SHA."
+    default: ""
+  single-action-production-base-sha:
+    description: "Native production base captured by replacement preflight."
+    default: ""
+  single-action-confirm-unpublished:
+    description: "Explicit maintainer confirmation that the exact replacement version is unpublished in every project registry."
+    default: "false"
   single-action-comment-id:
     description: "Optional issue comment ID to replace or append to."
     default: ""
@@ -57,7 +72,7 @@ inputs:
     description: "Run the trusted repository composite action before repository verification in generated workflows. Disabled by default."
     default: "false"
   issue-workflow-profile:
-    description: "JSON profile of enabled issue workflows."
+    description: "JSON profile of enabled issue workflows: schema 1 canonical fields, or schema 2 with explicit fieldMappings."
     default: ""
   branch-management-emoji:
     description: "Emoji to indicate branched issues. It will be ignored if emoji-labeled-title is false."