Uses independent semantic versions for the theme and plugin, a starter-content version, changelog entries, package checksums, and release-bound validation records.
Independent versions
The theme and plugin use semantic versions. Starter content records its own release version. Model profiles, benchmarks, and external implementation projects retain their own versions.
Release record
Record artifact names, SHA-256 checksums, build date in UTC, validation commands, known limitations, and rollback path. Never reuse a version number for different bytes.
Scope
This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.
Engineering considerations
- Identify the source, version, target environment, and owner.
- Separate observed values from estimates and externally reported values.
- Record trade-offs, unsupported cases, and fallback behavior.
- Link performance statements to a compatible benchmark methodology.
Verification questions
- What exact artifact, revision, backend, and environment were reviewed?
- Which assumptions could change the result?
- Which data should be retained so another engineer can reproduce the conclusion?