# Thortiq Plugin Developer Kit

Version `1.0.0` for Plugin API `1.0.0`.

This kit is the immutable release companion to the public Thortiq packages.
Start with [docs/quickstart.md](docs/quickstart.md), then choose a runtime in
[docs/runtime-choice.md](docs/runtime-choice.md). The complete public contract
is the release-built declarations under `types/`, the JSON Schemas under
`schemas/`, and [docs/api-reference.md](docs/api-reference.md).
Supported API/runtime/contribution/platform combinations are listed in
[docs/compatibility.md](docs/compatibility.md).
The external scaffold, build, validation, packaging, migration, and install
workflow is in [docs/development-lifecycle.md](docs/development-lifecycle.md).

## Included

- `bootstrap.mjs`, which creates a project using the bundled scaffolder and
  rewrites it to use the exact local Thortiq package tarballs;
- concise agent routing in `AGENTS.md`,
  the independently installable
  `skills/thortiq-plugin-development/SKILL.md`, and `llms.txt`;
- source documentation, schemas, declarations, templates, and examples built
  from the same contract sources as Thortiq;
- packed, exact-version Thortiq public packages under `packages/`; and
- `checksums.json`, covering every other canonical file in this tree.

The Thortiq package tarballs are usable without reaching the Thortiq source
repository. React, TypeScript, bundlers, test runners, and other third-party
template dependencies are not mirrored by Thortiq. Installing a packaged
template still requires those exact dependencies to be available from a trusted
local package source or npm registry. The plain live-customization template has
no runtime build dependency.

`examples/` includes vanilla and React native views, a React sandboxed page, a
plain-JavaScript live customization, declarative and host SearchView examples,
a note-editor mount, a trusted editor extension, live-sandboxed Jira sync, and
sandboxed-page CSV import.
The Jira and CSV adapters reuse the same runtime-neutral workflow cores as the
reference integrations while routing all authority through their public
runtime brokers.

Never use a live vault as a development fixture. Scaffold and test in a separate
directory with synthetic data, then install only validated build output.
