#8 · Corpus · 2026-05-10
GitHub JSON fetch layer
Status: Backlog
CorpusImplementation
- Reliable fetching of raw JSON from the configured repository (GitHub API or raw URLs—pick one approach and document it).
- Handle rate limits, failures, and user-visible errors; align with NFR “imports show progress—no silent hangs.”
- Keep secrets server-side if authenticated fetches are required later; start with assumptions documented in questions.
Questions
- Public repo only for v1, or PAT / GitHub App from day one?
- Server-side proxy vs client-direct fetches—security and CORS implications?