@prismer/runtime 2.0.7 → 2.0.8

package/built-in-skills/claim-agent-ownership/SKILL.md

@@ -0,0 +1,254 @@
+---
+name: claim-agent-ownership
+description: |
+  Orchestrator skill for resolving multi-daemon binding contention. Use when you (the
+  orchestrator) detect an `agent.binding.contested` sync event indicating two daemons
+  are racing for the same agent — explicitly rebind ownership to a chosen target daemon
+  so subsequent dispatches route deterministically. Implements Gap G-2-⑤ on top of the
+  Wave 2-B2 `/api/im/agent-bindings/:agentImUserId/rebind` endpoint.
+applies_to: [hermes, claude-code, openclaw, codex]
+requires:
+  - aip-identity
+phaseModel:
+  defaultPhase: tool_use
+version: 1
+---
+
+# Claim Agent Ownership
+
+When two daemons (typically Mac Studio at home + a k8s pod) both run `agent.host.declare`
+for the same agent, the first one wins ownership and the second registers a
+**contested** binding. The user UI surfaces a "binding contested" badge and the cloud's
+`resolveAgentDaemonRoute` keeps routing dispatches to the original owner — but a
+human-driven or orchestrator-driven decision is needed to converge.
+
+This skill is the **orchestrator's tool for that decision**. It calls the server's
+authoritative rebind endpoint, which atomically:
+
+1. flips `im_agent_bindings.boundDaemonId` to the chosen target daemon
+2. writes an audit row with `boundBy='user-explicit'` (or `'orchestrator'`)
+3. returns the **in-flight task count** on the previous owner so the orchestrator can
+   wait / drain before redirecting traffic
+4. emits a sync event (`agent.binding.rebound`) so other daemons drop their hosting
+   state for the agent
+
+## When to use
+
+- A sync event with type `agent.binding.contested` arrives in your inbox.
+- A user explicitly asks "the agent is bouncing between machines — pin it to my laptop".
+- You (orchestrator) decide to migrate an agent off a misbehaving daemon (high error
+  rate, stale heartbeats, etc.) and a target is available.
+- Devices panel shows >1 daemon claiming the same agent and the user requests
+  arbitration.
+
+**Do not** use it for:
+
+- Healthy single-daemon bindings (no contention — nothing to claim).
+- Agents the orchestrator does not own / has no permission for (server rejects 403).
+- Routing decisions that should be reversible at the chat-message level (use
+  `metadata.daemonId` overrides in single dispatches instead).
+
+## API
+
+There is **no generic `cloud im get` / `cloud im post`** subcommand in the
+runtime CLI today (release 201 audit, `sdk/prismer-cloud/runtime/src/cli/`).
+A dedicated `cloud agent rebind` verb is not landed either. The skill calls
+the cloud HTTP endpoint directly via `curl` (or the equivalent fetch from the
+orchestrator's MCP runtime), authenticating with the daemon API key already
+present in the environment as `$PRISMER_API_KEY`:
+
+```bash
+# Inspect the current bindings first.
+curl -fsS \
+  -H "Authorization: Bearer $PRISMER_API_KEY" \
+  "$PRISMER_CLOUD_BASE/api/im/workspaces/<workspaceId>/agent-bindings"
+
+# Issue the rebind. Requires workspace owner / active orchestrator / admin.
+curl -fsS \
+  -X POST \
+  -H "Authorization: Bearer $PRISMER_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"targetDaemonId":"<daemonId>","targetDaemonKind":"local","reason":"<short reason>"}' \
+  "$PRISMER_CLOUD_BASE/api/im/agent-bindings/<agentImUserId>/rebind"
+```
+
+`PRISMER_CLOUD_BASE` defaults to the cloud the daemon paired with
+(`https://prismer.cloud` in prod, `http://127.0.0.1:3000` in local dev).
+
+For pure-API use (orchestrator runtime, MCP tool, etc.), the underlying call is:
+
+```http
+POST /api/im/agent-bindings/:agentImUserId/rebind
+Authorization: Bearer <daemon api key>
+Content-Type: application/json
+
+{
+  "targetDaemonId":   "daemon-mac-studio-01",   // required, must exist in workspace
+  "targetDaemonKind": "local",                  // optional: 'k8s' | 'local' | 'edge'
+  "targetDaemonLabel": "Mac Studio (home)",     // optional display label
+  "reason":           "user prefers desktop daemon while on home network"
+}
+```
+
+Successful response:
+
+```json
+{
+  "ok": true,
+  "data": {
+    "binding": {
+      "agentImUserId":     "u_agent_ceo",
+      "boundDaemonId":     "daemon-mac-studio-01",
+      "boundDaemonKind":   "local",
+      "boundDaemonLabel":  "Mac Studio (home)",
+      "boundBy":           "user-explicit",
+      "boundAt":           "2026-05-22T16:30:00.000Z"
+    },
+    "inFlightTaskCount":   3,
+    "previousDaemonId":    "daemon-k8s-pod-7f4"
+  }
+}
+```
+
+Failure modes worth handling explicitly:
+
+| Status                | Code (in body)                  | Meaning                                                              |
+| --------------------- | ------------------------------- | -------------------------------------------------------------------- |
+| `400`                 | `target daemon ... not registered` | Target daemonId not in `im_containers` for this workspace.        |
+| `400` / missing field | `targetDaemonId is required`    | Body parse / missing required field — surface as developer error. |
+| `403`                 | `Forbidden`                     | Caller is not workspace owner / orchestrator / admin.             |
+| `404`                 | `Agent not found ...`           | Agent has no `im_agent_cards` row (deleted? wrong id?).           |
+| `404`                 | `No binding row exists ...`     | Agent never ran host.declare. Tell the daemon to declare first.   |
+| `409`                 | `target daemon ... is stopped`  | Target container has `stoppedAt` set — pick a different target.   |
+
+## Workflow
+
+1. **Subscribe to `agent.binding.contested` sync events.** The orchestrator's sync inbox
+   delivers these out of band; the skill consumes them.
+2. **Resolve the target daemon.** Read the binding list and pick the daemon you want to
+   keep — usually the one with:
+   - smaller `lastDispatchAt` skew (fresher),
+   - matching device kind to user preference (local vs k8s),
+   - lower `contestCount` (less flapping).
+3. **Decide whether to drain.** If `inFlightTaskCount > 0` on the previous owner,
+   surface this to the user ("3 tasks finishing on the old daemon before switching").
+   The orchestrator should usually let those finish — the rebind takes effect for
+   subsequent dispatches, in-flight tasks complete via the existing route.
+4. **Call rebind.** Pass `targetDaemonId` + `reason`. Optional kind/label improve UI
+   readability.
+5. **Verify.** Read `/workspaces/:wsId/agent-bindings` again and confirm `boundDaemonId`
+   matches your target. If still divergent, the daemon may have re-declared between
+   read and write — repeat once.
+
+## Operating Rules
+
+- **Never rebind to a daemon you cannot see in the workspace listing.** The server
+  validates via `im_containers` — calling with a fictional id returns 400. Don't guess.
+- **Always supply a reason.** It's persisted in the audit trail and surfaces in the
+  Devices panel ("rebound by orchestrator at HH:MM: <reason>"). Empty reason becomes
+  the default `'unspecified'` which is opaque to the user.
+- **One rebind per binding per minute (orchestrator self-limit).** The endpoint is
+  not throttled, but flapping rebinds spam sync events and confuse the user. If the
+  contest re-fires within 60s of a rebind, escalate to the human — don't auto-rebind
+  again.
+- **Wait for the dispatch in-flight count to drain before declaring "done"** if the
+  user is observing. The cloud routes new dispatches immediately, but the prior
+  daemon's outstanding tasks still finish on it.
+
+## Output reporting
+
+After successfully calling rebind:
+
+```
+[claim-agent-ownership] rebound agent=<agentImUserId> from=<previousDaemonId>
+                       to=<targetDaemonId> in-flight-on-previous=<n>
+                       reason="<reason>"
+```
+
+Then surface to the user as a chat message: who you rebound, where to, why, and how
+many tasks are still finishing on the old daemon (if any).
+
+After a 4xx/5xx failure: report the HTTP status + the server's error code + message
+verbatim. Do not silently retry on 400/403/404 — those need human attention.
+
+## Backing capabilities
+
+- **Server endpoint:** `POST /api/im/agent-bindings/:agentImUserId/rebind`
+  (Wave 2-B2, `src/im/api/agent-bindings.ts`)
+- **Data model:** `IMAgentBinding` (migration 410, fields:
+  `boundDaemonId`, `boundDaemonKind`, `boundDaemonLabel`, `boundBy`, `contestCount`,
+  `contestedSince`)
+- **Sync event consumed:** `agent.binding.contested` — emitted by `AgentBindingService`
+  when a second daemon declares an agent already bound to a different daemon.
+- **Sync event emitted (server-side):** `agent.binding.rebound` — broadcast after
+  successful rebind so all daemons + UI consumers drop stale routing state.
+- **Audit trail:** Each rebind writes an `IMTaskLog`-style entry with
+  `boundBy='user-explicit'` / `'orchestrator'` and the supplied reason; visible in the
+  Devices panel.
+
+## Examples
+
+### Example 1 — Orchestrator handling a contest event
+
+```
+Inbox event: { type: 'agent.binding.contested', agentImUserId: 'u_agent_ceo',
+               existingDaemonId: 'daemon-k8s-pod-7f4',
+               contendingDaemonId: 'daemon-mac-studio-01' }
+
+Orchestrator inspects bindings:
+  curl -H "Authorization: Bearer $PRISMER_API_KEY" \
+    "$PRISMER_CLOUD_BASE/api/im/workspaces/ws_abc/agent-bindings"
+
+Decision: user is on home network, prefer Mac Studio (local).
+
+Action:
+  curl -X POST -H "Authorization: Bearer $PRISMER_API_KEY" \
+    -H "Content-Type: application/json" \
+    -d '{"targetDaemonId":"daemon-mac-studio-01","targetDaemonKind":"local",
+         "reason":"user on home network, preferring local daemon"}' \
+    "$PRISMER_CLOUD_BASE/api/im/agent-bindings/u_agent_ceo/rebind"
+
+Response: boundDaemonId='daemon-mac-studio-01', inFlightTaskCount=2
+Orchestrator messages user: "Pinned CEO agent to your Mac Studio. 2 tasks finishing on
+                            the cloud pod first."
+```
+
+### Example 2 — User explicit "pin agent X to laptop"
+
+```
+User: "Make sure DesignAgent always runs on my laptop, not the k8s pod."
+
+Orchestrator (after reading bindings):
+  curl -X POST -H "Authorization: Bearer $PRISMER_API_KEY" \
+    -H "Content-Type: application/json" \
+    -d '{"targetDaemonId":"daemon-laptop-9a","targetDaemonKind":"local",
+         "reason":"user-explicit: pin to laptop"}' \
+    "$PRISMER_CLOUD_BASE/api/im/agent-bindings/u_design_agent/rebind"
+```
+
+### Example 3 — Failure to handle gracefully
+
+```
+Orchestrator tries to rebind to a daemon that just went offline:
+  POST .../rebind { targetDaemonId: "daemon-k8s-pod-7f4", ... }
+  ← 409 { error: "target daemon daemon-k8s-pod-7f4 is stopped" }
+
+Orchestrator should:
+  1. Re-read /workspaces/<wsId>/agent-bindings to find a live alternative.
+  2. If only one daemon remains and it's already the current owner, do nothing.
+  3. Otherwise retry with the live candidate.
+```
+
+## Anti-patterns
+
+- ❌ Calling rebind on every contested event without thinking — flap creates user
+  confusion. Wait until the user signals preference or a clear health signal arrives.
+- ❌ Supplying `targetDaemonKind` / `targetDaemonLabel` that contradict the server's
+  inference (e.g. claiming `kind=k8s` for a `deviceType=local` container). The server
+  trusts the body so misuse leads to a wrong-shaped UI badge.
+- ❌ Treating `inFlightTaskCount > 0` as a hard error — it's informational. The cloud
+  has already redirected new dispatches; existing in-flight work simply finishes on
+  the old route.
+- ❌ Re-binding while another orchestrator is also working on the same workspace
+  without coordination. Use the workspace's orchestrator lease (`orchestratorAgentId`)
+  to make sure you're the active arbiter before mutating bindings.

package/built-in-skills/claude-api/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Anthropic, PBC.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.