feat(register): a decided YES about tag history, and app-creator registered

Two changes that belong together: both are the register learning to record a
decision the engine could otherwise only re-report forever.

`tags_lightweight_accepted` — TAG-ANNOTATED-HISTORY (WARN) fires on 13
historical lightweight tags in three repos. A lightweight tag is movable
without a trace and the catalog pins plugins by tag, so the finding is real.
But the only remedy for a published one is force-moving it — the exact act the
check warns about — so the WARN could never be cleared. That is the `titles`
defect one axis over: the gate could not tell "we decided this" from "nobody
looked".

Keyed on tag NAME, never a count: a count stays satisfied the moment one tag is
re-cut and a different, unaccepted one takes its place.

An accepted tag emits `TAG-ANNOTATED-ACCEPTED` at OK naming the tags — it is
not dropped. An exemption is a finding, the rule `readme_desc_match` already
follows; an exception nobody can see reads exactly like a check that silently
stopped running.

13 entries, not the 14 lightweight tags that exist. `ktg-plugin-marketplace
v7.7.2` is deliberately absent: it is that repo's NEWEST tag, the one
lightweight tag with a safe remedy, and an ERROR today. Pre-accepting it would
mean cutting v7.8.0 instead of fixing it makes the finding vanish silently.
The engine enforces this independently — the newest tag cannot be accepted
away even if named, and a test pins that.

`app-creator` → `standalone` — `--refresh` measured 22 on the forge against 21
registered. Unregistered meant zero checks against a repo published on `open/`.
The class is derived, not guessed: no `.claude-plugin/plugin.json`, absent from
the catalog, own remote on `open/` — identical in form to the four existing
`standalone`.

Measured before and after across all 21 clones, every finding code diffed:
- TAG-ANNOTATED-HISTORY 3 WARN -> 0, converted 1:1 to 3 OK. None disappeared.
- TAG-ANNOTATED unchanged at 1 ERROR (ktg-plugin-marketplace v7.7.2).
- app-creator: 1 SKIP -> 16 judged findings (3 ERROR, 2 WARN). Recorded, not
  fixed — it records, it does not fix.
- Nothing else moved.
- `--refresh`: 22/22, no divergence.

The accepted lists are claims about three OTHER repos, measured from LOCAL
clones — which is the gap REMOTE-SYNC exists to name. They go to those repos by
coord so a wrong name can be disputed.

187 tests (was 182).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015AkHEqTSr1k3HbeiHu1ggW

register/repos.json

@@ -36,7 +36,8 @@
     "portfolio-optimiser": "standalone",
     "portfolio-optimiser-claude": "standalone",
     "llm-ingestion-pipeline-security": "standalone",
-    "llm-ingestion-okf": "standalone"
+    "llm-ingestion-okf": "standalone",
+    "app-creator": "standalone"
   },
 
   "$comment_non_repos": [
@@ -185,6 +186,34 @@
     "okr": "nb"
   },
 
+  "$comment_tags_lightweight_accepted": [
+    "Where a decided YES about lightweight tag HISTORY gets written down — the",
+    "same job `titles` does for a README H1, one axis over. A lightweight tag is",
+    "movable without a trace and the catalog pins plugins by tag, so it is a",
+    "supply-chain property; but the only remedy for a PUBLISHED one is force-",
+    "moving it, which is the act the check warns about. Without this list the",
+    "WARN can never be cleared, and the gate says the same thing forever.",
+    "",
+    "Keyed on tag NAME, never on a count. A count stays satisfied the moment one",
+    "tag is re-cut and a different, unaccepted one takes its place.",
+    "",
+    "MEASURED 2026-08-12 from the LOCAL clones, not from the forge — which is",
+    "the very gap REMOTE-SYNC exists to name, so these are claims about three",
+    "OTHER repos and were sent to them by coord so a wrong name can be disputed.",
+    "",
+    "13 entries, not the 14 lightweight tags that exist. `ktg-plugin-marketplace",
+    "v7.7.2` is DELIBERATELY ABSENT: it is that repo's newest tag, the one",
+    "lightweight tag with a safe remedy (`git tag -a -f`), and it is an ERROR",
+    "today. Pre-accepting it would mean that cutting v7.8.0 instead of fixing it",
+    "makes the finding vanish silently — the cheap fix skipped and unrecorded.",
+    "If it ages into history un-remedied, a fresh WARN is the correct signal."
+  ],
+  "tags_lightweight_accepted": {
+    "ktg-plugin-marketplace": ["v3.4.1", "v5.0.0", "v5.0.1", "v5.0.2", "v5.0.3", "v7.7.0", "v7.7.1"],
+    "llm-ingestion-okf": ["v0.2.0", "v0.3.0", "v0.3.1", "v0.3.2", "v0.4.0"],
+    "llm-ingestion-pipeline-security": ["v0.3.0"]
+  },
+
   "description_max_codepoints": 180,
   "$comment_length": [
     "180 codepoints, not bytes and not UTF-16 units. The same string measures 248",