Document the solver bonding and registration flow end-to-end

[james2177]

Description

Once issues #52 (registration endpoint), #96 (bond enforcement), and #103 (solver bot auth) ship, there's no single doc walking a prospective solver operator through the full flow — currently scripts/README.md only covers running the demo bot against pre-seeded fake solver data.

Requirements and context

• Should cover: registering, posting bond, connecting the bot with auth, and what deactivation/slashing means for them

Suggested execution

1. Fork the repo and create a branch

   git checkout -b docs/solver-onboarding-guide
   

2. Implement changes
   Relevant files:

• docs/solver-onboarding.md
• scripts/README.md

3. Test and commit

   • Run npm run lint && npm run typecheck && npm test && npm run test:e2e
   • Include test output / screenshots or logs demonstrating the fix in the PR

   Example commit message:

   docs: document the end-to-end solver bonding and registration flow
   

Guidelines

• Assignment required before starting — comment to claim this issue
• PR description must include: Closes #[this issue's number]
• Timeframe: 96 hours from assignment
• Complexity: High (200 points)

---

Part of the Drips Wave for vortex-backend.