fix: Release已读状态跨设备同步 + 仓库四字段持久化

[lostiv]

@

Summary

• Release 已读状态跨设备同步：标记已读时推送后端 PATCH，自动同步时从后端合并 is_read
• 仓库四字段持久化：forks_count / forks / last_release_fetch_time / has_fetched_releases 添加到 DB

Changes

前端

• store markReleaseAsRead/markAllReleasesAsRead 同步设置 is_read 到 Release 对象
• backendAdapter 添加 markReleaseAsRead/markAllReleasesAsRead 方法
• ReleaseTimeline fire-and-forget 调用后端标记已读
• autoSync 拉取时合并后端 is_read 到本地 readReleases Set

后端

• DB migration v2 添加四列到 repositories 表
• transformRepo/PUT/PATCH 支持新四字段

Test plan

• TypeScript 类型检查通过
• 标记 Release 已读后 Network 面板可见 PATCH /api/releases/:id
• 清除 IndexedDB 后自动同步恢复已读状态
• 仓库 forks_count 等字段经 backend 同步往返不丢失
  @

Summary by CodeRabbit

• New Features

  • Server-side AI repository analysis with batch processing and progress tracking
  • Automatic backup scheduling with retention policies
  • Docker-based deployment for frontend and backend services
  • Enhanced fork management and upstream synchronization

• Improvements

  • Dynamic version reporting from server configuration
  • Better data preservation during repository syncs
  • Improved release tracking and subscription management
  • Refined error handling and user feedback

• Chores

  • Version bumped to 0.6.2
  • Updated Node.js runtime to version 22
  • Docker Compose configured to use prebuilt images

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Warning

Ignoring CodeRabbit configuration file changes. For security, only the configuration from the base branch is applied for open source repositories.

📝 Walkthrough

Walkthrough

Adds backend analysis batches and auto-backup services with routes/scheduler, DB/schema/type changes, frontend pivot to backend-first workflows (analysis, sync, forks, releases, backup), proxy endpoints (translate/WebDAV), CI/docker/version updates, and extensive skills/docs.

Changes

End-to-end backend-first analysis/backup and frontend integration

Layer / File(s)	Summary
Full stack implementation and documentation .github/..., server/src/..., src/services/..., src/components/..., .agents/skills/*, docs/*, versions/*, package.json, Docker*, docker-compose.yml	Implements server analysis/backup with routes/scheduler and schema/types, migrates frontend services/components to backend-first flows, adds proxy endpoints and adapters, simplifies auto-sync, updates CI/docker/versioning, and adds skills/docs.

Sequence Diagram(s)

sequenceDiagram
  participant Frontend (UI)
  participant Backend Adapter
  participant Analysis Routes
  participant Analysis Service
  Frontend (UI)->>Backend Adapter: Start batch analysis (repoIds, configId, lang, categories)
  Backend Adapter->>Analysis Routes: POST /api/analysis/batch
  Analysis Routes->>Analysis Service: createBatch -> run
  loop Poll progress
    Frontend (UI)->>Backend Adapter: Get batch status
    Backend Adapter->>Analysis Routes: GET /api/analysis/batch/:id
  end
  Frontend (UI)->>Backend Adapter: Cancel (if needed)
  Backend Adapter->>Analysis Routes: POST /api/analysis/batch/:id/cancel

Loading

Estimated code review effort

🎯 5 (Critical) | ⏱️ ~120 minutes

Possibly related PRs

• AmintaCCCP/GithubStarsManager#132 — Also modifies ForkTimeline to use backend adapter for forks/sync/workflows.
• AmintaCCCP/GithubStarsManager#129 — Related release-sync flow; uses multi-repo release fetch and incremental handling.
• AmintaCCCP/GithubStarsManager#43 — Earlier backend integration groundwork (Express+SQLite) extended here with new routes/services.

Poem

Bunny ships a batch that hums,
Backups bloom on WebDAV drums.
Forks all march in tidy rows,
Releases flow where backend goes.
Skills and docs like clover spread—
Carrots tagged, the CI fed.
Thump! New versions hop ahead. 🥕✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.