@girardmedia/bootspring 1.1.0

package/docs/integrations/claude-code.md

@@ -0,0 +1,42 @@
+# Bootspring + Claude Code
+
+## Goal
+
+Connect Claude Code to Bootspring MCP so Claude can discover capabilities, run workflows, and respect premium entitlements.
+
+## Quickstart
+
+1. Install and configure Bootspring in your project.
+2. Run MCP server:
+
+```bash
+npm run mcp
+```
+
+3. Register Bootspring MCP server in Claude Code MCP settings.
+4. On session start, call:
+- `bootspring_capabilities`
+
+## Recommended call pattern
+
+1. Session bootstrap:
+- `bootspring_capabilities`
+
+2. Context and planning:
+- `bootspring_context action=summary`
+- `bootspring_orchestrator action=analyze`
+- `bootspring_orchestrator action=recommend`
+
+3. Execution:
+- `bootspring_orchestrator action=start workflow="<workflow-key>"`
+- `bootspring_orchestrator action=next`
+- `bootspring_orchestrator action=checkpoint signal="<signal>"`
+
+4. Learning loop:
+- `bootspring_telemetry action=upload`
+
+## Entitlement behavior
+
+- Premium-blocked paths emit `premium_prompted`.
+- Unlocked premium usage emits `premium_unlocked`.
+- Use these events to drive upgrade UX in Claude workflows.

package/docs/integrations/codex.md

@@ -0,0 +1,42 @@
+# Bootspring + Codex
+
+## Goal
+
+Use Bootspring MCP as Codex's execution layer for capability discovery, workflow orchestration, and measurable outcomes.
+
+## Quickstart
+
+1. Ensure Bootspring is installed in project.
+2. Start MCP server:
+
+```bash
+npm run mcp
+```
+
+3. Configure Codex MCP client to connect to Bootspring server.
+4. At session start, read:
+- `bootspring_capabilities`
+
+## Recommended call pattern
+
+1. Discover and adapt:
+- `bootspring_capabilities`
+
+2. Build execution plan:
+- `bootspring_context action=summary`
+- `bootspring_orchestrator action=recommend context="<task context>" limit=5`
+
+3. Execute workflow:
+- `bootspring_orchestrator action=start workflow="<workflow-key>"`
+- `bootspring_orchestrator action=next`
+- `bootspring_orchestrator action=status`
+
+4. Improve over time:
+- `bootspring_skill action=search query="<topic>"`
+- `bootspring_telemetry action=upload`
+
+## Production guidance
+
+- Keep npm package lean; use server-mode manifests for premium data.
+- Enforce contract drift checks with `npm run verify:mcp-contract`.
+- Use telemetry to rank workflows/skills by completion efficiency.

package/docs/mcp-api-platform.md

@@ -0,0 +1,102 @@
+# Bootspring MCP API Platform
+
+Bootspring provides a portable MCP capability layer that can add value to any AI coding client, including Claude Code and Codex.
+
+## Why this helps standalone clients
+
+1. Faster startup
+- `bootspring_capabilities` tells clients what is available by tier and mode.
+
+2. Better execution
+- `bootspring_orchestrator` provides workflow packs with checkpoints and phase progression.
+
+3. Safer premium delivery
+- `bootspring_skill sync` and signed manifests keep npm builds lean while protecting premium value.
+
+4. Measurable product loop
+- Telemetry events track workflow completion and premium conversion signals.
+
+## Tool contract highlights
+
+1. `bootspring_capabilities`
+- Use on session start.
+- Enables adaptive UI/UX and feature toggles in client integrations.
+
+2. `bootspring_skill`
+- Supports bounded content via `summary`, `sections`, `maxChars`.
+- Supports remote catalog sync with checksum/signature safeguards.
+
+3. `bootspring_orchestrator`
+- Supports lifecycle actions: list/show/start/next/checkpoint/status.
+- Supports recommendation action: `recommend` (context + telemetry ranked workflows/skills).
+- Exposes completion signal progress for workflow packs.
+
+4. `bootspring_telemetry`
+- Supports `status`, `list`, `upload`, `clear`.
+- Bridges local event log to hosted analytics pipeline.
+- Upload supports batching and retry semantics for production transport reliability.
+
+## Contract artifact
+
+- Canonical v1 contract snapshot: `mcp/contracts/mcp-contract.v1.json`
+- Regenerate: `npm run build:mcp-contract`
+- Verify no drift: `npm run verify:mcp-contract`
+- CI enforcement: `.github/workflows/ci.yml` and `.github/workflows/publish.yml` run contract verification.
+- Registry source of truth: `mcp/registry.js` composes tool/resource definitions and handlers.
+
+## Entitlement model
+
+1. Local mode
+- Premium features can run locally for development and internal testing.
+
+2. Server mode
+- Premium skills and workflows require entitlement (`tier` or explicit entitlement flag).
+- Blocked access emits `premium_prompted`.
+- Granted premium access emits `premium_unlocked`.
+
+## Policy profiles
+
+- Policy profile is included in capabilities response (`access.policyProfile` and `policy`).
+- Current profiles: `startup`, `regulated`, `enterprise`.
+- Regulated profile currently blocks external skills and selected workflows (for governance-first environments).
+
+## Telemetry taxonomy
+
+- `workflow_started`
+- `workflow_step_advanced`
+- `workflow_checkpoint_completed`
+- `pack_signal_checkpoint`
+- `workflow_completed`
+- `premium_prompted`
+- `premium_unlocked`
+
+## Website handoff notes
+
+Use this doc to generate:
+
+1. Product page section: "Works with Claude Code and Codex"
+2. Integration guide: "MCP quickstart"
+3. Enterprise page: "Entitlements, signatures, and audit-ready telemetry"
+
+See implementation-ready client docs:
+- `docs/integrations/claude-code.md`
+- `docs/integrations/codex.md`
+
+## Integration checklist (for any standalone client)
+
+1. Call `bootspring_capabilities` at session start and cache response for the session.
+2. Use tool `inputSchema` action enums as the single source of truth for UI/actions.
+3. Route premium-denied responses to an upgrade surface keyed by `premium_prompted`.
+4. Periodically call `bootspring_telemetry action=upload` (or after workflow completion).
+5. Log client type (`claude-code`, `codex`, custom) in telemetry payload metadata.
+
+## Why this is hard to replace
+
+1. Curated execution packs
+- Bootspring gives opinionated path-to-outcome workflows, not just command wrappers.
+
+2. Entitlement-safe premium model
+- Premium assets can stay server-delivered and signature-validated outside npm bundles.
+
+3. Outcome analytics loop
+- Workflow checkpoints and premium boundaries are instrumented as product signals, enabling compounding optimization.