fix: CI test failures for TypeScript and Python jobs

[anandgupta42]

Summary

• TypeScript tests: Test fixture was writing config to opencode.json but the config loader (after the rename) only looks for altimate-code.json. Updated the fixture to write to the correct filename.
• Python tests: pytest: command not found because pyproject.toml had no dev optional dependency group. Added dev = ["pytest>=7.0", "ruff>=0.1"] so pip install -e ".[dev]" works.

Test plan

• bun test test/permission-task.test.ts — all 21 tests pass locally
• CI should pass after merge

🤖 Generated with Claude Code

[sentry]

Bug: The writeConfig() test helper defaults to the old opencode.json filename, causing tests to run with an empty configuration instead of the intended one.
_{Severity: MEDIUM}

Suggested Fix

Update the default name parameter in the writeConfig() helper function located in packages/altimate-code/test/config/config.test.ts from "opencode.json" to "altimate-code.json". Review call sites of this helper to ensure they use the correct configuration file.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/altimate-code/test/fixture/fixture.ts#L27-L32

Potential issue: The configuration filename was updated from `opencode.json` to
`altimate-code.json`. However, a test helper function, `writeConfig()` in
`config.test.ts`, still defaults to writing to the old `opencode.json` filename. The
configuration loader no longer searches for this old filename and will silently return
an empty configuration object when it's not found. Consequently, tests that rely on this
helper function without specifying the new filename will run with an empty
configuration, potentially masking bugs in configuration-dependent logic and allowing
tests to pass when they should be failing.

_{Did we get this right? 👍 / 👎 to inform future reviews.}