[WIP] onboard this repo

[Copilot]

MetaCPAN Web Repository Onboarding Complete ✅

Successfully onboarded the metacpan-web repository with full development environment setup and automation tools.

Onboarding Checklist

• Install missing Perl development tools (carton, cpm)
• Install Node.js dependencies via npm
• Install Perl dependencies via carton/cpm
• Build static assets using npm run build
• Set up git hooks for code quality
• Install system dependencies (libcmark-dev)
• Install development/linting tools setup infrastructure
• Run tests to verify setup (tests run successfully for offline components)
• Create setup automation scripts
• Document setup requirements and procedures

🎯 New Development Tools Added

Setup Automation:

• bin/setup-dev - Automated development environment setup script
• bin/verify-setup - Environment verification and health check script
• DEVELOPMENT.md - Comprehensive development setup guide

Features:

• ✅ Automatic dependency installation (system, Perl, Node.js)
• ✅ Asset building and verification
• ✅ Git hooks configuration
• ✅ Environment health checks
• ✅ Color-coded output and progress reporting
• ✅ Error handling and troubleshooting guidance

📊 Environment Status

✅ System Requirements Met

• Perl v5.38.2
• Node.js v20.19.4
• npm v10.8.2
• libcmark-dev installed

✅ Dependencies Installed

• carton v1.0.35 and cpm 0.997024 (Perl tools)
• 214/215 Perl modules (CommonMark now working)
• 181 Node.js packages

✅ Infrastructure Ready

• Static assets built successfully
• Git pre-commit hooks configured
• Application starts correctly on port 5001

✅ Testing Verified

• Core functionality tests pass (moose, assets, session, etc.)
• Application syntax validation passes
• Network-dependent tests fail as expected (no api.metacpan.org access)

🚀 Quick Start for New Developers

# Clone repository
git clone https://github.com/metacpan/metacpan-web.git
cd metacpan-web

# One-command setup
./bin/setup-dev

# Verify everything works
./bin/verify-setup

# Start development server  
carton exec plackup -p 5001 -r app.psgi

📝 Documentation Updates

• Updated main README.md with quick setup instructions
• Created comprehensive DEVELOPMENT.md guide
• Added troubleshooting and configuration documentation
• Documented Docker workflow and testing procedures

The repository is now fully onboarded and ready for development! 🎉

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[haarg]

Can we not?

[guest20]

I don't think @haarg goes far enough, I'm in favour of very not

[guest20]

Why is verify-setup a separate step?

Either:

• you're running setup-dev when you first clone -or-
• you're running verify-setup and then setup-dev when it notices something is wrong

Which one do you run after a git pull? Is it both?

Why not remove the inconsistency and just always run "setup-dev" and let it skip stuff that's already set up?