fix(bmm): complete cleanup of epic-tech-context workflow removal (#1001)

- Remove references to deprecated epic-tech-context, story-context,
  validate-epic-tech-context, validate-story-context, and story-done workflows
- Simplify epic status: backlog → in-progress → done (was backlog → contexted)
- Update create-story to handle legacy 'contexted' status for backward compat
- Clean up sprint-planning instructions and status template
- Update docs: agents-guide, brownfield-guide, faq, glossary, quick-start

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Brian <bmadcode@gmail.com>

src/modules/bmm/docs/faq.md

@@ -90,7 +90,7 @@ When in doubt, start smaller. You can always run create-prd later if needed.
 
 ### Q: Do I always need architecture for Level 2?
 
-**A:** No, architecture is **optional** for Level 2. Only create architecture if you need system-level design. Many Level 2 projects work fine with just PRD + epic-tech-context created during implementation.
+**A:** No, architecture is **optional** for Level 2. Only create architecture if you need system-level design. Many Level 2 projects work fine with just PRD created during planning.
 
 ### Q: What's the difference between Level 1 and Level 2?
 
@@ -162,15 +162,6 @@ If status file exists, use workflow-status. If not, use workflow-init.
 
 ## Planning Documents
 
-### Q: What's the difference between tech-spec and epic-tech-context?
-
-**A:**
-
-- **Tech-spec (Level 0-1):** Created upfront in Planning Phase, serves as primary/only planning document, a combination of enough technical and planning information to drive a single or multiple files
-- **Epic-tech-context (Level 2-4):** Created during Implementation Phase per epic, supplements PRD + Architecture
-
-Think of it as: tech-spec is for small projects (replaces PRD and architecture), epic-tech-context is for large projects (supplements PRD).
-
 ### Q: Why no tech-spec at Level 2+?
 
 **A:** Level 2+ projects need product-level planning (PRD) and system-level design (Architecture), which tech-spec doesn't provide. Tech-spec is too narrow for coordinating multiple features. Instead, Level 2-4 uses:
@@ -178,13 +169,6 @@ Think of it as: tech-spec is for small projects (replaces PRD and architecture),
 - PRD (product vision, functional requirements, non-functional requirements)
 - Architecture (system design)
 - Epics+Stories (created AFTER architecture is complete)
-- Epic-tech-context (detailed implementation per epic, created just-in-time)
-
-### Q: When do I create epic-tech-context?
-
-**A:** In Phase 4, right before implementing each epic. Don't create all epic-tech-context upfront - that's over-planning. Create them just-in-time using the epic-tech-context workflow as you're about to start working on that epic.
-
-**Why just-in-time?** You'll learn from earlier epics, and those learnings improve later epic-tech-context.
 
 ### Q: Do I need a PRD for a bug fix?
 
@@ -219,17 +203,6 @@ PRDs are for Level 2-4 projects with multiple features requiring product-level c
 
 For Level 0-1 using tech-spec, story-context is less critical because tech-spec is already comprehensive.
 
-### Q: What if I don't create epic-tech-context before drafting stories?
-
-**A:** You can proceed without it, but you'll miss:
-
-- Epic-level technical direction
-- Architecture guidance for this epic
-- Integration strategy with other epics
-- Common patterns to follow across stories
-
-epic-tech-context helps ensure stories within an epic are cohesive.
-
 ### Q: How do I mark a story as done?
 
 **A:** You have two options:
@@ -271,7 +244,7 @@ The story-done workflow is faster and ensures proper status file updates.
 - What went well
 - What could improve
 - Technical insights
-- Input for next epic-tech-context
+- Learnings for future epics
 
 Don't wait until project end - run after each epic for continuous improvement.