Repository navigation
Conversation
ITSGJY
force-pushed
the
feat/project-build-direct-measured
branch
2 times, most recently
from
October 7, 2026 04:17
a69f9be to
002971f
Compare
ITSGJY
force-pushed
the
feat/project-build-direct-measured
branch
from
October 7, 2026 05:17
002971f to
44225ed
Compare
Owner
Author
|
Upstream submission yyjeqhc#960 has been merged. |
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.
Summary
project_buildlifecycle directly on the Adaptive Runtime surface at rank 94, immediately beforeproject_validateproject_build_v1Runner capability, Standard approval, authority, typed planning, durable Job identity, Runner-owned execution, andobserve_jobscontinuationMeasurement
Using the evidence discipline established by yyjeqhc#959, two fresh A/B pairs were run in opposite order with the same Codex Host, model, prompt, Runner, and Rust fixture. The comparison changed only model-facing exposure of the existing canonical build lifecycle.
read_tool_manifestx2 ->call_runtime_tool(project_build)project_buildcallInput-token and wall-time values are supporting observations for this fixed Host/task, not a general latency claim. The full method and evidence boundaries are recorded in
docs/experiments/project-build-direct-measurement.md.Contract
This is a model-facing discovery change. Build planning, Runner execution, authority, approval, Job identity, and result projection keep their existing canonical paths. Long builds remain the same durable Job, with
observe_jobsused for continuation; a pending result does not authorize retry or redispatch.Validation
webcodex-tool-contracts: 289 passedproject_buildcontinuation-guidance regression: passedcargo fmt --checkgit diff --check37575588180: success on44225edbba1b7fbb8e5f82f5048b6831678a770237575598119: success on the same headRelated to yyjeqhc#599.
Upstream submission: yyjeqhc#960.