coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

15
CAPABILITY-issue-tracking.yaml
View file

@ -6,14 +6,14 @@ metadata:
version: 0.2.1
type: connector
description: >
Backend-agnostic connector to external issue trackers (Gitea/Forgejo, SQLite).
Backend-agnostic connector to external issue trackers (Forgejo, SQLite).
Maps work-record UUIDs to external issue ids. Not the origin of fleet work records.
# What problems this capability solves
purpose:
primary: External tracker projection and ops (work-record-aware connector)
problems_solved:
- Direct API calls to Gitea/GitHub/GitLab (credential sprawl)
- Direct API calls to Forgejo/GitHub/GitLab (credential sprawl)
- No durable link from work-record UUID to tracker issue
- Platform-specific agent code for tracker CRUD
- Offline SQLite cache / backend sync for tracker data
@ -21,7 +21,7 @@ purpose:
# When agents should use this capability
usage_rules:
MUST_USE_INSTEAD_OF:
- "Direct Gitea API calls (requests.post to /api/v1/repos/...)"
- "Direct Forgejo API calls (requests.post to /api/v1/repos/...)"
- "GitHub CLI (gh issue create/list/...)"
- "GitLab CLI (glab issue create/list/...)"
- "Python libraries (PyGithub, python-gitlab) for routine tracker ops"
@ -67,7 +67,7 @@ integration:
required: true
method: manual # v1.0 - auto in 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"
@ -115,8 +115,9 @@ efficiency:
credentials:
method: environment_variables
variables:
- GITEA_API_TOKEN
- GITEA_URL (optional with config)
- FORGEJO_TOKEN (preferred; FORGEJO_API_TOKEN also accepted)
- GITEA_API_TOKEN / GITEA_TOKEN (deprecated aliases)
- FORGEJO_URL (optional with config; GITEA_URL deprecated alias)
security:
- "Tokens never in code or logs"
@ -259,7 +260,7 @@ support:
solution: "Run: issue backend add <name> <type>"
- problem: "Authentication failed"
solution: "Check GITEA_API_TOKEN is set and valid"
solution: "Check FORGEJO_TOKEN is set and valid (legacy GITEA_API_TOKEN still accepted)"
- problem: "Command not found: issue"
solution: "Run: pip install -e capabilities/issue-core/"