(magpie) branch main updated: fix(specs): update three stale Known gaps in meta-and-quality-tooling.md (#1074)

[po...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/magpie.git


The following commit(s) were added to refs/heads/main by this push:
     new 1cdfabd9 fix(specs): update three stale Known gaps in meta-and-quality-tooling.md (#1074)
1cdfabd9 is described below

commit 1cdfabd9dbe5c3224b971296d0d28c9129ad3f9f
Author: lalala <54...@users.noreply.github.com>
AuthorDate: Thu Aug 13 05:14:48 2026 +0800

    fix(specs): update three stale Known gaps in meta-and-quality-tooling.md (#1074)
    
    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 #938
    
    Generated-by: Claude Code (Fable 5)
    
    Co-authored-by: zheflow <wz...@gmail.com>
---
 tools/spec-loop/specs/meta-and-quality-tooling.md | 26 +++++++++++++++--------
 1 file changed, 17 insertions(+), 9 deletions(-)

diff --git a/tools/spec-loop/specs/meta-and-quality-tooling.md b/tools/spec-loop/specs/meta-and-quality-tooling.md
index 1ac0a3d2..cdbdf07e 100644
--- a/tools/spec-loop/specs/meta-and-quality-tooling.md
+++ b/tools/spec-loop/specs/meta-and-quality-tooling.md
@@ -145,15 +145,23 @@ uv run --project tools/spec-inventory --group dev pytest tools/spec-inventory/te
   required fields, but the next pass should make `mode`, `status`,
   `capability`, `organization`, and `source` combinations explicit and
   test-backed.
-- **Capability taxonomy drift is not yet checked.** The validator should
-  catch misspelled or undocumented capability values, and should surface
-  taxonomy rows that no skill/tool implements unless they are marked
-  reserved.
-- **`docs/modes.md` is manually synced.** The plan tracks a generated
-  consistency check so mode tables and shipped counts cannot silently
-  drift from skill frontmatter.
-- **Tool README prerequisites vary.** A prerequisites consistency pass
-  should normalize older tool READMEs before tightening the validator.
+- **Capability taxonomy drift is now checked.**
+  `validate_capability_taxonomy_coverage` parses the Axis 1 / Axis 2
+  vocabulary tables in `docs/labels-and-capabilities.md`, surfaces
+  taxonomy rows that no skill/tool implements (entries marked
+  *(reserved)* / *(future)* are exempt), and cross-checks the
+  `SKILL_CAPABILITIES` / `TOOL_CAPABILITIES` code constants against the
+  doc — all SOFT advisories. Undocumented frontmatter capability values
+  are rejected by skill validation separately.
+- **`docs/modes.md` is no longer manually synced.**
+  `validate_modes_doc_consistency` compares the doc's per-mode tables
+  against live skill frontmatter — missing skills, mode mismatches,
+  skill-count mismatches, and unlisted skills — as SOFT advisories.
+- **Tool README prerequisites are normalized and enforced.** The HARD
+  `tool-prerequisites-fields` check requires the bold sub-field labels
+  (**Runtime:**, **CLIs:**, **Credentials / auth:**, **Network:**) or
+  the pure-contract delegation shorthand in every tool README, so the
+  normalize-then-tighten ordering this bullet used to track is done.
 - **Pilot evidence shape is now defined and validated.** `docs/pilot-report-template.md`
   defines the required frontmatter schema and body sections; `tools/pilot-report-validator/`
   enforces the schema on every `.md` file with a YAML frontmatter block.