Mirrors archie-core's proto/forge/v1 change: the SDK Forge interface and
server dispatch gain CreateIssue; gitea resolves label names to IDs
(creating missing labels) and github passes label names through.
AcceptInvitations accepted every pending repository invitation, so any
GitHub user could add the forge's account to a repository by sending an
invitation. The host now passes the connection's configured repositories
in AcceptInvitationsRequest and the extension leaves an invitation to
anything else pending. The Gitea forge is unchanged: it has no
invitations to accept.
Every call shared one SDK client whose context was background, so no caller
could cancel a Gitea request; each call now binds its own. LinkBranch
hand-built JSON over raw HTTP and posted to an endpoint Gitea does not have;
it sets the issue's ref through the SDK. PRState and VerifyPush matched error
text instead of the status, label lookup stopped at the first 100 labels,
merges ignored the repository's merge style, and a review of the token's own
pull request requested changes Gitea refuses.
Errors say what GitHub refused in its own words instead of the request URL
and an empty field list. Webhook review states arrive lower-case and were
never normalised, so a webhook-delivered change request did not read as one.
A review the token would post as REQUEST_CHANGES on its own pull request
comments instead, which GitHub accepts. Secondary rate limits wait up to two
minutes and retry.