fix(specs): update three stale Known gaps in meta-and-quality-tooling.md - #1074
Open
zheflow wants to merge 1 commit into
Open
fix(specs): update three stale Known gaps in meta-and-quality-tooling.md#1074zheflow wants to merge 1 commit into
zheflow wants to merge 1 commit into
Conversation
Why: three Known gaps bullets described validator checks as missing or pending when all three have shipped (validate_capability_taxonomy_coverage, validate_modes_doc_consistency, and the HARD tool-prerequisites-fields check). The spec-loop plan beat reads Known gaps to choose the next work item, so stale gaps send the loop at finished work. Each rewritten bullet now names the check that closed it and its enforcement level. Closes apache#938 Generated-by: Claude Code (Fable 5)
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
1 participant
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.
Summary
Three
Known gapsbullets intools/spec-loop/specs/meta-and-quality-tooling.mddescribed validator checks as missing or pending when all three have shipped. Each bullet is rewritten to name the check that closed it and its enforcement level, so the spec-loop plan beat stops steering at finished work:validate_capability_taxonomy_coverage(SOFT advisories; (reserved) / (future) rows exempt; also cross-checks theSKILL_CAPABILITIES/TOOL_CAPABILITIESconstants)docs/modes.mdsync →validate_modes_doc_consistency(four SOFT checks: missing skill, mode mismatch, count mismatch, unlisted skill)tool-prerequisites-fieldscheck (bold sub-field labels or the pure-contract delegation shorthand), so the normalize-then-tighten ordering the old bullet tracked is doneType of change
tools/spec-loop/specs/)Test plan
uv run --project tools/spec-validator spec-validate tools/spec-loop/specs/— OK, no violationsprek run --all-files— all 23 hooks passvalidate_capability_taxonomy_coverageat__init__.pyL2283,validate_modes_doc_consistencyat L2821,tool-prerequisites-fieldsinHARD_CATEGORIES), per the issue's "verify by finding the call site" noteRFC-AI-0004 compliance
No runtime behaviour or state-changing workflow is changed — spec prose only.
Linked issues
Closes #938
Generative AI disclosure
Prepared with Claude Code (Fable 5). The commit carries a
Generated-by:trailer and no AICo-Authored-By:trailer.