todo(18): open

TODO

@@ -213,3 +213,32 @@ Created: 2025-12-31
 Relationships: 
 Description: Extend the built-in event-driven parser to be modeled after DOM
              recursive-descent HTML parser
+
+--ISSUE
+Content-Type: application/issue
+ID: 18
+Type: feature
+Title: implement saas wrapper for Forgejo
+Status: open
+Priority: medium
+Created: 2026-06-06
+Relationships: 
+Description: Add a new sub-package byteb4rb1e.utils.saas.forgejo, supporting the
+             same/similar operations as the Bitbucket wrapper
+             (byteb4rb1e.utils.saas.bitbucket) against the Forgejo REST API:
+             token-based authentication headers, repository existence checks,
+             repository creation within an owner/organization, and clone URL
+             construction. Implement as a thin layer over
+             byteb4rb1e.utils.http.client, consistent with the existing
+             Bitbucket and GitHub modules.
+             Unlike Bitbucket (one global SaaS instance, hence the hardcoded
+             api.bitbucket.org), Forgejo is self-hosted (e.g.
+             git.code.tiararodney.com). The wrapper MUST take a host/instance
+             URL parameter (or read one from config) rather than baking any
+             specific instance in. This is the biggest API-surface difference
+             from the bitbucket module.
+             Bitbucket's clone_url constructs SSH only. Forgejo's repository
+             API returns both clone_url (HTTPS) and ssh_url, and HTTPS is
+             needed in CI (no SSH host keys on the Woodpecker runner). The
+             wrapper SHOULD expose both, either as ssh_clone_url and
+             https_clone_url, or a single clone_url(..., scheme="ssh"|"https").