Docs/technical debt review

[frigini]

Summary by CodeRabbit

• Documentation
  • Updated roadmap: added Sprint 7.15 and 7.16, re-sequenced Sprints 8–9, reframed Sprint names to “Customer App”, and advanced MVP to Feb 17, 2026.
  • Expanded Sprint narratives with success criteria, risks, and timeline adjustments.
  • Added detailed Sprint 7.16 technical-debt plan (Keycloak automation, frontend warnings remediation, test coverage, refactors).
  • Reorganized technical-debt doc into a multi-sprint backlog and condensed prior sprint content.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds detailed Sprint 7.15 and Sprint 7.16 entries to the roadmap (package updates, resilience migration, scheduling), and reorganizes the technical-debt doc to a Sprint 6–7 framing with reprioritized frontend analyzers, test coverage, Keycloak automation, and refactor notes. All changes are documentation only.

Changes

Cohort / File(s)	Summary
Roadmap Documentation docs/roadmap.md	Inserted Sprint 7.15 and Sprint 7.16 narratives: NuGet/package updates, migration from Polly.Extensions.Http to Microsoft.Extensions.Http.Resilience, .NET 10 compatibility notes, Sprint 7.16 technical-debt plan, updated Sprint 8/9 milestones, adjusted MVP target/timelines, and revised risk/commit notes.
Technical Debt Documentation docs/technical-debt.md	Rewrote major sections to present a Sprint 6–7 technical-debt backlog: replaced Sprint 7.6 framing, moved/renamed sprint labels, added frontend warnings remediation, updated frontend test coverage targets (Sprint 7.16), Keycloak automation tasks, consolidated refactor proposals, and revised mitigation/monitoring guidance.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through lines of roadmap lore,
Added sprints and debt to store,
Polly bowed to resilience bright,
Keys and tests now set alight,
A tiny hop — the docs feel right! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request has no description provided by the author, despite a detailed template being available for the repository.	Add a pull request description following the repository template, including Summary, Problem, Solution, Changes, Impact, Testing, Checklist, Related issues, and Notes for Reviewers sections.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Docs/technical debt review' clearly summarizes the main change in the changeset, which involves updates to technical debt documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@docs/roadmap.md`:
- Around line 1071-1503: The file contains a duplicated "### ⏳ Sprint 7.16 -
Technical Debt Sprint (17-21 Jan 2026)" section; remove the second complete copy
(the later block starting with the same Sprint 7.16 header) so only the first
occurrence remains, ensuring the single header "Sprint 7.16 - Technical Debt
Sprint (17-21 Jan 2026)" and its tasks (Keycloak Client Automation, Frontend
Analyzer Warnings, Frontend Test Coverage, Records Standardization,
SearchProviders E2E Tests) are kept once and any trailing duplicate content
after that header is deleted.

In `@docs/technical-debt.md`:
- Line 15: Update the sprint labels in docs/technical-debt.md where items are
incorrectly marked "Sprint 8": replace the text "**Sprint**: Sprint 8
(planejado)" and other occurrences tied to the Frontend warnings, Frontend test
coverage, and Keycloak automation entries with "Sprint 7.16" (the Technical Debt
Sprint) to match roadmap.md; ensure all similar references (e.g., the lines
containing "Frontend warnings", "Frontend test coverage", "Keycloak automation")
are updated consistently across the document.

🧹 Nitpick comments (2)

docs/roadmap.md (1)

1099-1099: Consider using markdown link syntax for URLs.

Bare URLs on lines 1099 and 1316 could be converted to markdown links for better formatting and accessibility.

📝 Example conversion

-Monitorar: https://github.com/frankhommers/Hangfire.PostgreSql/issues
+Monitorar: [Hangfire.PostgreSql Issues](https://github.com/frankhommers/Hangfire.PostgreSql/issues)

Based on learnings: This is a minor documentation improvement, not a critical issue.

Also applies to: 1316-1316

docs/technical-debt.md (1)

187-190: Add language specifier to code fence.

The fenced code block showing the error message should have a language specifier for proper syntax highlighting and consistency.

📝 Proposed fix

-**Erro Encontrado**:
-```
-error CS0200: Property or indexer 'IOpenApiMediaType.Example' cannot be assigned to -- it is read only
-```
+**Erro Encontrado**:
+```text
+error CS0200: Property or indexer 'IOpenApiMediaType.Example' cannot be assigned to -- it is read only
+```

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@docs/roadmap.md`:
- Line 40: Update the roadmap to resolve the MVP launch date conflict by
choosing a single authoritative date and applying it consistently: locate the
entry with "🎯 **17 Fevereiro 2026**" and the "Sprint 9 Expected Results"
section that mentions "31 de Março de 2026", decide which date is correct (or a
new agreed-upon date), then replace the incorrect date occurrence(s) so both the
top-level MVP Launch line and the Sprint 9 Expected Results entry use the same
launch date and add a one-line note if the schedule was adjusted to reflect
scope/timeline changes.

In `@docs/technical-debt.md`:
- Around line 217-222: Update the "Padronização de Records" entry so the Sprint
and Severity fields are consistent with the roadmap: locate the "Padronização de
Records" section in technical-debt.md and change the metadata `**Severidade**:
BAIXA` to `**Severidade**: MÉDIA` and `**Sprint**: BACKLOG` to `**Sprint**:
Sprint 7.16 (Dia 5)` (or alternatively update the roadmap if you intend to keep
it in BACKLOG); also ensure the "Ação Sugerida" text references the same Sprint
designation (Sprint 7.16) to eliminate the contradiction between
technical-debt.md and roadmap.md.

🧹 Nitpick comments (1)

docs/roadmap.md (1)

1099-1099: Markdown style: Use proper link syntax for URLs.

Bare URLs should be formatted using markdown link syntax for better readability and consistency with documentation standards.

Suggested formats:

• Named link: [dotnet/aspire#6789](https://github.com/dotnet/aspire/issues/6789)
• Auto-link: <https://github.com/dotnet/aspire/issues/6789>

♻️ Proposed fix

If this is the URL on line 1099 (the context shows it's a GitHub issue link):

-- Link para issue upstream: [dotnet/aspire#6789](https://github.com/dotnet/aspire/issues/6789)
+- Link para issue upstream: <https://github.com/dotnet/aspire/issues/6789>

Or use named link format:

-- Link para issue upstream: [dotnet/aspire#6789](https://github.com/dotnet/aspire/issues/6789)
+- Link para issue upstream: [dotnet/aspire#6789](https://github.com/dotnet/aspire/issues/6789)

Apply similar fix to the duplicate occurrence in the second Sprint 7.16 section.

[github-actions]

📊 Code Coverage Report

Coverage: 90.27% (extracted from Cobertura (Aggregated Direct))

📈 Coverage Details

• Coverage badges:
• Minimum threshold: 80% (warning) / 90% (good)
• Report format: Auto-detected from OpenCover/Cobertura XML files
• Coverage source: Cobertura (Aggregated Direct)

📋 Coverage Analysis

• Line Coverage: Shows percentage of code lines executed during tests
• Branch Coverage: Shows percentage of code branches/conditions tested
• Complexity: Code complexity metrics for maintainability

🎯 Quality Gates

• ✅ Pass: Coverage ≥ 90%
• ⚠️ Warning: Coverage 80-89%
• ❌ Fail: Coverage < 80%

📁 Artifacts

• Coverage reports: Available in workflow artifacts
• Test results: TRX files with detailed test execution data

This comment is updated automatically on each push to track coverage trends.