Direct user requirement
Noema, Strix and OpenCode Review must obtain inference from https://litellm.poinnetworks.net on personal S1 (192.168.68.3), with a newly issued service key transferred directly into central GitHub Actions Secrets. The user reconfirmed the instruction and explicitly ordered implementation on2026-10-02. This is not the separate company HC/TNS issuance task.
Verified gap
Protected central main37b10243 still boots the runner-local provider-discovery sidecar. Repo5/org14 inference Secret metadata does not show an adopted personal gateway credential. Existing PR#1963 is a generic empty released-adapter port, not an implemented transport or personal endpoint deployment. Existing CLI smoke and server success counts do not prove CI use.
Current execution owner and boundaries
Hermes writing-skills integration owner holds the owned additive central checkout and implements a tested authenticated loopback relay to the exact fixed HTTPS API. The three consumer bootstrap steps use dedicated LLM_GATEWAY_API_KEY and explicitly verified LLM_GATEWAY_MODEL rather than vendor-key forwarding. Key generation remains serialized after exact existing-writer/in-flight checks; no provider/master keys may appear in chat/logs/artifacts. Legacy caller alias is compatibility naming, never free/ZDR attestation. Private data remains closed without actual retention evidence.
Acceptance
- real relay HTTP/JSON schema/tool/stream tests and full source/credential safety verification;
- one model-restricted non-admin key and direct, verified central Secret custody;
- authenticated actual-model calls through the named public TLS endpoint;
- complete local gates, independent current-head review, normal protected PR integration;
- actual Noema verdict publication, Strix report and OpenCode review receipt on current target head.
Missing keys/models and upstream failure must fail closed without silently reviving the old route. Reviewer identities, head/source binding, TLS/redirect protections and substantive independent verdicts remain mandatory. No skip, synthetic status or bypass counts as completion.
Related to #1963 and #2165. Gap CONTROL-PERSONAL-LITELLM-REVIEW-01. No merge or deployment is claimed.
Direct user requirement
Noema, Strix and OpenCode Review must obtain inference from
https://litellm.poinnetworks.neton personal S1 (192.168.68.3), with a newly issued service key transferred directly into central GitHub Actions Secrets. The user reconfirmed the instruction and explicitly ordered implementation on2026-10-02. This is not the separate company HC/TNS issuance task.Verified gap
Protected central main37b10243 still boots the runner-local provider-discovery sidecar. Repo5/org14 inference Secret metadata does not show an adopted personal gateway credential. Existing PR#1963 is a generic empty released-adapter port, not an implemented transport or personal endpoint deployment. Existing CLI smoke and server success counts do not prove CI use.
Current execution owner and boundaries
Hermes writing-skills integration owner holds the owned additive central checkout and implements a tested authenticated loopback relay to the exact fixed HTTPS API. The three consumer bootstrap steps use dedicated LLM_GATEWAY_API_KEY and explicitly verified LLM_GATEWAY_MODEL rather than vendor-key forwarding. Key generation remains serialized after exact existing-writer/in-flight checks; no provider/master keys may appear in chat/logs/artifacts. Legacy caller alias is compatibility naming, never free/ZDR attestation. Private data remains closed without actual retention evidence.
Acceptance
Missing keys/models and upstream failure must fail closed without silently reviving the old route. Reviewer identities, head/source binding, TLS/redirect protections and substantive independent verdicts remain mandatory. No skip, synthetic status or bypass counts as completion.
Related to #1963 and #2165. Gap CONTROL-PERSONAL-LITELLM-REVIEW-01. No merge or deployment is claimed.