Java: adr recording decision to keep everything in one module

[edburns]

No description provided.

[Copilot]

Pull request overview

Adds a Java Architecture Decision Record (ADR) documenting the decision to keep generated Java sources in the existing single copilot-sdk-java Maven module, noting that a sub-module split wouldn’t materially reduce the public API surface and would complicate stability/deprecation metadata propagation.

Changes:

• Introduces ADR-003 capturing the considered module-splitting options and rationale.
• Documents the decision to keep generated code and handwritten code in one module for simpler build/annotation constraints.
• Links related tracking items for follow-up work on stability/deprecation metadata.

Show a summary per file

File	Description
java/docs/adr/adr-003-sub-module-for-generated-code.md	New ADR documenting analysis and decision to keep generated code in the main Java module.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 0

[github-actions]

SDK Consistency Review ✅

This PR adds a single Architecture Decision Record (java/docs/adr/adr-003-sub-module-for-generated-code.md) and makes no changes to SDK code or public APIs.

No cross-SDK consistency issues. This is a Java-specific build-architecture decision (Maven module structure for generated code) with no equivalent concept in the other SDK implementations (Node.js, Python, Go, .NET, Rust). No action required in other language SDKs.

Generated by SDK Consistency Review Agent for issue #1588 · sonnet46 408.1K · ◷