Historical plugin-kit-ai v1, baseline 1.2.4
Prepared, unreleased authoring contract. This public page documents a reviewed future authoring workflow. Future authoring commands described here are not available in current releases; they do not claim that
plugin-kit-ai@2is available. Existing installer examples are identified separately. Public activation remains pending.
This index preserves a way to understand existing projects. Its command baseline is tag v1.2.4, resolving to commit 9beca10448ac50fbe526a52101d1433a12471980, rather than the broader command tree on the current documentation branch.
Project migration is not available in v2 yet. Maintain legacy projects using the v1 1.2.4 command set. A version pin records historical behavior; it does not promise a second maintained YAML engine or a new support commitment.
Choose the right context
| What you have | Where to go |
|---|---|
A new root plugin.json package | Prepared Build journey. |
| A package to install into an agent | Use plugins. |
plugin/plugin.yaml, generated targets, or launcher source | Use the historical baseline and retained references below. |
| A plan to convert a legacy project automatically | Migration is unavailable in v2; preserve the project. |
Do not run new Build commands against a legacy directory expecting conversion. Standard authoring has no YAML fallback, temporary conversion, or native hidden manifest fallback.
Exact historical command context
The tagged root command source registers init, bootstrap, doctor, dev, test, export, bundle, generate, import, inspect, compat, publish, publication, normalize, validate, capabilities, install, integrations, and version. Skills registration is visible separately in the tagged Skills source. These are historical names, not the v2 command navigation.
The tagged init source describes online-service, local-tool, and custom-logic, with authored source under plugin/. Runtime and platform switches there have historical meanings. For example, v1 test exercises launcher fixtures, while prepared v2 test is a static package check. The same command name does not imply the same behavior.
Use version 1.2.4 deliberately when maintaining those projects; avoid unversioned or latest-channel historical installation snippets. This index does not install or replace any executable. Package-wrapper development version placeholders in the tagged source are not the historical release version.
Retained explanations
These existing site pages remain intact. They are linked as legacy/support explanations; their current-branch wording is not a byte-for-byte v1.2.4 snapshot. Use the exact tagged sources above when a command detail depends on the version.
| Topic | Retained reading |
|---|---|
| YAML project and generated outputs | Managed project model, historical authoring workflow. |
| Runtime and target selection | Choosing runtime, target model. |
| Node and Python launcher projects | Node/TypeScript runtime, Python runtime. |
| SDK and runtime API context | Existing API index; these generated references are not the new authoring CLI contract. |
| Bundle and publication explanations | Bundle handoff, publishing guide. |
| Historical changes | Existing release records. |
Pinned design and support sources
- 1.2.4 YAML specification.
- 1.2.4 authoring documentation.
- 1.2.4 SDK README.
- 1.2.4 Node runtime README.
- 1.2.4 Python runtime README.
- 1.2.4 publication design.
- 1.2.4 repository tree.
The repository's 1.2.4 release note is dated 2026-05-24. Historical release records may describe planned downstream publication; they alone do not prove a channel is currently available. SDK and runtime helper packages also have their own versions, independent of any later authoring CLI major version.
Preservation is deliberate
Useful YAML implementation, dependencies, tests, examples, and design docs stay in their existing locations. Removing a command from the standard authoring surface does not authorize deleting its service or documentation. Unresolved capabilities remain preserved outside the standard dependency graph.
This index does not copy all historical pages, bulk-migrate examples, or advertise a maintained parallel engine. Future source removal requires an inventory and explicit owner acceptance. Public navigation and redirects need separate review before this preparation can be activated.