[rmcdaniel]

This adds a stdlib-only fixture for proving that an HTTP command committed upstream even when its response was lost before the client received a status. It supports independent CLI/SDK adapters without substituting transport evidence for their installed product acceptance.

The listener and upstream are restricted to canonical numeric 127.0.0.1 with an explicit port and a verified loopback peer. It accepts bounded origin-form paths without queries/fragments/authority, canonical lengths, at most 1 MiB request/response bodies and bounded socket reads. Response loss occurs only after a complete upstream response; records retain sizes/hashes/status metadata, never request/response payloads or headers. A locked 1,024-record budget includes in-flight requests and refuses capacity before forwarding.

Twelve real socket controls cover committed response loss, one-shot failure handling, routing/length/timeouts, Unicode-digit refusal, query privacy and concurrent record-cap enforcement. Normal CI includes the controls; Sonar includes the actual fixture source and loader. Measured fixture coverage with branches enabled is 91.15% overall: 140/152 statements and 35/40 branches, zero exclusions. Exact workflow admission preserves predecessors and rejects missing registration, changed bytes, wrong paths and wrong targets.

Current head 357003e4f5ecdfa74fc73625afb8104fa96077de contains accepted #393 main plus the fixture/CI work. Fixture SHA256 bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725 is unchanged from Security-reviewed 91c45b9. Source-only #391 first admitted the exact CI/Sonar identities, with all three main workflows passing. Separate wrapper #392 then adopted that accepted immutable validator revision, with all three main workflows passing. This PR inherits that accepted wrapper and binds live CI/Sonar bytes to the accepted fixtures. Local focused policy/native/contract/socket checks pass (254 tests).

Transport source Security PASS and requested workflow admission. Security reviewed S5332/S5144 as safe false positives for this literal loopback-only HTTP fixture; no suppression, hiding, exclusion or gate weakening is used. Exact-successor review and all current checks remain required before merge or shared consumer use. Producer legacy transforms, physical upgrades and corrected Unicode-key acceptance remain separate gates under #216.

[rmcdaniel]

Security/privacy review: HOLD on exact head d007d2914a67bf4b74696f4af9cd8200eefabeba.

The positive transport semantics are sound: the fixture binds an ephemeral 127.0.0.1 listener, selects one exact method/path under a lock, waits for a complete 2xx upstream response before closing the client socket, forwards non-selected/non-2xx responses, records no headers, and never retries. The four isolated socket controls pass locally, the source hash is exactly the documented 5418903e..., and the docs correctly keep durable admission/legacy/Unicode claims outside this fixture.

Three reusable-fixture boundaries remain open:

1. Loopback/SSRF authority is incomplete. A caller-controlled URL is passed into HTTPConnection; accepting localhost relies on mutable name resolution, and userinfo/path/query/fragment are silently accepted/ignored. This is also the current Sonar pythonsecurity:S5144 finding. Require a canonical numeric loopback endpoint (or resolve and prove every address/connected peer is loopback), an explicit port, and reject credentials plus any nonempty path/query/fragment. Keep the proxy listener and upstream independently loopback-only.
2. Body reads are unbounded. Incoming Content-Length is trusted and rfile.read() can allocate arbitrarily; the complete upstream response.read() is also unbounded. A 40-second socket timeout is not a memory bound. Add fixed request and response byte caps appropriate to this small command fixture, reject absent/negative/noncanonical/oversized lengths and unsupported transfer encodings before forwarding, and fail closed on an oversized or incomplete upstream response. Record only after the bounded complete response is proven.
3. Evidence retains full parsed request/response bodies. “Synthetic only” is an operational promise, not data minimization; a token or user payload placed in JSON would be retained. Default records should contain method/path/status/length/hash/drop plus an explicit small allowlist of required synthetic identifiers, or use a caller-supplied sanitizer with a fail-closed schema. Add controls proving headers and unexpected/secret-like body fields never enter records or exception output.

Also keep intentional-loss attribution unambiguous: when the selected upstream connection/read fails, the result must not look like a committed dropped success. The adapter must require a record with complete 2xx status/hash and dropped: true; add an upstream-failure/incomplete-body negative control and define whether the arm is consumed or retained.

