chore: Consolidate Maven organization to org.wvlet.uni

[xerial]

Summary

• Update Maven organization from org.wvlet to org.wvlet.uni to better distinguish uni modules from other wvlet projects (like Airframe)
• Update version references in documentation to 2026.1.0
• Fix artifact name references (uni-agent-bedrock → uni-bedrock)

Test plan

• ./sbt compile passes
• ./sbt scalafmtAll passes
• Verify documentation renders correctly

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @xerial, 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 centralizes the Maven organization for all Uni modules under "org.wvlet.uni", aiming to better separate these modules from other projects within the broader "wvlet" ecosystem. This change, along with a version update to "2026.1.0" and a minor artifact name correction, necessitates updates across the build configuration and all relevant documentation, marking a breaking change for existing users.

Highlights

• Maven Organization Update: The Maven organization for Uni modules has been changed from "org.wvlet" to "org.wvlet.uni" to provide clearer distinction from other "wvlet" projects.
• Version Bump: All documentation and build configurations now reflect a new version "2026.1.0".
• Artifact Renaming: The "uni-agent-bedrock" artifact has been renamed to "uni-bedrock" in documentation.

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 PR does a good job of consolidating the Maven organization and updating versions. I've found one minor inconsistency in the documentation that was missed and have a suggestion for a follow-up improvement to enhance project structure consistency.

[gemini-code-assist]

Good job updating the dependency snippets! However, I noticed that the module table on line 70 of this file still lists the old artifact name uni-agent-bedrock. To maintain consistency with the other changes in this PR, please update it to uni-bedrock.

- | `uni-agent-bedrock` | AWS Bedrock chat model integration |
+ | `uni-bedrock` | AWS Bedrock chat model integration |

[gemini-code-assist]

The artifact name is now correctly uni-bedrock. For long-term consistency and to avoid confusion for developers, it would be beneficial to also rename the project's source directory from uni-agent-bedrock to uni-bedrock. This would involve updating build.sbt at line 187 and renaming the directory in the file system. This could be handled in a follow-up PR if you prefer to keep this one focused.

// In build.sbt
lazy val bedrock = project
  .in(file("uni-bedrock")) // Changed from "uni-agent-bedrock"
  // ...