chore: address Copilot review round 4

- verify:skills:cli — the authoritative validator is now a GUARANTEED step in
  `local:gate` and CI, not a best-effort hand-off. It resolves the CLI itself
  (an installed one at 2.1.233+, else a pinned `npx -y`), so both tiers run the
  same script and cannot drift. `verify:skills` keeps skipping when the CLI is
  absent, which is right for `validate`: fast, offline, no Claude Code required.
- skill-manifest: the 1,536-char listing-entry cap covers `description` +
  `when_to_use` together; checking the description alone passed an over-cap
  entry. `when_to_use` is now parsed, validated and counted, with boundary tests
  at 1,536/1,537.
- verify-skills: report the budget as *this repo's contribution*. The real
  listing budget is shared with bundled skills and the contributor's own
  ~/.claude/skills, none of which is visible from here, so the number was
  claiming more than it measured.
- skill-eval: a negative case now means "no skill OF THIS REPO'S fired". It
  failed on any Skill invocation, so a contributor with an unrelated global
  skill got a false failure about their environment rather than these skills.
- docs/architecture + local-dev: the Node backend runner gets its
  `@inspector/core` alias from `clients/web/tsup.runner.config.ts`, not from
  Vite. The old text sent runner work to the wrong config.
- local-dev: the tarball does not ship "only each client's build/" — the
  allowlist also carries `clients/web/dist`, `clients/web/static` and the
  install helper. States the invariant that actually matters instead.
- issue-triage: the test for needing triage is "no board card". Adding "and no
  milestone" would skip the approved-but-unboarded case the same section then
  handles. Also corrected the `$M` note: the lookup is `--state all`, so closed
  issues DO have entries — `isopen` is about the invariants, not the lookup.
- issue-create: replaced "all five" with a per-version table. Steps 3 and 6
  (milestone, Priority) do not exist for v1, so the old list opened with a rule
  the same skill later tells you to violate.

Signed-off-by: cliffhall <cliff@futurescale.com>

scripts/skill-eval.test.mjs

@@ -197,3 +197,21 @@ test("runPrompt propagates a spawn error", async () => {
     /ENOENT/,
   );
 });
+
+test("a negative case ignores skills that are not this repo's", () => {
+  // A contributor's own `~/.claude/skills` entry, or a bundled skill, firing on
+  // a negative prompt says nothing about these skills — failing on it would be
+  // a false failure about someone else's environment.
+  const ours = new Set(["testing", "local-dev"]);
+  const foreign = new Set(['{"skill":"my-personal-notes"}']);
+  const mine = new Set(['{"skill":"testing"}']);
+
+  assert.equal(sampleHit(null, foreign, ours), true);
+  assert.equal(sampleHit(null, mine, ours), false);
+  assert.equal(sampleHit(null, new Set(), ours), true);
+  // A positive case is unaffected: it names the skill it wants.
+  assert.equal(sampleHit("testing", mine, ours), true);
+  assert.equal(sampleHit("testing", foreign, ours), false);
+  // With no repo set, any invocation still fails a negative case.
+  assert.equal(sampleHit(null, foreign), false);
+});