Establish the v0.2 product foundation

[fxdv]

What changed

• position Patchlog around safe release coordination and make patchlog release --dry-run / patchlog release the documented golden path
• apply safe core defaults (--bump auto --tag --push) only when no explicit release workflow is selected
• add actionable configuration and preflight recovery guidance
• make trend analytics opt-in and keep its exact output path inside the immutable release plan
• keep DPI, health, individual analytics, and gamification behind experimental labs
• automate post-publication verification of checksums, archive execution, provenance, @v0.1.3, and @latest
• generate checksum-pinned Homebrew and Scoop manifests while explicitly not claiming live channels before their tap/bucket repositories exist
• define the v0.2.0 stability contract and bump VERSION to 0.1.3

Why

The primary product promise should be deterministic and safe release coordination. Optional AI, metrics, Confluence analytics, and labs features should not complicate first use or introduce hidden default writes. The release workflow should also prove the artifacts consumers actually install after publication.

User and operational impact

A new user can now plan and apply the core release with two commands. Plain patchlog remains read-only. Explicit advanced release flags retain composed-workflow behavior. Trend snapshot storage changes from enabled by default to opt-in.

After merge, wait for the post-merge quality run on main, then create annotated tag v0.1.3 from that exact green commit. The tag-triggered release must remain green through the new post-publication verification job before the release is considered complete.

Proxy metrics are diagnostic only and are not release gates. True coverage remains a CI artifact; dependency risk requires a language-aware graph; lead and cycle time require PR and deployment timestamps.

Validation

• Go 1.26.5 race-enabled unit suite
• full integration suite
• all 29 orchestration E2E tests, including immutable dry-run and golden-path apply
• supported Go 1.22 compatibility suite
• release-manifest rendering tests
• Shellcheck for new release scripts
• workflow YAML parsing and git diff --check