7 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Opus 4.8	4c1f36f9eb	chore(rename): module gitea.d-ma.be → git.d-ma.be/mathias/gitea-mcp (#39) ... Gitea host renamed (infra ADR-0004); the mcp-chassis dep already migrated (3329ff3), so the sequencing gate is clear. `go mod edit -module` + bulk import rewrite across all .go files. gitea-mcp is a server binary (not an imported library), so no downstream consumers break. build + task check green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-03 22:48:26 +02:00
mathiasandClaude Opus 4.8	e0bede0547	fix(tools): reject empty repo/name identifier at tool layer (#37) ... An empty required repo identifier built a trailing-empty path segment (`/api/v1/repos/{owner}/`) and leaked gitea's bare 404. parseArgs now validates, via reflection, that `repo`/`name` string args are non-empty and returns a typed ErrValidation naming the field. Optional identifiers (e.g. code_search's owner-wide fan-out `repo`) opt out with `,omitempty`. `owner` is already enforced by the allowlist check. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-03 22:47:05 +02:00
mathiasandClaude Opus 4.8	93c32edbb5	feat(tools): make repo the canonical repo-identifier arg; name now an alias (#38) ... Every caller (claude.ai connector, LLMs primed on gitea/GitHub) sends the repo identifier as `repo`, but the 33 per-repo identifier tools advertised `name`. The v0.2.8 shim aliased repo->name so it worked, yet the advertised inputSchema still said `name` — a misleading contract, with the shim load-bearing. - Flip all 33 identifier tools: schema property + required + struct field/tag from `name` to `repo`. A compliant `repo` caller now matches the struct directly; the shim is pure back-compat. - normalizeAliases is now bidirectional (name<->repo), so legacy `name` callers still resolve, and repo_create / create_project_from_template — whose `name` means "name of the NEW repo", not an existing-repo id — keep `name` and still accept `repo`. - `number`/`index` left as-is (out of scope; separate pre-existing quirk where pr_merge advertises `index` rather than `number`). - Tests: schema-canonical assertion + flipped alias round-trip (explicit `repo` wins over `name`). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-03 21:42:18 +02:00
mathiasandClaude Opus 4.8	184d5a95dd	fix(tools,gitea): alias repo/index args and reject empty path segments ... Per-repo MCP tools 404'd while owner-level tools worked (#36). Root cause was a parameter-name contract mismatch, not a routing fault: every per-repo tool declares the repo identifier as 'name' (and issue/PR index as 'number'), but every caller — the claude.ai connector, LLMs primed on gitea's own API — sends 'repo' and 'index'. The unmatched fields zero-valued the upstream path segment, producing '/api/v1/repos/{owner}//...', which gitea answers with its generic api-404 whose body points at /api/swagger. That swagger pointer is gitea boiler- plate, not a misroute — the MCP dispatch was correct all along. Two layers of defence: - parseArgs aliases repo->name and index->number (explicit canonical wins; alias key left intact so pr_merge's real 'index' field is unaffected). Kills the recurrence by accepting the idiomatic argument names. - the gitea client rejects any path with an empty segment before the HTTP call, returning ErrValidation instead of forwarding a malformed path and surfacing gitea's opaque swagger-404. Kills the silent-misleading-error class. Closes #36 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-10 10:16:33 +02:00
mathias	c345025221	fix(lint): staticcheck S1030, QF1002 and remove unused _ctx stub	2026-05-05 09:02:39 +02:00
mathias	1f9934349b	chore(tools): centralize pagination cap helper	2026-05-04 23:06:38 +02:00
Mathias Bergqvist	18eadc0ae9	feat(tools): tool interface + helpers	2026-05-04 21:27:50 +02:00