Commit Graph

5 Commits

  • Fix session persistence after page refresh
    Root cause: loadManuallyCreatedProjects() was restoring projects with
    stale session arrays from localStorage. When loadProjects() tried to
    merge with fresh API data, the stale sessions would override.
    
    Fix 1: In loadManuallyCreatedProjects(), reset the sessions array to
    empty for each loaded project. This ensures sessions always come from
    the API (authoritative source) rather than localStorage.
    
    Fix 2: In createSessionInFolder(), remove the redundant initialize()
    call after loadProjects(). initialize() would reload stale localStorage
    data, undoing the fresh data fetched by loadProjects().
    
    Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
  • Fix virtual workingDir handling in addSessionToProject
    - Modified addSessionToProject to correctly extract projectKey from virtual workingDirs
    - Virtual workingDir format: /virtual/projects/{projectKey}
    - Previously was converting slashes to dashes, causing mismatch
    - Added console logging to track session-to-project assignment
    
    Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
  • Fix project isolation: Make loadChatHistory respect active project sessions
    - Modified loadChatHistory() to check for active project before fetching all sessions
    - When active project exists, use project.sessions instead of fetching from API
    - Added detailed console logging to debug session filtering
    - This prevents ALL sessions from appearing in every project's sidebar
    
    Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
  • Mark close button task as complete in PROMPT.md
    All requirements implemented:
    - Close buttons added to project tabs (session tabs already had them)
    - Code committed and documented
    - Responsive behavior implemented
    
    Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
  • Add final report and WordPress update script
    Created comprehensive final documentation for the WordPress blog post update:
    
    - FINAL-REPORT.md: Complete status report and assessment
    - update-wordpress.py: Automated update script (non-functional due to REST API)
    - Updated PROMPT.md with completion status
    
    Key findings:
    - WordPress REST API is not accessible (returns 404)
    - Manual update via WordPress admin is required
    - All content creation and documentation is complete
    - Step-by-step guide provided for manual update
    
    The task is functionally complete from an automation standpoint.
    Manual WordPress update is the only remaining action item.
    
    Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>