# Publishing notes for `My Wallet for OpenClaw`

This directory is the bundle-first OpenClaw distribution unit for the local wallet integration in this repository.
It is intended to be reviewable and publishable as a bundle without changing wallet runtime semantics.

## What ships

The staged bundle and `.tgz` archive should contain:

- `.codex-plugin/plugin.json`
- `.mcp.json`
- `package.json`
- `README.md`
- `PUBLISHING.md`
- `assets/`
- `launcher/`
- `payload/`
- `skills/`

The bundle manifest, bundle MCP config, launcher, skills, assets, and runtime payload inputs are now staged during the bundle build rather than maintained as tracked mirror copies in this source directory.

## Compatibility identifiers

Public listing copy should use `My Wallet for OpenClaw`.
The current machine-facing compatibility identifiers are:

- Bundle id: `mywallet`
- Staged archive: `mywallet.tgz`

Those compatibility identifiers are intentionally preserved for the current OpenClaw bundle contract and should not be changed in this slice.

## Release checklist

1. Run the focused bundle test:
   ```bash
   npm run test:headless:openclaw:bundle
   ```
2. Rebuild the staged bundle and archive:
   ```bash
   npm run build:headless:openclaw:bundle
   ```
3. Run at least one bundle-level smoke path against the staged archive:
   ```bash
   npm run test:headless:openclaw:smoke
   ```
4. Inspect the staged artifact before making any publication claim:
   ```bash
   openclaw plugins inspect mywallet
   tar -tzf ./headless/platforms/openclaw/bundle/.dist/mywallet.tgz | sort
   ```

## What this slice does not claim

- It does not claim the bundle is already published to ClawHub or accepted by any registry.
- It does not claim installer behavior beyond the documented local bundle/archive flows.
- It does not introduce native-plugin runtime semantics, host-owned wallet behavior, or approval bypasses.

## Reviewer watch-outs

- `mywallet_*` tool names are the canonical contract and must stay unchanged here.
- The staged bundle-root `.mcp.json` must continue to own the bundled subprocess wiring.
- `package.json`, the staged `.codex-plugin/plugin.json`, `README.md`, and the staged archive contents should stay aligned.
- The OpenClaw smoke path should stay Docker-only and archive-driven; do not reintroduce temp-home or host-checkout assumptions.
- If OpenClaw CLI misclassifies the bundle during local install, that is an OpenClaw-side installer quirk, not a reason to reintroduce native-plugin packaging in this slice.
