Migrate Unit.Tests → Web.Tests and remove Unit.Tests project

[mpaulosky]

Summary

The tests/Unit.Tests project is redundant — its handler tests either already exist in tests/Web.Tests or need to be merged there. This issue removes Unit.Tests entirely after migrating all unique tests.

Work Required

1. Migrate unique tests into Web.Tests

File	Action
Handlers/GetBlogPostByIdHandlerTests.cs	Add to Web.Tests/Handlers/ (not present there)
Handlers/CreateBlogPostHandlerTests.cs	Merge unique tests (Handle_Success_DoesNotCallInvalidateById) into Web.Tests version
Handlers/EditBlogPostHandlerTests.cs	Merge unique tests (Handle_ConcurrentUpdate_ReturnsConcurrencyErrorCode) into Web.Tests version
Handlers/GetBlogPostsHandlerTests.cs	Compare and merge any unique tests
Handlers/DeleteBlogPostHandlerTests.cs	Compare and merge any unique tests

• Update all namespaces from Unit.Handlers → Web.Handlers
• Update Web.Tests/GlobalUsings.cs to add any missing usings (e.g. Microsoft.EntityFrameworkCore, MyBlog.Domain.Abstractions)
• Ensure Web.Tests.csproj has Microsoft.EntityFrameworkCore package reference if needed for DbUpdateConcurrencyException

2. Remove Unit.Tests project

• Delete tests/Unit.Tests/ directory entirely
• Remove from MyBlog.slnx
• Remove from .github/workflows/squad-release.yml (3 references)
• Update src/Web/Properties/AssemblyInfo.cs: remove InternalsVisibleTo("Unit.Tests"), add InternalsVisibleTo("Web.Tests") (if not already added by [Sprint 6] fix(quality): resolve CA1515 — make Web feature types internal #138)

3. Verify

• dotnet build passes with zero errors
• dotnet test tests/Web.Tests passes

Branch

squad/144-migrate-unit-tests-to-web-tests (use next available issue number once created)

Acceptance Criteria

• All unique Unit.Tests handler tests exist in Web.Tests
• tests/Unit.Tests/ directory is gone
• Solution file, workflows, and AssemblyInfo updated
• Build and tests pass

[github-actions]

📋 Assigned to Gimli (Tester)

Issue: #151 — Migrate Unit.Tests → Web.Tests and remove Unit.Tests project

Gimli will pick this up in the next Copilot session.

For Copilot coding agent: If enabled, this issue will be worked automatically.
Otherwise, start a Copilot session and say:
Gimli, work on issue #151