docs(work): decompose platform-retrofit and walking-skeleton epics

platform-retrofit: 8 stories / 18 tasks (spec bundle into docs/product,
single-version release-please before deletions, demo feature removal,
web-next auth shell, optional cores, work-tree archive, library traces,
agent-doc rewrite). walking-skeleton: 11 stories / 28 tasks across
workspaces, discovery, core-runner-protocol, runner app, editor, and
the flagship connect-to-selection e2e; builds on platform-retrofit
(prose dependency note — cross-epic frontmatter unsupported).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK

docs/work/epics/platform-retrofit/02-single-version-release-please/_story.md

@@ -0,0 +1,41 @@
+---
+id: 02-single-version-release-please
+epic: platform-retrofit
+title: Rewrite release-please to a single root product version
+type: technical-story
+status: todo
+feature: tooling
+depends-on: []
+blocks: [03-delete-demo-apps-and-features, 08-rewrite-agent-docs]
+created: 2026-07-12T10:22:00Z
+---
+
+## Goal
+
+`release-please-config.json` + `.release-please-manifest.json` track the root package only — a single product version with plain `v*` tags (`include-component-in-tag` dropped), pre-1.0 bump policy retained. Veect is a hosted SaaS that deploys continuously; per-feature versions return only if an npm distribution ships.
+
+## Why
+
+release-please currently tracks five demo feature packages that stories 03/04 delete. Rewriting to root-only FIRST keeps ADR-021's Conventional-Commit → release automation working through the deletions: if a deletion commit touched a still-tracked `packages/<feature>/**` path, release-please would try to bump a package whose `package.json` no longer exists. Story 03 therefore depends on this story (PRD user story 5 + ADR-021 constraint).
+
+## Done when
+
+- `release-please-config.json` validates against its schema and tracks only `"."`.
+- `include-component-in-tag` is dropped (single `v*` tags); pre-1.0 bump policy (`bump-patch-for-minor-pre-major`) retained; changelog sections retained.
+- `.release-please-manifest.json` contains only the root entry.
+- Any release-please CI workflow references to per-package components still work.
+- `pnpm typecheck && pnpm lint && pnpm test && pnpm conformance && pnpm fallow:audit && pnpm coverage:diff` pass.
+
+## In scope
+
+- `release-please-config.json`, `.release-please-manifest.json`, and any CI workflow wiring that assumes per-component tags.
+
+## Out of scope
+
+- Deleting the feature packages themselves (story 03).
+- Renaming the root package (`template-vertical` → product name changes belong to the docs rewrite only if the PRD's next-PRD work requires it; this story touches versioning config only).
+- Retagging or rewriting existing git tags/releases.
+
+## Tasks
+
+- [ ] Rewrite `release-please-config.json` to track the root package only (drop the five `packages/*` entries and `include-component-in-tag`, keep the pre-1.0 bump policy and changelog sections), shrink `.release-please-manifest.json` to the root entry, and adjust any release CI workflow that assumed per-component tags — config validates, one commit, all gates pass.