ci: add workflows verifying compatibility with tools, docs, and agent…

[dbschmigelski]

Description

This PR adds three new GitHub workflow files to verify compatibility across the strands-agents ecosystem:

verify-agent-builder-compatibility.yml: Tests compatibility between sdk-python and the agent-builder repository
verify-docs-compatibility.yml: Ensures sdk-python works correctly with the documentation build process
verify-tools-compatibility.yml: Validates compatibility between sdk-python and the tools repository

All workflows:

• Run on pull requests and pushes to main branch
• Test against Python versions 3.10, 3.11, 3.12, and 3.13
• Because tests are executed using hatch, the workflows override the dependencies in the pyproject.toml since hatch will create its own isolated env

These workflows will help maintain compatibility across the ecosystem and catch potential breaking changes early in the development process.

Related Issues

N/A

Documentation PR

No documentation is needed for this PR.

Type of Change

• Other (please describe): Improving CI

Testing

[How have you tested the change?]

• hatch fmt --linter
• hatch fmt --formatter
• hatch test --all
• Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli

Changes have been verified on the https://github.com/dbschmigelski/sdk-python fork. The fork

• Docs https://github.com/dbschmigelski/sdk-python/actions/runs/15104144012
• Tools https://github.com/dbschmigelski/sdk-python/actions/runs/15104144016
• Agent Builder https://github.com/dbschmigelski/sdk-python/actions/runs/15104144021

Checklist

• I have read the CONTRIBUTING document
• I have added tests that prove my fix is effective or my feature works
• [n/a] I have updated the documentation accordingly
• [n/a] I have added an appropriate example to the documentation to outline the feature
• My changes generate no new warnings
• Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[Unshure]

Instead of updating the pyproject.toml, should we just add another target for pulling a local install?

[dbschmigelski]

Do you mean something like the following in the tools repo

[tool.hatch.envs.test]
dependencies = [
"strands-agents[ollama] @ file://${GITHUB_WORKSPACE}/sdk-python",
]

I thought about this but it leaves the workflow specific test logic in the pyproject which seemed odd to me. I can update if you think thats better than hiding the oddness in the workflow

[dbschmigelski]

I'm going to see if I can do this with an env var actually