Community recipes and independently versioned integrations for Superbee.
recipes/contains declarative models and Connector mappings.integrations/contains provider adapters, synthetic fixtures and their tests.- Core, the source engine and CLI loading belong in the Superbee repository.
Recipes install as data. Code integrations require an explicit installation and trust decision; contributing to this repository does not automatically enable code in a user's CLI or hosted workspace.
See CONTRIBUTING.md for the contribution boundary.
integrations/github contains the independently versioned GitHub issue
adapter and generated recipe payloads. Its private package.json supplies the existing loader
identity @superbee/integration-github, compatibility and build metadata. Integrations are
acquired from pinned Git checkouts; integration npm publication is disabled under the current
policy. Core, CLI and development tools continue to use their existing npm channels.
The canonical source-feeds and work-items
recipes live here. The GitHub example exercises the provider profile;
the Linear example proves the shared model with an offline projection
double. Linear is not an admitted runtime integration.
The local snapshot examples wrap caller-associated camera and nested
benchmark data for deliberately linked targets. Core owns mapping, reconciliation, generation
admission and input applicability through its
snapshot contract;
this checkout supplies data-only wrappers and declarations. The prior reviewed Core34 checkout
passed installed consumer journeys with stable CLI 0.4.3 (npm latest), which embeds Core 0.2.0-pre.34. These fixtures claim
no real render or benchmark execution. The comparison-review recipe
adds human discrepancies and revision-bound decisions; its two synthetic journeys
reuse these observations and the existing Artifact command without registering executable code.
Use a reviewed full 40-character commit SHA for REVIEWED_FULL_COMMIT_SHA. Verify that checkout
before trusting and building it. This checkout requires embedded Core 0.2.0-pre.37 exactly.
Install the published matching Core before building, and use a CLI with this helper pin.
Prerelease CLI 0.4.4-pre.2 is published on npm next from source tag
v0.4.4-pre.2
(008e00fa04d0ff726dfa3d6da80343cbcf230309), embedding Core 0.2.0-pre.37.
The library finalizer
and CLI finalizer
verified the published artifacts. Installed consumer qualification is described below.
Historical stable CLI 0.4.3 is published on npm latest from source tag
v0.4.3
(bb3589106691c27d15b156d8b45e4178836bd4be); its release finalizer
verified the registry bytes. It embeds Core 0.2.0-pre.34. The prior Core34 checkout passed the
installed GitHub author and comparison consumer journeys against those exact public artifacts.
The Core33/CLI22 library finalizer
and CLI finalizer remain historical
evidence. Maintainers can use the existing archive overrides for separate candidate qualification.
Use Node 26.8.2 for these build steps:
| Repository checkout | Exact Core helper pin |
|---|---|
Prior Core34 compatibility checkout, first reviewed at 0b9241c7ebc24de55e6a717a1533c4d38a7bf88a — stable CLI 0.4.3 |
0.2.0-pre.34 |
Prior Core33 compatibility checkout d8c2dc755ed598a3a0dc9190082198dfd2825c75 — CLI 0.4.3-pre.22 |
0.2.0-pre.33 |
Prior published compatibility checkout 769bf609f3fe9c78e962f94ead11567cac7fcfd3 — CLI 0.4.3-pre.21 |
0.2.0-pre.32 |
Prior Core30 compatibility checkout 333d537d3dd92aab87f5801c60f5a609daf648ee — CLI 0.4.3-pre.20 |
0.2.0-pre.30 |
Core29/CLI19 checkout a92e24820f6abc1968e73d9a278e7944a3eaef67 — CLI 0.4.3-pre.19 |
0.2.0-pre.29 |
0752fb1ca4374b09049c7e7adbd9990d943f8eae — published CLI 0.4.3-pre.18 |
0.2.0-pre.28 |
09e98187942690ec1a146f2cd7dae6863e3e79fb |
0.2.0-pre.27 |
91af04ecda6db0bd3f97245ed3e5c81152ab787c |
0.2.0-pre.26 |
e0186bf5b715895bcaab291877e98228719dab82 |
0.2.0-pre.25 |
7484875919098720732be9fd3d96dc34fe016ffe — published CLI 0.4.3-pre.14 |
0.2.0-pre.24 |
7534c84fde8f18d46a625473eb7b6c7ba41401e1 |
0.2.0-pre.23 |
CLI 0.4.3-pre.14 embeds Core24; use its full pinned checkout above.
Build and register a checkout matching the selected CLI’s embedded Core version.
A CLI embedding another Core helper version refuses this checkout; use a separately reviewed
checkout with the exact matching pin.
git clone https://github.com/Holaxis-ai/superbee-plugins.git
cd superbee-plugins
git checkout --detach REVIEWED_FULL_COMMIT_SHA
git rev-parse HEAD
git status --short
npm ci
npm install --no-save --package-lock=false --ignore-scripts @superbee/[email protected]
npm install --global [email protected]
npm run build
superbee source plugin register "$PWD/integrations/github"The last command previews the exact local bytes and returns a proposal digest without importing the profile. Review the trusted-code statement, then accept that digest explicitly:
superbee source plugin register "$PWD/integrations/github" --accept PROPOSAL_DIGEST
superbee source plugin list
superbee recipe add github:source-feeds --dir YOUR_BUNDLE
superbee recipe add github:work-items --dir YOUR_BUNDLEThese namespaced recipe commands install the accepted snapshot's inert definitions. Feed binding and execution remain explicit. Registration trusts the selected local bytes, not authenticated publisher origin, and approved code has ambient process authority. A later checkout or rebuild does not change the accepted snapshot. To update, select and review another full commit, rebuild, explicitly register/accept it, and rebind affected feeds; changed bindings reset observation and accepted overlay state for reacquisition.
After the same tool and public Core installation and build:
npm run typecheck
npm run test:unit
npm run test:packagedPublished Core 0.2.0-pre.37 provides the public host helper exports. It remains an
optional exact peer; build and typecheck require its explicit installation above. No Core source or sibling checkout
is used. A maintainer testing a compatible Core candidate may install its tarball with
npm install --no-save --package-lock=false --ignore-scripts <tarball> and set
SUPERBEE_CORE_TARBALL to that exact archive for the packaged consumer proof. Local candidate
paths never enter manifests or the lockfile. The packaged author journey defaults to the exact
published CLI [email protected]; SUPERBEE_CLI_TARBALL may explicitly select its
retained matching archive. The proof requires that exact version and unchanged archive bytes.
The data-only comparison proof preserves stable CLI 0.4.3 / source bb3589106691c27d15b156d8b45e4178836bd4be
as its normal historical control. An explicit CLI archive instead requires 0.4.4-pre.2 / source
008e00fa04d0ff726dfa3d6da80343cbcf230309; both paths require a clean npm-package identity.
These synthetic GitHub/comparison journeys do not establish native Blender rendering or video-host adoption.
Local npm pack tests are artifact portability checks, not an integration publication or required
user acquisition route. They install packed test bytes outside this checkout with a clean explicit
environment and check public types, browser exports, recipes and the source harness. Source CI
uses the matching published Core and CLI artifacts. Qualify a proposed exact head with both local archive
overrides during candidate qualification; ordinary consumer CI uses the matching public CLI. This
does not authorize a release. Integration metadata is private and prepublishOnly refuses
publication; no integration registry bootstrap, publisher setup or release workflow is planned.
The package proof imports a generated snapshot of Superbee's
owning package verification tools.
scripts/vendor/package-verification/snapshot.json records the public producer commit and file
digests. CI checks those bytes against the producer's actual Git objects before installing tools.
Do not edit snapshot files independently. From a clean producer checkout at the selected exact
commit, refresh and check using the owning exporter:
node packages/package-verification/export.mjs --source . --target <plugins-checkout>/scripts/vendor/package-verification --commit <new-sha> --expected <previous-sha>
node packages/package-verification/export.mjs --source . --target <plugins-checkout>/scripts/vendor/package-verification --checkA refresh requires both pinned commits in the producer's Git objects and a reviewed snapshot and CI pin update. These are build-time test tools; they do not provide plugin execution isolation.