Repository navigation
Bug: quality-tiers-yml-missing-at-repository-root #967
Description
Activity
Restoring sections dropped by the promotion tooling.
Suspected Cause / Notes
.claude/rules/**is pushed down from drm-copilot. The #178 governance sync deliberately kept TaskMaster's own coverage and tier policy and excluded the reference repository's tier system, so this rule may itself be the leak. Related to #668 (the coverage-threshold discrepancy between CLAUDE.md and the rules).Proposed Fix / Validation Ideas
- The maintainer decides: adopt tiers in TaskMaster, or reject the rule here.
- If adopted: add
quality-tiers.ymlcovering all.slnprojects, plus a CI check, with a negative control for an unclassified project. - If rejected: raise the upstream change under Bug: drm-copilot-upstream-template-and-payload-defects #932.
Summary
.claude/rules/quality-tiers.mdstates thatquality-tiers.ymlat the repository root maps every project to a tier, and that adding a project without a tier classification fails CI. The file does not exist onmain, and no CI stage validates it. Feature reviews for #931 and #956 both flagged it as missing.Environment
git ls-tree origin/main -- quality-tiers.yml(no result)Steps to Reproduce
quality-tiers.ymlat the repository root onmain. It is absent.tier-classificationCI stage. There is none.Expected Behavior
Either the file exists, listing every project and its tier and validated in CI, or the rule is reconciled with this repository's actual policy.
Actual Behavior
The rule references a file and a CI stage that do not exist.
Logs / Screenshots
quality-tiers.ymlis absent at the repository root"); PR fix(956): split SortEmail into partial files and seam the read-only retry prompt #965 follow-ups.Impact / Severity
Source
From: docs/features/potential/2026-10-01-quality-tiers-yml-missing-at-repository-root.md