Multi-Forge & Ticket Synchronization

CCCP connects your Git workflow directly to upstream issue trackers, automatically synchronizing open issues into a local markdown document (.antigravity/tickets.md) for developers and autonomous AI coding agents.

1. Supported Remote Forges

Forge Ecosystem	Supported Domains	Active Probing & Identification
Forgejo & Gitea	`codeberg.org`, self-hosted	Probes `/api/v1/version` for self-hosted instances
GitHub	`github.com`, GitHub Enterprise	Uses GitHub REST API v3, filtering out pull requests
GitLab	`framagit.org`, `gitlab.com`, custom	Probes `/api/v4/version` and supports nested subgroups
SourceHut	`git.sr.ht`, `*.sr.ht`	Extracts issues via SourceHut GraphQL tracker

2. Synchronizing Tickets (`cccp tickets`)

# Synchronize tickets using automatic remote forge detection:
cccp tickets

# Force a specific forge driver:
cccp tickets --provider forgejo

# Specify custom owner and repository slug:
TICKETS_OWNER=myteam TICKETS_REPO=myproject cccp tickets

3. Gosplan Hourly Quota Protection

To prevent API rate limit exhaustion against public endpoints (such as GitHub's 60 calls/hour ceiling for unauthenticated requests), CCCP monitors request timestamps in .git/cccp_tickets_rate_limit:

Ceiling: Default max 55 requests per sliding hour.
Zero-Disruption Guarantee: When quota is reached, CCCP cleanly exits with code 0 and emits a Gosplan quota notification without halting Git push chains or CI workflows.

4. Continuous Integration & Site Publishing

CCCP features an automated Forgejo Actions pipeline (.forgejo/workflows/ci.yml) that validates and deploys this documentation site on every push to main:

Cloudflare Workers (cccp.2lp.in): Primary deployment target with static assets and automated custom domain routing configured via wrangler.jsonc.
Codeberg Pages (pages branch): Redundant mirror automatically pushed using the action's built-in token.
Site Verification: bin/verify-site.sh guarantees zero broken links before deployment.