Evidence identity

Primary public sources

• Package: https://www.npmjs.com/package/superbee/v/0.1.3

• Source: https://github.com/Holaxis-ai/superbee/tree/v0.1.3

• Release commit: https://github.com/Holaxis-ai/superbee/commit/f4e1c37349627030f8201ff52028f71a9c92570a

Verification performed

The published npm package was installed into an isolated global prefix and invoked from its installed binary. Its version receipt agreed with the source commit and artifact hash above.

Read-only setup plans were exercised for Codex, Claude Code, Claude Desktop, and OpenCode. Each plan returned the documented host capability matrix, a single next action, a verification command, and the integrations requiring restart.

A disposable project then exercised:

1. init --create-only --dir .superbee with the default context-notes recipe;

2. generic typed document creation;

3. document read;

4. conventional-folder discovery from the project root;

5. home --no-update-check; and

6. status with zero reported conformance findings.

The document-open behavior is additionally grounded in generated 0.1.3 CLI help and the tagged implementation, which verifies the document before launching the existing local UI's corresponding DocPage route through the shared renderer.

Limits of this evidence

• The isolated-prefix setup probe intentionally did not mutate real host configuration.

• Live Skill, MCP, hook, and restart success remains host-specific and is verified by rerunning the setup conductor in that actual host.

• Windows is not claimed: npm's stable 0.1.3 package metadata excludes win32.

• This record establishes released behavior only. Later source on main is not stable-package evidence until it is published and independently identified.