fix: convert remaining Display/Present keywords to display tags

Remove redundant Display: label before display block, wrap bare
Display/Present keyword content in proper <display> tags, and remove
misplaced code fence pair in architecture step-03-starter.

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01-discovery.md

@@ -228,7 +228,7 @@ Present MENU OPTIONS below for user selection
 #### Menu Handling Logic:
 
 - IF C (Convert): Read fully and follow: {altStepFile} (step-e-01b-legacy-conversion.md)
-- IF E (Edit As-Is): Display "Proceeding with edits..." then load next step
+- IF E (Edit As-Is): <display>Proceeding with edits...</display> then load next step
 - IF X (Exit): Display summary and exit
 - IF Any other: help user, then redisplay menu
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-03-edit.md

@@ -228,7 +228,7 @@ editHistory:
 
 #### Menu Handling Logic:
 
-- IF V (Validate): Display "Starting validation workflow..." then read fully and follow: steps-v/step-v-01-discovery.md
+- IF V (Validate): <display>Starting validation workflow...</display> then read fully and follow: steps-v/step-v-01-discovery.md
 - IF S (Summary): Present edit summary and exit
 - IF A (Adjust): Accept additional requirements, loop back to editing
 - IF X (Exit): Display summary and exit

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md

@@ -131,7 +131,7 @@ From step e-03 change execution, compile:
 - **IF E (Edit More):**
   - <display>**Additional Edits**</display>
   - Ask: "What additional edits would you like to make?"
-  - Accept input, then display: "**Returning to edit step...**"
+  - Accept input, then <display>**Returning to edit step...**</display>
   - Read fully and follow: step-e-03-edit.md again
 
 - **IF S (Summary):**

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02-format-detection.md

@@ -166,7 +166,7 @@ Present MENU OPTIONS below for user selection
 #### Menu Handling Logic:
 
 - IF A (Parity Check): Read fully and follow: {altStepFile} (step-v-02b-parity-check.md)
-- IF B (Validate As-Is): Display "Proceeding with validation..." then read fully and follow: {nextStepFile}
+- IF B (Validate As-Is): <display>Proceeding with validation...</display> then read fully and follow: {nextStepFile}
 - IF C (Exit): Display format findings summary and exit validation
 - IF Any other: help user respond, then redisplay menu
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02b-parity-check.md

@@ -180,7 +180,7 @@ Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to r
 
 #### Menu Handling Logic:
 
-- IF C (Continue): Display "Proceeding with validation..." then read fully and follow: {nextStepFile}
+- IF C (Continue): <display>Proceeding with validation...</display> then read fully and follow: {nextStepFile}
 - IF E (Exit): Display parity summary and exit validation
 - IF S (Save): Confirm saved, display summary, exit
 - IF Any other: help user respond, then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-03-density-validation.md

@@ -43,7 +43,7 @@ Validate PRD meets BMAD information density standards by scanning for conversati
 
 - 🎯 Scan PRD for density anti-patterns systematically
 - 💾 Append density findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
+- 📖 <display>Proceeding to next check...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-04-brief-coverage-validation.md

