[trissim]

The registered lazy/public declaration API merged in #9 is absent from published 1.1.8. Prepare patch version 1.1.9 so OpenHCS registry preparation can consume it from an installed wheel. The Hatch-backed runtime version remains the sole package-version source.

Validation:

• Wheel and sdist built using existing interpreter plus an owned build-tool target; all four release artifacts pass twine check. No shared environment/source changes.
• Installed-wheel lazy factory, global config and context controls: 40 passed. OpenHCS main PR514 readiness test against both installed candidate wheels: 1 passed, with no default-factory evaluation.
• Runtime version, installed distribution metadata and artifact declaration agree. The existing immutable-release validator passed against a private local annotated tag and exact candidate HEAD. No public tag exists yet.

Candidate commit: 90951d09dcbd0633065aa44dc54405e2f13cf2a3. Planned release tag: v1.1.9 (publication pending review/authorization; final merged release commit must be revalidated before tagging).

Artifact	SHA256
objectstate-1.1.9-py3-none-any.whl	524eb9a72d5e4620dbbea0336f8dd7d32583f687e64a3c954b10f83560e67be6
objectstate-1.1.9.tar.gz	25f4b054e6ed92e4717514f8b8104abd31e83832a59389fdcfab939d783306bb

The older verify_release_ready.py token-name check rejects the existing trusted-publishing workflow. That unrelated script failure is retained; the actual workflow distribution check (twine check) passes.

This PR prepares release source only. It does not push a tag or publish PyPI artifacts. OpenHCS dependency floors must wait for actual publication.

Closes #11

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[trissim]

Release-owner coordination: user has explicitly authorized ordinary dependency publication. Current merged source a01f893 is byte-equal to qualified90951 for src/pyproject. Original Hatch wheel and sdist rebuilt in an owned receiving snapshot; SHA256 exactly matches both qualified artifacts in this PR (524eb9a72d5e4620dbbea0336f8dd7d32583f687e64a3c954b10f83560e67be6 / 25f4b054e6ed92e4717514f8b8104abd31e83832a59389fdcfab939d783306bb). PyPI1.1.9 is absent, public v1.1.9 tag absent, and no current release claim/run found. Planck is coordinating the original publisher and taking the existing annotated-tag/trusted-publish.yml route pinned to the merged1.1.9 source, not current1.2.0 main. No shared environment or source version edits. Will report actual workflow and official registry wheel identity separately from local qualification.

[trissim]

Publication complete through the original trusted-publisher workflow: https://github.com/OpenHCSDev/ObjectState/actions/runs/37193097025 — SUCCESS. Public annotated v1.1.9 peels to exact merged a01f893. Official PyPI1.1.9 metadata and downloaded artifact bytes independently verified: wheel SHA256 524eb9a72d5e4620dbbea0336f8dd7d32583f687e64a3c954b10f83560e67be6; sdist SHA256 25f4b054e6ed92e4717514f8b8104abd31e83832a59389fdcfab939d783306bb. Both exactly match qualified90951 artifacts. No old tag/release overwrite, source-version changes or shared install. Persistent receipt: engineering-wholemain-after394-20261004/OBJECTSTATE119-PUBLICATION.json under the parent issue-batch root.