Bug: muse hub proposal merge fails with API 422 — limit=200 exceeds server max of 100

Summary

muse hub proposal merge fails with a 422 validation error regardless of merge strategy. The merge endpoint is internally making a list/pagination request with limit=200, which exceeds the server's maximum of 100.

Steps to reproduce

muse hub proposal merge sha256:<any-valid-proposal-id> --strategy squash
# also fails with --strategy merge_commit and --strategy rebase

Error

❌ MuseHub API error 422: [{'type': 'less_than_equal', 'loc': ['limit'], 'msg': 'Input should be less than or equal to 100', 'input': 200, 'ctx': {'le': 100}}]

Environment

• muse version: 0.2.0rc7
• repo: aaronrene/knowtation (public, 634+ files)
• proposal: sha256:7eabc33fd0dff23f2e78769b167b29de18dbd230cac3972527c98129e95bc596
• all three strategies fail identically

Root cause hypothesis

The merge endpoint internally calls a list API (possibly to walk commits or files in the snapshot) with a hard-coded or default limit=200. The server-side Pydantic model caps limit at 100. The fix is either to lower the client-side default to ≤100 or to raise the server-side cap.

Impact

Proposal merges are completely blocked via CLI. This is a blocker for any team using the MuseHub-first workflow — proposals can be created and reviewed but not merged.

Workaround

None available via CLI. Merging must be done through the MuseHub UI if a merge button is available there, or by bypassing proposals and committing directly to main (which defeats the proposal workflow).