You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: periodic maintenance — deps update and spec sync (#83)
## What
Periodic maintenance per `specs/maintenance.md` checklist.
## Why
Keep dependencies current and specs aligned with code.
## How
- `cargo update` to bump minor/patch deps (aws-lc-sys, cc, cmake,
iri-string, jni-sys, mio, simd-adler32)
- Sync `specs/initial.md`: MCP tool name (`web_fetch` not `fetchkit`),
updated description and input schema to match implementation
- Sync `specs/fetchers.md`: document all 13 built-in fetchers (was 3),
update module structure and response format values
## Risk
- Low
- Dependency updates are minor/patch only; spec changes are
documentation-only
### Checklist
- [x] Unit tests are passed
- [x] Smoke tests are passed
- [x] Documentation is updated
- [x] Specs are up to date and not in conflict
- [x] All 8 maintenance sections reviewed
- Behavior: Fetches raw source files via GitHub API, detects language from extension, handles base64 decoding, returns metadata for files >1MB or binary
77
+
- Response format field: `"github_file"`
78
+
79
+
#### GitHubIssueFetcher
80
+
81
+
- Matches: `https://github.com/{owner}/{repo}/issues/{number}` and `https://github.com/{owner}/{repo}/pull/{number}`
82
+
- Excludes: Reserved owner paths, non-numeric IDs
83
+
- Behavior: Fetches issue/PR metadata, labels, assignees, milestone, and up to 100 comments; PRs include diff stats and merge status
84
+
- Response format field: `"github_issue"` or `"github_pull_request"`
0 commit comments