Breaking change in schema fix should be major version bump

[avrabe]

Issue Summary

The recent schema generation fix (PR #56) introduces a breaking change but only bumps the patch version (0.10.0 → 0.10.1), which violates semantic versioning.

The Problem

PR #56 fixes the critical schema generation bug but makes multi-parameter tools fail to compile:

// This now fails to compile with our fix
fn my_tool(&self, name: String, count: Option<u32>) -> String

Breaking changes require MAJOR version bumps according to semver.

Current Situation

• What it fixes: Critical bug where all schemas were empty
• What it breaks: Multi-parameter tool patterns (compile errors)
• Version bump: 0.10.0 → 0.10.1 (patch) ❌
• Should be: 0.10.0 → 0.11.0 (major) or make it non-breaking

Proposed Solutions

Option 1: Make it Non-Breaking ✅ (Recommended)

• Support both old multi-parameter AND new single-struct patterns
• Single-struct gets full JsonSchema support (fixed)
• Multi-parameter gets basic/fallback schema support (better than broken)
• Add deprecation warnings for multi-parameter pattern
• Breaking change in v0.12.0

Option 2: Accept Breaking Change

• Change version to 0.11.0 (major bump)
• Document clear migration path
• Accept that users need to update immediately

Option 3: Hybrid Approach

• Release 0.10.1 as hotfix with non-breaking implementation
• Release 0.11.0 later with full breaking changes

Impact Assessment

Who is affected:

• Users with multi-parameter tools (most examples, many real implementations)
• Projects that can't immediately migrate parameter patterns

Severity:

• 🔴 High: Breaks existing code compilation
• 🟡 Medium: Migration path is straightforward
• 🟢 Low: Old pattern was already broken (empty schemas)

Recommendation

Implement Option 1 to make the fix non-breaking:

1. Keep the JsonSchema fix for single-struct pattern (works perfectly)
2. Add fallback support for multi-parameter pattern (better than broken)
3. Version stays at 0.10.1 (patch for bug fix)
4. Add deprecation warnings to guide migration
5. Plan breaking change for v0.12.0

This approach:

• ✅ Fixes the critical bug immediately
• ✅ Doesn't break existing code
• ✅ Follows semantic versioning
• ✅ Provides smooth migration path

Action Items

• Decide on approach (Option 1, 2, or 3)
• Update PR fix: resolve schema generation regression with dual-pattern support (v0.10.1) #56 accordingly
• Update version number if needed
• Document migration strategy
• Update examples to demonstrate best practices

Related

• Fixes Parameter schema generation not working - all tools show empty inputSchema #55 (Schema generation regression)
• Related to PR fix: resolve schema generation regression with dual-pattern support (v0.10.1) #56 (Schema generation fix)

[avrabe]

✅ RESOLVED: Version has been updated to 0.11.0 in PR #56

Changes made:

• ✅ Workspace version: 0.10.1 → 0.11.0
• ✅ All package versions: 0.10.0 → 0.11.0
• ✅ PR title updated to indicate breaking change
• ✅ Proper semantic versioning now reflects the breaking nature

This correctly signals to users that:

1. Code changes are required (compilation errors guide migration)
2. API contract has changed (multi-parameter → single-struct pattern)
3. Non-trivial upgrade (not just a drop-in replacement)

The breaking change is now properly communicated through semantic versioning. 🎯

[avrabe]

Resolved by properly versioning as 0.11.0 breaking change in PR #56.