Field note /
Separate acceptance after a merged change
Codebase Memory CLI PR #20 tracked the revision, test environment, regression result, workflow result and acceptance on the host as separate facts.
How the finding changed
Belief
A merged change with passing targeted regressions and a successful targeted CI run could be called validated.
Evidence
The PSR-4 (PHP autoloading) regression tests passed in the GitHub run on the final revision, and a targeted Jenkins CLI build succeeded on an earlier revision.
Contradiction
The enclosing GitHub run on the final revision failed, the full Jenkins gate failed on a different revision, and a worker's report and process exit still did not satisfy host verification.
Correction
Record the checked-out revision, tested revision, test environment, regression result, enclosing workflow result, worker completion and acceptance on the host as separate facts.
Current claim boundary
PR #20 merged and the specific regressions passed. That does not show a fully green test matrix on the final revision, an accepted Agent Run or a root cause for the transport problem.