docs(ISSUE-WP-0006): Forgejo-only language and projection boundary

Prefer Forgejo as the self-hosted forge product. Keep Gitea only as the
Gitea-compatible API identifier (module backends/gitea, type string
gitea). FORGEJO_TOKEN is preferred; GITEA_* remains a deprecated alias.

INTENT/SCOPE quote ACT-ADR-005: issue-core is not the fleet ops claim
queue. Connector docs describe repo work record → hub index → optional
Forgejo projection, not activity-core → issue-core → harness.

Assistant: grok
Assistant-Session: 01a09dc6-3f0d-7c93-8b11-8e83c0623d49

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

@@ -1,7 +1,7 @@
 ---
 id: capability.infotech.issue-tracking
 name: External Issue Tracker Connector
-summary: Backend-agnostic CLI/Python connector to Gitea/Forgejo (and SQLite cache)
+summary: Backend-agnostic CLI/Python connector to Forgejo (and SQLite cache)
   with work-record UUID ↔ external issue mapping. Not the fleet work origin.
 owner: issue-core
 status: draft
@@ -29,10 +29,10 @@ external_evidence:
     confidence: medium
     basis: scope_vs_intent_and_consumer_expectations
     satisfied_expectations:
-    - Gitea + local SQLite backends
+    - Forgejo + local SQLite backends
     - CLI with JSON output; project/map commands
     - work_record_uuid optional on TaskSpec
-    - credential handling via env vars (GITEA_API_TOKEN, ISSUE_CORE_API_KEY)
+    - credential handling via env vars (FORGEJO_TOKEN preferred; GITEA_API_TOKEN deprecated alias; ISSUE_CORE_API_KEY)
     broken_expectations: []
     out_of_scope_expectations:
     - Fleet task origin / intake promotion (work-record canon)