Skip to content

Docs: complete agent-readable bounty template#558

Open
xingxi0614-cpu wants to merge 2 commits into
ramimbo:mainfrom
xingxi0614-cpu:codex/b456-agent-bounty-template-complete
Open

Docs: complete agent-readable bounty template#558
xingxi0614-cpu wants to merge 2 commits into
ramimbo:mainfrom
xingxi0614-cpu:codex/b456-agent-bounty-template-complete

Conversation

@xingxi0614-cpu
Copy link
Copy Markdown

@xingxi0614-cpu xingxi0614-cpu commented May 28, 2026

Refs #456

Summary

  • add a canonical agent-readable MRWK bounty post template to the bounty rules
  • update the GitHub bounty issue form so amount, evidence/tests, out-of-scope, duplicate, and stale-work rules are explicit required fields
  • expand the admin runbook posting checklist and protect the new template shape with docs smoke checks

Evidence

Compared this change against the current repository surfaces named in the bounty:

  • docs/bounty-rules.md: existing submission evidence templates and payout wording
  • docs/admin-runbook.md: maintainer bounty posting and acceptance flow
  • .github/ISSUE_TEMPLATE/bounty.yml: current issue form fields
  • scripts/docs_smoke.py: existing public documentation checks
  • public API/MCP bounty fields documented in project docs: title, issue URL, reward_mrwk, max_awards, awards_remaining, labels, and public comments

This version keeps the template copy-pasteable and uses stable headings:

  • ## MRWK Bounty
  • ## Work Needed
  • ## Acceptance Criteria
  • ## How To Submit
  • ## Evidence or Tests Required
  • ## Out of Scope
  • ## Duplicate and Stale Work Rules

After reviewer feedback, the current head also verifies that evidence, out_of_scope, and duplicate_stale_rules are all individually required fields.

Test Evidence

  • python scripts/docs_smoke.py -> docs smoke ok
  • python -m pytest tests/test_docs_public_urls.py tests/test_check_agents.py -q -> 26 passed
  • python -m ruff check scripts/docs_smoke.py tests/test_docs_public_urls.py -> All checks passed!
  • python -m ruff format --check scripts/docs_smoke.py tests/test_docs_public_urls.py -> 2 files already formatted
  • git diff --check -> clean

Out of Scope

  • no tokenomics, price, liquidity, exchange, bridge, cash-out, payout, wallet, or private-security-detail changes
  • no broad rewrite of bounty rules, ledger behavior, or payout logic

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 28, 2026

📝 Walkthrough

Walkthrough

Adds an agent-readable bounty template to docs, implements it as a GitHub issue template, updates admin runbook guidance, and enforces the shape via docs smoke validations and unit tests.

Changes

Bounty Template Standardization

Layer / File(s) Summary
Agent-readable bounty post template specification
docs/bounty-rules.md
Agent-Readable Bounty Post Template section specifies stable headings and structured fields (MRWK bounty title/body, acceptance criteria, submission, evidence/tests, out-of-scope, duplicate/stale rules) for consistent machine extraction.
Bounty issue template implementation
.github/ISSUE_TEMPLATE/bounty.yml
Template updated to standardized shape with markdown guidance block referencing docs/bounty-rules.md; three new required textarea sections added (evidence, out_of_scope, duplicate_stale_rules) with structured placeholders.
Admin runbook update
docs/admin-runbook.md
Refined Post a Bounty steps to require the agent-readable template, specify required title/body formatting (including reward and max_awards), acceptance criteria, and explicit out-of-scope/duplicate/stale/public-artifact cautions.
Docs smoke validation and CLI checks
scripts/docs_smoke.py
Extended required public phrases for docs/bounty-rules.md; added _template_field_block() and _template_field_is_required(); main() now verifies .github/ISSUE_TEMPLATE/bounty.yml exists, contains required field ids/phrases, and marks those fields required.
Unit tests for template validation
tests/test_docs_public_urls.py
Imports _template_field_is_required and adds a test asserting evidence, out_of_scope, and duplicate_stale_rules are required and checking required/optional behavior via template text substitutions.

Possibly related issues

Possibly related PRs

  • ramimbo/mergework#433: Related changes to docs/bounty-rules.md and scripts/docs_smoke.py for template/wording validation.
  • ramimbo/mergework#392: Related changes adding template-content smoke checks in scripts/docs_smoke.py.
🚥 Pre-merge checks | ✅ 6
✅ Passed checks (6 passed)
Check name Status Explanation
Title check ✅ Passed Title directly names the main changed surface (agent-readable bounty template docs) and accurately reflects the core change across bounty-rules.md, admin-runbook.md, issue template, and validation scripts.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Mergework Public Artifact Hygiene ✅ Passed PR strengthens hygiene by instructing authors to exclude price, investment, and cash-out claims. MRWK described as native coin with work-based tiers. No new problematic claims introduced.
Bounty Pr Focus ✅ Passed PR diff matches all 5 stated files, includes test evidence, avoids unrelated scope—no production code changes beyond validation only.
Description check ✅ Passed PR description covers all required template sections with concrete evidence and test results.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@Baijack-star Baijack-star left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed PR #558 at current head 154a4648efafff52304290bbc22c6ccd7bf07674 for the #456 agent-readable bounty template docs/form slice.

