From a1a0901d08c96a1b50275219c91090d87ef72bc1 Mon Sep 17 00:00:00 2001 From: Yige Date: Sat, 5 Sep 2026 19:00:40 -0400 Subject: [PATCH] fix(teams): align jurisdiction member with pinned release (#126) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Why / 背景 The pinned team release `73cd87a9901cc548871927e9d5dbec8e4cc6c2b1` contains `jurisdiction-auditor` version `1.0.0`, but the merged market entry advertised `1.2.0`. That metadata mismatch makes a valid pinned release fail exact roster validation during newcomer installation. 团队发布锁 `73cd87a9901cc548871927e9d5dbec8e4cc6c2b1` 中的 `jurisdiction-auditor` 实际版本为 `1.0.0`，已合并的市场条目却写成 `1.2.0`。该元数据不一致会让新人安装时的精确 roster 校验拒绝有效的 pinned release。 ## What changed / 变更 - Set only the market roster version for `jurisdiction-auditor` back to `1.0.0`. - Keep the pinned source ref, member commits, content hashes, governance sidecar, and all other members unchanged. - 仅将市场 roster 中 `jurisdiction-auditor` 的版本恢复为 `1.0.0`。 - pinned source ref、成员 commit、content hash、治理 sidecar 与其他成员均保持不变。 ## Validation / 验证 - `uv run scripts/catalog/validate_catalog_metadata.py --json` — 0 errors, 129 existing warnings - `uv run scripts/catalog/test_validate_catalog_metadata.py` — 47 passed - `uv run scripts/catalog/test_collection_generator.py` — 4 passed - `uv run scripts/i18n/validate-i18n.py` — 0 errors, existing warnings only - public-tree sensitive-pattern scan — zero matches --- teams/contract-review-team/entry.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/teams/contract-review-team/entry.json b/teams/contract-review-team/entry.json index ab76935..05da873 100644 --- a/teams/contract-review-team/entry.json +++ b/teams/contract-review-team/entry.json @@ -71,7 +71,7 @@ "id": "jurisdiction-auditor", "name": "法域合规官", "role": "member", - "version": "1.2.0" + "version": "1.0.0" }, { "id": "review-reporter",