open-index/open-npm huggingface dataset:
npm package: @murphai/contracts
Description: Owns the frozen vault contracts for the Murph baseline:
Latest version: 0.2.6

# `@murphai/contracts`

Owns the frozen vault contracts for the Murph baseline:

- canonical Zod schemas and parse helpers
- TypeScript declarations
- example records and frontmatter documents
- derived JSON Schema artifacts under `generated/`

Surface split:

- `@murphai/contracts` exports the canonical Zod-first runtime surface.
- `@murphai/contracts/schemas` exports the derived JSON Schema objects for artifact consumers.

Package-local commands:

- `pnpm --dir packages/contracts build`
- `pnpm --dir packages/contracts generate`
- `pnpm --dir packages/contracts verify`

Build layout:

- library entrypoints emit to `dist/*.js` and `dist/*.d.ts`
- package-local scripts emit to `dist/scripts/*.js`
npm package: @murphai/gateway-core
Description: Dedicated transport-neutral gateway boundary package for Murph.
Latest version: 0.2.6

# @murphai/gateway-core

Dedicated transport-neutral gateway boundary package for Murph.

This package owns Murph's gateway contracts, route helpers, projection/snapshot helpers, opaque ids, and event-log utilities. It intentionally does not depend on the assistant, inbox, or local runtime-state stacks.

Consumers that need the local vault-backed gateway adapter should depend on `@murphai/gateway-local` explicitly. That package owns the rebuildable `.runtime/projections/gateway.sqlite` source-backed projection store plus the local send/read wrapper surface.
npm package: @murphai/hosted-execution
Description: Shared hosted-execution helpers for the hosted `apps/web` control plane and the Cloudflare execution worker.
Latest version: 0.2.6

# `@murphai/hosted-execution`

Shared hosted-execution helpers for the hosted `apps/web` control plane and the
Cloudflare execution worker.

## Scope

- own the shared hosted execution dispatch and status contract types
- define hosted execution auth header names and request-canonicalization helpers
- normalize the shared hosted execution env variables that are deployment-vendor neutral
- build stable internal route paths for dispatch and runner side-effect calls
- own the shared dispatch contracts, signed callback routes, immutable outbox payload envelopes, and staged dispatch-payload ref helpers
- provide the typed shared dispatch/control helpers while keeping deployed auth adapters app-local

## Contract

- signed callback canonicalization stays timestamped and request-bound across app-local signers and verifiers
- the shared dispatch/status path layout stays stable between callers and the worker
- vendor-neutral env naming stays canonical so hosted web and Cloudflare do not drift
- this package owns only the shared hosted-execution transport seam: dispatch/status codecs, route builders, outbox payload helpers, auth header names, and canonicalization helpers
- deployment topology stays app-local: shared packages must not own worker hostnames, callback base-url defaults, or proxy-vs-server inference
- app-local auth adapters still own deployment-specific bearer token acquisition plus callback signing and verification
- operator-facing hosted public-origin fallback and Cloudflare callback-key config stay app-local and are intentionally documented in `apps/web/README.md`, not here
- Cloudflare operational control routes are private owner APIs, not part of this public package
- hosted device-sync runtime snapshot/apply/connect-link contracts live under `@murphai/device-syncd/hosted-runtime`
npm package: @murphai/openclaw-plugin
Description: First-party OpenClaw bundle for Murph.
Latest version: 0.2.6

# @murphai/openclaw-plugin

First-party OpenClaw bundle for Murph.

This package intentionally stays small. It ships a Murph skill bundle that teaches OpenClaw to use the existing `vault-cli` surface against the operator's vault instead of trying to spin up or manage a second Murph assistant runtime inside OpenClaw.

## What It Installs

- one OpenClaw-compatible bundle in the default Claude-layout shape under `skills/**`
- one Murph skill that teaches OpenClaw to use `vault-cli` through OpenClaw's built-in `exec` tool
- no separate daemon, no duplicate assistant state, and no OpenClaw-owned Murph runtime

## Install

Install Murph first so `vault-cli` is available on `PATH`:

```bash
npm install -g @murphai/murph@latest
murph onboard
```

Then install the OpenClaw bundle:

```bash
openclaw plugins install @murphai/openclaw-plugin
openclaw gateway restart
```

After that, new OpenClaw sessions can use Murph directly over the configured vault.

## Why This Package Is Skill-First

The integration is intentionally vault-first and simple:

- Murph continues to own the vault and its canonical write paths.
- OpenClaw learns how to call `vault-cli` well.
- Operators keep using the same Murph vault they already onboarded.
- There is no second Murph assistant runtime to configure, migrate, or reconcile.

## Requirements

- `vault-cli` must be installed and available on the host `PATH`.
- Murph should already know the default vault, usually because `murph onboard` was run.
- If you run sandboxed OpenClaw agents, `vault-cli` also needs to exist inside the sandbox image or setup command.

## Local Development

```bash
openclaw plugins install ./packages/openclaw-plugin
openclaw gateway restart
```