Repository navigation
[docs] network-doctor: network-doctor: cite trusted-service and Foundry upstream provenance in NET-003 - #11576
Draft
github-actions[bot] wants to merge 1 commit into
Conversation
…ce in NET-003 Adds provenance for PR #11345 (trusted LLM service sidecar upstream, exact HTTPS/443 proxy-only) and PR #11363 (Azure Foundry target on the same exact custom-port sidecar ACL path) to NET-003. Generated consumers are intentionally not regenerated here; trusted CI or a reviewer runs diagnostics:render. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This branch has not been deployed
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.
Coverage (this run)
updatedSincecursors were not advanced by this PR; intake state is cache-managed, not edited here.no-impact/coveredreceipts for the reviewed PRs. PRs Add opt-in trusted LLM service routing and secret headers #11345 and Add isolated Azure Foundry provider for decision models #11363 are left pending until this PR's citation is publicly verifiable.Change (finding NET-003)
grepon exactapi_upstream_*ACLs; read-only, secret-safe)src/services/api-proxy-env-config.ts,src/trusted-service.test.ts).FOUNDRY_API_TARGETreaches the same exact custom-port sidecar ACL path.Verified against default-branch source:
resolveApiProxyUpstreamsemitsproxyOnlyupstreams for trusted services;generateApiProxyUpstreamSectionemits exact host/port ACLs for the sidecar source only. The agent allowlist is not widened.Expected-policy vs defect
Expected policy denial: agent-origin custom-port requests and non-443 trusted-service targets remain denied. No defect was found in the reviewed batch.
Not changed
src/squid/config-sections.ts,containers/agent/setup-iptables.sh,src/host-iptables-rules.ts.diagnosis-findings.md,diagnose-awf.md, prompt/agent surfaces) are not regenerated here.npm run diagnostics:checkreports them stale until trusted CI or a reviewer runsnpm run diagnostics:render.Validation
npm run diagnostics:validate: Registry valid (26 findings).npm run diagnostics:freshness --as-of 2026-11-14: no overdue records.core.hooksPath=/dev/nullfor this JSON-only edit.Attribution
Automation used by the Network Doctor Updater on behalf of reviewers. No auto-merge. Reviewer ownership:
@github/gh-aw-firewall-maintainers.