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

2.5 KiB

Raw Permalink Blame History

api-basics

Core conventions for the Prisma Management API. All three prisma-postgres-* skills share these patterns.

Base URL

https://api.prisma.io/v1

API documentation: https://api.prisma.io/v1/doc

Response Envelope

Single resource

{
  "data": {
    "id": "proj_clx7abc123def456",
    "type": "project",
    "name": "My Project",
    "createdAt": "2025-06-15T10:30:00.000Z"
  }
}

Collection

{
  "data": [
    { "id": "proj_aaa", "type": "project", "name": "Alpha" },
    { "id": "proj_bbb", "type": "project", "name": "Beta" }
  ],
  "pagination": {
    "hasMore": true,
    "nextCursor": "clx7cursor123"
  }
}

Resource ID Prefixes

Every resource ID carries a type prefix:

Prefix	Resource
`proj_`	Project
`db_`	Database
`con_`	Connection
`wksp_`	Workspace

Always include the prefix when sending IDs in API requests.

Pagination

Collection endpoints use cursor-based pagination:

GET /v1/projects?limit=10
GET /v1/projects?cursor=clx7abc123&limit=10

Parameter	Type	Default	Description
`cursor`	string	—	Opaque cursor from `nextCursor`
`limit`	number	100	Maximum items per page

Continue fetching while pagination.hasMore is true, using pagination.nextCursor as the cursor parameter.

Error Responses

All errors follow this shape:

{
  "error": {
    "code": "resource-not-found",
    "message": "database with id db_abc not found"
  }
}

Error codes by HTTP status

HTTP Status	Error Code	Meaning
400	`client-error`	Malformed request
401	`authentication-failed`	Missing or invalid token
403	`permission-denied`	Token lacks required access
404	`resource-not-found`	Resource does not exist or is not accessible
422	`validation-error`	Request body failed validation
429	`rate-limit-exceeded`	Too many requests
500	`internal-server-error`	Server error — retry after a delay

Self-correction patterns

401: Token is invalid or expired. Create a new service token in Console → Workspace Settings → Service Tokens.
404: Verify the resource ID includes the correct prefix (proj_, db_, con_). Use GET /v1/projects or GET /v1/databases to list available resources.
422: Check the request body against the endpoint schema. Common issues: missing required fields, invalid region ID, empty name.
429: Wait 2–5 seconds and retry. If repeated, increase the backoff interval.

2.5 KiB Raw Permalink Blame History Unescape Escape