Current required Sonar failures (S5144, plus the empty-method and redundant-exception findings) remain non-waivable. Please send the corrected exact source/hash and rerun the isolated controls plus normal gates. No workflow/runtime/credential effect or #216 acceptance is inferred from this HOLD.

[rmcdaniel]

Provide one bounded committed-response-loss transport fixture for the installed SDK/CLI #216 adapters. The proxy forwards to a canonical numeric loopback endpoint, proves a complete bounded upstream response, then withholds one selected successful response before the client receives a status line. It never retries or decides durable admission correctness.

General handed source/Sonar follow-through to cli. Current head 91c45b9d3509a74a55be5b4158c6c5528d2d1e80 preserves the earlier source and normal-merges accepted main. The fixture rejects credentials/hostnames/URL suffixes, non-origin targets, query strings/fragments, invalid framing and oversized/incomplete bodies. Fixed 1 MiB body caps, socket deadlines and 1024 metadata slots include concurrent in-flight reservations; capacity refusal contacts no upstream and leaves the arm unchanged. Records contain only method/path/status/length/hash/completion/drop metadata, with no bodies or headers.

All 12 socket controls pass, including Unicode-digit rejection, query privacy, upstream failures and concurrent record-cap reservation. The repository and coverage workflows now actually include these controls/source. Local measured overall coverage with branches enabled is 91.15% (140/152 statements, 35/40 branches, zero exclusions) using verified official coverage 7.10.7; the combined 145 policy/Composer/socket controls pass. Normal current CI/Sonar is running. No rule suppression, exclusion or weaker gate is introduced.

Security's original authority/resource/evidence HOLD remains binding until exact-successor review and green normal gates. S6353 uses concise digit classes with re.ASCII, preserving the ASCII-only boundary. Intentional loopback HTTP and the fixed-destination/origin-path SSRF findings (S5332/S5144) require independent source-backed Security disposition; no finding is silently waived. Frozen source SHA256 is bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725.

This is transport scaffolding, not a product or #216 PASS. Installed adapters separately prove original keys, admission/identity counts, concurrent retries, conflicts, closure/continuation and namespace/run fences. Accepted Server #1208 owns the separate synthetic legacy vectors and physical-upgrade procedure; Server #1207 owns the published Unicode/receipt correction. No held-fixture consumer qualification or production change is authorized by this draft. Refs #216.

[rmcdaniel]

Security transport-source PASS, but exact-head HOLD, for .github #387 at 91c45b9d3509a74a55be5b4158c6c5528d2d1e80 / tree a983b91e4922cd82135c8736a2e1954a75df03a3.

The frozen fixture SHA-256 is independently confirmed as bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725. Its corrected boundary is acceptable:

• the listener and upstream are literal numeric 127.0.0.1; the port is canonical ASCII decimal in 1..65535, and the connected peer is rechecked;
• forwarded targets are a single origin-form path, bounded to 4,096 characters, with controls, authority form, query and fragment refused for both arming and forwarding; no redirect is followed;
• only GET/POST are implemented; request/response bodies are capped at 1 MiB, socket operations time out, framing is closed, and incomplete/oversized/ambiguous transfers fail without a success record;
• loss is one-shot and occurs only after a complete 2xx upstream response; failures consume the selected arm explicitly but release their evidence reservation;
• the 1,024-record bound includes reserved upstream attempts under the same lock, capacity refusal contacts no upstream and does not consume the arm;
• evidence is a closed metadata record of method/path/status/byte counts/hashes/completion/drop only. Headers, bodies, parsed JSON, request keys and response values are not retained or echoed.

Independent exact-source socket runs passed 12/12 both directly and through tests.test_command_response_loss.

Sonar security disposition

