chore(community): add contributing infra, issue/PR templates, npm publish workflow

Tier A infrastructure to convert 204★ momentum into durable community and
distribution. Pairs with PR #12 (ETHICS / CHANGELOG / fidelity smoke) — merge
PR #12 first, then this.

**Community docs**
- `CONTRIBUTING.md` — three-tier contribution flow (code vs docs vs master
  content), with a detailed §3 "how to contribute a new master" covering
  copyright tier self-check, `/create-master` vs manual path, SKILL.md
  frontmatter spec, voice.md Layer 0-3, fidelity.jsonl authoring.
- `CODE_OF_CONDUCT.md` — Contributor Covenant 2.1 + Buddhist-project-specific
  rules (no doctrinal supremacy, no using the repo as a dharma platform, no
  impersonating clergy, no apocryphal scripture citations).
- `SECURITY.md` — threat model (prompt injection, supply chain, secret leak,
  installer safety, religious-boundary adversarial input), SLA table, GH
  Security Advisory as primary channel.

**Issue / PR templates**
- `bug_report.yml` — area selector, master selector, repro template.
- `feature_request.yml` — non-master enhancement requests.
- `new_master.yml` — **MUST precede any new-master PR**; forces tier A/B/D
  self-judgment and citation planning before sunk cost.
- `boundary_violation.yml` — P0 template for ETHICS.md §3 violations.
- `config.yml` — directs users to Discussions for chatter, Security Advisory
  for vulnerabilities, email for urgent takedowns.
- `PULL_REQUEST_TEMPLATE.md` — change-type checkboxes, self-check list, new-
  master fields, local-test block.

**npm publish**
- `.github/workflows/npm-publish.yml` — release-tag + workflow_dispatch, with
  dry-run mode, tag-version match check, `npm publish --provenance`.
  First-time publish needs NPM_TOKEN secret (user action).
- `package.json` hardening:
  - `engines.node: >=18`
  - scripts: `validate`, `validate:fidelity`, `test`, `test:smoke`, `prepack`
  - `publishConfig` (public, npm registry)
  - `files` list expanded to include platform manifests + governance docs
  - richer `keywords`, `author`, `bugs`, `homepage` fields
  - expanded description mentions all 8 masters for search discoverability

**README**
- 贡献指南 section rewritten to point at CONTRIBUTING.md + Discussions +
  four issue templates, with "先开 New Master issue 征询" gate spelled out.

Discussions were enabled on the repo alongside this commit via `gh api`, so
the links in README/templates resolve immediately on merge.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
xianren
2026-04-16 13:52:30 +08:00
parent a69fc85ead
commit 3dfaa6bb62
12 changed files with 1005 additions and 7 deletions
@@ -0,0 +1,74 @@
name: 🚨 教界边界违规(P0
description: AI 角色给你传戒、印证开悟、灵媒化对话、给出修行诊断等 → 立即报告
title: "[Boundary Violation] "
labels: ["boundary-violation", "P0", "triage"]
body:
- type: markdown
attributes:
value: |
## ⚠️ P0 优先级
本项目的核心承诺之一是 AI 角色不会越过教界边界(见 [`ETHICS.md`](https://github.com/xr843/Master-skill/blob/main/ETHICS.md) §3)。
一旦发现越界,我们会:
1. 24 小时内确认
2. 优先于所有 feature 工作修复
3. 修复后更新 fidelity 测试确保不再回归
**请不要在 issue 中贴过长的 AI 回答原文**——只需能说明问题的关键片段,避免被错误引用为"祖师开示"。
- type: dropdown
id: violation-type
attributes:
label: 违规类型
options:
- AI 为用户传戒 / 授戒 / 证戒
- AI 印证用户开悟 / 授记 / 给法卷
- AI 给出修行状况诊断("你是某种禅病")
- AI 预测命数 / 因果业报细节 / 往生品位
- AI 充当"与已故法师对话"的灵媒
- AI 在心理危机场景给佛法替代医疗建议
- AI 声称自己就是某位法师
- 其它越过 ETHICS.md §3 边界的回答
validations:
required: true
- type: input
id: master
attributes:
label: 涉及哪位法师
placeholder: "例如:yinguang / xuanzang / ..."
validations:
required: true
- type: input
id: platform
attributes:
label: 使用平台
placeholder: "fojin.app/chat / Claude Code / Cursor / Codex CLI / OpenCode / Gemini CLI"
validations:
required: true
- type: textarea
id: trigger
attributes:
label: 触发问题(原话或改写)
description: 你问了什么让 AI 越界?
validations:
required: true
- type: textarea
id: response-snippet
attributes:
label: AI 回答的关键片段(非全文)
description: "**不要贴全文**。只贴越界的那几句,最好截图打码处理后附图。"
validations:
required: true
- type: textarea
id: harm
attributes:
label: 潜在危害
description: 你或别人可能因此受到什么误导?
validations:
required: false