test: drop the gitea-labels pin now the retrofit removed that target

tests/test-adr0020-targets.sh pinned the corpus dangling set as exactly
{gitea-labels, neuledge-context} and tests/test-skill-size-check.sh probed both
individually. The gitea-issues retrofit cut the composition sentence whose
'>'-folded scalar produced 'gitea-labels- milestones', so that target no longer
exists and both suites went red.

EXPECTED_DANGLING is now {neuledge-context} and the gitea-issues probe is
removed rather than skipped, per the rule the probe file states about itself: a
probe whose fixture has been retrofitted is a pin that needs updating, not an
assertion-free pass counted in the totals.

The exact-set assertion stays. An empty expected set is still valid and still
pins that no new dangling target appeared -- which is what it becomes once
research is retrofitted. Both loops carry a shellcheck SC2043 waiver for the
same reason: one entry is the expected steady state, not bad quoting.

Refs #99

tests/test-skill-size-check.sh

@@ -546,16 +546,21 @@ echo "--- the live dangling routing targets are caught (issue #100) ---"
 # in the totals, which is worse than no probe at all because it makes the suite
 # look one test stronger than it is. It also contradicted
 # tests/test-adr0020-targets.sh, which pins the live dangling set as EXACTLY
-# {gitea-labels, neuledge-context}; that file is the authority on the set, this
-# one only checks the two are individually detected.
+# {neuledge-context}; that file is the authority on the set, this one only
+# checks each member is individually detected.
 #
 # Both SKIP branches are gone with it, for the same reason. A probe whose fixture
 # has been retrofitted is not "still passing" — it is a pin that needs updating,
 # here and in the exact-set assertion in test-adr0020-targets.sh, and it should
 # say so out loud rather than quietly agreeing with whatever it finds.
+# The gitea-labels probe was dropped when the issue #99 retrofit cut the
+# composition sentence whose YAML fold produced that target. Per the rule above
+# it is removed, not skipped.
+# shellcheck disable=SC2043  # one probe left by design -- the list shrinks as
+# each fixture is retrofitted and reaches zero when `research` lands. Keeping the
+# loop means removing the last entry is a one-line edit, not a restructure.
 for probe in \
-  "plugins/bin/.apm/skills/research/SKILL.md:neuledge-context" \
-  "plugins/gitea/.apm/skills/gitea-issues/SKILL.md:gitea-labels"; do
+  "plugins/bin/.apm/skills/research/SKILL.md:neuledge-context"; do
   probe_file="$REPO_ROOT/${probe%%:*}"
   probe_name="${probe##*:}"
   if [[ ! -f "$probe_file" ]]; then