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
This commit is contained in:
parent
f9d276dadf
commit
ee9b85215d
34 changed files with 410 additions and 263 deletions
2
Makefile
2
Makefile
|
|
@ -22,7 +22,7 @@ help: ## Show issue core capability help
|
|||
@echo " issue-backend-list List configured backends"
|
||||
@echo " issue-backend-detect Auto-detect backend from repository"
|
||||
@echo " issue-backend-set-local Configure local SQLite backend"
|
||||
@echo " issue-backend-set-gitea Configure Gitea backend"
|
||||
@echo " issue-backend-set-gitea Configure Forgejo backend (Gitea-compatible API)"
|
||||
@echo ""
|
||||
@echo "Synchronization:"
|
||||
@echo " issue-sync Sync with remote backend"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue