Repository navigation
Reorganize and optimize the repo for AI reference - #3
Conversation
…es, add compact/shard/domain AI views, clean entry docs
…check backfill, related graph, expanded purposes
|
Enhancement packs A–C are folded into this PR (4 additional commits): Pack A — freshness. New Pack B — alternatives graph. New Pack C — thin entries. 100 short purpose lines expanded with a fit/constraint clause, propagated to the category and catalog pages. The remaining 119 obscure entries were left as-is rather than padded with guesses. The 4 cross-listed URLs (Catch2, google/benchmark, Tracy, WAMR) were verified as already grouped by project_id — project-groups.json covers non-GitHub endpoints only, so no change was needed. Adds Validation after all packs: |
Reorganizes the repository so an AI assistant can use it as a reference without ingesting fake data or the whole 2.3 MB catalog.
Validation: python scripts/validate.py passes (2,202 records, 97 categories), unit tests 5/5, and no placeholder URLs remain outside archive/.