suzmii
d1bfe4c08b
Project CI / AI game creator shell Rust lane 1/2 (pull_request) Has been cancelled
Project CI / AI game creator shell Rust lane 2/2 (pull_request) Has been cancelled
Project CI / AI game creator shell Rust crates (pull_request) Has been cancelled
Project CI / Backend tests (pull_request) Has been cancelled
Project CI / Native shell tests (pull_request) Has been cancelled
Project CI / Frontend tests (pull_request) Has been cancelled
Project CI / Repository checks (pull_request) Has been cancelled
Project CI / AI game creator shell web tests (pull_request) Has been cancelled
- H1：购买事务在扣费前判定 `game.owner_user_id == user_id` 并失败关闭，领域 `resolve_game_purchase_decision` 新增 `is_owner` 标记返回 `OwnerCannotPurchase`（文案「作者本人无需购买」）；api-server `map_purchase_error` 映射为 400 `GAME_PURCHASE_OWNER_EXEMPT`；购买路由按角色显式拒绝管理员令牌（403 `GAME_PURCHASE_ADMIN_NOT_ALLOWED`），管理员免购买不扣费。 - M1：`version_detail_payload` 的历史版本价格改为 `frozen_version_price_mud_points(version).unwrap_or(0)`，与待审列表及审核通过后生效的游戏行价格统一；同步把既有断言改为「历史版本缺 `priceMudPoints` 按免费（0）」。 - M2：`shared-contracts::GameDistributionVersionSummary.entry_url` 改为 `#[serde(default)] Option<String>`，与公开投影对未购买者下发的 `entryUrl: null` 一致。 - M3/L5：SpacetimeDB 购买事务改为复用 `module_game_distribution::resolve_game_purchase_decision`（新增 `game_distribution_visibility` 与 `resolve_game_distribution_purchase_decision` 包装），可购买性口径统一为「活动版本存在且 `status = published`」（复用 `public_game_distribution_version`），删除事务内联判定。 - 测试：内存领域作者自购拒绝；SpacetimeDB 购买判定五分支（免费 / 未公开 / 版本未公开 / 已拥有 / 作者自购）、事务源扫描（先判定后扣费、公开投影口径）、审核通过时历史版本价格生效为 0；api-server 管理员令牌 403、公开投影 `entryUrl: null` 可被 Rust DTO 解析、错误映射补作者豁免。 - `scripts/check-game-distribution-dto-parity.mjs` 增加可空性一致性比对（TS `| null` ⟺ Rust `Option`，允许 `?` 表示可省略），已用负例验证能拦住同类漂移。 - 同步更新 docs/【后端架构】server-rs与SpacetimeDB数据契约：登记作者豁免 / 管理员 403 / 可玩性口径 / 历史价格按 0；顺带修复 `module-game-distribution` 与 `spacetime-module` 既有未格式化行。
shared-contracts 共享 crate 说明
日期：2026-04-21
1. crate 职责
shared-contracts 是前后端兼容 contract 共享 crate，后续负责：
- HTTP 请求与响应 DTO
- SSE 事件结构与事件名约定
- response envelope、错误结构、兼容头部契约
- 各模块对外暴露的共享协议类型
2. 当前阶段说明
当前阶段已完成 Stage1 最小真实落地：
- 统一 response envelope / 头部常量
auth/login-optionsauth/meauth/sessionsruntime/settings
当前阶段继续补齐的 Stage2 鉴权 DTO：
auth/entryauth/refreshauth/logoutauth/logout-allauth/phone/send-codeauth/phone/loginauth/wechat/startauth/wechat/callbackauth/wechat/bind-phoneauth/wechat/miniprogram-login
当前阶段继续补齐的 Stage3 公开请求 DTO：
assets/direct-upload-ticketsassets/read-urlassets/objects/confirmassets/objects/bindstory-sessions/beginstory-sessions/continue
当前阶段继续补齐的 Stage4 显式成功响应 DTO：
assets/direct-upload-ticketsassets/read-urlassets/objects/confirmassets/objects/bindstory-sessions/beginstory-sessions/continue
当前阶段新增 Stage6 character visual 兼容 DTO：
assets/character-visual/generateassets/character-visual/jobs/:taskIdassets/character-visual/publish
当前阶段新增 Stage7 character animation 模板与导入兼容 DTO：
assets/character-animation/templatesassets/character-animation/import-video
当前阶段新增 Stage8 character workflow cache 第一批兼容 DTO：
assets/character-workflow-cacheassets/character-workflow-cache/:characterId
当前阶段新增 Stage9 character animation 主链兼容 DTO：
assets/character-animation/generateassets/character-animation/jobs/:taskIdassets/character-animation/publish
当前阶段新增 Stage5 story session scoped runtime story 写读 DTO：
BeginStoryRuntimeSessionRequestResolveStoryRuntimeActionRequestStoryRuntimeProjectionResponseStoryRuntimeMutationResponseStoryRuntimeSnapshotPayload仅用于 story session scoped 写侧持久化边界，不复用旧/api/runtime/story/*总入口 contract。
WP-DEL 已删除旧 runtime story HTTP DTO：RuntimeStoryStateResolveRequest、RuntimeStoryBootstrapRequest/Response、RuntimeStoryActionResponse 和旧 RuntimeStorySnapshotPayload。runtime_story 模块中仍保留的 RuntimeStoryViewModel、RuntimeStoryPresentation、RuntimeStoryPatch 与 battle presentation 是当前投影/表现构件，不作为旧 HTTP 写入口。
当前仍刻意未做：
- SSE 事件结构
- 自动代码生成或跨语言 contract 同步
- 其他尚未收口模块的 handler 响应体显式 DTO 化
3. 边界约束
shared-contracts只放协议类型与兼容结构，不承接业务规则、供应商适配或状态写入逻辑。- 各模块 crate 对外暴露的协议优先复用这里的共享定义，避免重复散落。
- 前端兼容契约一旦进入本 crate，就必须与任务清单和基线文档同步维护。
assets模块依赖platform-oss的稳定返回类型，默认通过oss-contractsfeature 给api-server使用；SpacetimeDB WASM 构建链路必须通过 workspace 依赖关闭默认 feature，避免把platform-oss/reqwest/wasm-bindgen带进spacetime-module。