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

workplans/ISSUE-WP-0005-connector-alignment-implementation.md

@@ -35,7 +35,7 @@ Close the gap between:
 | Layer | State at start of this WP |
 | --- | --- |
 | **INTENT** | Work-record-aligned connector (2026-07-22) |
-| **SCOPE §1 shipped** | Models, SQLite/Gitea, CLI, REST TaskSpec, backend sync |
+| **SCOPE §1 shipped** | Models, SQLite/Forgejo, CLI, REST TaskSpec, backend sync |
 | **SCOPE §1.8 / target** | Mapping store/API, boundary sync, work_record_uuid, dual-lifecycle rules |
 
 Deliver a **minimum viable connector core**: durable mapping + project/link
@@ -137,14 +137,14 @@ state_hub_task_id: "027871b0-696d-5ab7-b18c-b26167e97813"
 Per `docs/uuid-external-id-mapping.md`:
 
 - Table `work_record_issue_map` (or equivalent) on local backend / dedicated
-  store used even when CRUD backend is Gitea
+  store used even when CRUD backend is Forgejo
 - Uniqueness: active `(backend, external_id)` and active
   `(work_record_uuid, backend)`
 - Domain service `MappingService`: upsert, resolve by UUID, by canonical id
   (if provided), by external id, detach
 - Unit tests for idempotent project and uniqueness
 
-**Acceptance:** Tests pass without a live Gitea; store survives reconnect;
+**Acceptance:** Tests pass without a live Forgejo; store survives reconnect;
 SCOPE §1.8 “mapping store” can move toward shipped with an honest partial
 note until CLI/API land.
 
@@ -208,7 +208,7 @@ Implement **outward-only** application of T03 rules for mapped records
 - Do **not** write work-record files
 - Inward sync remains out of scope for this task (document as next)
 
-**Acceptance:** Policy tests + one integration-style test on local/Gitea mock;
+**Acceptance:** Policy tests + one integration-style test on local/Forgejo mock;
 SCOPE distinguishes backend sync vs work-record boundary sync clearly.
 
 ## Task: SCOPE inventory refresh after implementation