Outcome
Give content CI, editor, automation, wrapper, and Go conformance stable independently consumable toolkit releases.
Scope and invariants
- Define semver policy across crates, CLI, JSON command/result/diagnostic schemas, artifact specs, fixtures, and corpus compatibility.
- Publish reproducible crates/binaries/source plus schema/fixture archives, checksums, SBOM, provenance, dependency notices, and compatibility manifest.
- Make all CLI commands explicit-input/output, noninteractive-capable, bounded, machine-readable, and atomic; human output remains separate.
- Provide wrapper profile/local source override contract without submodules or consumer manifest edits.
- Document supported authored/content versions and deprecation/breaking process.
Acceptance criteria
- Editor builds independently against released crates; content CI/wrapper use released CLI; Go tests use released fixture/spec assets.
- Schema/API compatibility tests and release consumer smoke projects run in CI.
- No release requires Python, renderer, client, editor, server, or source-tree layout.
- Every artifact has immutable version/digest and actual license metadata.
- Breaking changes require migration tooling/spec and coordinated issues before release.
Dependencies and parallelization
Can build release plumbing early; final M2 release requires #3-#6 stable surfaces.
Licensing
Toolkit code is MIT. Original past contributions by a person listed in the merged approved MIT provenance-grantor registry in atrinik/atrinik#275 may be copied, migrated, translated, or relicensed under MIT only after a complete, non-shallow Git-history audit, including renames and moves, proves the selected material is that grantor's solely authored original work and contains no embedded third-party or conflicting-licensed material. Record the exact evidence, applicable grantor, and destination. Mixed authored data and fixtures retain their actual licenses.
Outcome
Give content CI, editor, automation, wrapper, and Go conformance stable independently consumable toolkit releases.
Scope and invariants
Acceptance criteria
Dependencies and parallelization
Can build release plumbing early; final M2 release requires #3-#6 stable surfaces.
Licensing
Toolkit code is MIT. Original past contributions by a person listed in the merged approved MIT provenance-grantor registry in atrinik/atrinik#275 may be copied, migrated, translated, or relicensed under MIT only after a complete, non-shallow Git-history audit, including renames and moves, proves the selected material is that grantor's solely authored original work and contains no embedded third-party or conflicting-licensed material. Record the exact evidence, applicable grantor, and destination. Mixed authored data and fixtures retain their actual licenses.