feat: add TER metadata and public listing conformance checks

- Add TC-55/56/57: mechanical checks for composer.json support URLs
- Add TC-80: LLM review for TER, Packagist, docs.typo3.org listings
- Add TC-81: LLM review for TER publish workflow metadata setup
- Add ter-publishing.md: TER metadata setup, Packagist, docs.typo3.org
- Update conformance checklist with TER metadata and public listings

Author: CybotTM

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "typo3-conformance",
-  "version": "2.2.1",
+  "version": "2.4.0",
   "description": "Evaluate TYPO3 extensions for conformance to v12/v13/v14 standards",
   "repository": "https://github.com/netresearch/typo3-conformance-skill",
   "license": "MIT",

skills/typo3-conformance/checkpoints.yaml

@@ -231,6 +231,28 @@ mechanical:
     severity: info
     desc: "ext_tables.php should exist for backend module registration (if needed)"
 
+  # === TER PUBLISHING CHECKS ===
+  - id: TC-55
+    type: json_path
+    target: composer.json
+    pattern: '.support.issues'
+    severity: warning
+    desc: "composer.json should define support.issues URL for bug tracker link"
+
+  - id: TC-56
+    type: json_path
+    target: composer.json
+    pattern: '.support.source'
+    severity: warning
+    desc: "composer.json should define support.source URL for repository link"
+
+  - id: TC-57
+    type: json_path
+    target: composer.json
+    pattern: '.homepage'
+    severity: warning
+    desc: "composer.json should define homepage URL"
+
 llm_reviews:
   # === CODE QUALITY REVIEWS ===
   - id: TC-60
@@ -281,3 +303,62 @@ llm_reviews:
       5. Verify version compatibility is clearly stated
     severity: info
     desc: "Extension documentation should be complete"
+
+  # === PUBLIC LISTING VERIFICATION ===
+  - id: TC-80
+    domain: publishing
+    prompt: |
+      Verify public listing presence and completeness for the extension.
+      Extract the composer package name from composer.json and the extension
+      key from ext_emconf.php, then check:
+
+      1. TER Listing (extensions.typo3.org/extension/{extension_key}):
+         - Extension page exists and is accessible
+         - Sidebar links are populated (Extension Manual, Found an Issue,
+           Code Insights, Packagist.org)
+         - If links are missing, they must be set via:
+           TYPO3_API_TOKEN=... tailor ter:update \
+             --composer="vendor/package-name" \
+             --manual="https://github.com/..." \
+             --issues="https://github.com/.../issues" \
+             --repository="https://github.com/..." \
+             {extension_key}
+         - Version shown matches latest release
+
+      2. Packagist Listing (packagist.org/packages/{vendor/name}):
+         - Package exists and is findable
+         - Description is meaningful (not empty)
+         - License is set
+         - Latest version is published
+
+      3. Documentation (docs.typo3.org):
+         - If Documentation/ directory with guides.xml exists, check if
+           rendered documentation is available at docs.typo3.org
+         - Alternatively, README or external docs linked from TER
+
+      Report missing or incomplete listings as actionable items.
+    severity: warning
+    desc: "Extension should have complete TER, Packagist, and documentation listings"
+
+  - id: TC-81
+    domain: publishing
+    prompt: |
+      Check the TER publishing workflow for metadata setup completeness:
+
+      1. Verify .github/workflows/ contains a TER publish workflow
+      2. Check if the workflow includes a tailor ter:update step that sets:
+         - --composer (package name for Packagist link)
+         - --manual (documentation/repository link)
+         - --issues (issue tracker link)
+         - --repository (source code link)
+      3. If ter:update is missing from the workflow, recommend adding it
+         as a post-publish step or as a separate one-time setup step
+
+      The ter:update command sets the sidebar links on extensions.typo3.org.
+      Without it, the TER page shows no links to documentation, issues,
+      source code, or Packagist - making the extension appear incomplete.
+
+      This is a MANDATORY step for initial TER setup. The links persist
+      across releases, so it only needs to run once (or when URLs change).
+    severity: warning
+    desc: "TER publish workflow should include metadata setup via tailor ter:update"

skills/typo3-conformance/references/ter-publishing.md

@@ -230,6 +230,108 @@ Details: ${RELEASE_URL}"
 
 ---
 
