Spike: evaluate MCPB desktop extension packaging after core demo stabilizes

[itprodirect]

Objective

Evaluate whether the repo should eventually include a Claude Desktop MCPB-style packaged extension for the sample MCP server, without implementing it yet.

Context

A one-click desktop extension could be valuable for non-technical users, but it is advanced distribution work. It should come after the README, primer, core server, and walkthrough are stable.

Scope

Create a short design/spike note such as:

docs/design/mcpb-packaging-spike.md

The note should answer:

• What problem would MCPB solve for this repo?
• Which users would benefit?
• What would the package include?
• What security risks would packaging introduce?
• What platforms should be tested?
• Should this live in this repo or a separate repo?

Acceptance criteria

• Design note explains why MCPB is delayed until after the core demo is stable.
• Design note identifies minimum packaging contents and manifest needs at a high level.
• Design note includes security warnings for local code execution, permissions, secrets, and sample-data-only use.
• Design note lists a future implementation checklist.
• No .mcpb bundle is created in this issue.
• No desktop-extension code is added in this issue.

Non-goals

• Do not implement MCPB packaging.
• Do not add Node/TypeScript unless a later issue explicitly requires it.
• Do not package claims workflows.
• Do not ask users to expose real claim folders.

Validation

ruff check .
mypy --strict .
pytest -q

Suggested Codex /goal summary

Create a design note that evaluates MCPB packaging as a future distribution option and keeps the current repo focused on the beginner learning path.