Merge pull request #14 from Leftyshields/improve/workflow-postmortem-h3m8

Workflow: local dev parity gates from Wallet Watcher postmortem

Author: Leftyshields

.cursor/commands/capture_issue.md

@@ -97,6 +97,9 @@ Write the issue to `.ai/context/last_capture.md` using **exactly** this structur
 # Priority
 [low / medium / high]
 
+# Environment
+[optional: local-dev | staging | production | vendor-sandbox]
+
 # Open Questions
 [questions here]
 

.cursor/commands/design_decisions.md

@@ -71,6 +71,14 @@ For auth, payments, email, or third-party APIs, document:
 
 Copy [DEV_RUNBOOK_TEMPLATE.md](docs/DEV_RUNBOOK_TEMPLATE.md) → `docs/DEV_RUNBOOK.md` and add rows as you learn.
 
+### 9. Data provenance (when multiple sources)
+
+If data comes from external APIs **and** local seed/fixtures:
+
+- List sources (e.g. vendor API, seed script, manual entry)
+- UI/API field for source or inference rule
+- Cleanup behavior on reconnect/relink/re-auth
+
 ### 10. External API identifiers (verify at implement time)
 
 For LLM, payment, or vendor APIs, document:

.cursor/commands/pre_implementation_checklist.md

@@ -81,7 +81,18 @@ If adding new API endpoints:
 
 ---
 
-### 5. Content Rendering Strategy
+### 5. Monorepo & local runtime
+
+- [ ] Documented whether API/services import workspace packages from **`dist/`** or **`src/`**
+- [ ] Dev workflow notes shared rebuild if applicable
+- [ ] Emulator/database: single-instance rule and port recovery in `DEV_RUNBOOK`
+- [ ] If feature needs demo data: seed script planned and wired to `package.json`
+
+**Next Step:** Continue to step 6.
+
+---
+
+### 6. Content Rendering Strategy
 
 If adding formatted content (markdown, HTML, rich text):
 
@@ -93,11 +104,11 @@ If adding formatted content (markdown, HTML, rich text):
 
 **Action:** Add to design decisions document
 
-**Next Step:** Continue to step 6.
+**Next Step:** Continue to step 7.
 
 ---
 
-### 6. React State Management Patterns
+### 7. React State Management Patterns
 
 If using React state updates:
 

.cursor/commands/workflow.md

@@ -63,6 +63,7 @@ See also: [Product vs genome mission](docs/PRODUCT_VS_GENOME_MISSION.md).
    - Apply backend changes to **all documented entry points** (see `docs/ARCHITECTURE.md`)
    - Use functional state updates when updating state based on props/state
    - Implement format conversions as documented
+   - **Ship local dev tooling** (seed scripts, npm scripts, runbook rows) when UI needs data to demo
 
    **Optional:** Run `/tdd` for complex logic (test-driven development)
 
@@ -86,8 +87,9 @@ See also: [Product vs genome mission](docs/PRODUCT_VS_GENOME_MISSION.md).
    **Next:** Fix critical/high findings, then run `/qa_checklist`
 
 9. **QA Checklist** (`/qa_checklist`) — *standard*
-   - Manual testing checklist: happy path, edge cases, error handling, visual/UX
-   - Human validation only (no automated tests)
+   - **Automated:** agent runs `npm test` and builds for affected workspaces
+   - **Manual:** checklist for happy path, edge cases, error handling, visual/UX
+   - Save issue-scoped checklist to `.ai/context/qa_checklist_<feature>.md` when helpful
 
    **Next:** Fix any issues found, then run `/peer_review` (optional)
 
@@ -159,7 +161,7 @@ For smaller changes or bug fixes:
 | `/tdd` | Optional | Red–green–refactor for complex logic during implementation |
 | `/code_review` | Standard | Automated review: security, correctness, architecture, quality, performance |
 | `/security_scan` | Optional | Dedicated security pass: secrets, deps, auth, data at rest, encryption, proprietary/IP |
-| `/qa_checklist` | Standard | Human manual-test checklist (happy path, edge cases, UX) |
+| `/qa_checklist` | Standard | Automated tests + human manual-test checklist (happy path, edge cases, UX) |
 | `/peer_review` | Optional | Human review of changes; accept/reject feedback with rationale |
 | `/postmortem` | Standard | Reflect on friction and rework; improve process and docs |
 | `/project_wrap_up` | Optional | Handover: security audit, onboarding docs, next-op briefing |

.genome/expression_profiles/organ-Build.md

@@ -4,3 +4,4 @@
 - Decomposition: organs→tissues and below
 - Role library: Build (organs), Implementation (tissues), Worker (cells), read_file (molecules)
 - Contracts: Build → Implementation
+- **Handoff gate:** Before declaring implementation complete, verify the smallest user-visible happy path in the target environment (or document exact commands for the human to do so).

.genome/expression_profiles/tissue-Implementation.md

@@ -4,3 +4,4 @@
 - Decomposition: tissues→cells, cells→molecules
 - Role library: Implementation (tissues), Worker (cells), read_file (molecules)
 - Contracts: Build → Implementation
+- **Handoff gate:** Ship seed/demo tooling with features that need persisted data; state exact happy-path commands before `/code_review`.

docs/INSTANTIATED_APP_FEEDBACK.md

@@ -24,6 +24,18 @@ Changelog of workflow improvements derived from real app development (postmortem
 
 Local dev parity was documented aspirationally but not treated as part of “done.” Demoability should be a deliverable, not a QA surprise.
 
+### Changes incorporated into Genesis (PR `improve/workflow-postmortem-h3m8` — #14)
+
+- `/execute_plan` — Local Dev Verification gate
+- `/pre_implementation_checklist` — Monorepo & local runtime section; plan ID must match capture
+- `/workflow` — Flexible design/plan order; closure docs; common mistakes expanded
+- `/qa_checklist` — Automated tests + manual checklist split
+- `/postmortem` — Required closure artifact outputs
+- `/capture_issue` — Optional `# Environment` field
+- `/design_decisions` — Data provenance subsection
+- `DEV_RUNBOOK_TEMPLATE` — Script integrity rule + terminology table
+- Expression profiles — Happy-path handoff gates
+
 ---
 
 ## 2026-06-07 — AI Tastemakers (Daily Digest, EPH-20260606-DIG1)
@@ -82,6 +94,8 @@ Local dev parity was documented aspirationally but not treated as part of “don
 - `DEV_RUNBOOK_TEMPLATE` — same-day re-run + post-bot deploy rows
 - `/execute_plan` — same-day pipeline warning; post-digest Pages verification
 
+---
+
 ## 2026-07-02 — AI Tastemakers (Landing Layout v2, EPH-20260701-LAND)
 
 **Source:** [ai-tastemakers](https://github.com/Leftyshields/ai-tastemakers) — full workflow through QA close; flag-gated static layout experiment.
@@ -100,7 +114,7 @@ Local dev parity was documented aspirationally but not treated as part of “don
 
 Static HTML generators treated Tailwind class strings like JSX utilities, but Tailwind v4 content scanning does not reliably emit rules from dynamic TS template literals.
 
-### Changes incorporated into Genesis (PR `improve/tastemakers-postmortem-land`)
+### Changes incorporated into Genesis (PR `improve/tastemakers-postmortem-land` — #17)
 
 - `/explore` — partial/WIP conflicts table in snapshot
 - `/design_decisions` — static HTML generator styling section