fix: map Title, CategoryId, and StatusId in UpdateIssueCommand; fix EditCategory/StatusPage name fields

[Copilot]

EditIssuePage.HandleSubmit built UpdateIssueCommand with only Description, silently dropping Title, CategoryId, and StatusId. The same pattern affected EditCategoryPage (missing CategoryName) and EditStatusPage (missing StatusName).

Changes

UpdateIssueCommand — new fields

• Added CategoryId: ObjectId? and StatusId: ObjectId?

UpdateIssueHandler — category/status lookup

• Injected ICategoryRepository and IStatusRepository
• When CategoryId/StatusId are set, resolves full DTOs from their respective repos before updating the issue; returns NotFound if either lookup fails

Edit pages — complete field mapping

Before (EditIssuePage.razor):

var command = new UpdateIssueCommand
{
    Id = ObjectId.Parse(Id),
    Description = request.Description   // Title, CategoryId, StatusId dropped!
};

After:

var command = new UpdateIssueCommand
{
    Id = ObjectId.Parse(Id),
    Title = request.Title,
    Description = request.Description,
    CategoryId = ObjectId.TryParse(request.CategoryId, out var catId) ? catId : (ObjectId?)null,
    StatusId = ObjectId.TryParse(request.StatusId, out var statId) ? statId : (ObjectId?)null
};

• EditCategoryPage: UpdateCategoryCommand now includes CategoryName
• EditStatusPage: UpdateStatusCommand now includes StatusName

Tests

• UpdateIssueHandlerTests: updated for 4-arg constructor; added coverage for CategoryId/StatusId happy paths and invalid-ID not-found cases
• UpdateIssueHandlerIntegrationTests: updated constructor call with substituted category/status repos

[Copilot]

Pull request overview

Fixes incomplete field mapping when updating issues/categories/statuses by ensuring update commands include all relevant fields and the API resolves category/status DTOs when IDs are provided.

Changes:

• Extend UpdateIssueCommand with optional CategoryId / StatusId and map them from the edit UI.
• Update UpdateIssueHandler to resolve and apply category/status DTOs (or return NotFound if missing).
• Update unit/integration tests to use the new handler constructor and add coverage for category/status update paths.

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
src/Shared/Contracts/UpdateIssueCommand.cs	Adds CategoryId / StatusId fields to support updating related entities.
src/Api/Handlers/Issues/UpdateIssueHandler.cs	Injects category/status repositories and resolves DTOs before updating the issue.
src/Web/Components/Features/Issues/EditIssuePage.razor	Maps Title, CategoryId, and StatusId into UpdateIssueCommand during submit.
src/Web/Components/Features/Categories/EditCategoryPage.razor	Ensures CategoryName is included in UpdateCategoryCommand.
src/Web/Components/Features/Statuses/EditStatusPage.razor	Ensures StatusName is included in UpdateStatusCommand.
tests/Api.Tests.Unit/Handlers/Issues/UpdateIssueHandlerTests.cs	Updates constructor usage and adds category/status update/not-found tests.
tests/Api.Tests.Integration/Handlers/UpdateIssueHandlerIntegrationTests.cs	Updates handler construction to include substituted category/status repositories.
src/Web/package-lock.json	Reformatted lockfile (appears whitespace-only), increasing diff size/noise.

[Copilot]

Same concern for status resolution: if StatusId is posted but unchanged, UpdateIssueHandler will still hit the status repository. Adding an ID equality check before fetching can reduce DB traffic in the common "edit title/description" path.

Suggested change

	var statusResult = await _statusRepository.GetByIdAsync(command.StatusId.Value, cancellationToken);
	if (!statusResult.Success || statusResult.Value is null)
	return Result.Fail<IssueDto>($"Status with ID '{command.StatusId}' was not found.", ResultErrorCode.NotFound);
	status = statusResult.Value;
	var currentStatusId = getResult.Value.Status.Id;
	if (command.StatusId.Value != currentStatusId)
	{
	var statusResult = await _statusRepository.GetByIdAsync(command.StatusId.Value, cancellationToken);
	if (!statusResult.Success || statusResult.Value is null)
	return Result.Fail<IssueDto>($"Status with ID '{command.StatusId}' was not found.", ResultErrorCode.NotFound);
	status = statusResult.Value;
	}

