taodeng/ocp
1
0
Fork 0
mirror of https://github.com/dtzp555-max/ocp.git synced 2026-07-21 21:15:09 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
1c29f4867f3137e5aaacc0e27568ff31be210344
ocp/.github/PULL_REQUEST_TEMPLATE.md
T
dtzp555-maxGitHubtaodengClaude Opus 4.7
 497ff1dcd2 chore(governance): add release-kit overlay + PR self-check + auto-release workflow (#35) 
Implements cc-rules v1.4's 第五律 5.5 project overlay requirement.

- CLAUDE.md: declare release_kit: YAML block (version_source,
  changelog, release_channel, docs_source, resource_lists,
  new_feature_doc_expectations, bootstrap_quirk_policy)
- .github/PULL_REQUEST_TEMPLATE.md: add 5.3 user-visible-change
  self-check section with reviewer gate instruction
- .github/workflows/release.yml (NEW): auto-create GitHub Release
  from CHANGELOG.md section on v* tag push. Idempotent (checks if
  release already exists). Closes the gap that caused v3.9.0 /
  v3.10.0 / v3.11.0 to each miss their GH Release.

Governance-only change. No code, no user-visible behavior change
(the workflow only fires on future tags). No README update needed.

Co-authored-by: Tao Deng <dtzp555@gmail.com>
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
2026-04-21 05:16:38 +10:00

2.6 KiB
Raw Blame History

Pull Request

Summary

Claude Code Alignment Evidence (REQUIRED)

Per ALIGNMENT.md, every PR that touches server.mjs or any network-facing surface must fill out this section. PRs with this section blank or unchecked will receive a request changes review and cannot be merged.

  • Corresponding cli.js reference. I have identified the cli.js function and line range that performs the operation this PR forwards. Citation (format cli.js:NNNN or cli.js vE4 <functionName>):

  • If cli.js does not perform this operation, I have stated this explicitly below and justified the scope under ALIGNMENT.md Rule 2. (Note: in almost all cases this means the PR should be closed, not merged. Proxy layers do not invent endpoints.)

  • Commit message citations. Every "Claude Code uses X" or "cli.js uses X" assertion in every commit of this PR is immediately followed by a cli.js:NNNN or cli.js vE4 <functionName> citation. I have verified this by rereading each commit message.

Type of change

  • Bug fix (alignment with existing cli.js behavior)
  • Feature (new cli.js behavior now surfaced through OCP)
  • Refactor (no wire-level behavior change)
  • Deletion (unalignable feature removal per ALIGNMENT.md Unalignable Policy)
  • Documentation / governance

Reviewer checklist

Reviewers: this section is for you, not the author. Do not approve until every box is checked.

  • I opened cli.js at the cited line range and confirmed the operation matches.
  • I ran (or confirmed CI ran) .github/workflows/alignment.yml and it passed.
  • I am not the commit author of any commit in this PR (Iron Rule 10).
  • If the PR asserts scope without a cli.js citation, I confirmed the justification is sound per ALIGNMENT.md Rule 2.

Related

  • ALIGNMENT.md Rule(s) invoked:
  • Related issue / prior PR:
  • Historical lesson reference (if relevant):

User-visible change self-check (铁律第五律 5.3)

  • This PR has user-visible changes → README has corresponding documentation (paste diff link or line range)
  • This PR has no user-visible changes → stated "no user-visible change" in summary above

Reviewers: if "user-visible" is checked but README diff is empty, block merge (per 5.3 reviewer gate).

Reference in New Issue View Git Blame Copy Permalink