feat: compile with mypyc and add install scripts

[kowyo]

Compile the package with mypyc for native performance and streamline installation.

Build

• Switch from uv_build to setuptools + mypyc

Type fixes

• agent.py: annotate working_status/thinking_status as Status | None
• models.py: annotate model_id as str | None at first assignment

CI

• Matrix build across ubuntu/macos/windows; ubuntu builds sdist + wheel, others wheel only
• Release job updates README install version and uploads platform-native wheels

Install scripts

• install.sh: macOS/Linux — detects arch, prefers native wheel, falls back to pure Python
• install.ps1: Windows — same logic via Invoke-RestMethod

Makefile

• Add build (uv build --wheel) and clean targets
• Scope ty check to src/ to exclude setup.py

[cubic-dev-ai]

3 issues found across 9 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="README.md">

<violation number="1" location="README.md:18">
P1: Pin the PowerShell install script URL to a release tag/commit instead of `main` before piping to `iex` to avoid executing mutable remote code.</violation>
</file>

<file name="install.sh">

<violation number="1" location="install.sh:17">
P2: `aarch64` is normalized to `arm64`, which breaks Linux ARM wheel matching (`manylinux`/`musllinux` wheels are tagged `aarch64`).</violation>

<violation number="2" location="install.sh:35">
P1: The script assumes `uv` is installed; the documented one-line installer will fail on fresh systems without a prerequisite check or guidance.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: aarch64 is normalized to arm64, which breaks Linux ARM wheel matching (manylinux/musllinux wheels are tagged aarch64).

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At install.sh, line 17:

<comment>`aarch64` is normalized to `arm64`, which breaks Linux ARM wheel matching (`manylinux`/`musllinux` wheels are tagged `aarch64`).</comment>

<file context>
@@ -0,0 +1,36 @@
+esac
+
+case "${ARCH}" in
+  arm64|aarch64) ARCH_TAG="arm64" ;;
+  x86_64)        ARCH_TAG="x86_64" ;;
+  *) echo "Unsupported architecture: ${ARCH}"; exit 1 ;;
</file context>

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional findings.

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="scripts/install.sh">

<violation number="1" location="scripts/install.sh:10">
P2: The default reply value conflicts with `[Y/n]`: pressing Enter now defaults to `n` and aborts instead of installing `uv`.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: The default reply value conflicts with [Y/n]: pressing Enter now defaults to n and aborts instead of installing uv.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At scripts/install.sh, line 10:

<comment>The default reply value conflicts with `[Y/n]`: pressing Enter now defaults to `n` and aborts instead of installing `uv`.</comment>

<file context>
@@ -7,7 +7,7 @@ API_URL="https://api.github.com/repos/${REPO}/releases/latest"
   echo "'uv' is required but not installed."
   read -r -p "Would you like to install uv now? [Y/n] " REPLY </dev/tty
-  if [[ "${REPLY:-y}" =~ ^[Yy]$ ]]; then
+  if [[ "${REPLY:-n}" =~ ^[Yy]$ ]]; then
     echo "Installing uv..."
     curl -LsSf https://astral.sh/uv/install.sh | sh
</file context>

Suggested change

	if [[ "${REPLY:-n}" =~ ^[Yy]$ ]]; then
	if [[ "${REPLY:-y}" =~ ^[Yy]$ ]]; then

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 12 additional findings in Devin Review.

[devin-ai-integration]

🔴 install.sh default reply is 'n' but prompt convention [Y/n] implies default is 'Y'

On line 10, ${REPLY:-n} sets the default to n when the user presses Enter without typing anything. However, the prompt on line 9 uses the [Y/n] convention (capital Y), which universally signals that pressing Enter should accept (i.e., default to 'Y'). As a result, a user who presses Enter expecting to proceed with installation will instead get the "Aborting" message. Compare with the PowerShell version (scripts/install.ps1:7) which correctly handles the empty-input case by checking $reply -eq "" first.

Suggested change

	if [[ "${REPLY:-n}" =~ ^[Yy]$ ]]; then
	if [[ "${REPLY:-Y}" =~ ^[Yy]$ ]]; then

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[cubic-dev-ai]

2 issues found across 2 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="scripts/install.ps1">

<violation number="1" location="scripts/install.ps1:7">
P2: This change breaks the `[Y/n]` default behavior: empty input is no longer treated as consent, so pressing Enter aborts installation unexpectedly.</violation>
</file>

<file name="scripts/install.sh">

<violation number="1" location="scripts/install.sh:39">
P2: `|| true` on the asset-fetch pipeline hides real curl/API failures and can produce a misleading "No compatible wheel found" error instead of failing at the fetch step.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 12 additional findings in Devin Review.