@ycodium-ai/plugin-api 0.2.3114 → 0.2.3120

package/README.md

@@ -255,6 +255,15 @@ over these kinds must handle the new member. `ctx.communication.records.send` ca
 `communication.read` can read who is looking (`person` is `null` once the viewer no longer qualifies); the
 handle expires with the call, and a stale handle is refused with the new `viewer-expired` reason.
 
+Create and fork use `ctx.threads.create(input)` and `ctx.threads.fork(input)`. Declare
+`thread.create` or `thread.fork`, keep the old command id as `requestId`, and omit `type`,
+`createdAt` and `createdBy`. Both return `{ sequence, status }`. Create grants execution ownership;
+when it names an `origin`, the parent must be admitted and the child cannot have a looser runtime
+mode. Fork checks the source thread, copies messages before a user-message cut point with fresh
+ids, and grants execution ownership only when the plugin owns the source. Fork keeps the source's
+runtime mode without creating a parent-child relationship. Generic dispatch remains available
+for these two commands while existing first-party callers migrate.
+
 API 11 moves starting a turn, changing thread metadata and answering questions to data ports. `ctx.commands.dispatch` no
 longer takes `thread.turn.start`, `thread.meta.update` or `thread.user-input.respond`: call `ctx.threads.turns.start(input)` and
 `ctx.threads.update(input)` and `ctx.threads.userInput.respond(input)` instead, still declaring those types in `commands.dispatch`. The input is the