feat: add py.typed file

[olivermeyer]

This allows type checkers to work with the library.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.
see 1 file with indirect coverage changes

[claude]

Claude finished @olivermeyer's task in 2m 3s —— View job

---

Code Review Complete

I've thoroughly reviewed PR #47 for adding PEP 561 type checking support via py.typed. Here are my findings:

---

✅ What's Good

1. Correct Implementation: The py.typed file is correctly placed at src/aignostics_foundry_core/py.typed and is empty, which is the standard PEP 561 approach.

2. Existing Type Annotations: The codebase has comprehensive type hints throughout (verified in console.py, service.py, and other modules).

3. Classifier Already Present: The "Typing :: Typed" classifier is already in pyproject.toml:45, which is great.

4. Package Inclusion: The hatchling configuration include = ["src/*"] will automatically include the py.typed file in the wheel distribution.

5. Commit Message: "feat: add py.typed file" follows conventional commits correctly.

6. CI Passing: All quality gates passed (SonarQube, Codecov).

---

🚨 Blocking Issues

Version Rollback Conflict

Location: Multiple files (VERSION, pyproject.toml, sonar-project.properties, CHANGELOG.md, uv.lock)

Issue: This PR branch is based on commit 04d2e5e (before the 0.11.1 release), but main is now at 4f83f9c (version 0.11.1). The diff shows:

- version = "0.11.1"
+ version = "0.11.0"

This will revert the version from 0.11.1 back to 0.11.0 and remove the 0.11.1 changelog entry when merged.

Fix Required: Rebase this branch on top of current main:

git fetch origin main
git rebase origin/main
git push --force-with-lease

After rebasing, the only change should be the addition of src/aignostics_foundry_core/py.typed.

---

💡 Suggestions

Documentation Update

While not blocking, consider documenting this feature:

README.md could mention type checking support:

## Type Checking

This package includes full type annotations and a `py.typed` marker file for PEP 561 compliance. Type checkers like mypy and pyright can verify usage of this library.

Or in the relevant section of FOUNDRY_README.md under tooling/development.

---

Summary

The py.typed implementation itself is perfect. However, the branch needs to be rebased on current main to avoid reverting version 0.11.1. Once rebased, this PR will be ready to merge.

Recommendation: Rebase and force-push, then re-run CI to confirm.

---

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud