Move webhook tests to root tests/ dir and restructure to be non-flaky. Setup webhook capture server once via preload, tear down on process exit. Tests now clean up their own PRs in afterEach. Added bridge test to verify Spike PRs create Discord threads. Made Discord client login explicit via startDiscord(). Updated config with new dev Discord channel and Spike username mappings.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Split nested dev/prod config object into a Config type with separate devConfig and prodConfig objects. This makes it clearer which values apply to which environment and ensures both configs match the type.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Each test now creates its own PR and cleans up after itself. Tests no longer depend on shared state or ordering, making them resilient to failures.
Added retry logic to mergePR for Gitea's 404/405 responses while computing mergeability. Used crypto.randomUUID() for unique branch names instead of Date.now() to eliminate collision risk.
Split the monolithic gitea/helpers.ts (which had Discord imports and created circular dependencies) into three focused libs:
1. **gitea/** — Pure API client: fetchPR, fetchReviewComments, convertUsername, threadName. No side effects or external deps.
2. **discord/** — Discord client setup: bot login, event listeners, slash commands. Now isolated from Gitea internals.
3. **bridge/** — New integration layer: webhook handler, DB mappings (Gitea PR ↔ Discord thread), Discord helpers, and createPRComment.
Dependencies now flow one direction: bridge → gitea and bridge → discord. No circular imports.
Added:
- Barrel exports (index.ts) for each lib with public API
- README.md for each lib documenting the barrel exports
- Comprehensive spike README.md with setup guide and architecture explanation
- Integration tests for webhooks (callback-based, no race conditions)
- Unit tests for pure API functions
- CLAUDE.md with links to each lib's README
This architecture makes it possible for AI to understand a lib by reading just its README, keeping context focused and small.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
