Created
Jul 04, 01:50
Started
Jul 04, 01:50
Completed
Jul 04, 04:58
DevOps handoff
Type
Bug
Shape
ui-only
Worktree Slug
drop-qa-readonly-cleared-block-spec
Repositories
mcritchie-studio
Release Slug
—
Branch
feat/drop-qa-readonly-cleared-block-spec
Acceptance Criteria
Expected Test Plan
Checks Run
Agent Context
Prod-smoke false alarm: post-ship bin/prod-smoke runs the @qa-readonly subset against PROD, and board_cleared_block.spec.js asserts the seeded e2e-cleared-block-demo fixture (#card-e2e-cleared-block-demo), which never exists on prod -> red seal false alarm (memory feedback_qa_readonly_no_seed_fixtures). Fix = drop the @qa-readonly tag from the test title; the spec stays [e2e]-tier and runs against seeds. Regression-test-first is not practical here (the defect IS a test-suite tag); verification = the untagged spec green in the e2e tier + grep that the qa-readonly subset no longer matches it. NOTE for reviewer: alex_pipeline.spec.js (added today, PR 347) also carries @qa-readonly but its only data assertion is span count >= 1, which prod satisfies structurally (real narration spans always exist), so it keeps the tag; if we ever want prod-smoke to be strictly fixture-free too, that is an operator call.
Stage Timeline
Who handled each stage, the time it took (measured), and the model / tokens / cost reported (best-effort) — plus who's on it right now. — means the agent didn't report that metric.
Conversation
QA review feedback, agent handoffs, and follow-up notes for this task.
No task feedback has been recorded yet.
Sealed-bid sizing
Edit →Alex (PM)
—
Avi (PO)
—
Dev
SMALL
Actual
LARGE
We emailed a one-tap sign-in link to . It expires shortly and can only be used once.
No email? Check spam, or close this and try again.