Tickline v0.9.0 — Runtime diagnostics and service hardening

v0.9.0 — Runtime diagnostics and service hardening

Tickline v0.9.0 introduces a Go-based developer console that consolidates
local verification, diagnostics, operational workflows, persisted execution
evidence, and artifact-integrity verification.

Highlights

• Shared execution engine for plain output, versioned JSON, and an interactive
  Bubble Tea terminal interface.
• Declarative verification stages with dependency-aware planning.
• Repository and toolchain diagnostics through tickline-dev doctor.
• Operational workflow discovery and execution.
• Process-tree cancellation using Linux process groups.
• Per-run stdout, stderr, and combined stage logs.
• Canonical schema-version-2 result.json documents.
• Schema-version-1 artifacts.json integrity inventories.
• Plain and JSON verification through tickline-dev artifacts verify.
• Release-readiness workflow metadata and persisted evidence.
• Unit, integration, race-detector, and static-analysis coverage.

Artifact model

Executed verification runs write their evidence under:

reports/check-local/<run-id>/

The directory contains the canonical result, stage logs, and an integrity
manifest. Verification checks manifest structure, repository containment,
artifact type, file size, and SHA-256 digest.

The manifest is an integrity inventory, not an authenticity mechanism. It is
not digitally signed and does not establish authorship, provenance, or trust
in the manifest itself.

Limitations

• The console is repository-local and is not a remote orchestration service.
• Generated reports are excluded from Git.
• Artifact manifests are not digitally signed.
• Hosted Unity execution is not configured in GitHub Actions.
• Production deployment and remote evidence services remain outside this release.