v0.1.0

chore: configure releases and licensing

Spec-first: canonical=none; contract=main-branch semantic releases target the current triggering commit and published source is Apache-2.0 licensed; mechanism=serialized SHA-gated semrel workflow with verified tooling and release tags; collapse-check=n/a: no release-domain spec.

Rationale: change=add automated v-prefixed releases and Apache 2.0 licensing for Great Lion Technologies; invariant preserved=only the current main SHA may create a release and every created release tag resolves to that SHA; why this shape=explicit SHA targeting, stale-run rejection, pinned actions, checksum-verified tooling, and least-privilege tokens make releases reproducible and bounded to reviewed code.

Invariant: kind=entailed; property=only the current main SHA may create a release and every created release tag resolves to that SHA; from=entailed by automated semantic releases; violation=an out-of-order or preexisting tag publishes an older or different commit under the calculated version.

Structural-check: invariant=created release tag resolves to the triggering SHA; illegal-state=release version names a different commit; representable-because=irreducible external GitHub state; decision=runtime check by fetching and peeling the published remote tag.

Spec: none; Plan: none; divergences: none.

Review: four adversarial rounds converged; fixed release ordering, moving-target, failure masking, mutable tooling, token scope, and tag-target verification findings; canonical Apache text review found no licensing issues.

Tests: go test ./...; actionlint v1.7.12; semrel --dry-run --verbose; git diff --cached --check; semrel 0.6.1 asset digest verified.