Test against a wide variety of repositories

[andrew]

Need to do some fuzz testing against many different repos with different kinds of:

• package manifests/lockfiles
• numbers of dependencies
• numbers of commits
• numbers of branches

[andrew]

Successful Repos (8/13)

Repository	Type	Ecosystem	Commits	With Deps	Init Time	DB Size
sinatra/sinatra	library	rubygems	4,666	300	2.7s	1.7MB
jekyll/jekyll	library	rubygems	11,857	371	5.2s	3.6MB
fastify/fastify	library	npm	4,594	645	3.8s	2.5MB
pallets/flask	library	pypi	5,474	240	3.9s	1.9MB
psf/requests	library	pypi	6,379	130	2.5s	1.9MB
gin-gonic/gin	library	go	1,945	179	2.0s	1.2MB
mastodon/mastodon	web app	rubygems+npm	20,195	5,346	238s	105MB
discourse/discourse	web app	rubygems	48,000*	3,619	~8min	70MB

*Discourse stopped at 48k of 62k commits - possible memory issue

Failed Repos (5/13)

All show Command 'init' not yet implemented error mid-processing:

Repository	Type	Ecosystem	Commits Processed
expressjs/express	library	npm	~5,500/6,105
serde-rs/serde	library	cargo	~100/4,338
tokio-rs/tokio	library	cargo workspace	~450/4,352
babel/babel	library	npm workspaces	~9,000/18,292
forem/forem	web app	rubygems+npm	~850/14,165

Bugs Found

1. Spurious "Command 'init' not yet implemented" error - appears mid-processing for certain repos (cargo, npm workspaces, some mixed ecosystems). Needs investigation.
2. Discourse stops at ~48k commits - might be memory related or hitting some internal limit.
3. Benchmark scripts use outdated API - bin/benchmark full fails with missing keyword: :ecosystem error.

Performance

• Libraries: 1,000-2,500 commits/sec
• Large web apps: 85-500 commits/sec (more dependency-changing commits)
• Mastodon has 26% dep-changing commits vs typical 3-6%

[andrew]

Fixed the "Spurious "Command 'init' not yet implemented" error -" bug