fix(aos-eval): ship the PEP 561 marker, so a typed consumer sees types #1113
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agentic-os!1113
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/gh56-aos-eval-typed"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found by adopting
aos-evalin agent-compose, which is why that repo went first.evalkit-checkrunsmypy --strict. On the first sync againstaos-eval-v0.1.0it returned seven errors, all the same one:The package is fully annotated and shipped no PEP 561 marker, so every consumer under strict typing reads it as untyped. That is a defect in what I published, not in the consumer.
Fix
aos_eval/py.typedadded[tool.setuptools.package-data], because present in the tree is not the same as present in the built wheel0.1.1Three tests for the shipping contract
The failure mode here is that a packaging mistake is invisible in-repo and only appears in a consumer.
tests/test_packaging.pynow asserts:aos_evalinspect-ai,openai,anthropic,litellm) has crept into the dependency setThe third is the invariant the second package exists for, and nothing was checking it.
Verification
just aos-eval-test- 61 passedpre-commit run --all-files- cleanOrdering
agent-compose's adoption branch is written and green apart from this, and pins
aos-eval-v0.1.1. It can land once this merges and the train cuts that tag.Generated with Claude Code