Connapse: Instructions file for Claude Code

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Build & Run

# Build
dotnet build

# Run web app (requires backing services)
dotnet run --project src/Connapse.Web

# Start backing services (PostgreSQL + MinIO, ports exposed to host)
docker compose -f docker-compose.yml -f docker-compose.dev.yml up -d

# Full stack via Docker
docker compose up -d

Tests

# All tests
dotnet test

# Unit tests only (no Docker required)
dotnet test --filter "Category=Unit"

# Integration tests (needs Docker for Testcontainers)
dotnet test --filter "Category=Integration"

# Single test class
dotnet test --filter "FullyQualifiedName~Connapse.Core.Tests.CloudScope.CloudScopeServiceTests"

# Single test method
dotnet test --filter "FullyQualifiedName~ClassName.MethodName_Scenario_ExpectedResult"

# Retrieval eval harness (Docker + Ollama; see tests/Connapse.Eval/README.md)
dotnet run --project tests/Connapse.Eval -- run --suite v1 --config hybrid

• xUnit framework, FluentAssertions (.Should()), NSubstitute for mocking
• Integration tests share a single PostgreSQL+MinIO container pair via SharedWebAppFixture (collection-based)
• Every test container is capped at 2 CPUs and 4 GB by TestContainerLimits; set CONNAPSE_TEST_CONTAINER_LIMITS to <cpus>,<memory> (e.g. 4,8g) or off to change that. New fixtures must add .WithCreateParameterModifier(TestContainerLimits.Apply)
• Tag tests: [Trait("Category", "Unit")] or [Trait("Category", "Integration")]; speed gates that time real work use [Trait("Category", "Gate")] and run in their own CI step
• Test naming: MethodName_Scenario_ExpectedResult

Database Migrations

Two separate EF Core migration histories:

• KnowledgeDbContext (Storage): dotnet ef migrations add Name --project src/Connapse.Storage
• ConnapseIdentityDbContext (Identity): dotnet ef migrations add Name --project src/Connapse.Identity

Migrations run automatically on app startup.