docs(ai-plan): 迁移数据仓库持久化计划 by GeWuYou · Pull Request #258 · GeWuYou/GFramework

GeWuYou · 2026-04-19T14:33:11Z

hBc

Summary by CodeRabbit

发布说明

文档
- 新增"数据仓库持久化"主题的规划、追踪和历史归档文档，完整记录该阶段的目标、实现决策和验证结果
- 更新项目规划索引和治理追踪信息，完善主题映射关系和恢复点标记

hBc

coderabbitai · 2026-04-19T14:33:27Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 37d0b25b-8d1f-42d2-aebb-e377b45337db

📥 Commits

Reviewing files that changed from the base of the PR and between 58f3253 and 254d354.

📒 Files selected for processing (7)

ai-plan/public/README.md
ai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
ai-plan/public/data-repository-persistence/archive/todos/data-repository-persistence-history-pre-rp001.md
ai-plan/public/data-repository-persistence/archive/traces/data-repository-persistence-history-pre-rp001.md
ai-plan/public/data-repository-persistence/todos/data-repository-persistence-tracking.md
ai-plan/public/data-repository-persistence/traces/data-repository-persistence-trace.md

📜 Recent review details

⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

GitHub Check: Build and Test
GitHub Check: Code Quality & Security
GitHub Check: Analyze (C#)

🧰 Additional context used

📓 Path-based instructions (5)

**/README.md

📄 CodeRabbit inference engine (AGENTS.md)

Every user-facing package or module directory that contains a *.csproj intended for direct consumption MUST have a sibling README.md with canonical filename README.md. A module README MUST describe the module's purpose, relationship to adjacent runtime/abstractions/generator packages, major subdirectories/subsystems, minimum adoption path, and corresponding docs/zh-CN/ entry points.

Files:

ai-plan/public/README.md

ai-plan/public/**/*

📄 CodeRabbit inference engine (AGENTS.md)

ai-plan/public/**/*: Contributors MUST keep committed ai-plan/public/** content safe to publish in Git history. Never write secrets, tokens, credentials, private keys, machine usernames, home-directory paths, hostnames, IP addresses, proprietary URLs, or other sensitive environment details into any ai-plan/** file.
Never record absolute file-system paths in ai-plan/**; use repository-relative paths, branch names, PR numbers, or stable document identifiers instead.

Files:

ai-plan/public/README.md
ai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
ai-plan/public/data-repository-persistence/archive/todos/data-repository-persistence-history-pre-rp001.md
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
ai-plan/public/data-repository-persistence/todos/data-repository-persistence-tracking.md
ai-plan/public/data-repository-persistence/traces/data-repository-persistence-trace.md
ai-plan/public/data-repository-persistence/archive/traces/data-repository-persistence-history-pre-rp001.md

ai-plan/public/README.md

📄 CodeRabbit inference engine (AGENTS.md)

ai-plan/public/README.md MUST list only active topics. Do not add ai-plan/public/archive/** content to the default boot index. When a worktree-to-topic mapping changes or when a topic becomes active/inactive, contributors MUST update ai-plan/public/README.md in the same change.

Files:

ai-plan/public/README.md

ai-plan/public/*/todos/**/*

📄 CodeRabbit inference engine (AGENTS.md)

When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under ai-plan/public/<topic>/todos/ in the same change. Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point. Tracking files are recovery entrypoints, not append-only changelogs, and MUST stay concise.

Files:

ai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
ai-plan/public/data-repository-persistence/todos/data-repository-persistence-tracking.md

ai-plan/public/*/traces/**/*

📄 CodeRabbit inference engine (AGENTS.md)

Contributors MUST maintain a matching execution trace under ai-plan/public/<topic>/traces/ for complex work. The trace should record the current date, key decisions, validation milestones, and the immediate next step. Update traces at each meaningful milestone before pausing or handing work off.

Files:

ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
ai-plan/public/data-repository-persistence/traces/data-repository-persistence-trace.md

🧠 Learnings (16)

📓 Common learnings

Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/todos/**/* : When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under `ai-plan/public/<topic>/todos/` in the same change. Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point. Tracking files are recovery entrypoints, not append-only changelogs, and MUST stay concise.

Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Use `ai-plan/public/**` only for durable, handoff-safe task state. Put temporary notes, local experiments, or worktree-specific scratch recovery data under `ai-plan/private/`.

Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/traces/**/* : Contributors MUST maintain a matching execution trace under `ai-plan/public/<topic>/traces/` for complex work. The trace should record the current date, key decisions, validation milestones, and the immediate next step. Update traces at each meaningful milestone before pausing or handing work off.

Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: For any multi-step refactor, migration, or cross-module task, contributors MUST create or adopt a dedicated recovery document under `ai-plan/public/<topic>/todos/` before making substantive code changes. Recovery documents MUST record the current phase, the active recovery point identifier, known risks, and the next recommended resume step so another contributor or subagent can continue the work safely.

Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a topic is fully complete, move the entire topic directory under `ai-plan/public/archive/<topic>/` and remove it from `ai-plan/public/README.md` in the same change.

Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/**/* : Never record absolute file-system paths in `ai-plan/**`; use repository-relative paths, branch names, PR numbers, or stable document identifiers instead.

Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/README.md : `ai-plan/public/README.md` MUST list only active topics. Do not add `ai-plan/public/archive/**` content to the default boot index. When a worktree-to-topic mapping changes or when a topic becomes active/inactive, contributors MUST update `ai-plan/public/README.md` in the same change.

Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a stage inside an active topic is fully complete, move the finished artifacts into that topic's `archive/` directory instead of leaving every completed step in the default boot path. When completed and validated stages begin to accumulate, archive their detailed history out of the active `todos/` and `traces/` entry files. Keep only the current recovery point, active facts, active risks, immediate next step, and pointers to relevant archive files in the default boot path.

Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: If a task depends on observations from `ai-libs/**`, record the referenced path and conclusion in the active plan or trace when the work is multi-step or complex, or when an active tracking document already exists, rather than editing the third-party reference copy.