+## MANDATORY: TER Metadata Setup (Sidebar Links)
+
+**CRITICAL:** The TER extension page sidebar links (Extension Manual, Found an Issue?, Code Insights, Packagist.org) are **NOT** populated from `composer.json`. They must be set explicitly via `tailor ter:update`.
+
+Without this step, the TER page looks incomplete — no links to documentation, issues, source code, or Packagist.
+
+### The Problem
+
+New extensions uploaded to TER show an empty sidebar with no links:
+- No "Extension Manual" button
+- No "Found an Issue?" button
+- No "Code Insights" button
+- No "Packagist.org" button
+
+This makes the extension appear unprofessional and hard to use.
+
+### The Solution
+
+Run `tailor ter:update` after the first TER upload:
+
+```bash
+TYPO3_API_TOKEN=your-token tailor ter:update \
+  --composer="vendor/package-name" \
+  --manual="https://github.com/vendor/repo" \
+  --issues="https://github.com/vendor/repo/issues" \
+  --repository="https://github.com/vendor/repo" \
+  --tags="tag1,tag2,tag3" \
+  extension_key
+```
+
+### Available Metadata Fields
+
+| Option | TER Sidebar Button | Required |
+|--------|--------------------|----------|
+| `--manual` | Extension Manual | **YES** |
+| `--issues` | Found an Issue? | **YES** |
+| `--repository` | Code Insights | **YES** |
+| `--composer` | Packagist.org (auto-linked) | **YES** |
+| `--tags` | Search tags | Recommended |
+| `--paypal` | Sponsoring link | Optional |
+
+### When to Run
+
+- **First release:** MANDATORY after the first `ter:publish`
+- **URL changes:** Only when repository, docs, or issue tracker URLs change
+- **Links persist:** Once set, they carry across all future version uploads
+
+### Automation via CI
+
+Add to your TER publish workflow as a post-publish step:
+
+```yaml
+- name: Update TER metadata
+  if: env.FIRST_RELEASE == 'true'  # or always, idempotent
+  run: |
+    TAILOR="$(composer global config bin-dir --absolute)/tailor"
+    "${TAILOR}" ter:update \
+      --composer="${COMPOSER_NAME}" \
+      --manual="${REPO_URL}" \
+      --issues="${REPO_URL}/issues" \
+      --repository="${REPO_URL}" \
+      "${TYPO3_EXTENSION_KEY}"
+```
+
+### Verification
+
+After setting metadata, verify on the TER page:
+
+```bash
+# Check that all 4 sidebar links are present
+curl -s "https://extensions.typo3.org/extension/${EXT_KEY}" | \
+  grep -c 'Extension Manual\|Found an Issue\|Code Insights\|Packagist\.org'
+# Expected: 4
+```
+
+---
+
+## Packagist Listing
+
+Extensions with a `composer.json` should be listed on [Packagist](https://packagist.org):
+
+1. **Submit package** at https://packagist.org/packages/submit
+2. **Enable auto-update** via GitHub webhook (Packagist Settings > Enable GitHub Hook)
+3. **Verify** the package appears with correct description and version
+
+The `--composer` flag in `ter:update` creates the Packagist link on the TER page.
+
+---
+
+## Documentation Rendering on docs.typo3.org
+
+Extensions with a `Documentation/` directory and `guides.xml` can have their documentation rendered at docs.typo3.org:
+
+1. **Create** `Documentation/guides.xml` with project metadata
+2. **Add RST files** following TYPO3 documentation standards
+3. **Webhook** is automatically triggered when the extension is on Packagist
+4. **Verify** at `https://docs.typo3.org/p/vendor/package-name/main/en-us/`
+
+If not using docs.typo3.org, set `--manual` to the GitHub repository URL or a hosted documentation site.
+
+---
+
 ## Release Comment Best Practices
 
 ### Writing Effective Release Notes
@@ -369,6 +471,21 @@ GitHub Actions Workflow:
 [ ] Uses typo3/tailor for publishing
 [ ] Secrets properly configured
 
+TER Metadata (MANDATORY for initial setup):
+[ ] tailor ter:update --manual has been run (Extension Manual link)
+[ ] tailor ter:update --issues has been run (Found an Issue link)
+[ ] tailor ter:update --repository has been run (Code Insights link)
+[ ] tailor ter:update --composer has been run (Packagist.org link)
+[ ] All 4 sidebar links visible on extensions.typo3.org
+
+Public Listings:
+[ ] Extension page exists on extensions.typo3.org
+[ ] Package exists on packagist.org
+[ ] Documentation available (docs.typo3.org or linked from TER)
+[ ] composer.json has support.issues URL
+[ ] composer.json has support.source URL
+[ ] composer.json has homepage URL
+
 Release Process:
 [ ] Semantic versioning followed
 [ ] CHANGELOG.md updated before release