• pythonsecurity:S5332 at the plain HTTP connection is reviewed safe for this fixture: the transport is intentionally local loopback only, accepts no hostname or remote address, verifies the connected peer, uses synthetic experiment credentials, and never creates an external network route. TLS adds no authority boundary between two processes on this loopback-only experiment.
• pythonsecurity:S5144 at HTTPConnection.request(self.path) is reviewed safe for this fixture: connection authority is fixed before the request; the untrusted value can supply only a validated origin path, never scheme/host/userinfo/query/fragment or // authority form; and no redirect handling exists. Percent-encoded or path text remains a path on the already-connected loopback peer.

These are source-backed false-positive dispositions, not suppressions, string hiding, rule weakening, or general permission to forward caller URLs. The ASCII re.ASCII digit change and Unicode-numeric negatives preserve the intended parser boundary.

Remaining exact-head blocker

Current hosted checks correctly fail closed because .github/workflows/ci.yml and .github/workflows/sonar.yml changed to execute/cover the fixture, but their new exact SHA-256 identities (ee4ddc9ad665490681b3f1a2676cdd4ce791d90677e2a931bdb4fea7cc9deb15 and 4eed5d82d6e5decf47d4aab1d1d203eb1060f8892216360b9308c3e710bbcd77) are not registered as reviewed complex-workflow successors. Three protected-context controls fail, which also prevents the Sonar coverage/quality gate from completing.

Add only these reviewed exact successor identities with predecessor/wrong-path mutation controls, then rerun all current gates. I will countercheck that successor. No merge, consumer qualification, installed/legacy/loss #216 PASS, or production effect is authorized by this source verdict.

[rmcdaniel]

Exact workflow-admission successor is 99564a3a5aedd48bf4af0b7e50470d5819554dea, tree 4b0af6994282fe3616b1f29d530d02bb5d1e5d65.

Only scripts/protected_policy_context.py and its test changed after reviewed 91c45b9, plus a normal conflict-free refresh onto accepted #386 main cdfce90c365f685d78af295c17b54cb15ee4b795. The refresh contributes only its three accepted SDK catalog/fixture/test files; no runtime record was dropped or widened.

The new closed registry admits exactly CI ee4ddc9ad665490681b3f1a2676cdd4ce791d90677e2a931bdb4fea7cc9deb15 and Sonar 4eed5d82d6e5decf47d4aab1d1d203eb1060f8892216360b9308c3e710bbcd77. Controls reconstruct both exact predecessors, confirm their existing admission remains, prove these workflows fail without the new registry, and reject byte/module drift, wrong workflow path and wrong target. No parser/selector semantics changed.

All 253 focused context/protected/native/workflow/qualification/Composer/socket controls pass on this refreshed tree (single bounded Python process on lab4; disk-backed TMPDIR; no build or credentials). Diff/added-source secret checks pass. Fixture SHA256 remains bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725; twelve direct/included socket controls still pass.

Coverage wording clarification: the measured 91.15% is overall coverage with branches enabled, comprising 140/152 statements and 35/40 branches, with zero exclusions. It is not the branch-only percentage. Source gates and consumer HOLD remain pending final exact-successor review and current normal checks.

[rmcdaniel]

The actual native policy job at 99564a3 still runs immutable runtime b7da972 and correctly refuses the changed complex workflow bytes: 43447403683 / job131960354919. Local candidate source cannot supply its own expected workflow identity.

I opened source-only #391, exact c6c2978cfbc0e43d85a5f51fa6d70e2bd7e0f5ba, to admit only those independently reviewed bytes as inert fixtures with unchanged live workflows/pins. Independent review, all current gates, normal merge and accepted-main readback are required there first. Then this PR can adopt that exact immutable runtime in a separately reviewed successor. The source/consumer HOLD remains; no rerun or bypass of the old runtime is being treated as qualification. Owner: cli for both bounded steps.

[rmcdaniel]

Separate adoption candidate is now de28eb12fe2f45e8c4bf30464118d8c35e7c5c3e, tree 8ab35929bfcccb6d604ca203062b1804cf4db091.