I do not see a docs/test blocker in the current diff. The PR adds a copy-pasteable stable-heading template in docs/bounty-rules.md, updates the maintainer runbook to require the title/reward/max-awards/body shape, makes evidence, out_of_scope, and duplicate/stale rules required in .github/ISSUE_TEMPLATE/bounty.yml, and adds docs-smoke coverage for the new template and issue-form fields.

Evidence checked:

  • inspected .github/ISSUE_TEMPLATE/bounty.yml, docs/admin-runbook.md, docs/bounty-rules.md, and scripts/docs_smoke.py;
  • compared the scope against #456 acceptance criteria: title format, reward/max-awards repetition, stable headings, evidence/out-of-scope/duplicate/stale fields, API/MCP/GitHub parsing rationale, and public-artifact cautions are present;
  • compared against already-open #469 and #499: this is the same bounty surface, so maintainers should merge/pay at most one winner, but #558 is a coherent implementation and protects more of the template shape than #499 by including docs-smoke checks.

Validation run locally on this head:

  • PYTHONPATH=. PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /Users/apple/Documents/paid-demand-goal-reset/mergework-review/.venv/bin/python scripts/docs_smoke.py -> docs smoke ok
  • PYTHONPATH=. PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /Users/apple/Documents/paid-demand-goal-reset/mergework-review/.venv/bin/python -m pytest tests/test_docs_public_urls.py tests/test_check_agents.py -q -> 25 passed
  • PYTHONPATH=. PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /Users/apple/Documents/paid-demand-goal-reset/mergework-review/.venv/bin/python -m pytest -q -> 414 passed
  • /Users/apple/Documents/paid-demand-goal-reset/mergework-review/.venv/bin/python -m ruff check . -> passed
  • /Users/apple/Documents/paid-demand-goal-reset/mergework-review/.venv/bin/python -m ruff format --check . -> 79 files already formatted
  • PYTHONPATH=. PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /Users/apple/Documents/paid-demand-goal-reset/mergework-review/.venv/bin/python -m mypy app -> success
  • git diff --check origin/main...HEAD -> clean

GitHub Quality/readiness/docs/image checks are successful on the same head. CodeRabbit was still pending when I posted this, so this review is scoped to the repository diff, local validation, and current GitHub CI state.

Copy link
Copy Markdown

@Baijack-star Baijack-star left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requesting changes for a narrow docs-smoke coverage gap.

The docs/form content itself is mostly aligned with #456, but scripts/docs_smoke.py does not actually protect all of the required issue-form fields that this PR adds and that #456 asks agents to rely on. It checks that id: evidence, id: out_of_scope, and id: duplicate_stale_rules exist, then only verifies that the out_of_scope block contains required: true. The new evidence and duplicate_stale_rules fields could be changed back to optional while docs smoke still prints docs smoke ok.

Concrete reproduction on head 154a4648efafff52304290bbc22c6ccd7bf07674:

  • changed only .github/ISSUE_TEMPLATE/bounty.yml so id: evidence has required: false;
  • changed only .github/ISSUE_TEMPLATE/bounty.yml so id: duplicate_stale_rules has required: false;
  • ran PYTHONPATH=. PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /Users/apple/Documents/paid-demand-goal-reset/mergework-review/.venv/bin/python scripts/docs_smoke.py;
  • result: docs smoke ok.

That leaves the promised regression guard weaker than the PR summary and the bounty acceptance criteria. Please extend the docs smoke check to assert required: true inside the evidence, out_of_scope, and duplicate_stale_rules field blocks, or add an equivalent focused test that fails when any of those concrete required fields become optional.

Baseline validation on the unmodified PR head still passes:

  • PYTHONPATH=. PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /Users/apple/Documents/paid-demand-goal-reset/mergework-review/.venv/bin/python scripts/docs_smoke.py -> docs smoke ok
  • PYTHONPATH=. PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 /Users/apple/Documents/paid-demand-goal-reset/mergework-review/.venv/bin/python -m pytest tests/test_docs_public_urls.py tests/test_check_agents.py -q -> 25 passed
  • git diff --check origin/main...HEAD -> clean

@tinyopsstudio
Copy link
Copy Markdown

Reviewed current PR #558 head 88f94f80e9a1706536ca568fd2504f236dc2d7f2 for the agent-readable bounty template docs/form slice.

No blocker found on this head.

Evidence checked:

  • inspected .github/ISSUE_TEMPLATE/bounty.yml, docs/admin-runbook.md, docs/bounty-rules.md, scripts/docs_smoke.py, tests/test_docs_public_urls.py, and the review thread;
  • confirmed the earlier docs-smoke coverage gap is fixed: _template_field_is_required() now checks evidence, out_of_scope, and duplicate_stale_rules individually for validations.required: true;
  • confirmed test_docs_smoke_requires_bounty_evidence_exclusion_and_duplicate_fields covers the required-field helper and negative cases;
  • confirmed the docs/template still include the stable bounty title/body shape, evidence requirements, out-of-scope rules, duplicate/stale rules, API/MCP/GitHub parsing rationale, and public artifact cautions;
  • ran python scripts/docs_smoke.py: docs smoke ok;
  • ran pytest tests/test_docs_public_urls.py tests/test_check_agents.py -q: 26 passed;
  • ran ruff check scripts/docs_smoke.py tests/test_docs_public_urls.py: all checks passed;
  • ran ruff format --check scripts/docs_smoke.py tests/test_docs_public_urls.py: 2 files already formatted.

This looks mergeable from my reviewed slice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants