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
This commit is contained in:
2026-07-12 12:28:51 +02:00
parent 442b70476c
commit 99180887f3
22 changed files with 1286 additions and 3 deletions

View File

@@ -0,0 +1,45 @@
---
id: platform-retrofit
prd: docs/work/prds/platform-retrofit.prd.md
title: Platform retrofit — repurpose template-vertical as the Veect monorepo
type: epic
status: in-progress
features:
[
blog,
media,
marketing-pages,
navigation,
web-tanstack,
web-next,
core-events,
core-realtime,
]
created: 2026-07-12T10:22:00Z
---
## Goal
Turn the `template-vertical` starter into a clean, truthful Veect monorepo: commit the product spec under `docs/product/`, delete the four demo content features and `apps/web-tanstack`, reduce `apps/web-next` to a compiling auth shell, scaffold `core-events` + `core-realtime`, archive the shipped template work, move release-please to a single root version, pre-approve the editor's library traces, and rewrite CLAUDE.md/AGENTS.md for Veect — with every conformance gate green on every slice.
## Why
Three concrete pains (PRD): dispatch agents in worktrees cannot read the untracked `.proto/` spec bundle; `pnpm work status`, CLAUDE.md/AGENTS.md, and release-please all describe a blog/CMS starter that no longer reflects the product; and the demo features occupy the workspace, router/CMS composition, and versioning config that the Veect features (workspaces, projects, design-doc, discovery, ai) need. ADR-027/028/029 are the decision baseline; this epic implements their repo-level consequences only.
## Stories
- [ ] [01 — Commit the product spec and design references under docs/product/](01-commit-product-docs/_story.md)
- [ ] [02 — Rewrite release-please to a single root product version](02-single-version-release-please/_story.md)
- [ ] [03 — Delete web-tanstack and the four demo content features](03-delete-demo-apps-and-features/_story.md)
- [ ] [04 — Reduce web-next to an auth shell with a boot smoke assertion](04-web-next-shell/_story.md)
- [ ] [05 — Scaffold core-events and core-realtime](05-scaffold-optional-cores/_story.md)
- [ ] [06 — Archive the shipped template work tree](06-archive-template-work/_story.md)
- [ ] [07 — Library traces for @xyflow/react and zustand](07-editor-library-traces/_story.md)
- [ ] [08 — Rewrite CLAUDE.md and AGENTS.md for Veect](08-rewrite-agent-docs/_story.md)
## Out of scope (from PRD)
- Any new Veect feature code (walking-skeleton PRD and successors).
- The landing page (`polish-playground-landing` PRD).
- Generator retargeting beyond what deletions force — the feature generator's Payload+tRPC shape is correct for Veect's control plane (ADR-027 §5) and stays as-is.
- Runner infrastructure, Docker images, fixtures; billing, GitHub App, self-host distribution (deferred per ADR-027).