feat: Initial Python project setup with monorepo structure

[DamianReeves]

Summary

• Set up morphir-python as a production-ready Python 3.14+ project with monorepo structure
• Configure mise for tool management and uv for Python package management
• Create two workspace packages: morphir (core library) and morphir-tools (CLI/extensions)
• Set up strict type checking (mypy + pyright), linting (ruff), and testing (pytest + behave)
• Add GitHub Actions CI/CD workflows for continuous integration and PyPI releases
• Create documentation including AGENTS.md for code agent guidelines

Changes

Project Structure

morphir-python/
├── packages/
│   ├── morphir/           # Core library (IR models, types)
│   └── morphir-tools/     # CLI tools and extensions
├── tests/                 # Unit tests (pytest)
├── features/              # BDD tests (behave)
├── .config/mise/          # Tool configuration and tasks
└── .github/workflows/     # CI/CD pipelines

Development Tooling

• Python 3.14 with strict type annotations
• uv for fast package management with workspace support
• mise for tool acquisition and task running
• ruff for linting and formatting (Google-style docstrings)
• mypy + pyright for dual type checking in strict mode
• pytest + behave for TDD and BDD testing

Available Commands

mise run check      # Run all checks (lint, format, typecheck, tests)
mise run test       # Run pytest unit tests
mise run test-bdd   # Run behave BDD tests
mise run lint       # Run ruff linter
mise run typecheck  # Run mypy and pyright
mise run build      # Build packages

Test plan

• mise install successfully installs Python 3.14 and uv
• uv sync --all-groups installs all dependencies
• mise run lint passes (All checks passed)
• mise run format-check passes (12 files properly formatted)
• mise run typecheck passes (mypy and pyright both clean)
• mise run test passes (10 unit tests)
• mise run test-bdd passes (3 scenarios, 11 steps)
• mise run check passes (all checks combined)

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6afe20d788

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Prevent NameError from TYPE_CHECKING-only Context

These step functions annotate context with Context, but Context is only imported under if TYPE_CHECKING earlier in the file and there is no from __future__ import annotations. On Python’s default runtime annotation evaluation, that means importing this module will raise NameError: name 'Context' is not defined, so Behave will fail before any steps run. This is environment-dependent on annotation evaluation (default in 3.11/3.12); without deferring annotations or quoting the type, the BDD tests will crash at import time.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Install Python 3.14 before uv sync

The workflow runs uv sync on ubuntu-latest without installing a Python interpreter, but the workspace and both packages require >=3.14. If the runner’s default Python is below 3.14 (the usual case on ubuntu-latest), uv sync will fail because no compatible interpreter is available, so lint/typecheck/test jobs won’t start. This will be avoided only if the runner image already ships Python 3.14 or you explicitly install it (e.g., actions/setup-python or uv python install) before the sync.

Useful? React with 👍 / 👎.