Skip to content

docs: contagem de testes e registro do review (v0.5.3) - #18

Merged
lglucas merged 2 commits into
mainfrom
docs/v0.5.3-counts
Aug 9, 2026
Merged

docs: contagem de testes e registro do review (v0.5.3)#18
lglucas merged 2 commits into
mainfrom
docs/v0.5.3-counts

Conversation

@lglucas

@lglucas lglucas commented Aug 9, 2026

Copy link
Copy Markdown
Owner

Ajustes de acerto de contas do v0.5.3, sem mudança de comportamento.

  • Contagem de testes 92 → 94 no README, CHANGELOG, release notes e session-log. As duas regressões adicionadas na rodada de review do PR feat(docs): CODEMAP como camada de documentação (v0.5.3) #17 entraram depois que esses textos já estavam escritos.
  • Session-log ganha a seção do review: os dois bugs reais (symlink seguido na leitura, continuação de cabeçalho # descartada) e a contradição entre a skill afirmar "não precisa regenerar ao editar o corpo" e o CI falhar exatamente nesse caso.

O registro dessa terceira importa mais que os números: o defeito nasceu de documentar o comportamento imaginado em vez do implementado, que é uma classe de erro que nenhum teste pega.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated release notes and project documentation to reflect 94 passing tests.
    • Expanded codemap test coverage details to include symlink-boundary validation.
    • Corrected codemap regeneration guidance and documented defects identified during review.

As duas regressões adicionadas na rodada de review (continuação de
cabeçalho `#` e symlink) mudaram a contagem depois que o CHANGELOG e as
release notes já estavam escritos.

Session-log ganha a seção do review: dois bugs reais, e a contradição
entre a skill dizer "não precisa regenerar ao editar o corpo" e o CI
falhar exatamente nesse caso. O defeito nasceu de eu documentar o
comportamento que imaginei ter implementado.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 9, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@lglucas, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 35 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 507c6f4f-421c-499d-a32a-9ef9b05f1034

📥 Commits

Reviewing files that changed from the base of the PR and between 4a6f36b and 48a083c.

📒 Files selected for processing (2)
  • README.md
  • session-log/2026-08-08-v0.5.3-codemap.md
📝 Walkthrough

Walkthrough

Documentation updates record 19 Codemap tests, 94 total tests, symlink-boundary validation, review findings, and corrected regeneration guidance.

Changes

Codemap coverage documentation

Layer / File(s) Summary
Update test counts and coverage records
CHANGELOG.md, README.md, RELEASE-NOTES-v0.5.3.md, session-log/...
The documentation records 19 Codemap tests and 94 total tests. It adds symlink-boundary coverage and documents review findings and regeneration guidance.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning A descrição resume as mudanças, mas não preenche as seções obrigatórias de tipo, checklist, impacto e plano de testes. Preencha as seções Type of change, OS coherence checklist, Vibe-coder impact e Test plan conforme o template.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed O título identifica claramente a atualização da contagem de testes e o registro do review na documentação do v0.5.3.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/v0.5.3-counts

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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 281: Update the README test-count description for the node --test command
so it does not label all 94 tests as unit tests; use the neutral wording “94
tests” or provide separate unit and integration counts, accounting for the
integration test in scripts/test/codemap.test.js.

In `@session-log/2026-08-08-v0.5.3-codemap.md`:
- Around line 79-91: Atualize a seção que descreve os dois bugs corrigidos para
registrar explicitamente quando os respectivos testes de regressão foram
adicionados, deixando claro que isso ocorreu após a redação inicial desta
documentação. Preserve os detalhes existentes sobre os defeitos, a correção e a
cobertura.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1cf36fed-6396-47f1-b6d3-1a046a2519a5

📥 Commits

Reviewing files that changed from the base of the PR and between 8bab74c and 4a6f36b.

📒 Files selected for processing (4)
  • CHANGELOG.md
  • README.md
  • RELEASE-NOTES-v0.5.3.md
  • session-log/2026-08-08-v0.5.3-codemap.md

Comment thread README.md Outdated
Comment thread session-log/2026-08-08-v0.5.3-codemap.md
… entraram

O README classificava os 94 como unitários, mas o teste de symlink roda
o gerador num repo temporário via execFileSync — é integração.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@lglucas
lglucas merged commit c610447 into main Aug 9, 2026
3 checks passed
@lglucas
lglucas deleted the docs/v0.5.3-counts branch August 9, 2026 03:41
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