Add the ttg-ops plugin: six skills for the forge estate

The marketplace held only MCP servers so far. These are skills for the
work that keeps costing manual effort and quietly breaking:

- ttg-publish-module — releasing a library, and verifying from a clean
  external project that the release is actually fetchable. Encodes the
  trap that cost the most: Gitea redirects old repo paths, but not Go
  module paths, so a repo can be reachable while `go get` fails.
- ttg-move-repo — moving a repo and following it through every place
  that names it, including the ones redirects do not cover.
- ttg-new-repo — creating one in the right org and registering it, so
  it cannot end up absent from the clone list the way batocera-store did.
- ttg-ci-enroll — wiring a repo into the build, and the usual failure
  where the config exists but the repo was never registered.
- ttg-audit-forge — the drift check between forge, clone list, wiki,
  catalog and CI.
- ttg-update-docs — README, wiki page and the public site (Vue page plus
  both locale files) after a change.

The rules stay in REPO_REFACT.md, WIKI_CONNECTION.md and
ECOSYSTEM_PLAN.md; the skills read them instead of carrying a second
copy that drifts.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

.claude-plugin/marketplace.json

@@ -23,6 +23,15 @@
       "author": {
         "name": "TTG"
       }
+    },
+    {
+      "name": "ttg-ops",
+      "source": "./plugins/ttg-ops",
+      "description": "Skills for the TTG forge estate — publishing modules and gems, moving and creating repos, enrolling CI, auditing consistency, and updating the README, wiki and public site after a change.",
+      "version": "0.1.0",
+      "author": {
+        "name": "TTG"
+      }
     }
   ]
 }