[muqsitnawaz]

Release commit for v0.32.0, as eb2cc9d did for v0.30.0: __version__ 0.32.0, the Unreleased CHANGELOG entry (#75) dated, README and install.sh pinned to v0.32.0 with EXPECTED_SHA256 = sha256 of linear at this commit (7f64f3754a970326c6186649de64f2093af45ab468fa1da3de34f26307af71c2). After merge the merge commit is tagged v0.32.0 and released, so the installer's pin resolves.

Why now: AGI EXT 0.9.406 reads tickets with linear tasks --project <id>. With v0.31.0 a project id Linear no longer has lists an empty project silently (seen on a fleet laptop: exit 0, no issues). v0.32.0 makes it an error.

Run:

$ python3 -m unittest test_linear
Ran 284 tests in 2.915s
OK (skipped=4)
$ ./linear --version
linear-cli 0.32.0

🤖 Generated with Claude Code

[muqsitnawaz]

Verdict: APPROVE

No BLOCKING or NON-BLOCKING findings.

Verified:

• install.sh:11 EXPECTED_SHA256 (7f64f375...71c2) equals shasum -a 256 linear on the branch.
• The branch is one commit (392ea90) on top of origin/main (58c24e2); merge-base equals origin/main. A rebase-merge is a fast-forward, so the linear blob at the v0.32.0 tag will be byte-identical. Cross-check: origin/main's linear with only the version string changed hashes to the same sha. install.sh:30-57 compares the download of <tag>/linear against that sha and fails closed.
• linear:76 __version__ = "0.32.0"; install.sh:9 and README.md:33,39 pinned to v0.32.0. No other 0.31/0.30 strings in skill.md or test_linear.py.
• CHANGELOG.md:10 dates 0.32.0 as 2026-10-17 with an empty Unreleased above it. git log v0.31.0..origin/main shows only a031dd8 and 58c24e2, both covered by the single Fixed entry.
• python3 -m unittest test_linear: Ran 284 tests, OK (skipped=4).
• No v0.32.0 tag exists yet; it must be cut on the merge commit.
• Shape matches eb2cc9d.