# Plugin E2E Publication

This checklist covers the plugin-first publication path for `dyslex.ia`.

Do not run publication commands until the owner explicitly approves.

## Scope

Primary artifact:

- `.codex-plugin/plugin.json`
- `skills/`
- host adapter plans under `adapters/`

Compatibility artifact:

- `dyslexia mcp`
- `server.json`

The bridge path is optional and must not be the only published integration.

## 1. Local Source Validation

```bash
pnpm install
pnpm typecheck
pnpm lint
pnpm skills:validate
pnpm plugin:validate
pnpm test
pnpm build
```

Expected result:

- TypeScript passes.
- 16 skills validate.
- `.codex-plugin/plugin.json` validates.
- all adapters are `plugin-first`.
- optional bridge tests still pass.

## 2. Package Validation

```bash
npm pack --dry-run
npm pack
```

Expected package contents:

- `.codex-plugin/plugin.json`
- `skills/**`
- `adapters/**`
- `docs/**`
- `server.json`
- `dist/src/**`

## 3. Codex Local Plugin E2E

Use a disposable project and a disposable plugin marketplace.

```bash
codex plugin marketplace add <path-to-local-marketplace-root>
codex plugin add dyslex-ia@<marketplace-name>
codex plugin list
```

Then start a new Codex chat:

```text
/plugins
```

Expected result:

- `dyslex.ia` appears as an installed plugin.
- the 16 skills are available in the new chat.
- a deliberately ambiguous prompt triggers the relevant skills before implementation.

## 4. Codex Compatibility Bridge E2E

Only for compatibility:

```bash
codex mcp add dyslex-ia --env DYSLEXIA_SUPERPOWERS_PATH="C:\path\to\superpowers" --env DYSLEXIA_HOST=codex-cli -- npx -y @firou91/dyslex.ia mcp
codex mcp list
```

Expected result:

- the server initializes;
- tools/resources/prompts can be listed;
- real tool calls preserve technical tokens.

Remove the server after the test:

```bash
codex mcp remove dyslex-ia
```

## 5. Host Adapter E2E Matrix

Run the install plan generator for every supported host:

```bash
dyslexia install --host claude-code
dyslexia install --host antigravity
dyslexia install --host codex-app
dyslexia install --host codex-cli
dyslexia install --host cursor
dyslexia install --host factory-droid
dyslexia install --host copilot-cli
dyslexia install --host kimi-code
dyslexia install --host opencode
dyslexia install --host pi
```

For each host, verify:

- Superpowers is installed and detected;
- the generated `install-plan.json` says `integrationPriority: plugin-first`;
- the skills catalog path is valid;
- the compatibility bridge is marked optional only;
- user config mutations are backed up or manually approved.

## 6. npm Publication

Recommended route:

```bash
git tag v<version>
git push origin v<version>
```

GitHub Actions publishes with trusted publishing and provenance.

After release:

```bash
npm view @firou91/dyslex.ia version
npm audit signatures
```

## 7. Plugin Marketplace Publication

Codex marketplace publication is separate from npm publication.

Publish or register the plugin in the target marketplace only after npm and local plugin E2E pass.

For a local or team Codex marketplace:

```bash
codex plugin marketplace add <marketplace-root>
codex plugin add dyslex-ia@<marketplace-name>
```

For other agents, use the host-specific marketplace or plugin channel documented by that agent. If an agent has no public marketplace, publish installation instructions and keep the adapter as a static install plan until the channel exists.

## 8. Post-Publication Verification

From a clean project:

```bash
npm install @firou91/dyslex.ia
npx dyslexia doctor --verbose
npx dyslexia compatibility
```

Then verify each target agent:

- plugin visible in its plugin UI or list command;
- skills visible in a new session;
- ambiguous prompt scenario works;
- optional bridge compatibility still initializes where configured.