Add session learnings and context notes to v1.1.14 history

Key learnings documented:
- Diagnostic-first approach after multiple failed fixes
- User has no live access currently (testing delayed)
- Release workflow now well-established
- Shell context handling with absolute paths
- Debug logging best practices
- Context preservation from session summary

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

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

CLAUDE.md

@@ -1860,6 +1860,27 @@ Total products available: 4
 
 **Status:** v1.1.14 released and deployed, awaiting user to enable WP_DEBUG and share logs
 
+**Additional session notes:**
+
+This session demonstrated the importance of changing debugging strategy after multiple failed fix attempts. Key takeaways:
+
+1. **Diagnostic First, Fix Later**: After 3 consecutive fix attempts failed (v1.1.11-v1.1.13), the approach changed to adding comprehensive logging instead of guessing at another fix. This systematic approach is more efficient than trial-and-error.
+
+2. **User Has No Live Access**: User reported "We have currently no live access to that version", meaning they cannot test v1.1.14 immediately. The debug release will be tested when they have access again, and logs will be provided then.
+
+3. **Release Workflow Perfected**: The release creation process (dev → version bump → merge main → tag → package → checksums → push) is now well-established and executed cleanly without errors.
+
+4. **Shell Context Issues**: Encountered shell working directory issues during release packaging (pwd failures after temp directory removal), but worked around by using absolute paths with `-C` flag for git commands and absolute paths for Read/Glob tools.
+
+5. **Debug Logging Patterns**:
+   - Always wrap in `WP_DEBUG` checks for production safety
+   - Log at every decision point in the process
+   - Use `print_r($array, true)` for complex data structures
+   - Log both inputs (criteria, query args) and outputs (posts found, final count)
+   - Include identifiable markers (product IDs, names) in logs
+
+6. **Context Preservation**: This session continued from a summary that preserved all critical information about the v1.1.11-v1.1.13 debugging journey, allowing seamless continuation of work.
+
 ---
 
 **For AI Assistants:**