[Copilot]

This change appears to reformat the entire package-lock.json (tabs -> spaces) without changing dependencies, which creates a very large/noisy diff and increases merge-conflict risk. If there were no actual dependency updates intended in this PR, consider reverting the lockfile reformat or moving it to a separate dedicated PR.

[Copilot]

The new "Handle_WithCategoryId_UpdatesCategory" test doesn't actually verify that UpdateIssueHandler passes the resolved category into IIssueRepository.UpdateAsync. Since UpdateAsync is stubbed with Arg.Any(), the test would still pass even if the handler ignored CategoryId. Consider asserting the argument to UpdateAsync (e.g., Arg.Is(i => i.Category.Id == categoryId)) so the test genuinely exercises the new behavior.

[Copilot]

Same issue as the category test: "Handle_WithStatusId_UpdatesStatus" stubs UpdateAsync with Arg.Any(), so it doesn't prove the handler applied the resolved status. Add an assertion on the IssueDto passed to UpdateAsync (and optionally also assert Category remains unchanged).

[Copilot]

For the invalid CategoryId path, it would be good to assert that IIssueRepository.UpdateAsync is not called when the category lookup fails. Without this, the test won't catch a bug where the handler continues updating with the old category after a lookup failure.

[Copilot]

For the invalid StatusId path, consider asserting IIssueRepository.UpdateAsync is not called when the status lookup fails, to ensure the handler short-circuits correctly on lookup errors.

Suggested change

	result.ErrorCode.Should().Be(ResultErrorCode.NotFound);
	result.ErrorCode.Should().Be(ResultErrorCode.NotFound);
	_repository.ReceivedCalls()
	.Should()
	.NotContain(call => call.GetMethodInfo().Name == nameof(IIssueRepository.UpdateAsync));

[Copilot]

UpdateIssueHandler now always performs a category lookup whenever CategoryId is provided, even when it matches the issue's current category ID. Since the edit UI typically posts the selected CategoryId even when unchanged, this adds an extra DB call on most updates. Consider skipping the repository lookup when command.CategoryId.Value == getResult.Value.Category.Id (and similarly for StatusId) to avoid unnecessary reads.

[github-actions]

Test Results Summary

  6 files  ±0   33 suites  ±0   11s ⏱️ ±0s
839 tests +4  839 ✅ +4  0 💤 ±0  0 ❌ ±0 
850 runs  +4  850 ✅ +4  0 💤 ±0  0 ❌ ±0 

Results for commit 307ec88. ± Comparison against base commit 7180786.

[codecov]

Codecov Report

❌ Patch coverage is 79.31034% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 55.76%. Comparing base (7180786) to head (307ec88).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
...Web/Components/Features/Issues/EditIssuePage.razor	0.00%	4 Missing ⚠️
...ponents/Features/Categories/EditCategoryPage.razor	0.00%	1 Missing ⚠️
.../Components/Features/Statuses/EditStatusPage.razor	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #131      +/-   ##
==========================================
+ Coverage   55.52%   55.76%   +0.24%     
==========================================
  Files         124      124              
  Lines        2826     2853      +27     
  Branches      313      318       +5     
==========================================
+ Hits         1569     1591      +22     
- Misses       1027     1031       +4     
- Partials      230      231       +1     

Files with missing lines	Coverage Δ
src/Api/Handlers/Issues/UpdateIssueHandler.cs	97.56% <100.00%> (+2.32%)	⬆️
src/Shared/Contracts/UpdateIssueCommand.cs	100.00% <100.00%> (ø)
...ponents/Features/Categories/EditCategoryPage.razor	0.00% <0.00%> (ø)
.../Components/Features/Statuses/EditStatusPage.razor	0.00% <0.00%> (ø)
...Web/Components/Features/Issues/EditIssuePage.razor	0.00% <0.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mpaulosky]

✅ Ralph (Work Monitor): All test suites pass (unit, integration, bunit, architecture). The E2E failure is a pre-existing CI infrastructure issue (DB init failure, Redis SSL errors) unrelated to this PR's changes. Merging.