fix(workflows): remove hardcoded years from WebSearch queries (#1040)

* update 2024 to 2025

* fix(workflows): remove hardcoded years from WebSearch queries

Years in search queries (2024/2025) do not improve results - search
engines already prioritize current documentation. Tested all patterns
and confirmed identical quality results with/without years.

Removes years from:
- step-03-starter.md (5 queries)
- step-04-decisions.md (2 queries)
- game-architecture/instructions.md (2 queries)

Leaves file-utils.md unchanged (test fixture data, not a search query).

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

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(workflows): remove year placeholders from research WebSearch queries

Search engines return current results regardless of year - removes
{{current_year}} and hardcoded 2025 from step-05-technical-trends.md

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

Co-Authored-By: Claude <noreply@anthropic.com>

* refactor(workflows): replace {{current_year}} with semantic alternatives

Replaces year placeholder with context-appropriate wording:
- 'current data' for up-to-date information
- 'web searches' without year qualifier
- Updated failure mode to focus on using web searches

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

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(workflows): clarify failure mode about stale training data

Rephrased to explicitly mention training data cutoff as the reason
to use web searches for current technology trends.

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

Co-Authored-By: Claude <noreply@anthropic.com>

* refactor(workflows): make web search references platform-agnostic

- Remove hardcoded year references from WebSearch queries
- Replace `WebSearch` tool name with natural language "search the web"
- Soften "training data is stale" to "verify and supplement your knowledge"
- Add web search prerequisite check to research workflow
- Add platform-agnostic design note to CLAUDE.md

This framework targets 15+ agentic platforms, not just Claude Code.
Tool-specific syntax like `WebSearch:` won't work across all platforms.

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* refactor(research): clean up prompts and routing

---------

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

src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md

@@ -140,14 +140,14 @@ I see {{epic_count}} epics with {{story_count}} total stories.
   </check>
 
 <action>Search for relevant starter templates with websearch, examples:
-<WebSearch>{{primary_technology}} starter template CLI create command latest {date}</WebSearch>
-<WebSearch>{{primary_technology}} boilerplate generator latest options</WebSearch>
+Search the web: "{{primary_technology}} starter template CLI create command latest"
+Search the web: "{{primary_technology}} boilerplate generator latest options"
 </action>
 
   <check if="starter_templates_found">
     <action>Investigate what each starter provides:
-      <WebSearch>{{starter_name}} default setup technologies included latest</WebSearch>
-      <WebSearch>{{starter_name}} project structure file organization</WebSearch>
+      Search the web: "{{starter_name}} default setup technologies included latest"
+      Search the web: "{{starter_name}} project structure file organization"
     </action>
 
     <check if="{user_skill_level} == 'expert'">
@@ -176,7 +176,7 @@ I see {{epic_count}} epics with {{story_count}} total stories.
 
     <check if="user_accepts_starter">
       <action>Get current starter command and options:
-        <WebSearch>{{starter_name}} CLI command options flags latest 2024</WebSearch>
+        Search the web: "{{starter_name}} CLI command options flags latest"
       </action>
 
       <action>Document the initialization command:
@@ -282,7 +282,7 @@ Let's work through the remaining {{remaining_count}} decisions."
 
 <step n="4" goal="Facilitate collaborative decision making" repeat="for-each-decision">
   <critical>Each decision must be made WITH the user, not FOR them</critical>
-  <critical>ALWAYS verify current versions using WebSearch - NEVER trust hardcoded versions</critical>
+  <critical>ALWAYS search the web to verify current versions - NEVER trust hardcoded versions</critical>
 
 <action>For each decision in priority order:</action>
 
@@ -327,8 +327,8 @@ Let's work through the remaining {{remaining_count}} decisions."
 
   <check if="decision_involves_specific_technology">
     <action>Verify current stable version:
-      <WebSearch>{{technology}} latest stable version 2024</WebSearch>
-      <WebSearch>{{technology}} current LTS version</WebSearch>
+      Search the web: "{{technology}} latest stable version"
+      Search the web: "{{technology}} current LTS version"
     </action>
 
     <action>Update decision record with verified version: