docs(ISSUE-WP-0006): Forgejo-only language and projection boundary
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Build and Publish Container Image / build-and-push (push) Successful in 34s

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
This commit is contained in:
tegwick 2026-09-14 04:52:58 +02:00
parent f9d276dadf
commit ee9b85215d
34 changed files with 410 additions and 263 deletions

View file

@ -55,7 +55,7 @@ A **Capability Implementation** is a concrete realization of a Capability Family
**Characteristics:**
- Provides **concrete functionality** (code, CLI, API)
- May implement **multiple backend variants** (Gitea, GitHub, local)
- May implement **multiple backend variants** (Forgejo, GitHub, local)
- Has **maturity levels** (experimental, beta, production)
- Can be **composed with other capabilities**
@ -255,7 +255,7 @@ metadata:
implementation: issue-core
version: 1.0.0
description: >
Unified interface for issue tracking across Gitea, GitHub, GitLab.
Unified interface for issue tracking across Forgejo, GitHub, GitLab.
Enables agent coordination via standardized issue operations.
purpose:
@ -315,7 +315,7 @@ purpose:
- "Unified issue management for polyglot platform environments"
problems_solved:
- "Direct API calls to GitHub/GitLab/Gitea (avoids credential sprawl)"
- "Direct API calls to GitHub/GitLab/Forgejo (avoids credential sprawl)"
- "Inconsistent issue tracking access patterns"
- "Platform-specific code in agents"
- "Offline/online workflow synchronization"
@ -323,7 +323,7 @@ purpose:
# When to use this capability
usage_rules:
MUST_USE_INSTEAD_OF:
- "Direct Gitea/GitHub/GitLab API calls"
- "Direct Forgejo/GitHub/GitLab API calls"
- "Platform-specific CLIs (gh, glab)"
- "Python libraries (PyGithub, python-gitlab)"
@ -361,7 +361,7 @@ integration:
required: true
method: manual # auto-detection planned for v1.1
steps:
- "Export GITEA_API_TOKEN environment variable"
- "Export FORGEJO_TOKEN environment variable (GITEA_API_TOKEN is a deprecated alias)"
- "Run: issue backend add myproject gitea"
- "Provide: URL, owner, repo when prompted"
- "Run: issue backend set-default myproject"
@ -416,8 +416,8 @@ efficiency:
credentials:
method: environment_variables
variables:
- GITEA_API_TOKEN
- GITEA_URL # optional with config
- FORGEJO_TOKEN # preferred; GITEA_API_TOKEN is a deprecated alias
- FORGEJO_URL # optional with config; GITEA_URL deprecated alias
security:
- "Tokens never in code or logs"
@ -736,7 +736,7 @@ metadata:
```
Project A needs GitHub issues
Project B needs GitLab issues
Project C needs Gitea issues
Project C needs Forgejo issues
→ Pattern: "We need issue tracking"
→ Family: "issue-tracking"