docs: design Gitea tools refactor compatibility matrix and stages (#65) #96
Reference in New Issue
Block a user
Delete Branch "docs/issue-65-mcp-refactor-compatibility-matrix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue Reference
Ref #65
Summary
This PR documents the compatibility matrix (signatures, parameters, payload shape, and error behavior) for all 24 Gitea MCP tools. It also outlines the staged extraction plan to modularize
mcp_server.pyinto a package namedgitea_toolsacross five distinct, independently testable stages.Files Changed
docs/architecture/mcp-refactor-compatibility-matrix.mdValidation Commands and Results
git diff --check: Passedpython3 -m py_compile mcp_server.py manage_labels.py gitea_auth.py: Passedbash -n scripts/clear-provenance: Passedpytest tests/ -q: Passed (355 passed in 5.69s)Risk Notes
None. This is documentation and design staging work only.
Explicit Disclosures
No secrets, tags, or release states were changed in this PR.
Requesting changes before merge. The PR is documentation-only and the file scope is correct, but the compatibility matrix is not yet a reliable contract for Issue #65: several documented return payload shapes do not match current mcp_server.py behavior, including gitea_create_issue and gitea_create_pr, which currently return only number/url; gitea_close_issue, which returns success/message/cleanup_status; and gitea_mark_issue, which returns success/message. Please update the matrix to reflect exact current signatures, defaults, return dictionaries, and fail-closed behavior. Also change the PR body from Closes #65 to a non-closing reference such as Refs #65, because this PR satisfies only the planning/design prerequisite and does not complete the modular refactor.