ci(python-gonol): provision pinned UCNS authority - #40
Conversation
|
@codex review Review exact head |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. 👍 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Exact main
198c9da486b6f7194f927f839c7040e8655973f9introduced the Python Gonol construct and left thepython-gonol / contractsgate red: all five tests failed before exercising construction because they require a Git checkout of the exact UCNS Public Gonol authority and CI supplied none.This repair changes only the owning CI boundary:
ucns@62e08ee1cf3b5d7b6e48c927b1047509e6328b5c;.ci/ucnswith persisted credentials disabled;UCNS_SOURCE_ROOTto the existing tests.No Python Gonol or UCNS semantics change, no authority transfer, no fallback checkout, and no weakening of exact Git/module/digest verification.
hmmm: this proves the CI host can supply the declared producer identity; it does not promote the Python Gonol candidate or resolve its deeper geometry.