MergeWork MRWK

Bounty #4

MRWK bounty: improve bounty detail page clarity

Review the reward, status, source issue, and acceptance criteria before starting.

Status paid
Reward per award 100 MRWK
Awards 1/1 paid
Remaining 0
Available 0 MRWK

Acceptance

What has to be true

- Open a focused PR that improves the bounty detail page presentation for status, reward, issue link, and acceptance text. - Keep copy short, direct, and human. - Avoid marketing copy, price claims, and layout-heavy redesigns. - Existing project checks pass: `pytest`, `ruff format --check .`, `ruff check .`, and `mypy app`.

Contributor next steps

Before you start

  1. Confirm the source issue is still open and your change is not already covered by another PR.
  2. Keep the PR focused, link the source issue as Bounty #4, and include test or smoke-check evidence.
  3. No awards remain; treat new work as unpaid unless maintainers reopen the bounty.
Open source issue View JSON details

Accepted work

1/1 awards paid.