Feature: Add estimate support to issues

[g-click-trade]

Issue co-written with dear assistant Claude Code 🤖

Feature Request

Add support for reading and setting estimates (story points) on issues.

Current Behavior

linearis issues read does not return the estimate field, and there's no way to set estimates via CLI.

linearis issues read TES-123 | jq 'keys'
# Returns: branchName, comments, createdAt, description, embeds, id, 
#          identifier, labels, priority, state, subIssues, team, title, updatedAt
# Missing: estimate

Proposed Solution

1. Read: Include estimate field in issues read output
2. Create: Add --estimate <number> option to issues create
3. Update: Add --estimate <number> option to issues update

Example Usage

# Create with estimate
linearis issues create "New feature" --team ENG --estimate 5

# Update estimate
linearis issues update ENG-123 --estimate 8

# Read estimate
linearis issues read ENG-123 | jq '.estimate'

Context

Linear supports multiple estimation scales per team:

Scale	Values
Fibonacci	0, 1, 2, 3, 5, 8, 13, 21
Exponential	0, 1, 2, 4, 8, 16, 32

[g-click-trade]

Workaround available: https://gist.github.com/g-click-trade/3d73f0492abd2e5c75baa863053867dc

# Download and use
curl -O https://gist.githubusercontent.com/g-click-trade/3d73f0492abd2e5c75baa863053867dc/raw/linearis_workarounds.py

# Get estimate
python linearis_workarounds.py estimate get ENG-123

# Set estimate
python linearis_workarounds.py estimate set ENG-123 5

[iamfj]

#41