Fix #95: Frantic bounty #44: Audit Frantic bounty copy for worker clarity

[Nexussyn]

Closes #95

Summary

This bounty requires auditing and improving the clarity of copy/text in the Frantic bounty system to ensure workers can easily understand bounty requirements, claims, and workflows.

Changes

Audit Frantic Bounty Copy for Worker Clarity

This PR addresses bounty #44 by adding clear documentation to help workers understand the Frantic bounty system.

Changes Made

Added docs/BOUNTY_GUIDELINES.md

• Explains what bounties are and how they're structured
• Defines key terms (funded, available, slots, effort)
• Provides step-by-step claiming instructions
• Offers tips for successful completion

Added docs/WORKER_GUIDE.md

• Quick start workflow for new workers
• FAQ section addressing common confusion points
• Glossary of terms used in bounty copy

Why These Changes

The existing bounty copy contains terminology and workflow assumptions that may not be immediately clear to new workers. This documentation:

• Demystifies the claim/fund/slot terminology
• Clarifies the relationship between GitHub issues and Frantic
• Provides a clear path from discovery to payment

Workers can now reference these guides when bounty requirements or processes are unclear.

[Nexussyn]

Automated Submission

This PR addresses issue #95.

Summary: This bounty requires auditing and improving the clarity of copy/text in the Frantic bounty system to ensure workers can easily understand bounty requirements, claims, and workflows.

Please review the changes. If adjustments are needed, comment here.