docs: Add timestamp requirement to issue template

- Updated ISSUE_TEMPLATE.md with stricter timestamp guidelines
- Added requirement: EVERY entry must have timestamp - no exceptions
- Added examples of entries that need timestamps
- Added section on common mistakes to avoid
- Created memory note: /workspace/memory/TIMESTAMP-REQUIREMENT.md
- All future progress.md entries will follow YYYY-MM-DD HH:MM format

ISSUE_TEMPLATE.md

@@ -220,6 +220,8 @@
 
 **IMPORTANT: All entries MUST include full timestamps (YYYY-MM-DD HH:MM) to track issue progress across multiple days.**
 
+**CRITICAL RULE:** Every single entry in the session log must have a timestamp. No exceptions.
+
 - **[YYYY-MM-DD HH:MM]:** [Event description - e.g., "Project initiated, diagnosis started"]
 - **[YYYY-MM-DD HH:MM]:** [Event description - e.g., "Diagnostic tests completed, root cause identified"]
 - **[YYYY-MM-DD HH:MM]:** [Event description - e.g., "Parts ordered, awaiting delivery"]
@@ -227,6 +229,12 @@
 
 **Session Log Guidelines:**
 - Use full timestamp format: YYYY-MM-DD HH:MM (24-hour format)
+- **Include timestamp for EVERY action, test, and decision**
+- Track when parts were ordered, received, and installed (may span multiple days)
+- Note when tests were performed and results observed
+- Record when vehicle was test-driven and any issues found
+- **This enables accurate troubleshooting timeline and pattern recognition across multiple days**
+- **Do not skip timestamps for any entries - even quick notes or observations**
 - Include timestamp for EVERY action, test, and decision
 - Track when parts were ordered, received, and installed (may span multiple days)
 - Note when tests were performed and results observed