T05 entry 4: wire consumer relations and refresh issue-core evidence.

Add supports/related_to for vergabe-teilnahme and activity-core, cite
SCOPE.md, update test count to 120 (verified), and document dual-canonical
relationship with CAPABILITY-issue-tracking.yaml.

registry/capabilities/capability.infotech.issue-tracking.md

@@ -15,10 +15,10 @@ maturity:
     current: D4
     target: D5
     confidence: high
-    rationale: Repo already carries its own detailed capability manifest (CAPABILITY-issue-tracking.yaml)
+    rationale: SCOPE.md, CAPABILITY-issue-tracking.yaml (agent-integration deep spec), AGENT_INTEGRATION.md,
-      plus AGENT_INTEGRATION.md, ROADMAP.md, and a .capability/ feedback-submission mechanism; usage rules,
+      ROADMAP.md, and .capability/ feedback cover usage rules, API surface, and credential handling. This
-      API surface, and credential handling are all explicitly documented. This entry migrates that existing
+      registry entry is the federation-facing normalization of that material — the YAML manifest remains
-      description into the standard registry location rather than drafting fresh.
+      the detailed agent-integration companion, not superseded.
   availability:
     current: A2
     target: A3
@@ -70,15 +70,18 @@ availability:
   - library import
 relations:
   depends_on: []
-  supports: []
+  supports:
-  related_to: []
+  - capability.procurement.vergabe-teilnahme
+  related_to:
+  - capability.activity.event-coordinate
 evidence:
   documentation:
+  - SCOPE.md
   - CAPABILITY-issue-tracking.yaml
   - AGENT_INTEGRATION.md
   - ROADMAP.md
   tests:
-  - tests/ (109 tests, 61% coverage per CAPABILITY-issue-tracking.yaml testing section)
+  - tests/ (120 tests collected 2026-07-07; 61% coverage per CAPABILITY-issue-tracking.yaml)
   consumer_feedback: []
   bug_reports: []
   incidents: []
@@ -89,6 +92,7 @@ consumer_guidance:
   - needs requiring MCP server integration (not shipped yet)
   known_limitations:
   - manual backend configuration in v1.0; no built-in issue locking beyond assignee convention
+  - CAPABILITY-issue-tracking.yaml and registry/capabilities/ coexist — update both when agent rules change
 promotion_history: []
 ---
 
@@ -96,7 +100,7 @@ promotion_history: []
 
 ## Overview
 
-`issue-core` is a universal interface for issue-tracking coordination across Gitea, GitHub, and GitLab, giving agents a unified Python API and CLI instead of direct platform API calls. This registry entry migrates the repo's own pre-existing `CAPABILITY-issue-tracking.yaml` capability manifest (109 tests, 61% coverage, documented usage rules and credential handling) into the standard `registry/capabilities/` location.
+`issue-core` is a universal interface for issue-tracking coordination across Gitea, GitHub, and GitLab, giving agents a unified Python API and CLI instead of direct platform API calls. This registry entry is the federation-facing form of the repo's `CAPABILITY-issue-tracking.yaml` manifest (120 tests, 61% coverage, documented usage rules and credential handling). The YAML file remains the detailed agent-integration companion.
 
 ## Assessment notes
 
@@ -124,5 +128,5 @@ intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.
 - [x] ID follows `capability.<domain>.<name>` pattern
 - [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
 - [x] `external_evidence` is populated separately from `maturity`
-- [ ] Relations reference valid capability IDs (none yet)
+- [x] Relations reference valid capability IDs (vergabe-teilnahme, activity-core)
 - [x] Index entry added in `registry/indexes/capabilities.yaml`

registry/indexes/capabilities.yaml

@@ -1,5 +1,5 @@
 version: 1
-updated: '2026-07-06'
+updated: '2026-07-07'
 domain: helix_forge
 capabilities:
 - id: capability.infotech.issue-tracking