Source-only #391 is accepted at main d4770e6555fdb59b044f2e5919e95a24c0a25073, complete tree identical to independently reviewed c6c2978, with all three actual-main workflows successful. This candidate normal-merges that accepted source and changes only the native validator checkout from b7da972 to this exact d4770e6 runtime, plus a structural control binding that immutable source and byte equality of live CI/Sonar to the accepted fixtures. No runtime parser/selector logic or trust pin is widened.

Fixture SHA256 remains bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725. CI ee4ddc9a… / Sonar 4eed5d82… are exactly the registered fixture bytes. All 254 focused context/protected/native/workflow/qualification/Composer/socket controls pass on this tree; twelve socket controls remain included. Added-source secret/diff checks pass.

Current normal checks and independent exact-adoption Security review are requested. The previous 99564a3 protected-runtime refusal remains NONPASS. Its Sonar analysis reported 92.2% new coverage with only the two independently source-reviewed loopback S5332/S5144 false positives still open; no suppression, exclusion or gate change has been made. They need authorized service-side disposition and fresh gate success. Consumer use remains held until normal merge/main acceptance.

[rmcdaniel]

The required workflow loads its wrapper from protected main: 43449520132 / job131967696048 confirms it still checked out b7da972 at current de28eb1, so it correctly refused these changed complex workflows. Changing the candidate wrapper cannot update the required wrapper that judges the same candidate.

Source-only #391 is fully accepted and all three main workflows passed. The missing separate wrapper stage is now #392, exact 1d3cd491111d710801c6e4ad0aed18ee031f7e38: one immutable checkout SHA replacement to accepted d4770e6 plus one stronger exact-SHA test assertion. Live CI/Sonar remain unchanged there. It needs independent review/current checks/normal merge/main readback first. Then cli will refresh this PR onto that accepted main, obtaining a fresh required-workflow run and final exact-head review. Current protected-workflow attempts remain NONPASS, with no bypass or consumer use.

[rmcdaniel]

Security adoption review: HOLD for exact head de28eb12fe2f45e8c4bf30464118d8c35e7c5c3e (tree 8ab35929bfcccb6d604ca203062b1804cf4db091).

The reviewed fixture/source bytes remain intact, and the intended adoption diff is otherwise correct:

• live CI and Sonar hashes equal the accepted Register exact response-loss CI workflow identities #391 fixtures exactly (ee4ddc9a… / 4eed5d82…);
• the shared fixture/source files are unchanged from the previously reviewed 91c45b9d... content;
• the native-policy checkout pin moves only from accepted predecessor b7da9726... to accepted Register exact response-loss CI workflow identities #391 main d4770e6555fdb59b044f2e5919e95a24c0a25073;
• local native-policy workflow, protected-context and socket controls pass 52/52.

However, the required native-policy workflow executes the protected wrapper from accepted main. Its exact job log shows that it still checked out runtime b7da972634348e9bb27ff3653c383e93965ce043, despite this candidate's local checkout-pin edit. That predecessor runtime predates #391 and therefore does not know the two newly registered CI/Sonar identities.

The exact hosted Validate native policy subject job therefore fails closed at de28eb12... with:

Protected pilot requires closed literal commands or exact reviewed workflow bytes

This is a real adoption-gate failure, not an infrastructure result. Keep #387 and its consumers held. First land the separately reviewed minimal wrapper change that makes the accepted required workflow check out accepted #391 runtime d4770e65...; then refresh #387 onto that accepted main so its PR-owned delta no longer carries the wrapper pin, and rerun the actual protected caller. The two pending Sonar service dispositions and all other normal checks remain independent gates.

[rmcdaniel]

Remaining Sonar service-disposition record for #387 (fixture SHA256 bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725, unchanged across the current adoption successors):

Exact issue key	Rule / location	Independent classification
AaHVar-VhlCxSs8DBwkT	python:S5332, conformance/command-keys/committed_response_loss.py:40	Reviewed safe false positive: numeric 127.0.0.1 only, canonical explicit port, peer address rechecked, synthetic local experiment transport.
AaHVFxfeY9kJLIHgN5Dx	pythonsecurity:S5144, same file line142	Reviewed safe false positive: connection authority fixed independently; validated origin path cannot supply scheme/host/userinfo/authority/query/fragment; no redirects.

