test(web): gitea issue creation — wire api coverage, module docs, section comment

The Gitea create-issue path (server route, client, wire api, facade, UI
button/dialog) landed with the forge user-lookup work; close the remaining
verification/documentation gaps:

- wire: gitea.test.ts covers issueCreate (POST /api/gitea/issues/create,
  full/optional body, error throw)
- docs: DOCUMENTATION.md lists createIssue client method and the
  POST /repos/{owner}/{repo}/issues endpoint (labels as names)
- ui: fix stale 'read-only by design' JSDoc in GiteaIssuesSection — creation
  is offered here and the detail view provides edit/close/reopen

packages/ui/src/components/views/git/GiteaIssuesSection.tsx

@@ -18,7 +18,9 @@ const issueLabelBadgeClass =
  * Open Gitea issues for the context panel's PR view. The list is fetched
  * lazily (the parent only mounts this component while the Issues tab is
  * active); selecting a row mounts the shared `ForgeEntityDetailView` for the
- * issue detail. Read-only by design — no create, update, or close actions.
+ * issue detail. Issue creation is supported here via the "new issue" button
+ * and `ForgeCreateIssueDialog`; the detail view also offers edit, close/reopen,
+ * comments, and metadata editing through the Gitea provider's write methods.
  */
 export const GiteaIssuesSection: React.FC<{ directory: string }> = ({ directory }) => {
   const { t } = useI18n();