MRWK bounty: 400 MRWK - read-only proposed-work intake triage report

[ramimbo]

MRWK Bounty

Status: proposed bounty. This issue is not claimable until the treasury proposal executes, the public bounty page exists, and the Reserved on MergeWork claims-open comment is posted.

Reward: 400 MRWK per accepted award
Max awards: 1

Related proposed-work intake: #672. That issue is accepted intake under #649 only; this issue is the separate implementation proposal.

Work Needed

Add a read-only proposed-work triage report for maintainers. The report should help review proposed-work issues without making acceptance, payout, or bounty-creation decisions.

The report should list proposed-work issues and, where public data supports it:

• detect missing proposed-work labels and missing template sections;
• show MRWK bounty: 50 MRWK - accepted proposed-work requests, round 1 #649 paid or pending status for accepted proposed-work intake where available;
• group likely related proposals conservatively with evidence;
• suggest possible consolidated bounty scopes;
• warn on duplicate-looking, vague, already-routed, rejected, label-missing, or non-live-confused proposals.

Acceptance Criteria

Accepted work must be a focused PR that adds a read-only report path, for example a script under scripts/, with fixture-driven behavior and no GitHub or treasury mutations.

The implementation must:

• support offline fixture input;
• optionally support a live gh read-only mode;
• produce Markdown or JSON output;
• include focused tests for complete, incomplete, duplicate-looking, routed, rejected, paid/pending, and label-missing proposed-work issues;
• document maintainer usage in docs/admin-runbook.md or the nearest existing maintainer runbook section;
• keep pending proposals separate from proof-backed paid work.

How To Submit

After this issue becomes live, open a focused PR that references this bounty issue and includes validation evidence. Do not submit implementation work before the public bounty row exists and the claims-open reserve comment is posted.

Evidence or Tests Required

• Fixture tests for labeled and unlabeled proposed-work issues.
• Fixture tests for missing template sections and vague proposals.
• Fixture tests for likely related proposal grouping with evidence.
• Fixture tests for MRWK bounty: 50 MRWK - accepted proposed-work requests, round 1 #649 pending versus proof-backed paid status where public data is available.
• Tests or monkeypatch coverage proving live mode uses only public gh reads.
• pytest for the focused tests.
• ruff check and ruff format --check for touched files.
• scripts/docs_smoke.py if docs are touched.

Out of Scope

• No automatic labels, comments, issue edits, bounty creation, claim submission, acceptance decisions, or payments.
• No admin-token APIs, production database access, private deployment state, or secret material.
• No broad rewrite of pr_queue_health.py or claim_inventory.py unless the change is a small reuse of existing helpers.
• No price, investment, exchange, liquidity, bridge, cash-out, fabricated payout, private security detail, secret, or token claims.

Duplicate And Stale Work Rules

Duplicate work is judged by the first useful, focused PR that implements the accepted report scope. Work that only reports generic issue lists, rewrites unrelated queue tooling, or treats proposed-work issues as live implementation bounties does not qualify.

[ramimbo]

Public treasury proposal created: https://api.mrwk.online/api/v1/treasury/proposals/99

Status: pending create_bounty. Earliest execution: 2026-06-01T15:09:24Z if no valid blocking challenge exists.

This issue is not claimable yet. Claims open only after proposal execution creates the public bounty row and finalizes the GitHub issue with mrwk:bounty plus the claims-open reserve comment.

[ramimbo]

Reserved on MergeWork: https://mrwk.online/bounties/100

Claims are now open for accepted work that matches this bounty's criteria.

[attaboy11]

/claim #694

PR: #767

Validation evidence:

• PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 .venv/bin/python -m pytest tests/test_proposed_work_triage.py -q -> 7 passed.
• .venv/bin/python -m ruff check scripts/proposed_work_triage.py tests/test_proposed_work_triage.py docs/admin-runbook.md -> passed.
• git diff --check origin/main...HEAD -> passed.
• git merge-tree --write-tree origin/main HEAD -> clean tree 1a6bafd579bf6db146844801b24e7894362cce51 after fetching current origin/main.
• Earlier full-suite validation on this prepared branch passed before the bounty went live: 598 passed, 1 warning.

Scope summary: read-only proposed-work intake triage report with offline fixture input, optional read-only gh live mode, Markdown/JSON output, missing-label/template checks, conservative duplicate grouping, routed/rejected/non-live-confused warnings, #649 pending-vs-proof-backed payment status handling, focused tests, and admin-runbook docs. No automatic labels/comments/issue edits, bounty creation, claim acceptance, payments, admin-token APIs, private state, secrets, or price/exchange/bridge/cash-out behavior.