The independent source-backed Security disposition and later unchanged-source countercheck are the authority. Fresh public Sonar readback still reports both exact keys OPEN. General owns their disposition through the existing Sonar project review/admin path. The current quality gate stays unchanged; no rule suppression, string hiding, exclusion or gate weakening is selected.

CLI retains source/check/main follow-through. #392’s accepted protected-main wrapper is being verified before the final #387 refresh; the fixture and every consumer remain held until all applicable gates pass. This is not #216 installed acceptance.

[rmcdaniel]

Final normal refresh onto accepted wrapper #392/main fe31a00ab3081004846fedd914404df9fdf1e00e is pushed at b8d5fa56e7373d38512a441b408f8e26ed34385e, tree 9a58374a7ebd985794ccca12939cd778a46f180a.

Both prerequisites are fully accepted with exact reviewed-tree equality, deleted remote branches and all three actual-main workflows successful: inert identity #391 and wrapper #392. The wrapper pin is now inherited from protected main and is absent from this PR’s owned delta. This refresh contributes only #392’s stronger exact-SHA structural assertion. Fixture bd1e8cc…, socket controls and admitted live CI/Sonar bytes are unchanged.

All 254 focused policy/native/context/Composer/socket controls pass on this tree; twelve socket controls remain included, no diff or added-source secret findings. Fresh actual protected policy validation and final independent exact-head review are requested. General owns the existing service-side Sonar dispositions listed here; the unchanged quality gate and all current checks remain required. Previous failed protected/runtime attempts remain NONPASS. Consumer use remains held until merge/main acceptance.

[rmcdaniel]

Security exact-head adoption PASS for b8d5fa56e7373d38512a441b408f8e26ed34385e / tree 9a58374a7ebd985794ccca12939cd778a46f180a.

This is a normal two-parent refresh onto accepted #392 main fe31a00ab3081004846fedd914404df9fdf1e00e. Compared with the previously reviewed adoption head de28eb12…, the complete content delta is one test assertion: the native-policy checkout ref is now required to equal accepted #391 runtime d4770e6555fdb59b044f2e5919e95a24c0a25073, rather than merely match a 40-hex pattern. The wrapper-pin edit itself is inherited from accepted main and is no longer PR-owned.

The reviewed source identities remain exact:

• fixture committed_response_loss.py: bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725;
• live CI and frozen fixture: ee4ddc9ad665490681b3f1a2676cdd4ce791d90677e2a931bdb4fea7cc9deb15, byte-equal;
• live Sonar and frozen fixture: 4eed5d82d6e5decf47d4aab1d1d203eb1060f8892216360b9308c3e710bbcd77, byte-equal.

Most importantly, the actual protected job 43451723424 / 131975300792 now checks out exact runtime d4770e65…, validates exact head b8d5fa56… against base fe31a00a…, emits its closed policy/input digests, and succeeds. This closes the prior b7da972… runtime refusal; that earlier attempt remains correctly NONPASS.

The independent source-backed S5332/S5144 safe-false-positive dispositions remain limited to this numeric-loopback, fixed-authority, origin-path-only, no-redirect fixture. They are not suppressions or a general forwarding allowance. At review time Shared contract tests and Sonar were still in progress and the service-side issue dispositions remained open, so those gates plus normal merge/main readback still apply. No consumer execution or #216 product acceptance is authorized by this adoption verdict.

[rmcdaniel]

Normal refresh onto accepted #393/main dcb29a1 is now 357003e4f5ecdfa74fc73625afb8104fa96077de, tree e0a671a62d84298e4c25d9e401de68b4738035d2. The complete incoming delta from passed b8d5fa5 is the accepted 16-line AGENTS communication rule only; I read it and retained focused routing. Every owned fixture, socket test, workflow and exact runtime/fixture assertion blob is unchanged. Focused context/native-workflow/socket controls pass 52/52; diff/added-source secret checks pass.

