rulemason 0.8.0__tar.gz

rulemason-0.8.0/.gitignore

@@ -0,0 +1,6 @@
+.DS_Store
+.venv/
+__pycache__/
+.pytest_cache/
+.ruff_cache/
+CLAUDE.local.md

rulemason-0.8.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

rulemason-0.8.0/NOTICE

@@ -0,0 +1,4 @@
+rulemason
+Copyright 2026 The rulemason Authors
+
+This product includes software developed by The rulemason Authors.

rulemason-0.8.0/PKG-INFO

@@ -0,0 +1,203 @@
+Metadata-Version: 2.5
+Name: rulemason
+Version: 0.8.0
+Summary: 给 AI 编码工具的共享规则与检查点：一处维护规则，项目内生成只读副本，方案与代码前后自动判断与审查
+Project-URL: Homepage, https://github.com/rulemason/rulemason
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.11
+Requires-Dist: json5>=0.9
+Requires-Dist: pydantic>=2.12
+Requires-Dist: pyyaml>=6.0.3
+Requires-Dist: typesafe-sdk>=0.7.5
+Description-Content-Type: text/markdown
+
+# rulemason
+
+给 AI 编码工具（Claude Code、OpenCode、Cursor、Codex）的共享规则与检查点。它只管三件事：
+
+- **规则**：AI 写方案和代码时要守的写法规矩（九条、各语言落法（Python、React）、界面文案三档、方案写法）。规则只在本仓库维护，每个项目里是一份随项目提交的只读副本，克隆项目的人、云端 agent 与 CI 不装 rulemason 也能读到。
+- **检查点**：方案写完、写代码前、写完代码后，AI 按规矩自动检查——判断方案、精简代码、独立审查、lint 与测试。
+- **判断**（可选）：用 TypeSafe 的 Jev 模型判断方案是否违反已写下的规矩，输出 pass / review / block；没有 key 时人工逐条判断。
+
+## 安装（每台机器一次）
+
+从 PyPI 安装（需要 [uv](https://docs.astral.sh/uv/)）：
+
+```bash
+uv tool install rulemason
+rulemason --version
+```
+
+## 常用命令
+
+| 什么时候 | 命令 |
+|---|---|
+| 项目第一次接入，或增减 AI 工具 | `rulemason init` |
+| 以后任何时候：升级、补齐缺的配置、恢复被改的副本 | `rulemason update` |
+| 看现状与下一步（CI 里也用它） | `rulemason check` |
+| 配一次 Jev 的 key（只在启用判断时需要） | `rulemason key` |
+| 不再使用：从项目卸载 | `rulemason remove` |
+| 手动判断一个方案 | `rulemason judge --change 功能名` |
+| 在 AI 工具里补项目简介、红线、命令表，或启用判断 | `/rulemason` |
+
+## 第一次接入
+
+在项目根目录运行：
+
+```bash
+rulemason init                              # 交互选择工具，列出文件计划，确认一次后写入
+rulemason init --tools claude,codex --yes   # 非交互：不提问
+```
+
+`init` 只做能确定做对的事：生成规则副本与各工具的入口，补齐方案写法规则、OpenSpec apply / archive 时给 AI 的检查点提示（`config.yaml` 的 `operations`）、ruff / ESLint 继承与项目的检查点规格；改不了的（例如 ruff 配置写了 `select`）只报告，不强行改写。不提交、不推送，不碰计划以外的文件。没有 `openspec/` 时会先询问并代为运行 `openspec init`。
+
+然后在 AI 工具里运行 `/rulemason`，补项目简介、红线（注明出处并逐条确认）与命令表。
+
+## 日常
+
+日常开发走 OpenSpec，检查点由 AI 自动运行，不用记命令：
+
+```txt
+/opsx:propose 功能名   方案写完 -> 判断：格式问题 AI 自己改，碰红线的报告给你
+/opsx:apply 功能名     写代码前再判断一次，有 block 就停下等你
+                       写完 -> 自动精简 -> 独立只读审查 -> ruff -> 测试 -> 前端 lint -> 文案检查
+/opsx:archive 功能名   归档，提交
+```
+
+自动精简只处理本次改动里的重复、死代码、冗余抽象或过复杂逻辑，保持需求、外部行为与 API 不变；Claude Code 下这一步用内置的 `/simplify`。独立审查者拿不到文件与命令工具，只看提供给它的改动与方案；必须修的问题自动修复并重新审查，不要求你逐条审核代码。
+
+## 看现状
+
+```bash
+rulemason check     # 只读，在项目任意子目录运行都可以
+```
+
+第一行就是结论和下一步，照着做即可，例如：
+
+```txt
+补项目信息：在 AI 工具中运行 /rulemason
+接入：运行 rulemason update
+日常巡检：一切一致
+```
+
+规则副本被改、工具入口缺失、lint 没有继承基础规则、项目还是旧格式时以非 0 退出，可以直接放进 CI：
+
+```yaml
+- uses: astral-sh/setup-uv@v6
+- run: uv tool install rulemason==0.8.0
+- run: rulemason check
+```
+
+### 给 AI 与脚本
+
+```bash
+rulemason check --json          # 结构化结果：next.code 是稳定的动作代码，text 是上面的报告全文；退出码同上
+rulemason init --plan [--json]  # 只列接入计划：不写文件、不提问、不运行 openspec init
+rulemason update --dry-run [--json]   # 只列升级与补齐计划，不写文件
+```
+
+`/rulemason` 读的就是 `check --json`；AI 替你接入前会先用 `init --plan` 给你看计划。
+
+## 升级
+
+```bash
+uv tool upgrade rulemason
+rulemason update
+```
+
+`update` 直接刷新 rulemason 自己管的规则副本与入口；你自己的文件（ruff、ESLint、`openspec/config.yaml` 等）缺了配置时，它先列出补齐计划，确认后才写，非交互环境里要加 `--yes`。之后在项目里跑一遍 lint 与测试再提交。
+
+## 判断（可选）
+
+判断要求项目在 git 里、已归档至少 3 个 change；`rulemason check` 的「判断」一行会写明还差什么。要启用时在 AI 工具里运行 `/rulemason` 并说明要启用判断，它会整理候选判断规则让你逐条确认。
+
+配 key（在自己的终端里运行，输入不显示，不会进命令历史）：
+
+```bash
+rulemason key
+```
+
+key 写在 `~/.config/rulemason/env`（权限 600），只在本机，不进任何仓库；环境变量 `TYPESAFE_API_KEY` 优先。
+
+手动运行判断：
+
+```bash
+rulemason judge --change 功能名               # 审 openspec/changes/功能名（已归档的也能直接用名字）
+rulemason judge --change 功能名 --lint-only   # 只跑正则检查，不联网
+rulemason judge --copy                        # 审新增或改过的界面文案（项目配了 openspec/judge.yaml 才有）
+rulemason judge --change 功能名 --dry-run     # 打印将要发送的请求，不发送
+rulemason judge --template judgments          # 打印启用判断用的模板（judgments、judge、judge_cases）
+```
+
+项目代码也可以把引擎当库用：`from rulemason.judge import load_rules, verdict_or_pending`。
+
+## 卸载
+
+```bash
+rulemason remove --plan   # 只看计划，不改任何文件
+rulemason remove          # 列出计划，确认后卸载；非交互环境加 --yes
+```
+
+`remove` 删掉 rulemason 生成的东西：规则副本、各工具的 skill、`.rulemason.yaml`、AGENTS.md / CLAUDE.md 里的 rulemason 标记块、OpenCode 配置里指向 `.rulemason/` 的条目，以及没被改过的 `operations` 提示。ruff、ESLint 还在继承基础规则时，会把这两个文件移到项目的 `lint/` 并改好路径，lint 结果不变。手改过的副本保留；产物写法规则、项目的检查点规格、命令表和红线已是项目内容，只在汇报里列出，不删。本机装的 rulemason 不受影响，不用了再运行 `uv tool uninstall rulemason`。
+
+## 出了问题怎么办
+
+rulemason 往项目里写三类东西，都由它管理，不要手改：
+
+- **规则副本**：`.rulemason/` 与各工具目录下的 `skills/rulemason/SKILL.md`。
+- **标记块**：`AGENTS.md`、`CLAUDE.md` 里 `<!-- rulemason:… -->` 与 `<!-- /rulemason:… -->` 之间的内容；块外是你自己的内容，rulemason 不碰。
+- **清单**：`.rulemason.yaml`，记录选了哪些工具、rulemason 版本与每个副本的校验值。
+
+| `check` 第一行 | 原因 | 怎么办 |
+|---|---|---|
+| `接入：运行 rulemason update` | 副本或标记块被手改、入口缺失、配置没补齐 | 运行 `rulemason update`；要改规矩，到本仓库改了发布新版本 |
+| `接入：修改 .gitignore，放行 skills/rulemason/` | `.gitignore` 忽略了工具目录，副本提交不上去 | 改成只放行 `skills/rulemason/`；说明单独写一行，git 不支持行尾注释 |
+| `接入：运行 rulemason init` | 这个目录（或它所在的仓库）还没接入 | 在项目根运行 `rulemason init` |
+| `接入：先修正 .rulemason.yaml` | 清单被改坏，读不出来 | 按提示修正，或删掉它后重新 `rulemason init` |
+| `接入：运行 rulemason init 迁移格式` | 项目还是 rulekit 0.5 的格式 | 见下一节 |
+| `补项目信息：…` | 项目简介、红线待补，或有旧名残留 | 在 AI 工具里运行 `/rulemason` |
+
+## 从 rulekit 迁移
+
+rulemason 的前身叫 rulekit（0.5.x）。已接入 rulekit 的项目：
+
+```bash
+uv tool uninstall rulekit
+uv tool install rulemason
+rulemason init        # 识别 .rulekit.yaml，列出迁移计划，确认一次后迁移
+rulemason check       # 看还有哪些旧名残留
+```
+
+迁移把 `.rulekit/`、`.rulekit.yaml`、`skills/rulekit/`、`<!-- rulekit:… -->` 标记块，以及 opencode、ruff、ESLint、项目检查点规格里的 `.rulekit/` 路径换成新名，结果与直接接入相同。旧副本被手改过时迁移停下并列出文件，不写任何东西。
+
+标记块以外的旧名不会被自动修改，`check` 会列出来，在 AI 工具中运行 `/rulemason` 逐处确认后替换：
+
+- 命令表里的 `jev-judge --change <name>` → `rulemason judge --change <name>`
+- `.gitignore` 里的 `!.claude/skills/rulekit/` → `!.claude/skills/rulemason/`
+- 项目测试里的 `from jev_judge import …` → `from rulemason.judge import …`
+
+key 不用重配：`~/.config/rulemason/env` 不存在时，会读旧位置 `~/.config/jev-judge/env`；也可以运行一次 `rulemason key` 写到新位置。
+
+## 参与修改
+
+改共享规则会影响所有接入项目：在本仓库开 OpenSpec change，在受影响的项目里验证，发布新 tag 后各项目运行 `rulemason update`。
+
+启用提交前钩子，拦截本机绝对路径（每个 clone 一次）：
+
+```bash
+git config core.hooksPath .githooks
+```
+
+本地开发：
+
+```bash
+uv sync
+uv run ruff check .
+uv run pytest
+```
+
+## 许可证
+
+[Apache-2.0](LICENSE)。版权声明见 [NOTICE](NOTICE)。

rulemason-0.8.0/README.md

@@ -0,0 +1,188 @@
+# rulemason
+
+给 AI 编码工具（Claude Code、OpenCode、Cursor、Codex）的共享规则与检查点。它只管三件事：
+
+- **规则**：AI 写方案和代码时要守的写法规矩（九条、各语言落法（Python、React）、界面文案三档、方案写法）。规则只在本仓库维护，每个项目里是一份随项目提交的只读副本，克隆项目的人、云端 agent 与 CI 不装 rulemason 也能读到。
+- **检查点**：方案写完、写代码前、写完代码后，AI 按规矩自动检查——判断方案、精简代码、独立审查、lint 与测试。
+- **判断**（可选）：用 TypeSafe 的 Jev 模型判断方案是否违反已写下的规矩，输出 pass / review / block；没有 key 时人工逐条判断。
+
+## 安装（每台机器一次）
+
+从 PyPI 安装（需要 [uv](https://docs.astral.sh/uv/)）：
+
+```bash
+uv tool install rulemason
+rulemason --version
+```
+
+## 常用命令
+
+| 什么时候 | 命令 |
+|---|---|
+| 项目第一次接入，或增减 AI 工具 | `rulemason init` |
+| 以后任何时候：升级、补齐缺的配置、恢复被改的副本 | `rulemason update` |
+| 看现状与下一步（CI 里也用它） | `rulemason check` |
+| 配一次 Jev 的 key（只在启用判断时需要） | `rulemason key` |
+| 不再使用：从项目卸载 | `rulemason remove` |
+| 手动判断一个方案 | `rulemason judge --change 功能名` |
+| 在 AI 工具里补项目简介、红线、命令表，或启用判断 | `/rulemason` |
+
+## 第一次接入
+
+在项目根目录运行：
+
+```bash
+rulemason init                              # 交互选择工具，列出文件计划，确认一次后写入
+rulemason init --tools claude,codex --yes   # 非交互：不提问
+```
+
+`init` 只做能确定做对的事：生成规则副本与各工具的入口，补齐方案写法规则、OpenSpec apply / archive 时给 AI 的检查点提示（`config.yaml` 的 `operations`）、ruff / ESLint 继承与项目的检查点规格；改不了的（例如 ruff 配置写了 `select`）只报告，不强行改写。不提交、不推送，不碰计划以外的文件。没有 `openspec/` 时会先询问并代为运行 `openspec init`。
+
+然后在 AI 工具里运行 `/rulemason`，补项目简介、红线（注明出处并逐条确认）与命令表。
+
+## 日常
+
+日常开发走 OpenSpec，检查点由 AI 自动运行，不用记命令：
+
+```txt
+/opsx:propose 功能名   方案写完 -> 判断：格式问题 AI 自己改，碰红线的报告给你
+/opsx:apply 功能名     写代码前再判断一次，有 block 就停下等你
+                       写完 -> 自动精简 -> 独立只读审查 -> ruff -> 测试 -> 前端 lint -> 文案检查
+/opsx:archive 功能名   归档，提交
+```
+
+自动精简只处理本次改动里的重复、死代码、冗余抽象或过复杂逻辑，保持需求、外部行为与 API 不变；Claude Code 下这一步用内置的 `/simplify`。独立审查者拿不到文件与命令工具，只看提供给它的改动与方案；必须修的问题自动修复并重新审查，不要求你逐条审核代码。
+
+## 看现状
+
+```bash
+rulemason check     # 只读，在项目任意子目录运行都可以
+```
+
+第一行就是结论和下一步，照着做即可，例如：
+
+```txt
+补项目信息：在 AI 工具中运行 /rulemason
+接入：运行 rulemason update
+日常巡检：一切一致
+```
+
+规则副本被改、工具入口缺失、lint 没有继承基础规则、项目还是旧格式时以非 0 退出，可以直接放进 CI：
+
+```yaml
+- uses: astral-sh/setup-uv@v6
+- run: uv tool install rulemason==0.8.0
+- run: rulemason check
+```
+
+### 给 AI 与脚本
+
+```bash
+rulemason check --json          # 结构化结果：next.code 是稳定的动作代码，text 是上面的报告全文；退出码同上
+rulemason init --plan [--json]  # 只列接入计划：不写文件、不提问、不运行 openspec init
+rulemason update --dry-run [--json]   # 只列升级与补齐计划，不写文件
+```
+
+`/rulemason` 读的就是 `check --json`；AI 替你接入前会先用 `init --plan` 给你看计划。
+
+## 升级
+
+```bash
+uv tool upgrade rulemason
+rulemason update
+```
+
+`update` 直接刷新 rulemason 自己管的规则副本与入口；你自己的文件（ruff、ESLint、`openspec/config.yaml` 等）缺了配置时，它先列出补齐计划，确认后才写，非交互环境里要加 `--yes`。之后在项目里跑一遍 lint 与测试再提交。
+
+## 判断（可选）
+
+判断要求项目在 git 里、已归档至少 3 个 change；`rulemason check` 的「判断」一行会写明还差什么。要启用时在 AI 工具里运行 `/rulemason` 并说明要启用判断，它会整理候选判断规则让你逐条确认。
+
+配 key（在自己的终端里运行，输入不显示，不会进命令历史）：
+
+```bash
+rulemason key
+```
+
+key 写在 `~/.config/rulemason/env`（权限 600），只在本机，不进任何仓库；环境变量 `TYPESAFE_API_KEY` 优先。
+
+手动运行判断：
+
+```bash
+rulemason judge --change 功能名               # 审 openspec/changes/功能名（已归档的也能直接用名字）
+rulemason judge --change 功能名 --lint-only   # 只跑正则检查，不联网
+rulemason judge --copy                        # 审新增或改过的界面文案（项目配了 openspec/judge.yaml 才有）
+rulemason judge --change 功能名 --dry-run     # 打印将要发送的请求，不发送
+rulemason judge --template judgments          # 打印启用判断用的模板（judgments、judge、judge_cases）
+```
+
+项目代码也可以把引擎当库用：`from rulemason.judge import load_rules, verdict_or_pending`。
+
+## 卸载
+
+```bash
+rulemason remove --plan   # 只看计划，不改任何文件
+rulemason remove          # 列出计划，确认后卸载；非交互环境加 --yes
+```
+
+`remove` 删掉 rulemason 生成的东西：规则副本、各工具的 skill、`.rulemason.yaml`、AGENTS.md / CLAUDE.md 里的 rulemason 标记块、OpenCode 配置里指向 `.rulemason/` 的条目，以及没被改过的 `operations` 提示。ruff、ESLint 还在继承基础规则时，会把这两个文件移到项目的 `lint/` 并改好路径，lint 结果不变。手改过的副本保留；产物写法规则、项目的检查点规格、命令表和红线已是项目内容，只在汇报里列出，不删。本机装的 rulemason 不受影响，不用了再运行 `uv tool uninstall rulemason`。
+
+## 出了问题怎么办
+
+rulemason 往项目里写三类东西，都由它管理，不要手改：
+
+- **规则副本**：`.rulemason/` 与各工具目录下的 `skills/rulemason/SKILL.md`。
+- **标记块**：`AGENTS.md`、`CLAUDE.md` 里 `<!-- rulemason:… -->` 与 `<!-- /rulemason:… -->` 之间的内容；块外是你自己的内容，rulemason 不碰。
+- **清单**：`.rulemason.yaml`，记录选了哪些工具、rulemason 版本与每个副本的校验值。
+
+| `check` 第一行 | 原因 | 怎么办 |
+|---|---|---|
+| `接入：运行 rulemason update` | 副本或标记块被手改、入口缺失、配置没补齐 | 运行 `rulemason update`；要改规矩，到本仓库改了发布新版本 |
+| `接入：修改 .gitignore，放行 skills/rulemason/` | `.gitignore` 忽略了工具目录，副本提交不上去 | 改成只放行 `skills/rulemason/`；说明单独写一行，git 不支持行尾注释 |
+| `接入：运行 rulemason init` | 这个目录（或它所在的仓库）还没接入 | 在项目根运行 `rulemason init` |
+| `接入：先修正 .rulemason.yaml` | 清单被改坏，读不出来 | 按提示修正，或删掉它后重新 `rulemason init` |
+| `接入：运行 rulemason init 迁移格式` | 项目还是 rulekit 0.5 的格式 | 见下一节 |
+| `补项目信息：…` | 项目简介、红线待补，或有旧名残留 | 在 AI 工具里运行 `/rulemason` |
+
+## 从 rulekit 迁移
+
+rulemason 的前身叫 rulekit（0.5.x）。已接入 rulekit 的项目：
+
+```bash
+uv tool uninstall rulekit
+uv tool install rulemason
+rulemason init        # 识别 .rulekit.yaml，列出迁移计划，确认一次后迁移
+rulemason check       # 看还有哪些旧名残留
+```
+
+迁移把 `.rulekit/`、`.rulekit.yaml`、`skills/rulekit/`、`<!-- rulekit:… -->` 标记块，以及 opencode、ruff、ESLint、项目检查点规格里的 `.rulekit/` 路径换成新名，结果与直接接入相同。旧副本被手改过时迁移停下并列出文件，不写任何东西。
+
+标记块以外的旧名不会被自动修改，`check` 会列出来，在 AI 工具中运行 `/rulemason` 逐处确认后替换：
+
+- 命令表里的 `jev-judge --change <name>` → `rulemason judge --change <name>`
+- `.gitignore` 里的 `!.claude/skills/rulekit/` → `!.claude/skills/rulemason/`
+- 项目测试里的 `from jev_judge import …` → `from rulemason.judge import …`
+
+key 不用重配：`~/.config/rulemason/env` 不存在时，会读旧位置 `~/.config/jev-judge/env`；也可以运行一次 `rulemason key` 写到新位置。
+
+## 参与修改
+
+改共享规则会影响所有接入项目：在本仓库开 OpenSpec change，在受影响的项目里验证，发布新 tag 后各项目运行 `rulemason update`。
+
+启用提交前钩子，拦截本机绝对路径（每个 clone 一次）：
+
+```bash
+git config core.hooksPath .githooks
+```
+
+本地开发：
+
+```bash
+uv sync
+uv run ruff check .
+uv run pytest
+```
+
+## 许可证
+
+[Apache-2.0](LICENSE)。版权声明见 [NOTICE](NOTICE)。

rulemason-0.8.0/lint/eslint-base.mjs

@@ -0,0 +1,10 @@
+// ESLint 基础规则：代码写法的机械部分（rules/code-style.md）。只导出纯规则，不引插件：插件会从本仓库目录解析，而这里没有 node_modules
+export default {
+  "no-console": "error",
+  "no-nested-ternary": "error",
+  // 空块（含空 catch，九条第 8 条）。确需空 catch 的项目在自己的配置里放宽并写明原因
+  "no-empty": "error",
+  // 取 15 而非 Python 的 10：JSX 里每个 && 和 ?: 都算一个分支，同样的上限放到组件上会严得多。
+  // 项目当前代码超出时，在自己的配置里用当前最复杂函数的值覆盖，写明递减计划，只降不升
+  complexity: ["error", 15],
+};

rulemason-0.8.0/lint/ruff-base.toml

@@ -0,0 +1,23 @@
+# ruff 基础规则：代码写法的机械部分（rules/code-style.md）。项目用 extend 继承，只写自己的豁免并注明原因，不写 select。
+
+[lint]
+# 只启用 select 里点名的预览规则（PLW1514）；预览模式也会改变部分稳定规则的行为，升级 ruff 后留意新增报错
+preview = true
+explicit-preview-rules = true
+select = [
+    "ERA001",   # 注释掉的代码（九条第 6 条）
+    "T201",     # print（第 6 条）
+    "BLE001",   # 过宽的 except Exception（第 8 条）
+    "E722",     # 裸 except:（第 8 条）
+    "C901",     # 圈复杂度
+    "F",        # pyflakes：未用导入与变量、未定义名（第 6、9 条）
+    "E701",     # 冒号后接语句写在同一行（附加条款「一行只做一件事」）
+    "E702",     # 一行用分号写多条语句（同上）
+    "RUF021",   # a and b or c 不加括号（附加条款「要停下来想优先级的表达式拆开写」）
+    "PLW1514",  # 读写文本不写 encoding（python.md；Windows 中文版默认按 GBK 读写）
+    "B",        # bugbear：zip 不写 strict、可变默认值等常见坑；框架约定在参数默认值里调函数的，由项目用 extend-immutable-calls 声明
+    "I",        # import 排序
+]
+
+[lint.mccabe]
+max-complexity = 10

rulemason-0.8.0/openspec-base/artifact-rules.yaml

@@ -0,0 +1,16 @@
+# 产物写法基础版：各项目照写进 openspec/config.yaml 的 rules 段，只追加不改写（OpenSpec 配置不能引用外部文件）
+rules:
+  proposal:
+    - 必须说明本次明确不做的事：Non-goals 小节，或 What Changes 中以「不做」开头的条目，二者取一即可
+    - 控制在 60 行以内，只写为什么和改什么，不写怎么实现
+  design:
+    - Decisions 每条决策写明至少一个被否决的备选方案及否决理由
+    - Risks 每条用「[风险] → 对策」格式，一行一条
+    - Migration Plan 写明上线顺序与回滚方式
+    - 列出新增与修改的文件及每个文件的估计行数，apply 后对照；超出一倍要说明原因
+  specs:
+    - 每个 Requirement 至少一个 Scenario，用 WHEN / THEN
+    - 用 SHALL / MUST 表达约束，不用 should / may
+    - 每条 Requirement 正文不超过 500 个字符（openspec validate --strict 的上限）
+  tasks:
+    - 每条任务两小时内可完成，并写明怎么验证它完成了