Add kernel coverage for router, helpers, ignite, and sentry

[gocanto]

Summary

• add coverage for kernel Ignite failure handling and App accessors
• exercise App.NewRouter success and error paths to ensure middleware wiring
• verify MakeSentry configuration and RecoverWithSentry Sentry integration behavior

Testing

• go test ./...

---

https://chatgpt.com/codex/tasks/task_e_68d4fb5a6a2c8333a1f4f4c0dde49ea0

Summary by CodeRabbit

• New Features

  • Enhanced CLI export with clearer, color-coded progress logs, including output directory, written file path, and final confirmation.

• Tests

  • Added comprehensive coverage for startup failure handling, router initialization success/error paths, and environment state checks.
  • Expanded Sentry integration tests, including panic recovery behaviors and event capture.
  • Verified logging initialization and shutdown behavior.
  • Introduced lightweight test utilities to support deterministic paths and event recording.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Adds CLI log output to seo generator Export. Introduces extensive kernel tests covering panic paths, Sentry integration behavior, router creation outcomes, logging setup, and utility helpers. No production APIs altered; functional changes are limited to user-facing logs.

Changes

Cohort / File(s)	Summary
CLI SEO generator logging metal/cli/seo/generator.go	Added progress/logging calls (Warningln, Cyanln, Blueln, Grayln) within Export to emit execution status, output directory, written file path, and completion messages. No control flow or error handling changes.
Kernel tests and Sentry scaffolding metal/kernel/kernel_test.go	Added tests for Ignite panic on missing env file, App accessors and environment state, NewRouter error/success cases, Sentry setup (timeouts, Repin/WaitForDelivery), RecoverWithSentry behavior including nil hub, recording transport mock, logging initialization checks, and helper utilities.

Sequence Diagram(s)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• Integrate Sentry into HTTP handling #112 — Touches Sentry integration and kernel test scaffolding similar to MakeSentry/RecoverWithSentry and related tests; likely overlaps in approach and interfaces.

Poem

A bunny taps the console keys—click, click!
New logs hop out, cyan-blue and slick.
In burrows of tests, Sentry keeps watch,
Catching each panic with a gentle notch.
The router’s path is sure and bright—
Hippity-hop, all green tonight! 🐇✨

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/review-all-tests-for-coverage-and-pass-status

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8400a54 and 963064f.

📒 Files selected for processing (2)

• metal/cli/seo/generator.go (1 hunks)
• metal/kernel/kernel_test.go (5 hunks)

---

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.}

[gemini-code-assist]

Summary of Changes

Hello @gocanto, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the test coverage for core application components, including the kernel's initialization process, App's environment and database accessors, the NewRouter function's success and error paths, and the Sentry error reporting integration. The new tests aim to ensure the stability and correct behavior of these critical parts of the application, particularly around error handling and middleware setup.

Highlights

• Enhanced Kernel Ignite Testing: Added tests to ensure Ignite panics correctly when a .env file is missing, improving robustness in environment loading.
• Comprehensive App Accessor Verification: Introduced tests for App's accessor methods (IsLocal, IsProduction, GetEnv, GetDB, GetSentry) to confirm they return expected values and states.
• Thorough Router Initialization Coverage: Expanded testing for App.NewRouter to cover nil receiver errors, token handler creation failures, and successful initialization with correct middleware wiring and component assignments.
• Sentry Integration Validation: Added tests to verify MakeSentry configuration (e.g., Timeout, Repanic, WaitForDelivery based on environment) and RecoverWithSentry's ability to capture panics and handle nil Sentry hubs gracefully.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds significant test coverage for the kernel, router, helpers, and Sentry integration, which is a great improvement for the project's stability. My review focuses on further enhancing the new tests by suggesting the use of sub-tests (t.Run) for better structure and failure isolation, and improving the robustness of some test assertions. These changes will make the tests more maintainable and provide clearer output on failures.