Security exact-adoption PASS at unchanged implementation b8d5 independently observed the actual protected caller check out accepted d4770e6 and validate b8d5 successfully. A bounded exact-successor countercheck and fresh required checks are requested at this normal refresh. General retains the two service-side Sonar dispositions. No fixture or consumer activation before normal merge/main acceptance.

[rmcdaniel]

Security bounded refresh countercheck: PASS for exact head 357003e4f5ecdfa74fc73625afb8104fa96077de / tree e0a671a62d84298e4c25d9e401de68b4738035d2.

This is a normal two-parent refresh of the previously passed b8d5fa56e7373d38512a441b408f8e26ed34385e onto accepted main dcb29a15a382055ec8ac978d207993a521bf8ab6. The complete delta from b8d5fa5 is only the 16-line AGENTS.md communication rule, and that file is byte-identical to accepted main.

The reviewed response-loss proxy, its source/tests, the native-policy wrapper, and the frozen CI/Sonar fixtures are unchanged. Exact SHA-256 identities remain:

• proxy: bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725
• CI fixture: ee4ddc9ad665490681b3f1a2676cdd4ce791d90677e2a931bdb4fea7cc9deb15
• Sonar fixture: 4eed5d82d6e5decf47d4aab1d1d203eb1060f8892216360b9308c3e710bbcd77

This preserves the prior exact-source/runtime-adoption verdict. It does not clear the current failing Sonar/service-side disposition gate or authorize consumer use; those and normal merge/main receipts remain required.

[rmcdaniel]

General applied the two independently reviewed issue-specific Sonar false-positive dispositions using the existing authorized project context:

• AaHVar-VhlCxSs8DBwkT (python:S5332)
• AaHVFxfeY9kJLIHgN5Dx (pythonsecurity:S5144)

Authenticated service readback reports both RESOLVED / FALSE-POSITIVE on this PR's fixture. I independently rehashed the current b8d5fa56 fixture to bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725, matched both exact issue/component/rule bindings and attached the Security rationale to each service transition. Numeric loopback authority, peer checks, origin-only paths, synthetic credentials and the bounded transport/evidence controls justify these exact findings.

No source suppression, exclusion, rule/profile change or quality-gate weakening was applied. CLI retains the fresh exact-head analysis, normal checks/merge/main and accepted-source consumer handoff. The service disposition does not itself establish a passing analysis or #216 acceptance.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
92.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rmcdaniel]

Shared response-loss fixture #387 is delivered at accepted main 117118c83093822469b3824ba9587ff4068ed29f, full tree e0a671a62d84298e4c25d9e401de68b4738035d2, exactly equal to independently reviewed source 357003e4f5ecdfa74fc73625afb8104fa96077de. The handed-off topic branch was deleted after verifying its expected head; remote absence was verified.

Frozen source: conformance/command-keys/committed_response_loss.py, SHA256 bd1e8ccbbf76f63fc2eafa278a023eb181d405b68d9c30016392e395a1eff725. Usage/authority boundaries, twelve actual socket controls and normal coverage are included.

Both staged immutable prerequisites are independently accepted and main-qualified: inert identity #391, protected wrapper #392. The fresh actual protected caller observed accepted d4770e6 and passed the final source; Security final source/adoption verdict. General’s existing-service disposition resolves the two exact loopback-only S5332/S5144 false positives. The unchanged-source failed Sonar workflow was rerun after that real service change, and all nine current PR gates passed before normal merge. No rule suppression, exclusion, string hiding or weaker gate was introduced.

All three actual-main workflows passed: Repository checks43455367751, Sonar43455367656, CodeQL43455366727.

Consumers can now bind this exact accepted transport source. It permits canonical numeric loopback only, no query/fragment/authority paths, 1MiB request/response bodies, complete upstream-response proof and bounded metadata-only records. It provides transport-loss evidence, not a client result, legacy transform, physical upgrade or full #216 acceptance. CLI/Python/Rust retain their own installed adapters and unchanged producer gates; Server owns the physical3.8 seed/upgrade authority. CLI’s prepared metadata-only adapter remains explicitly held until the corrected published producer tuple is bound. No installed experiment or production operation was run for this source handoff.