feat: relax Python version requirement to `>=3.11` or `>=3.10`

[KimigaiiWuyi]

Context

Python>=3.13 is quite restrictive, as many environments (including CI systems and production setups) are still on Python 3.10–3.12, all of which are actively used and supported.

Problem

The strict requirement on Python>=3.13 prevents installation and usage in otherwise compatible environments.

From testing and inspection:

• The codebase works on Python >=3.11 without any changes
• With a small modification, it can also support Python 3.10

Evidence

• Python 3.11+: works out of the box (no syntax or runtime issues)
• Python 3.10: only requires replacing StrEnum with Enum in:

memv/src/memv/models.py

Line 5 in c567227

from enum import StrEnum

memv/src/memv/models.py

Lines 15 to 18 in c567227

	class MessageRole(StrEnum):
	USER = "user"
	ASSISTANT = "assistant"
	SYSTEM = "system"

memv/src/memv/models.py

Lines 159 to 163 in c567227

	class ProcessStatus(StrEnum):
	PENDING = "pending"
	RUNNING = "running"
	COMPLETED = "completed"
	FAILED = "failed"

fix with:

from enum import Enum 

class MessageRole(str, Enum):
    USER = "user"
    ASSISTANT = "assistant"
    SYSTEM = "system"

class ProcessStatus(str, Enum):
    PENDING = "pending"
    RUNNING = "running"
    COMPLETED = "completed"
    FAILED = "failed"

[KimigaiiWuyi]

have any new thoughts on this?

[brgsk]

Good research — the arguments are sound. Let's go with >=3.10.

Would you like to take this one? The scope would be:

• StrEnum → (str, Enum) change in models.py
• requires-python bump to >=3.10
• CI matrix expansion to test 3.10, 3.11, 3.12, 3.13 (.github/workflows/ci.yml)

You've already done most of the hard work identifying the changes needed!