feat(gastown): Contributing guide with bounty program — curated issues with Kilo credit rewards

[jrf0110]

Summary

Create a public-facing contributing guide for Gastown that includes a bounty program. Specific issues can be tagged as bounty-eligible with a stated Kilo credit reward. When a contributor's PR is merged for a bounty issue, they receive the credits.

Requirements

Contributing Guide

• CONTRIBUTING.md in the cloud repo (or a dedicated docs/gastown/contributing.md) covering:
  • How Gastown is architected (high-level: TownDO, reconciler, container, agents)
  • How to set up a local dev environment
  • How to run tests (vitest, integration tests)
  • PR conventions (commit format, PR template, CI checks)
  • Where to find bounty issues

Bounty Program

Credit values for the bounty are subject to change. These are just starting points.

• New label: bounty — applied to curated issues that are eligible for Kilo credit rewards
• New label format for credit amount: bounty:10, bounty:50, bounty:100, etc. (or a custom field on the GitHub Project)
• Bounty issues should have a clear, self-contained scope — a contributor should be able to pick one up without deep Gastown context
• Each bounty issue includes a "Bounty" section in the body:

  ## Bounty
  
  This issue is eligible for a **100 Kilo credit** bounty.
  Credits are awarded upon successful merge of a PR that fully addresses
  the acceptance criteria. Partial work may receive partial credit at
  maintainer discretion.
  

• A public-facing bounty board — either:
  • A filtered GitHub Projects view (label:bounty, grouped by credit amount)
  • A page on kilo.ai/bounties or kilo.ai/gastown/bounties that pulls from the GitHub API
  • Or simply a link in the contributing guide to https://github.com/Kilo-Org/cloud/labels/bounty

Credit Fulfillment

• Process for awarding credits after merge:
  • Maintainer reviews and merges the PR
  • Maintainer adds a comment: /award-bounty @contributor (or manual process initially)
  • Credits are applied to the contributor's Kilo account
  • If the contributor doesn't have a Kilo account, the merge comment includes a signup link with a redemption code
• Track awarded bounties (a simple table in a doc or spreadsheet is fine for v1)

Issue Curation

Not every issue should be a bounty. Good bounty candidates:

• Well-scoped bug fixes with clear reproduction steps
• UI polish tasks with visual before/after specs
• Documentation improvements
• Test coverage gaps
• Performance improvements with measurable targets

Bad bounty candidates:

• Architectural changes that require deep system knowledge
• Security-sensitive work
• Features that are still in design flux

Acceptance Criteria

• Contributing guide exists and is linked from the repo README
• bounty label created with credit amount variants
• At least 5 initial issues curated and tagged as bounties
• Each bounty issue has a Bounty section with credit amount and terms
• Bounty board is publicly accessible (filtered view or dedicated page)
• Credit fulfillment process documented (even if manual for v1)

References

• Kilo Credits — existing credit system
• [Gastown] PR 25: Documentation & API Reference #231 — Documentation and API reference (related but broader scope)

[zhaog100]

/attempt

[zhaog100]

/attempt

[zhaog100]

Hi! I'd like to work on this bounty.

My Plan:

• Analyze the requirements
• Implement the solution
• Submit PR within 24-48 hours

Payment Address:

• Platform: OKX
• Token: USDT (TRC20)
• Address: TGu4W5T6q4KvLAbmXmZSRpUBNRCxr2aFTP

Let's get this done! 🚀

[zhaog100]

Hi! I'd like to work on this bounty.

My Plan:

• Analyze the requirements
• Implement the solution
• Submit PR within 24-48 hours

Payment Address:

• Platform: OKX
• Token: USDT (TRC20)
• Address: TGu4W5T6q4KvLAbmXmZSRpUBNRCxr2aFTP

Let's get this done! 🚀