diff --git a/plugins/kyberforge/.apm/skills/agent-audit/scripts/validate.sh b/plugins/kyberforge/.apm/skills/agent-audit/scripts/validate.sh index fc0f711..b13a210 100755 --- a/plugins/kyberforge/.apm/skills/agent-audit/scripts/validate.sh +++ b/plugins/kyberforge/.apm/skills/agent-audit/scripts/validate.sh @@ -446,8 +446,17 @@ def known_targets(start_dir): # condition, pc-run's "run pre-commit hooks" reads as a route to a # non-existent `pre-commit` skill. # * A BARE arrow target counts only in ADR-0020's compressed boundary form, -# `Not -> `. Without that, diagnose's process chain -# "fix -> regression-test" reads as a route to `regression-test`. +# `Not -> `. The example that motivated it is gone: +# diagnose's process chain "fix -> regression-test", which without the +# gate read as a route to a non-existent `regression-test` skill, was cut +# when issue #99 retrofitted that description. So the gate is currently +# UNEXERCISED — gating and not gating produce the same verdict corpus-wide. +# Keep it anyway. It is a false-positive guard against prose no one has +# written yet, and any new process chain re-arms it. Unexercised is not the +# same as unnecessary, and the branch it guards is still load-bearing: the +# bare-arrow rule is the sole extractor for three real targets in +# kyberforge's audit skills (agent-audit -> agent-author, agent-audit -> +# skill-audit, skill-audit -> skill-author), all written unbackticked. # * A backticked hyphenated token counts only inside a boundary sentence. # Unconditionally, `pre-push` or `commit-msg` in a TRIGGER clause is a hard # FAIL with no escape hatch. Gating it costs nothing (measured over this diff --git a/plugins/kyberforge/.apm/skills/skill-audit/scripts/validate.sh b/plugins/kyberforge/.apm/skills/skill-audit/scripts/validate.sh index f9c0df7..e169390 100755 --- a/plugins/kyberforge/.apm/skills/skill-audit/scripts/validate.sh +++ b/plugins/kyberforge/.apm/skills/skill-audit/scripts/validate.sh @@ -372,8 +372,17 @@ def known_targets(start_dir): # condition, pc-run's "run pre-commit hooks" reads as a route to a # non-existent `pre-commit` skill. # * A BARE arrow target counts only in ADR-0020's compressed boundary form, -# `Not -> `. Without that, diagnose's process chain -# "fix -> regression-test" reads as a route to `regression-test`. +# `Not -> `. The example that motivated it is gone: +# diagnose's process chain "fix -> regression-test", which without the +# gate read as a route to a non-existent `regression-test` skill, was cut +# when issue #99 retrofitted that description. So the gate is currently +# UNEXERCISED — gating and not gating produce the same verdict corpus-wide. +# Keep it anyway. It is a false-positive guard against prose no one has +# written yet, and any new process chain re-arms it. Unexercised is not the +# same as unnecessary, and the branch it guards is still load-bearing: the +# bare-arrow rule is the sole extractor for three real targets in +# kyberforge's audit skills (agent-audit -> agent-author, agent-audit -> +# skill-audit, skill-audit -> skill-author), all written unbackticked. # * A backticked hyphenated token counts only inside a boundary sentence. # Unconditionally, `pre-push` or `commit-msg` in a TRIGGER clause is a hard # FAIL with no escape hatch. Gating it costs nothing (measured over this diff --git a/plugins/kyberforge/skills/agent-audit/scripts/validate.sh b/plugins/kyberforge/skills/agent-audit/scripts/validate.sh index fc0f711..b13a210 100755 --- a/plugins/kyberforge/skills/agent-audit/scripts/validate.sh +++ b/plugins/kyberforge/skills/agent-audit/scripts/validate.sh @@ -446,8 +446,17 @@ def known_targets(start_dir): # condition, pc-run's "run pre-commit hooks" reads as a route to a # non-existent `pre-commit` skill. # * A BARE arrow target counts only in ADR-0020's compressed boundary form, -# `Not -> `. Without that, diagnose's process chain -# "fix -> regression-test" reads as a route to `regression-test`. +# `Not -> `. The example that motivated it is gone: +# diagnose's process chain "fix -> regression-test", which without the +# gate read as a route to a non-existent `regression-test` skill, was cut +# when issue #99 retrofitted that description. So the gate is currently +# UNEXERCISED — gating and not gating produce the same verdict corpus-wide. +# Keep it anyway. It is a false-positive guard against prose no one has +# written yet, and any new process chain re-arms it. Unexercised is not the +# same as unnecessary, and the branch it guards is still load-bearing: the +# bare-arrow rule is the sole extractor for three real targets in +# kyberforge's audit skills (agent-audit -> agent-author, agent-audit -> +# skill-audit, skill-audit -> skill-author), all written unbackticked. # * A backticked hyphenated token counts only inside a boundary sentence. # Unconditionally, `pre-push` or `commit-msg` in a TRIGGER clause is a hard # FAIL with no escape hatch. Gating it costs nothing (measured over this diff --git a/plugins/kyberforge/skills/skill-audit/scripts/validate.sh b/plugins/kyberforge/skills/skill-audit/scripts/validate.sh index f9c0df7..e169390 100755 --- a/plugins/kyberforge/skills/skill-audit/scripts/validate.sh +++ b/plugins/kyberforge/skills/skill-audit/scripts/validate.sh @@ -372,8 +372,17 @@ def known_targets(start_dir): # condition, pc-run's "run pre-commit hooks" reads as a route to a # non-existent `pre-commit` skill. # * A BARE arrow target counts only in ADR-0020's compressed boundary form, -# `Not -> `. Without that, diagnose's process chain -# "fix -> regression-test" reads as a route to `regression-test`. +# `Not -> `. The example that motivated it is gone: +# diagnose's process chain "fix -> regression-test", which without the +# gate read as a route to a non-existent `regression-test` skill, was cut +# when issue #99 retrofitted that description. So the gate is currently +# UNEXERCISED — gating and not gating produce the same verdict corpus-wide. +# Keep it anyway. It is a false-positive guard against prose no one has +# written yet, and any new process chain re-arms it. Unexercised is not the +# same as unnecessary, and the branch it guards is still load-bearing: the +# bare-arrow rule is the sole extractor for three real targets in +# kyberforge's audit skills (agent-audit -> agent-author, agent-audit -> +# skill-audit, skill-audit -> skill-author), all written unbackticked. # * A backticked hyphenated token counts only inside a boundary sentence. # Unconditionally, `pre-push` or `commit-msg` in a TRIGGER clause is a hard # FAIL with no escape hatch. Gating it costs nothing (measured over this