feat: enable proven Forgejo and Gitea mutations

[mariusvniekerk]

Enable SDK-backed comment, issue creation, state/content edit, merge, and review approval capabilities for Forgejo and Gitea providers. Workflow approval and ready-for-review remain unsupported until those operations are proven through provider interfaces and tests.

[mariusvniekerk]

This change is part of the following stack:

• docs: plan Forgejo provider implementation #265
  • feat: add Forgejo and Gitea SDK client skeletons #267
    • feat: share Forgejo and Gitea provider core #268
      • feat: convert Forgejo and Gitea SDK records #269
        • feat: read Forgejo and Gitea through shared provider core #270
          • feat: start Forgejo and Gitea providers at runtime #271
            • feat: recognize Forgejo and Gitea provider configuration #266
              • test: cover Forgejo and Gitea repository imports #272
                • feat: expose Forgejo and Gitea repository imports #273
                  • test: add Forgejo and Gitea container fixtures #274
                  • feat: enable proven Forgejo and Gitea mutations #275 ◀
                  • docs: document Forgejo and Gitea setup #276
                  • feat: add gitealike Actions CI parity #281

_{Change managed by git-spice.}

[roborev-ci]

roborev: Combined Review (65abe58)

Enabling Gitea/Forgejo mutations has medium-risk correctness and coverage gaps that should be addressed before merge.

Medium

• internal/platform/gitealike/provider.go:282
  Edited merge-request comments are normalized with merge request number 0, so the returned event can be associated with the wrong MR and may corrupt or update the wrong local activity row.
  Fix: Preserve the owning MR/issue number when editing comments, either by passing it through the mutator API or enriching CommentDTO from the transport response before normalization.

• internal/platform/gitea/client.go:87, internal/platform/forgejo/client.go:88
  Core mutation workflows are enabled for Gitea/Forgejo without full-stack e2e coverage through the HTTP API and SQLite persistence path.
  Fix: Add e2e tests for representative Gitea/Forgejo mutation endpoints, including merge, comment, state flows, and local DB updates.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (6e24689)

No Medium, High, or Critical issues were reported.

All review agents found the code clean or provided no findings.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (0fd2c47)

No Medium-or-higher issues found across the reviews.

All agents that reported findings agree the code is clean.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (c1dae33)

No Medium, High, or Critical findings were reported.

All review agents agree the code is clean for the requested severity threshold.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (0862fad)

Summary verdict: one medium test coverage gap remains; no high or critical issues were reported.

Medium

• internal/server/api_test.go:8636 - The new full-stack Gitea-like mutation test covers comments, review, merge, state changes, and issue creation, but does not exercise the server API path for editing PR title/body, even though the change enables EditMergeRequestContent for Gitea/Forgejo. Add coverage to TestAPIGitealikeMutationsPersistThroughServer or a similar e2e test that calls the PR content edit endpoint and asserts the updated title/body persist.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (f2bfea8)

Merge support has one medium-severity provider error-handling regression to fix before merging.

Medium

• internal/server/huma_routes.go:1717: Gitea/Forgejo merge failures now surface through gitealike.HTTPError, but mergePR only preserves status/details for *github.ErrorResponse. Provider-side 409, 405, or 422 merge failures can be returned as generic 502s and skip the conflict-sync path.

  Fix: Add platform-neutral HTTP/status error handling for non-GitHub providers. Map merge conflicts and method-not-allowed responses to 409 with sync, and forward other relevant 4xx statuses where appropriate.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (4e48478)

No Medium, High, or Critical issues found.

All review outputs are clean.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (940615d)

No Medium, High, or Critical issues found across the reviews.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (8a29033)

No Medium, High, or Critical findings were reported.

All review agents found no actionable issues to include.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (bb46abc)

No Medium, High, or Critical findings were reported.

All agents that provided review content found the code clean for reportable issues.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)