@@ -46,7 +46,7 @@ Validate that PRD covers all content from Product Brief (if brief was used as in
 - 💬 If no brief: Skip this check and report "N/A - No Product Brief"
 - 🎯 If brief exists: Map brief content to PRD sections
 - 💾 Append coverage findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
+- 📖 <display>Proceeding to next check...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-05-measurability-validation.md

@@ -44,7 +44,7 @@ Validate that all Functional Requirements (FRs) and Non-Functional Requirements
 - 🎯 Extract all FRs and NFRs from PRD
 - 💾 Validate each for measurability and format
 - 📖 Append findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
+- 📖 <display>Proceeding to next check...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-06-traceability-validation.md

@@ -44,7 +44,7 @@ Validate the traceability chain from Executive Summary → Success Criteria →
 - 🎯 Build and validate traceability matrix
 - 💾 Identify broken chains and orphan requirements
 - 📖 Append findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
+- 📖 <display>Proceeding to next check...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-07-implementation-leakage-validation.md

@@ -44,7 +44,7 @@ Ensure Functional Requirements and Non-Functional Requirements don't include imp
 - 🎯 Scan FRs and NFRs for implementation terms
 - 💾 Distinguish capability-relevant vs leakage
 - 📖 Append findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
+- 📖 <display>Proceeding to next check...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-08-domain-compliance-validation.md

@@ -47,7 +47,7 @@ Validate domain-specific requirements are present for high-complexity domains (H
 - 💬 If low complexity (general): Skip detailed checks
 - 🎯 If high complexity: Validate required special sections
 - 💾 Append compliance findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
+- 📖 <display>Proceeding to next check...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-09-project-type-validation.md

@@ -47,7 +47,7 @@ Validate project-type specific requirements are properly documented - different
 - 🎯 Validate required sections for that project type are present
 - 🎯 Validate excluded sections for that project type are absent
 - 💾 Append compliance findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
+- 📖 <display>Proceeding to next check...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md

@@ -46,7 +46,7 @@ Validate Functional Requirements meet SMART quality criteria (Specific, Measurab
 - 🎯 Score each FR on SMART criteria (Specific, Measurable, Attainable, Relevant, Traceable)
 - 💾 Flag FRs with score < 3 in any category
 - 📖 Append scoring table and suggestions to validation report
-- 📖 Display "Proceeding to next check..." and load next step
+- 📖 <display>Proceeding to next check...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md

@@ -46,7 +46,7 @@ Assess the PRD as a cohesive, compelling document - evaluating document flow, du
 - 🎯 Use Advanced Elicitation for multi-perspective assessment
 - 🎯 Evaluate document flow, dual audience, BMAD principles
 - 💾 Append comprehensive assessment to validation report
-- 📖 Display "Proceeding to next check..." and load next step
+- 📖 <display>Proceeding to next check...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-12-completeness-validation.md

@@ -47,7 +47,7 @@ Final comprehensive completeness check - validate no template variables remain,
 - 🎯 Validate section-specific completeness
 - 🎯 Validate frontmatter completeness
 - 💾 Append completeness matrix to validation report
-- 📖 Display "Proceeding to final step..." and load next step
+- 📖 <display>Proceeding to final step...</display> and load next step
 - 🚫 FORBIDDEN to pause or request user input
 
 ## CONTEXT BOUNDARIES:

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md

@@ -195,7 +195,6 @@ overallStatus: '{Pass/Warning/Critical based on all findings}'
   - Return to menu
 
 - **IF X (Exit):**
-  - Display:
     <display>
     **Validation Report Saved:** {validationReportPath}
 

src/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md

@@ -266,8 +266,6 @@ Prepare the content to append to the document:
 
 **Note:** Project initialization using this command should be the first implementation story.
 
-```
-
 ### 9. Present Content and Menu
 
 Show the generated content and present choices:
@@ -340,4 +338,3 @@ When user selects 'C', append the content directly to the document using the str
 After user selects 'C' and content is saved to document, load `./step-04-decisions.md` to begin making specific architectural decisions.
 
 Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!
-```

src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-04-self-check.md

@@ -74,8 +74,7 @@ If `{execution_mode}` is "tech-spec":
 
 ## IMPLEMENTATION SUMMARY
 
-Present summary to transition to review:
-
+<display>
 ```
 **Implementation Complete!**
 
@@ -86,6 +85,7 @@ Present summary to transition to review:
 
 Proceeding to adversarial code review...
 ```
+</display>
 
 ---
 

src/bmm/workflows/generate-project-context/steps/step-01-discover.md

@@ -36,7 +36,7 @@ First, check if project context already exists:
 
 - Look for file at `{project_knowledge}/project-context.md or {project-root}/**/project-context.md`
 - If exists: Read complete file to understand existing rules
-- Present to user: "Found existing project context with {number_of_sections} sections. Would you like to update this or create a new one?"
+- <display>Found existing project context with {number_of_sections} sections. Would you like to update this or create a new one?</display>
 
 ### 2. Discover Project Technology Stack
 

src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md

@@ -105,7 +105,7 @@ When an agent asks the user a specific question:
 
 - End that response round immediately after the question
 - Clearly highlight: **[Agent Name] asks: [Their question]**
-- Display: _[Awaiting user response...]_
+- <display>_[Awaiting user response...]_</display>
 - WAIT for user input before continuing
 
 **Rhetorical Questions:**