Repository navigation
Publish UK Orrery graphs with the existing local build service - #1151
Merged
Merged
Conversation
This was referenced Oct 8, 2026
anth-volk
force-pushed
the
feat/minimal-orrery-publication
branch
3 times, most recently
from
October 9, 2026 15:40
6f93d06 to
79d1624
Compare
anth-volk
force-pushed
the
feat/minimal-orrery-publication
branch
from
October 12, 2026 12:13
79d1624 to
61fa608
Compare
A failed UK build now publishes its graph evidence to orrery-failure/ in the attempt evidence directory instead of the output directory, so an earlier successful bundle and its completion marker stay consistent. Interrupts keep local evidence and the queue entry without waiting for an upload or staging to Hugging Face, and a failure while saving evidence no longer replaces the build's own error. The graph worker survives local queue errors. A job whose preserved directory was removed stays pending with preserved_files_missing; the status file is written after the queue commit, and claims take the earliest-due job first. Remove the unused socket publication action, share origin validation with the collector, return typed collector credentials and graph finalization results, type the ORM publication columns, and replace private cross-module access with public accessors. Update the publication guide and add regression tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
anth-volk
force-pushed
the
feat/minimal-orrery-publication
branch
from
October 12, 2026 15:04
61fa608 to
95c4cc9
Compare
anth-volk
marked this pull request as ready for review
October 12, 2026 20:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1150
Publish completed UK build graphs using an independent durable worker in the existing local telemetry emitter service. This replaces #1148 and keeps the current embedded service layout; extracting delivery into the single
microcosm-emitterpackage is a separate draft change in #1153.UK full-build commands export recorded execution evidence, preserve an explicit public-file inventory, attempt authenticated immutable publication before Hugging Face artifact staging, and record graph/evidence files plus a publication receipt. Pending jobs survive unavailable credentials and process restarts independently of telemetry event retention. The retry command leaves the original Hugging Face receipt unchanged.
Use explicit inventory, receipt, artifact and staging-delivery contracts. The durable queue uses SQLAlchemy ORM and Alembic. Existing Hugging Face login supplies identity; this pull request adds no producer environment variables or secrets. Hosted publication still depends on the separately implemented collector and runs-app changes; this pull request does not certify or deploy those services.
Rebased the six publication commits onto current repaired
main. Already merged #1099/#1144 commits are not replayed. Preserve the updated UK engine floor, property-input changes and stricter native-evidence validation frommain; the only manual conflict resolution updates the approved digest to match the combined lockfile. Existing publication and lifecycle source behavior remains unchanged.Affected-only local qualification after this rebase:
The previous complete-suite results are historical and do not qualify this rebased tree. No full-suite rerun or queued-check monitoring was performed. No merge, package publication or hosted deployment is included.
Follow-up: microcosm-emitter #4, Microcosm #1153, and microcosm-runs #4. #1153 must wait for the single emitter distribution to be published, then replace its temporary source pin and regenerate the lockfile before merge.