172bc22404
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
CI(Backend tests 与 Repository checks)在 `check:spacetime-schema` 红: 「SpacetimeDB 表 game_distribution_game 的第 26 个字段从 price_mud_points 变为 fork_authorization,疑似字段顺序被调整」。 根因:本次合并把两侧各自「在表尾追加」的列并成了「我们的列在 master 的列之前」——schema guard 对表的字段 相对顺序是按 index 逐位比对的(只允许在结构体末尾追加)。 - `game_distribution_game` 表:`price_mud_points`(master 先追加,第 26 位)回到原位,本分支的 `fork_authorization` 追加在它**之后**(表尾); - `GameDistributionGameSnapshot` 按同一纪律排(同一 game 行的 RPC 形状,避免表与快照两套顺序); - 重新生成绑定:`module_bindings/game_distribution_game_type.rs`、`..._game_snapshot_type.rs` (列顺序属 wire format,客户端绑定必须与模块同步); - 两处结构体注释写明该纪律(master 的列保持 index、我们的列追加在后),避免下一次合并再踩; - 文档:`docs/project-memory/shared-memory/pitfalls.md` 增一条「合并 master 后 schema guard 的基线盲区」—— 本地守卫默认基线是 `git merge-base HEAD origin/master`,**merge 提交尚未建立时看不见**这类重排, 因此合并后必须用 `SPACETIME_SCHEMA_BASE_REF=<PR base>` 复跑。 门禁:`SPACETIME_SCHEMA_BASE_REF=9f4c7d76 npm run check:spacetime-schema` 0(98 表);wasm build 0; `cargo check --all-targets` 0;`cargo test -p module-game-distribution` 113 passed;`cargo test -p api-server game_distribution` 101 passed;`cargo test -p module-runtime` 0;`cargo test -p spacetime-client` 43 passed; `cargo test -p spacetime-module` 294 passed / 1 ignored;DTO parity 0(62 组 / 17 构建器 / 15 手拼类型); `check:project-bundle-policy-parity` OK;`check:production-ops` OK;`check:doc-index` OK(261 份);`check:encoding` 0(5525 files);`cargo fmt --all --manifest-path server-rs/Cargo.toml -- --check` 0;`git diff --check` 0。