gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-10-27 05:57:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Isolate lock-evidence fixture keys without clearing guest fences

Browse Source 
Retained full-suite proof reports an inherited agent-cooldown before the invalid-UTF8 lock case dispatches any command. Give each synthetic case a distinct base path, keeping all clients in that case on its shared key. A same-listener control retains the prior uncertainty fence unchanged. No runtime guest guard, native target or assertion is weakened.

Change-source: pulse-maintainer
This commit is contained in:
pulse-triage[bot]
2026-10-14 14:47:17 +01:00
parent 5b895ff78e
commit 757acf055e
3 changed files with 66 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/release-control/v6/internal/subsystems/monitoring.md
+6
View File
@@ -69,6 +69,12 @@ criterion. It records elapsed time and both targets' request counts; unchanged
pin, admission and routing assertions remain required. Runtime timeouts and
separate timeout/cancellation controls are unchanged. This is not a diagnosis
or dismissal of the retained earlier one-second timeout.
Lock-evidence fixture cases use independent base-path namespaces while each
case's clients share the same guard key. A recycled loopback port cannot inherit
an earlier synthetic guest's cooldown. `TestGuestAgentLockEvidenceFixtureIsolation`
shares one listener and retains an earlier uncertainty fence unchanged while an
independent fixture completes its lock/command checks. No runtime fence is
cleared, expired or weakened; native guest recovery is not established.
This establishes source/consumer behaviour, not native recovery or attribution
of a guest, PBS or certificate report.
docs/release-control/v6/internal/subsystems/security-privacy.md
+6
View File
@@ -70,6 +70,12 @@ criterion. It records elapsed time and both targets' request counts; unchanged
pin, admission and routing assertions remain required. Runtime timeouts and
separate timeout/cancellation controls are unchanged. This is not a diagnosis
or dismissal of the retained earlier one-second timeout.
Lock-evidence fixture cases use independent base-path namespaces while each
case's clients share the same guard key. A recycled loopback port cannot inherit
an earlier synthetic guest's cooldown. `TestGuestAgentLockEvidenceFixtureIsolation`
shares one listener and retains an earlier uncertainty fence unchanged while an
independent fixture completes its lock/command checks. No runtime fence is
cleared, expired or weakened; native guest recovery is not established.
This establishes source/consumer behaviour, not native recovery or attribution
of a guest, PBS or certificate report.