Python Backend

• Add/extend repo tests (pytest) so that:
  • Red phase: at least one relevant test fails before implementation
  • Green phase: the same test passes after the code change
  • New behavior is covered
• Tests must contain real assertions
• Do not weaken or delete existing tests

Acceptance harness

• If FEATURE_DIR/acceptance/ is missing:
  • Create FEATURE_DIR/acceptance/tests/
  • Use FastAPI TestClient
  • Write black-box tests hitting actual endpoints
• Translate behavior described in FEATURE.md into executable checks

Virtualenv policy

• If Python is detected:
  • .venv/ at repo root is required
  • Never delete .venv
  • Prefer incremental repair
  • If available, use $HOME/.codex/scripts/ensure_venv
• All Python tools must be run via .venv/bin/python -m <tool>

Reference repos (Python backend)

Use only if current repo lacks a needed pattern.

• $HOME/software/marcocello/meshify-backend
  • FastAPI service layout
  • pytest fixtures style
  • ruff config conventions

When using a reference repo:

• Borrow patterns, not whole implementations.
• Mention repo + pattern reused (1 line).