refactor: isolate developer-tools module in data layer

[pettinarip]

Summary

This is a proposal to refactor the developer tools data layer code for better isolation and maintainability.

Problem

The current implementation has bidirectional imports between the data layer and app code:

• src/data-layer/fetchers/fetchDeveloperTools.ts imports functions from app/[locale]/developers/apps/utils.ts
• This breaks the convention that the data layer should be isolated and not depend on app-level code

Solution

Move all developer tools fetching logic into a dedicated folder:

src/data-layer/fetchers/developer-tools/
├── index.ts           # Main orchestrator (fetchDeveloperTools)
├── utils.ts           # Types, constants, utility functions
├── fetchBuidlGuidl.ts # BuidlGuidl API fetcher
├── fetchGitHub.ts     # GitHub GraphQL enrichment
└── fetchNpmJs.ts      # npm downloads enrichment

Changes

• Moved to data layer:

  • DeveloperToolsDataEnvelope and DeveloperAppsComputedSelections types
  • DEV_APP_CATEGORY_SLUGS constant (data-only version)
  • All utility functions: seededRandom, seededShuffle, getHighlightsByCategory, etc.

• Kept in app code:

  • getCategoryTagStyle (UI-specific, uses TagProps)
  • DEV_APP_CATEGORIES (has Icon components)

• Updated imports:

  • tasks.ts imports from ./fetchers/developer-tools
  • index.ts imports types from new location
  • Helper fetchers import DeveloperApp from local utils

Benefits

1. Data layer is now fully self-contained
2. No runtime function imports from app code
3. Only type-only import of DeveloperApp remains (acceptable as shared data contract)
4. Cleaner module organization

---

🤖 Generated with Claude Code

[wackerow]

👍

thanks!