docs(quality): deepen issue traceability terminology parity#3218
docs(quality): deepen issue traceability terminology parity#3218ootakazuhiko merged 3 commits intomainfrom
Conversation
Generate Artifacts PreviewGenerated at: 2026-04-10T08:37:46.142Z
|
|
Coverage: n/a | Alerts: none | Formal: n/a | BDD: 3 criteria (Reserve inventory without going negative or double-booking) | LTL sugg: 3 | GWT: 0 | Adapters ok/warn/err=0/0/0 | | Replay: n/a | Trace: Harness Health
Change Package
Change Package Validation
Plan Artifact
Assumptions
Files expected to change
Verification plan
Rollback planRevert the plan-artifact schema, scripts, policy-gate integration, and PR summary wiring. Required human input
Notes
Plan Artifact Validation
|
Progress Summary
|
KvOnce Trace Validation
|
There was a problem hiding this comment.
Pull request overview
This PR updates the Japanese wording in the quality guide for issue→requirements traceability while keeping the English/CLI contract intact, and adjusts example code fences to better match doctest/documentation intent.
Changes:
- Update
lastVerifiedand refine Japanese terminology/phrasing for traceability steps. - Change example fences from
tstotextfor non-executable comment examples. - Keep the English section and CLI examples unchanged.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
CI Status Snapshot (2026-04-10T08:06:28.940Z)
|
CI Auto RerunWorkflow |
563a0b6 to
e27c37b
Compare
Summary
tstotextso doctest matches the documentation intentValidation