[JONASXZB]

/claim #694

PR: #766

Validation evidence at current head 92fa2e283ebfc8331dfa78c0de49d8bfe0fe61be:

• .venv/bin/python -m pytest -> 634 passed, 1 warning.
• .venv/bin/python -m mypy app -> success, no issues in 38 source files.
• .venv/bin/ruff check . -> passed.
• .venv/bin/ruff format --check . -> 104 files already formatted.
• .venv/bin/python scripts/docs_smoke.py -> docs smoke ok.
• .venv/bin/python -m pytest tests/test_proposed_work_triage.py tests/test_pr_queue_health.py tests/test_claim_inventory.py -> 35 focused tests passed.

Scope summary: read-only proposed-work intake triage report with offline fixture input, optional read-only gh live mode, Markdown/JSON/text output, missing-label/template checks, conservative duplicate grouping, routed/rejected/non-live-confused warnings, public payment-state handling for pending vs proof-backed paid rows, hardened read-only GitHub command guards, focused tests, and admin-runbook docs.

No labels, comments, issue edits, bounty creation, payout execution, private/admin API calls, secrets, exchange/bridge/cash-out behavior, or mutation automation are included.

[attaboy11]

/claim #694

Correction/update for my earlier claim: please evaluate PR #763, not the superseded PR #767.

Current submission: #763
Current head: ca891839cbcc95ef20160fb90db0541beb582668

Latest follow-up in ca89183 addresses CodeRabbit's remaining detail-fetch downgrade test note:

• hoisted the live-mode FakeResponse helper to module scope;
• added test_proposed_work_triage_live_mode_warns_when_bounty_detail_fetch_fails;
• covers the path where the public bounty list fetch succeeds but a per-bounty detail request fails;
• asserts the visible payment_state_incomplete warning and Markdown data warning: output.

Final status evidence checked after the follow-up fixes:

• GitHub hosted Quality, readiness, docs, and image checks: success on head ca89183.
• CodeRabbit on ca89183: passed / review skipped; inline detail-fetch note marked addressed.
• Follow-up PR evidence comment: Add proposed-work intake triage report #763 (comment)
• CodeRabbit thread reply: Add proposed-work intake triage report #763 (comment)

Validation evidence on the current branch:

• .venv/bin/python -m pytest tests/test_proposed_work_triage.py -q -> 12 passed.
• .venv/bin/python -m pytest tests/test_proposed_work_triage.py tests/test_pr_queue_health.py tests/test_claim_inventory.py -q -> 36 passed.
• .venv/bin/python -m pytest -q -> 635 passed, 1 warning.
• .venv/bin/ruff check scripts/proposed_work_triage.py tests/test_proposed_work_triage.py -> passed.
• .venv/bin/ruff format --check scripts/proposed_work_triage.py tests/test_proposed_work_triage.py -> 2 files already formatted.
• git diff --check and git diff --check origin/main...HEAD -> passed.
• Earlier live read-only smoke on this PR series: scripts/proposed_work_triage.py --repo ramimbo/mergework --limit 3 --format json -> 3 issues, payment counts {"none": 2, "pending": 1}, data_warnings: [].

Scope summary: read-only proposed-work intake triage report with offline fixture input, optional read-only gh live mode, Markdown/JSON output, missing-label/template checks, conservative duplicate grouping, routed/rejected/non-live-confused warnings, #649 pending-vs-proof-backed payment status handling, visible incomplete-payment-state warnings for both list and detail fetch failures, focused tests, and admin-runbook docs. No automatic labels/comments/issue edits, bounty creation, claim acceptance, payments, admin-token APIs, private state, secrets, or price/exchange/bridge/cash-out behavior.

[attaboy11]

Update for my #694 claim / PR #763:

Current PR head is 5cbbb3d11dfe124d980793bfb395e540afa0c3a2. I added an explicit live-mode gh safety allowlist so the proposed-work triage helper only permits read-only gh issue list and gh issue view; mutating commands are rejected before subprocess.run.

Current validation:

• proposed-work triage tests: 13 passed
• adjacent script suites: 37 passed
• full suite: 636 passed, 1 warning
• targeted ruff check / ruff format --check: passed / already formatted
• git diff --check: passed
• live read-only smoke: 3 issues, payment counts {"none": 2, "pending": 1}, data_warnings: []
• hosted CI: passed
• CodeRabbit: success
• GitHub merge state: CLEAN

PR evidence comment: #763 (comment)