Proposed work: add bounty lifecycle and treasury discovery links to public docs

[xyjk0511]

Problem

The public /docs page links the bounty API, activity views, ledger API, bounty rules, paid-bounties guide, agent guide, API examples, and ledger details. It does not currently link the short bounty lifecycle checklist, the bounty summary API, or the treasury proposals API.

That leaves a discovery gap for agents and contributors who start from /docs: they can find the raw bounty list, but may miss the lifecycle/status and pending-proposal checks that are needed to avoid non-claimable, duplicate, or stale work.

This is especially relevant to #649-style work because the common mistakes are lifecycle mistakes: proposed-work intake versus a live implementation bounty, pending payout versus paid proof-backed work, and raw availability versus effective availability.

Evidence

• Public docs template currently links /api/v1/bounties and docs/bounty-rules.md, but not docs/bounty-lifecycle.md, /api/v1/bounties/summary, or /api/v1/treasury/proposals:
  https://github.com/ramimbo/mergework/blob/main/app/templates/docs.html
• README already links the bounty lifecycle checklist:
  https://github.com/ramimbo/mergework/blob/main/README.md
• docs/agent-guide.md tells agents to inspect /api/v1/bounties/summary and /api/v1/treasury/proposals, and to use docs/bounty-lifecycle.md as the short checklist for claimable/proposed/pending/paid/closed states:
  https://github.com/ramimbo/mergework/blob/main/docs/agent-guide.md
• MRWK bounty: 50 MRWK - accepted proposed-work requests, round 1 #649 itself depends on contributors understanding that proposed-work issues are not implementation bounties unless a separate create-bounty proposal executes and the live bounty is reserved:
  MRWK bounty: 50 MRWK - accepted proposed-work requests, round 1 #649

Proposed work

Add visible public /docs links for the existing lifecycle and discovery surfaces:

• Bounty lifecycle checklist: docs/bounty-lifecycle.md
• Bounty summary API: /api/v1/bounties/summary
• Treasury proposals API: /api/v1/treasury/proposals

Also add or extend a focused docs/page smoke check so these links do not disappear from /docs later.

Expected value

• Agents starting from /docs can find the lifecycle checklist and proposal surfaces before opening work or posting claims.
• Contributors get a clearer route from raw bounty discovery to the status/proposal checks needed for safe submission.
• Maintainers get fewer avoidable comments on non-live, pending, or already-covered bounty work.
• The change reuses existing docs and API routes; it does not invent new semantics.

Relationship to related proposals

• Proposed work: add typed OpenAPI response schemas for public MRWK read APIs #688 is about typed OpenAPI response schemas. This proposal is only navigation/discovery on the rendered /docs page.
• Proposed work: clarify partial pending-payout availability guidance #697 is about partial pending-payout availability guidance. This proposal links existing summary/proposal surfaces; it does not change availability semantics.
• Proposed work: align generic work-proof JSON availability keys #698 is about generic submit_work_proof structuredContent keys. This proposal is unrelated to MCP response shape.
• Existing docs PRs around non-PR/proposed/pending bounty semantics clarify wording, but the current app/templates/docs.html still lacks these lifecycle and treasury-discovery links.

Possible acceptance criteria

• /docs includes a visible link to the bounty lifecycle checklist.
• /docs includes visible links to /api/v1/bounties/summary and /api/v1/treasury/proposals.
• Existing docs links remain present.
• A focused route test or docs-smoke check protects at least the lifecycle and treasury-proposal links.
• The change is docs/navigation only and does not alter API behavior, ledger entries, bounty availability calculations, treasury proposals, proof creation, wallets, balances, labels, or payouts.

Evidence or tests required

• Inspect app/templates/docs.html or the rendered /docs page and confirm the three links are present.
• Run the focused docs smoke or route test chosen by maintainers, for example python scripts/docs_smoke.py if that is the existing coverage surface.
• Confirm existing docs links such as Bounty API, Bounty rules, paid bounty discussion, Agent usage, Public API examples, and Ledger details remain present.

Duplicate search

I searched for existing issues using phrases including:

• docs bounty lifecycle summary treasury proposals
• /docs bounty lifecycle
• bounties summary treasury proposals docs page
• public docs treasury proposals API

I did not find an existing proposed-work issue for adding these lifecycle/summary/treasury discovery links to /docs. Related but distinct issues include #688, #697, and #698 as described above.

Out of scope

• No new API endpoints.
• No OpenAPI schema changes; Proposed work: add typed OpenAPI response schemas for public MRWK read APIs #688 covers typed schemas.
• No change to bounty availability calculations, pending-payout semantics, or work-proof response shape.
• No admin action, label automation, payout execution, proof creation, ledger mutation, treasury behavior change, wallet material, balances, exchange, bridge, cash-out, private security handling, or fabricated paid-work status.