docs: update readme, logs and prd

Author: jaiswalism

Implementation.md

@@ -114,15 +114,31 @@ Go back through Phases 2–7 and make sure every case in the PRD's error table i
 
 ---
 
-## Phase 11 — QA Pass
+## Phase 11 — Sync Past Submissions
+
+1. Implement GraphQL/API scraping to fetch all previously "Accepted" submissions from LeetCode.
+2. Inject scraping script into a foreground tab to securely use CSRF cookies.
+3. Batch queue these historical solutions through the `sync-engine` to prevent duplicate spam and handle rate limiting gracefully.
+
+---
+
+## Phase 12 — Multi Platform Support
+
+1. Refactor or extend `PlatformAdapter` to handle sites like GeeksForGeeks or HackerRank.
+2. Implement specific `GeeksForGeeksAdapter` including DOM observation and code extraction.
+3. Update Options UI so users can select which platforms to sync from.
+
+---
+
+## Phase 13 — QA Pass
 
 1. Manual test matrix: multiple languages, all 3 difficulties, all 4 folder structures, re-submission (duplicate + version-bump paths), rate-limit simulation (mock 403 response), token revocation mid-session.
 2. Memory/perf sanity check — nothing in this PRD's original targets was load-bearing, but do confirm the popup doesn't lag and the content script isn't leaking listeners on SPA navigation (LeetCode is a SPA — watch for content script re-injection issues across problem navigations).
 3. Fresh-profile install test — the exact first-run flow a new user hits, no dev-console assists.
 
 ---
 
-## Phase 12 — Chrome Web Store Packaging
+## Phase 14 — Chrome Web Store Packaging
 
 1. Write the store listing emphasizing the security model (fine-grained PAT, single repo, no OAuth, no telemetry) — this is your actual differentiator, lead with it.
 2. Privacy policy page (even a static one) — required for Web Store listing, and directly reinforces the trust positioning from your Guiding Philosophy section.
@@ -142,11 +158,13 @@ Phase 4  → sync engine (joins 1+2+3)
 Phase 5  → README generator
 Phase 6  → commit templating
 Phase 7  → retry queue
-Phase 8  → popup UI
-Phase 9  → options page
-Phase 10 → error handling pass
-Phase 11 → QA
-Phase 12 → Web Store packaging
+Phase 8  → GitHub Actions CI
+Phase 9  → popup UI
+Phase 10 → options page
+Phase 11 → sync past submissions
+Phase 12 → multi platform support
+Phase 13 → error handling & QA
+Phase 14 → Web Store packaging
 ```
 
 Phases 2 and 3 can be built in parallel (or in either order) since neither depends on the other — they only meet at Phase 4. Everything from Phase 5 onward is strictly sequential.

PRD.md

@@ -259,13 +259,11 @@ Users can change repository, disconnect repository, or switch repositories.
 
 # 8. V1.5 / V2 Features
 
-## Import Existing History
+## Import Existing History (Moved to V1)
 
 Fetch all past accepted submissions and upload them retroactively, using the same `_v1`, `_v2` suffix scheme for any problem with multiple historical submissions.
 
-*(Deferred from V1 — not required to prove the core detect → commit → README loop; adds meaningfully to initial scope and GitHub API load.)*
-
-## Multi Platform
+## Multi Platform (Moved to V1)
 
 LeetCode, GeeksforGeeks, Codeforces, CodeChef, HackerRank, AtCoder
 
@@ -424,9 +422,9 @@ Repository, Folder Structure, README, Commit Template, Retry Queue, Advanced
 
 # 16. Roadmap
 
-**V1** — LeetCode, GitHub Sync, README, PAT, Logs, Retry Queue, Duplicate Detection, Version History (`_v1`/`_v2` suffixing)
+**V1** — LeetCode, GitHub Sync, README, PAT, Logs, Retry Queue, Duplicate Detection, Version History, Import Existing History, Multi Platform (GeeksForGeeks, HackerRank)
 
-**V1.5 / V2** — Import Existing History, Multiple Platforms, Statistics Dashboard, Study Notes, Revision Planner, Multi-language Solutions, AI Explanation
+**V1.5 / V2** — Statistics Dashboard, Study Notes, Revision Planner, Multi-language Solutions, AI Explanation
 
 **V3 (not scoped)** — Plugin Marketplace, Self-hosted Sync, VS Code Companion, Mobile Companion — revisit after V2 ships, no commitments made in this document.
 

README.md

@@ -14,6 +14,8 @@
   - By Language (`javascript/1-two-sum.js`)
   - Flat structure
 - **Duplicate Detection**: Intelligently hashes your code to prevent spamming your repo with identical submissions if you click "Submit" multiple times.
+- **Offline Retry Queue**: If your internet drops or GitHub's API rate limits you, your submissions are safely stored in a local queue and automatically retried later.
+- **Popup Dashboard**: Click the extension icon to view your sync status, see detailed logs, and manage any pending commits directly from the queue.
 - **Smart Versioning**: Optionally keep a history of your attempts (e.g., `_v1`, `_v2`) or choose to overwrite them in place.
 - **Auto-generated README**: Automatically maintains a markdown table and difficulty stats right in your repository.
 - **File Headers**: Automatically prepends metadata (Title, Difficulty, Runtime, Memory, LeetCode URL) to every uploaded file.

WORK_LOG/CHANGELOG.md

@@ -27,7 +27,8 @@
 - [x] Phase 5: README Generator (`src/github/readme-generator.ts`)
 - [x] Phase 6: Commit Templating & Batched Commits via Git Database API
 - [x] Phase 7: Retry Queue & Popup Dashboard Management
-- [x] Phase 8 & 9: Popup UI and Options Page (`src/popup`, `src/options`)
+- [x] Phase 8: GitHub Actions CI/CD Release Pipeline
+- [x] Phase 9 & 10: Popup UI and Options Page (`src/popup`, `src/options`)
 - [x] Rebranding & Git History Rewrite: Renamed project to CommitCode, rebuilt Git history, expanded `README.md`.
 ### Details
 **Phase 4: Sync Engine**

WORK_LOG/CURRENT_FOCUS.md

@@ -1,6 +1,7 @@
 # Current Focus
 
-Phase 8 — Advanced: GitHub Actions / CI Integration (Optional/Exploratory)
-- Evaluate whether we want to provide users with a pre-built GitHub Action to automatically run tests or update their README in the repo itself.
-- Consider polishing the codebase for public release (e.g., removing debug logs, checking edge cases).
-- Ensure all previously built phases are perfectly stable.
+Phase 11 — The "Holy Grail": Sync Past Submissions
+- We need a mechanism to fetch the user's entire LeetCode submission history.
+- Add a "Sync All Previous Submissions" button in the Options page.
+- Need to parse history via LeetCode GraphQL API.
+- Need to batch process them and send them to the SyncEngine.