feat(protection): implement multi-layered protection for feature_list.json

Introduces a comprehensive strategy to safeguard the feature_list.json file from accidental modifications. Key enhancements include:

1. **Prompt-Level Warnings**: Added explicit warnings in agent prompts to prevent direct modifications.
2. **Dedicated MCP Tool**: Implemented the UpdateFeatureStatus tool for safe feature updates.
3. **File-Level Validation & Auto-Backup**: Added validation checks and automatic backups before modifications to prevent data loss.
4. **Tool Access Control**: Restricted agent access to critical tools, ensuring only the designated MCP tool can modify the feature list.

This update significantly reduces the risk of catastrophic data loss and ensures a robust feature management process.

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

.automaker/initializer_prompt.md

@@ -58,6 +58,16 @@ Features can ONLY be marked as passing (change "passes": false to "passes": true
 Never remove features, never edit descriptions, never modify testing steps.
 This ensures no functionality is missed.
 
+**🚨 CRITICAL: AFTER CREATING .automaker/feature_list.json 🚨**
+Once you create this file in this session, you MUST NEVER directly modify it again.
+In all future sessions, feature_list.json is COMPLETELY OFF-LIMITS for:
+- Write tool
+- Edit tool
+- Any bash commands (echo, sed, awk, etc.)
+- Any form of direct file modification
+
+The ONLY way to update features is through the UpdateFeatureStatus MCP tool.
+
 ### SECOND TASK: Create init.sh
 
 Create a script called `init.sh` that future agents can use to quickly