Add UpdateFeatureStatus custom MCP tool for safe feature status updates

- Created createFeatureToolsServer() method that creates an MCP server with
  the UpdateFeatureStatus tool
- Tool accepts featureId and status parameters to safely update feature status
- Updated all prompts to instruct agents to use the custom tool instead of
  directly modifying feature_list.json
- Added mcpServers configuration to all query options
- This prevents race conditions and accidental state restoration when
  Claude Code updates feature status

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

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

.automaker/feature_list.json

@@ -25,7 +25,7 @@
     "category": "Kanban",
     "description": "When adding a new feature inside the modal there's an add feature button. Can you add a shortcut of shift? Enter which if you click shift enter I'll automatically add it in",
     "steps": [],
-    "status": "in_progress"
+    "status": "verified"
   },
   {
     "id": "feature-1765287141131-dz489etgj",
@@ -39,7 +39,7 @@
     "category": "Core",
     "description": "I'm noticing that when cards finish running, sometimes Cloud Code will update the featureless JSON and restore old state. I think instead of actually modifying the featureless JSON manually, it should call an custom tool, and that tool should update a card directly into the JSON so that Cloud Code isn't potentially messing with other things. All it needs to do is just pass in an ID and a status, and that's going to update in the JSON list.",
     "steps": [],
-    "status": "in_progress"
+    "status": "verified"
   },
   {
     "id": "feature-1765287638726-rtxxdpobi",