Contracts for this version#
These references are generated from this build’s real public type and hook exports. They describe API contracts; they do not grant permissions or prove that a provider or feature exists. The kit carries SDK version 1.0.0 and compatible @i2l-sim/* import names.
- Complete service reference — public methods, signatures and source locations.
- Complete hook reference — events, owners and lifecycle behaviour.
- Download the complete author kit — exact local tarballs, source type definitions, Markdown references, examples and notices.
- Artifact manifest — download bytes and SHA-256 digests.
Source locations in generated references refer to the SDK’s repository layout. Public source definitions are included inside the corresponding sdk/*.tgz package in the kit. They are shown as locations rather than links to a private repository. Do not assume a declared future service has an implementation in this MVP.
Lifecycle and identity#
Use only exported SDK entrypoints and the calling plugin’s context. Declare required/optional injected services. Own every registration, listener, task and disposer. Handle owner loss and cancellation around awaited work; do not publish late results after unload or replacement.
Browser contributions share the host’s React/kernel/locale runtime. The internal first-party workspace facade is not part of the finite Store V1 public browser import contract. Existing public exports such as the UI components/locale entrypoints have their documented host mappings; do not infer that any arbitrary exported subpath can be imported by a Store package.
Data and authority#
Session mutations use sessions.dispatch; screens read projections. Persistent plugin data belongs in storage.ns(ctx.id). Never import another plugin’s SQL connection, secret storage or private source. Handle explicit revision conflicts rather than silently retrying transaction callbacks.
A manifest declaration does not approve network access, provider calls, public pages or other privileged operations. Review the actual host seam and permission prompt. Enabled plugins have full host access; static inspection and AI review are not isolation mechanisms.
Packaging and review#
The kit’s first-party packages are Apache-2.0. Their public dependencies retain their own licences and terminology attribution. The full application and separately licensed feature plugins are not included. The author kit does not need public first-party npm publication, a registry account, an API key or real patient data for its checks.
Use the creation guide for the tested local package path. Store packaging and submission require the actual assigned publisher namespace, supported prebuilt artifact format and the registry/host’s current eligibility policy. A local tarball hash establishes bytes, not the truth of a publisher’s provenance or clinical claims.