Fix Homebrew formula and auto-update on release

[rursache]

Summary

Updates Formula/polymarket.rb from the placeholder template (v0.1.0 + REPLACE_WITH_SHA256) to v0.1.4 with verified checksums so brew install polymarket works immediately.

The release workflow auto-update added in bc7349d will keep it current going forward, but the formula needs this one-time fix to point at a real release.

Fixes #7
Fixes #2

Changes

File	Change
Formula/polymarket.rb	Version → 0.1.4, real SHA256 values for all 4 targets

Test plan

• brew tap Polymarket/polymarket-cli https://github.com/Polymarket/polymarket-cli && brew install polymarket installs v0.1.4 successfully

---

Note

Medium Risk
Auto-pushing formula changes from CI adds some repo-integrity risk if the workflow or checksum fetch fails/misbehaves, though the change is localized to release automation and packaging metadata.

Overview
Updates the Homebrew formula Formula/polymarket.rb to point at CLI v0.1.4 and replaces the placeholder REPLACE_WITH_SHA256 values with real checksums for macOS (x86_64/arm64) and Linux (x86_64/arm64) tarballs.

Extends the GitHub Actions release workflow to auto-update the formula on each tagged release by generating checksums.txt, running scripts/update-formula.sh to rewrite the formula with the new version/hashes, and committing the result back to main.

^{Written by Cursor Bugbot for commit 9a2b8d2. This will update automatically on new commits. Configure here.}

[trystanmortimer]

Tested this branch locally on Linux x86_64 and the Homebrew fix works ✅

What I ran:

1. Checked out pr-8-test (9a2b8d2)
2. Copied Formula/polymarket.rb into a fresh local tap
3. brew install maeve/test-polymarket/polymarket

Results:

• Install succeeded (no missing asset / 404)
• Homebrew metadata shows stable=0.1.4 and installed=0.1.4
• Binary runs (polymarket markets list --limit 1 works)

One small follow-up I noticed (not blocking this PR):

• polymarket --version still prints 0.1.0 even when installing the v0.1.4 artifact. Might be worth aligning the CLI-reported version with release tags in a separate PR so users don’t get confused after install.

[rursache]

@trystanmortimer version reporting is fixed in #11

[suhailkakar]

ty for the pr! merged