2 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	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