@ycodium-ai/plugin-api 0.2.3831 → 0.2.3904

package/README.md

@@ -61,7 +61,7 @@ import { definePlugin } from "@ycodium-ai/plugin-api";
 
 export default definePlugin({
   id: "my-plugin",
-  apiVersion: 60,
+  apiVersion: 66,
   activate: (ctx) => {
     ctx.log.info("hello");
 
@@ -290,12 +290,56 @@ sessions continue using the streaming process interface.
 
 ## THERE WILL BE COMPATIBILITY-BREAKING CHANGES
 
-The definition's `apiVersion` is a closed window: the host loads 60, and refuses every other
+The definition's `apiVersion` is a closed window: the host loads 66, and refuses every other
 value. Declare the version your plugin targets as a literal; do not read the host's
-`PLUGIN_API_VERSION` to make the declaration automatically match. The current API is 60. Plugins
+`PLUGIN_API_VERSION` to make the declaration automatically match. The current API is 66. Plugins
 targeting an older API are refused before activation; the message names the version the plugin
 declared and the one this Ycodium loads, and the plugin card offers an update. A plugin that
-declares a version newer than 60 is refused until Ycodium itself is updated, with no update button.
+declares a version newer than 66 is refused until Ycodium itself is updated, with no update button.
+
+API 66 adds an optional `reasonCode` to machine task failures. Every change is additive.
+
+- `MachineTaskFailure.reasonCode` is one of `git-missing`, `project-folder-missing` or `git-probe-failed`
+  when the built-in `project.sync` could not inspect the project folder; clients translate a coded reason
+  and show the English `reason` otherwise.
+- Every machine whose project folder is a Git checkout lists `project.sync` even without a tasks table; a
+  `sync` entry in `ycodium.json` replaces it. The action catalog allows 64 machine actions plus 33 project
+  entries.
+
+API 65 lets a thread annotation mark a conversation's tab: set `placement: "tab"` and `icon: "monitor"` on a
+`ui.threadAnnotations.command` row, and the tab gets the `tone` as a tinted background plus the icon, with `labelKey` as
+its name. Such a row stays out of the text badges in the sidebar and conversation header. Every change is additive.
+
+API 64 adds the command action for machine tasks. Every change is additive.
+
+- `MachineActionKind` gains `command`. A machine that declares the capability lists the action
+  `runtime.command`; machines that do not declare it do not list it.
+- `ctx.work.machineTasks.create` accepts `runtime.command` with `command`, optional `args`, optional `cwd`
+  (a path inside the project folder) and optional `timeoutSeconds`. The command runs with the executing
+  user's environment. A task for another machine still needs that machine's owner until same-account
+  trust (ADR-0041) lands.
+
+API 63 adds execution-machine consent for machine tasks. A local agent can run on its own machine
+without approval. Cross-machine tasks require the executing owner's explicit policy or a task-bound,
+single-use approval receipt. Human-only machineSettings.machineTasks.approve issues the receipt on
+the executing machine; work.machineTasks.respond carries optional approval and rememberProject.
+Project trust is optional machineTaskConfirmation.remoteProjectTrust, bound to both the home machine
+and project. Cross-machine same-account inference awaits ADR-0041.
+
+Machine-task failures may include optional `reasonCode` (`git-missing`, `project-folder-missing` or
+`git-probe-failed`) for localized UI text. `reason` remains the English fallback when no code is present;
+raw Git diagnostics stay in the log comment.
+
+API 62 adds `ctx.schedules.list` and `ctx.schedules.runs.list`, reads of a project's schedules, and an optional `repeat`
+on scheduled wake-up reads. Plugins cannot create or change schedules.
+
+API 61 lets a client admit the machines it is connected to in the background, without the Machines settings
+section being open. Every change is additive.
+
+- `projects.machines.list` output gains an optional `removedEnvironmentIds`: machines a person removed from the
+  project, which automatic admission skips.
+- `projects.machines.joinCode.create` input gains an optional `automaticEnvironmentId`: the code is bound to that
+  machine and cannot undo a person's removal. Omit it for an explicit invitation.
 
 API 60 registers this machine's runtime, proxy and provider maintenance in the data capability table. Every
 change is additive.
@@ -312,8 +356,7 @@ change is additive.
 - Machine actions add `runtime.restart` and `runtime.upgrade` (`MachineActionKind` gains `restart` and `upgrade`),
   and the action input takes an optional `targetVersion`. Action lists drop entries this build does not recognise
   instead of failing.
-
-API 60 also adds the skill directory. Every change is additive.
+  API 60 also adds the skill directory. Every change is additive.
 
 - `ctx.plugins.skillDirectory.search({ query, limit? })` searches skills.sh; each result names the GitHub
   `repository` it installs from, or `null`.
@@ -1125,7 +1168,7 @@ An empty page with a cursor still continues. All failures propagate unchanged, i
 `ThreadNotFoundError` when the thread is missing; use `isThreadNotFound(error)` to identify it.
 `ctx.communication.inbox.read` is gone; that port always rejected a plugin, because only the agent
 in the thread has its own inbox. Plugins targeting these earlier versions are refused on the current host;
-the minimum version is 60.
+the minimum version is 66.
 
 API 8 changed what the UI gets for a communication record. `ConversationCommunicationRecord`
 (from the conversation host's `useCommunicationRecord`) and `CommunicationViewExchange` carry `bodyState`, and their