wire-ci ships no CI templates: docs/templates/ci/ missing from repo and package — skill's verify gate fails

[56phil]

Summary

wire-ci is a Build-phase skill whose entire deliverable — the bundled CI templates at docs/templates/ci/<forge>/ — does not exist in the repository or the published package. The skill's own → verify: directive fails against the package itself, and bash scripts/wire-ci.sh --self-test fails.

Evidence (bigpowers v2.87.5)

1. skills/wire-ci/SKILL.md states (line 32): "Templates live in docs/templates/ci/<forge>/ inside the bigpowers package" and its → verify: (line 110) is:

   test -f docs/templates/ci/github/test-build-release-node.yml && test -f scripts/lib/detect-forge.sh
   

2. docs/templates/ci/ does not exist in the package (only templates/codex/AGENTS.md exists), and docs/templates/ci is also not present in the GitHub repo at danielvm-git/bigpowers (confirmed via the API).
3. bash scripts/wire-ci.sh --self-test output:

   FAIL: self-test — github/node project did not resolve: wire-ci: forge=github stack=node
   wire-ci: SKIP — no bundled template at <pkg>/docs/templates/ci/github/test-build-release-node.yml
   FAIL: wire-ci self-test — 1 problem(s)
   

4. scripts/lib/detect-forge.sh exists and works; only the template directory is missing.
5. scripts/run-skill-verify.sh reports both wire-ci checks as FAIL.

Impact

Every agent that follows this skill will emit SKIP — no bundled template for any forge, including GitHub. The skill's promise — "no network dependency on any third party's repository" — is unmet: with the templates absent, there is nothing for the skill to install. Related history: #73 (CI/CD template consolidation, closed) and #104 (GitHub-lock note) did not result in the templates actually shipping; this issue is the concrete, still-open defect.

Expected behavior

• Ship a docs/templates/ci/github/ set (starting with test-build-release-node.yml as the verify gate requires) plus whatever the skill documents for other forges.
• Ensure bash scripts/wire-ci.sh --self-test passes against the package (the "github/node project" resolution).
• Add a packaging test so a future release can't drop the templates again (e.g. include docs/templates/ci/ in the npm files list).