Files

T

Jeffery f44200f543 feat: 完成 B 群組 — 資料層與核心領域模型

- 導入 Prisma 7.9.1 + SQLite（better-sqlite3 driver adapter），prisma.config.ts 管理連線設定
- 完整資料模型：User／Work／Character／CharacterAlias／EpisodicMemory／SemanticMemory／
  ProceduralRule／EmotionState／Relationship／SentimentLedgerEntry
- packages/db：Prisma Client 存取層（ESM，因 Prisma 7 產出的 generated client 僅支援 ESM）
- apps/api 隨之改為 ESM 以相容 packages/db
- packages/shared：新增角色／記憶／情緒／關係共用型別，api 與 web 皆從此匯入
- prisma/seed.ts：建立測試使用者與元氣型測試角色，含完整關係帳本與記憶種子資料
- apps/api：新增 GET /characters
- scripts/smoke/B.mjs：驗證資料表齊全、API 讀出種子角色、關係與記憶可寫入讀出
- 保留 Prisma 官方隨 CLI 附的 agent skill 文件（.agents/skills 等），供後續群組查閱

npm run restart && npm run smoke -- B 皆通過（B-V），A 群組冒煙測試無回歸。

2026-08-13 09:43:15 +08:00

3.2 KiB

Raw Permalink Blame History

verify-cutover-checklist

Verification checklist for a v6 → Prisma Next cutover: the data never moves — only the code does.

Priority

CRITICAL

Why It Matters

A v6 → Next migration is a client and workflow migration against the same MongoDB database — there is no data export/import step, and introducing one (or pointing the new stack at a fresh database) turns a code migration into an outage. The checklist below keeps the cutover observable and reversible.

Ground rules

No data moves. The Next contract is authored to describe the existing collections; both stacks read the same database during the staged phase.
v6 stays runnable until cutover is verified. Do not delete the v6 client, schema, or dependencies until the checklist passes.

Checklist

Same database, verified: the Next config points at the same connection string / database name the v6 app uses (minus v6-specific URL parameters that the mongodb@^7 driver rejects — validate the URL with the driver first).
Server floor: MongoDB server is 8.0+ (Next's requirement; v6 tolerated older). Confirm before authoring any contract.
Contract round-trip on a copy: on a staging copy (or mongodb-memory-server), emit the contract, run plan → migrate → verify → sign, and confirm verify passes against data copied from production shape. Verification failures here are contract-mapping bugs, not database problems.
Index parity: enumerate indexes on every collection (db.collection.getIndexes()) and confirm the Next contract declares the same set — v6 db push may have created indexes the new contract must re-declare, or verification and query performance will diverge.
Validator impact assessed: Next emits closed $jsonSchema validators by default; confirm legacy documents (extra fields, drifted shapes) pass them on the staging copy before applying to production.
Storage-name addressing audited: every ported call site uses collection storage names (db.orm.users), not model names (see schema-contract-mapping.md).
Transaction inventory mapped: grep the v6 app for $transaction; each hit gets a driver-session equivalent (the mongodb driver is directly available; the façade wrapper is expected soon — see client-api-mapping.md).
Raw call inventory mapped: every $runCommandRaw / findRaw / aggregateRaw call has an explicit Next-side replacement (mongoRaw(...) lane or pipeline builder).
Staged read-only soak: run the Next stack read-only against staging/production data alongside v6 and compare outputs before allowing writes.
Cutover + rollback: switch writes to Next only after the soak; keep the v6 branch deployable as the rollback path. Rolling back is a code rollback — the data was never moved.

After cutover, install and follow Prisma Next's own skills for ongoing work (see the hand-off rule in SKILL.md).

References

v6 MongoDB documentation
Prisma Next migrations + queries skills — authoritative for the Next side; verified @ a2791c5dd59d579b4b3052942ae7f8fe5e2ee852

3.2 KiB Raw Permalink Blame History