Skip to content

chore: add backend agent guidance and portable template tests - #1337

Open
udgover wants to merge 3 commits into
mainfrom
docs/agent-guidance
Open

chore: add backend agent guidance and portable template tests#1337
udgover wants to merge 3 commits into
mainfrom
docs/agent-guidance

Conversation

@udgover

@udgover udgover commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • add repository-local guidance for backend agents, including the current uv, Ruff, ty, pytest, and safety conventions
  • isolate template API tests in per-test temporary directories instead of writing to /opt/yeti/templates
  • register logging and environment cleanup before failure-prone setup so state cannot leak into later tests

Why

The backend participates in a local multi-repository workspace, but its automation guidance needs to remain accurate when the repository is used independently. During validation, the template API tests reproduced five host-only PermissionError failures because they assumed a container filesystem path. The test-only hardening keeps production behavior unchanged while making local validation portable.

Validation

  • uv sync --group dev
  • uv run --no-sync ruff check .
  • uv run --no-sync ruff format . --check
  • uv run ty check --exit-zero-on-warning
  • focused red/green check: uv run pytest tests/apiv2/templates.py tests/core_tests/taskscheduler.py (6 passed)
  • CI-equivalent suites with local Redis and ArangoDB:
    • uv run pytest tests/schemas (190 passed)
    • uv run pytest tests/apiv2 (205 passed)
    • uv run pytest tests/core_tests (31 passed)

Total: 426 tests passed. Existing dependency and serializer warnings remain unchanged.

udgover added 3 commits August 5, 2026 01:21
Use a per-test temporary template directory so the API suite runs on non-container hosts without writing under /opt. Register environment and logging cleanup before database setup so failures cannot leak process-wide state into later tests.
Document the repository map, uv-based toolchain, validation commands, cross-repository API contract, and safety boundaries so automated contributors operate consistently with current manifests and CI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant