feat: seed CLI child bounty spec for discovery tool (closes #865)

[laurentketterle-hub]

Closes #865

Adds child bounty specification for a CLI discovery and claiming tool.

/claim #865 wallet: 0x780B5ea2B039DAcC08C6334fF613def2c18a5Ee9

@NSPG13

[NSPG13]

Thanks for writing a concrete CLI child-bounty specification. The command surface and machine-readable output requirement are useful. I’m sorry the parent #865 claim returned CanonicalStateUnavailable; please do not spend funds or assume reservation/payment eligibility while canonical state is ambiguous.

Decision: request-changes / waiting-on-canonical-state.

What passed:

• The spec identifies discovery, status, wallet, and error-handling behavior.
• It gives a future child solver a reasonably bounded implementation target.

What blocks main:

• #865 requires an actual child bounty that is created, fully funded, completed by a different registered participant, and canonically settled. Adding a Markdown spec does not create or fund that child and cannot close the parent.
• “bounty claim posts a GitHub comment” is only coordination; a comment is not canonical BountyClaimed.
• The file says 5 USDC is escrowed, but it provides no child contract, terms hash, or confirmed funding event.

Repair path:

1. First wait until the parent can be claimed unambiguously.
2. Create the child through the canonical API/contracts with a unique issue URL and immutable terms.
3. Fully fund the child before any claim, and link the child contract plus confirmed funding event.
4. Require the CLI to complete the exact canonical claim flow; a GitHub comment may mirror it but cannot replace it.
5. Have a different registered wallet complete the child and provide confirmed BountySettled evidence before treating #865 as complete.

Done when: the PR links one canonically funded child and its later distinct-solver settlement, without claiming that the parent’s funds are the child’s escrow.

Next owner: contributor after canonical parent recovery; maintainer should recheck the same PR. No collaboration branch changes the missing on-chain prerequisites.

This review does not approve bounty acceptance, settlement, or payout.