[BrewingCoder]

Implements OP2-84: Gitea / Forgejo as a code provider with a self-hosted base URL, covering the whole GitHub tool surface (repos, commits, issues, pull requests, triage, files).

Shape

It plugs in the way Gmail joined mail, so none of the tools have to know which provider they're talking to:

• ProviderKind.Gitea is one provider for both Gitea and Forgejo, since Forgejo serves the same /api/v1. It's stored by name like the other providers, so no migration.
• ICodeProvider : IGitHubService plus CodeServiceRouter (src/OutPost2.Infrastructure/Code/CodeProviders.cs). These do dispatch only. Two providers registered for one kind is a startup error, and an unsupported kind gets a one-sentence GitHubException instead of a call made with the wrong token. GitHubService is now one ICodeProvider; IGitHubService resolves to the router, so CodeTools and RepoResolver are unchanged apart from the connection filter.
• The tools keep their github_* names. Renaming them would break every MCP client already configured. Their descriptions now mention Gitea and Forgejo. GitHubException is still the single exception type the code tools catch, documented as historical.
• Capabilities: Gitea declares code.read and code.write. Read starts on and write starts off, as for GitHub. CodeTools now accepts GitHub or Gitea connections, so the per-provider-default rules apply unchanged.

Gitea is not wire-compatible with GitHub: the differences, all in GiteaService

GitHub	Gitea / Forgejo
search/issues?q=review-requested:@me …	repos/issues/search?type=pulls&review_requested=true (also created, assigned, mentioned). review_requested needs Gitea 1.20+; that's in the README
repo: qualifier in the query	No repository filter on search. A per-repository personal search asks by owner and keeps only the matching repository.full_name, paging until it has enough
total_count in the body	X-Total-Count header. Triage counts use limit=1
draft	pull_request.draft on newer servers, or a WIP:/[WIP] title. That's Gitea's own convention, and the only signal on older servers
per_page=100	limit, capped at the server's MAX_RESPONSE_ITEMS (50 by default). Repository listing stops at the same 500 ceiling as GitHub
pushed_at	No equivalent. updated_at moves on a push, so it's used instead and the list is sorted client-side
Authorization: Bearer	Authorization: token …, which every release accepts
raw media type	repos/{repo}/raw/{path}, for files the contents API doesn't inline
contents/ at the root	contents with nothing after it

Unassigned and all-open questions without a repository are refused, as on GitHub. Repo-scoped all-open and unassigned use repos/{repo}/issues?type=…. A 409 on commits is an empty repository. 404, 401 and 403 each get their own sentence naming the host.

Connecting

• GiteaConnectionService.Normalise takes what a person types: git.example.com, a URL with a trailing slash, the API URL itself, a server under a sub-path (https://example.com/git), or http://ip:port. It returns …/api/v1/. A blank address is refused, because there is no public default host.
• The probe calls GET /user and gives a fix for each failure:
  • 401: the token was rejected.
  • 403: the token needs the read:user scope, plus read:repository and read:issue.
  • 404: there's no Gitea/Forgejo API at that address.
  • An HTML response: something answered, but it isn't the API.
• It also reads /version and logs whether the server is Gitea or Forgejo (Forgejo reports …+gitea-…). Nothing behaves differently based on it.
• Web changes:
  • A new Gitea / Forgejo option in the add-connection dialog. The server field is required and there's a token scope hint.
  • POST /connections/gitea/add, replace-token support, and the health check.
  • The repo-names page and endpoint include Gitea connections.
  • The voice-phrase preview has a Gitea entry.
• There's a new gitea HTTP client with the private-CA handler (OP2-45), since these servers are self-hosted by definition.

Tests

tests/OutPost2.Tests/Code/GiteaTests.cs has 38 tests, all against mocked HTTP:

• URL normalisation (7 forms, plus blank).
• Connect: token header, the stored provider and instance, the capabilities, and that a failed connect writes nothing.
• Each probe failure's message, including an HTML page.
• Triage counts from the header, with draft detection by flag and by WIP:.
• The flag for each scope.
• The owner-plus-filter path for a single repository.
• Unassigned filtering in a repository, and refusing unscoped all-open queries.
• Repositories: paging and ordering.
• Commits: the author fallback and the empty-repository 409.
• An item lookup that finds a PR through the issues endpoint.
• Contents: the root route, path encoding, base64 decoding, the raw fallback, binary and submodule refusals, and a directory asked for as a file.
• The router: dispatch, unsupported provider, duplicate registration.
• CodeTools choosing a Gitea connection and answering github_triage from it end to end.

Full suite (Linux, .NET 10.0.403, local Postgres): 1042 passed, 20 failed, 52 skipped. The 20 failures are the FormBindingTests/OAuthFlowTests web-page tests that fail the same way on unmodified main in this environment (HTTP 500 without Vault/Garage); this branch adds none. Since those page tests can't render here, the new add-connection form hasn't been rendered. It copies the YouTrack and GitHub forms' markup.

Not done / worth knowing

• Not run against a live server. This was written against Gitea's published API (1.20+ swagger) and Forgejo's matching routes. A LiveGiteaProbe in the style of LiveGitHubProbe would be the next step for someone with a server.
• user/repos scope: I've relied on it returning the token's owned, collaborator and organisation repositories, but haven't checked that against a live server. If an org's repositories are missing, the fallback is to page orgs/{org}/repos for each org from user/orgs.
• Write tools: none, the same as GitHub today. code.write is declared, and off, so a later write tool has a capability to check.
• Merging with Print Gmail times in the account's own zone, via a per-provider zone seam (OP2-285) #14 and Sweep provider text into tool output, fix every gap, and guard it mechanically (OP2-286) #15: I merged all three branches into main locally and they merge without conflicts. The combined suite gives 1128 passed and the same 20 environment failures. Sweep provider text into tool output, fix every gap, and guard it mechanically (OP2-286) #15's hostile-text harness finds tool classes by reflection, so it also exercises the Gitea router path.

https://claude.ai/code/session_01V7aurnqD63TPgNSBec8xrk

---

Generated by Claude Code