Repository navigation
docs: drop per-work-item process files from docs/ (03 方案分级, 04 符合度清单, 05 自测记录) - #19
Merged
Merged
Conversation
…he work items Method grading notes, the compliance checklist and the self-test report are per-work-item artifacts and are kept on the corresponding GitHub issues, as the dev-design / dev-issue / dev-test skills prescribe. Keeping copies under docs/ forced a rewrite every time the baseline moved. README and CLAUDE.md pointers updated; docs/ now holds the requirement, the design baseline, the intake report, the blueprint and the Word deliverables. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VR2khJ3Me96btawVsfG6jb
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Maintainer decision of 2026-09-03: delete the three per-work-item process documents from
docs/. Method grading notes, the compliance checklist and the test report are artifacts of individual work items and are kept on the corresponding GitHub issues (as dev-design, dev-issue §4.5 and dev-test prescribe); keeping copies underdocs/forced a rewrite every time the baseline moved.docs/03-方案分级.md,docs/04-需求符合度清单.md,docs/05-自测记录.md(their final content remains in git history and on issues Design baseline V1.0 and delivery-document conformance fixes (docs 00–03, README, CLAUDE.md, CI) #9 / Align code with confirmed design V1.0: bonus role segregation, one active plan per period, "adjusted" marker; refresh compliance checklist and self-test record #10 / Sharing-service hardening: rule-name length bound, legacy rows without plan, reconcile branch coverage #5 / UI copy: indicator field label 「责任板块(考核部门)」 should be 「部门板块」 per requirements glossary §1.4 #13).docs/00(design baseline V1.0),docs/01(intake report),docs/02(blueprint) and the Word deliverables underdocs/交付/.No code change;
pnpm verifyunaffected.🤖 Generated with Claude Code
https://claude.ai/code/session_01VR2khJ3Me96btawVsfG6jb
Generated by Claude Code