Represent deployed builds and deployment evidence on tasks - #666
Merged
Merged
Conversation
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
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.
Tasks can now identify the deployed build that delivers their work, inspect deployment attempts and status receipts, and select a verified deployment as the current work product. The implementation adds separate build/deployment/observation concepts, canonical task links, authenticated receipt ingestion and traversal APIs, and task-panel history. Identical retries reuse records; conflicting evidence is rejected; rollback preserves attempt history.
The producer contract and scoped vocabulary activation procedure are documented in
docs/engineering/deployment_evidence.md. Recording evidence does not deploy code or complete tasks; future producers explicitly submit receipts.Validation:
Explicitly authorised DGX deployment completed at 2026-09-13T16:06:35Z on merge revision 30dc27b. Local and authenticated Cloudflare health agreed on PID 2777950; runtime was clean, database/worker/scheduler ready, and served taskPanel.js/styles.css matched. The database target and Jira migration service were preserved. Scoped vocabulary and the first real production receipt were canonically read back, including idempotent retry and the task's selected deployment work product. The unchanged startup workflow-purity advisory remains non-blocking.
Von task #V#task_agent_8f35430789702d95864e5def732c43cd is completed. Production deployment record: #V#deployment_50975745e20a5711195792dea8e1605762796e525b8851825030a83790faa845. Operator evidence is retained outside Git under /home/mjw/.codex-von-worker/build-tracking-acceptance-20260913/. The temporary acceptance server has been stopped.