chore: checkpoint hermes-generated ops skills

docs/releases/2.0.0-preview/release-notes.md

@@ -0,0 +1,51 @@
+# ECC 2.0 Preview Release Notes
+
+## Positioning
+
+ECC 2.0 preview turns the repo into a more explicit cross-harness operating system.
+
+Claude Code is still a core target. Codex, OpenCode, and Cursor remain first-class. Hermes now joins the public story as the operator shell that can sit on top of ECC.
+
+## What Changed
+
+- Public repo metadata now aligns with the 2.0 direction already visible in the plugin manifest and architecture docs.
+- Hermes setup is documented as a sanitized, reusable operator stack.
+- Hermes-generated skills are now easier to explain as part of ECC's reusable workflow layer.
+- Same-day launch collateral is included in-repo so the release can ship without rebuilding the messaging from scratch.
+
+## Why This Matters
+
+ECC is no longer just “Claude Code tips in a repo.”
+
+It is a reusable system for:
+
+- engineering execution
+- research and market intelligence
+- outbound and comms operations
+- content production and distribution
+- operator accountability through hooks, cron jobs, and workflow packs
+
+## Preview Boundaries
+
+This is a public preview, not the final form.
+
+What ships now:
+
+- cross-harness positioning
+- Hermes setup documentation
+- launch content pack
+- version alignment across root package surfaces
+
+What can land later:
+
+- richer sanitized Hermes templates
+- more public MCP presets
+- deeper CRM and Google Workspace playbooks
+- additional operator packs distilled from live usage
+
+## Suggested Upgrade Motion
+
+1. Update to the ECC 2.0 public surface.
+2. Read the [Hermes setup guide](../../HERMES-SETUP.md).
+3. Pick the workflows you want public first: content, research, outreach, or engineering.
+4. Use the launch pack in this folder to announce the release without re-drafting everything from scratch.