fraqtal/agentic-dev
Template
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
483c7b2c8ed4b8da1ff05cc217e75d7f5958d3ad
agentic-dev/docs/work/epics/walking-skeleton/11-flagship-e2e/_story.md
Danijel Martinek 99180887f3 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
2026-07-12 12:28:51 +02:00

2.5 KiB
Raw Blame History

id, epic, title, type, status, feature, depends-on, blocks, created
id epic title type status feature depends-on blocks created
11-flagship-e2e walking-skeleton flagship e2e — connect vite-kitchen to selection round-trip user-story todo web-next
10-web-next-wiring
2026-07-12T10:24:14Z

Goal

Land the repo's flagship Playwright spec — the M0-recast acceptance: sign in → connect vite-kitchen via git URL + PAT → staged progress completes → the editor shows Button rendered inside the adapter's iframe → click the button in the iframe → the editor selection overlay appears and the selection state names the component.

Why

This spec is the epic's definition of done in executable form. It exercises every seam at once — provisioning, clone/install/scan, adapter, realtime progress, and the cross-origin selection round-trip — asserting through the UI and the protocol, never against runner internals, so the runner stays refactorable while the protocol is the contract (PRD Testing decisions).

Done when

  • The Playwright spec (dev-seed + local-process provisioner) covers the full flow from the PRD Success criteria and asserts on iframe content, not a screenshot double.
  • The flow completes within the connect-to-rendered-component budget: < 3 min on the warm fixture (PRD budget, spec §16).
  • The spec is tagged as the repo's flagship spec and runs green in CI.
  • The equivalent flow with the Docker provisioner works on a dev machine per story 06's documented manual check (CI stays on the process provisioner).
  • pnpm typecheck && pnpm lint && pnpm test && pnpm test:e2e && pnpm conformance && pnpm fallow:audit && pnpm coverage:diff all pass.

In scope

  • The flagship Playwright spec under the existing pnpm test:e2e surface, running against dev-seed mode with the process provisioner.
  • Any test-only plumbing needed to run the spec in CI (fixture serving, runner spawn) reusing the story 01 helpers.

Out of scope

  • Docker-provisioner automation in CI (manual check only, per PRD Success criteria).
  • Additional e2e coverage beyond the flagship flow (later PRDs).

Tasks

  • Add the flagship Playwright spec (dev-seed + process provisioner): sign in → connect vite-kitchen via git URL + PAT → staged progress completes → Button rendered inside the adapter iframe (assert on iframe content) → click in the iframe → selection overlay appears and the selection state names the component; completes within the < 3 min warm-fixture budget; tagged as the repo's flagship spec; green in CI.