Fleet changelogs · dev.ecs0.net
rdmsm4x-changelog-20260828-1929-hyperfile-p1-peer-validation-test-quality-followup

rdmsm4x-changelog-20260828-1929-hyperfile-p1-peer-validation-test-quality-followup

Bounded test-quality follow-up: committed PID propagation coverage for the HyperFile privileged-helper peer validator, so both accepting and rejecting paths prove the original XPC client PID and the shared code-signing requirement are forwarded exactly once.

Scope

Changed file

No production helper code, project generator spec, generated Xcode project, entitlement, signing, helper registration, helper installation, launch, deployment, iOS, or MCP configuration was changed.

Test-first evidence

  1. Before the fake recorded PIDs, the focused unsigned test command executed 2 tests and failed both exact PID assertions: observed [] rather than [73731] and [42424].
  2. After the test-double-only repair, the following passed:
xcodebuild -project HyperFile.xcodeproj -scheme HyperFileHelperPeerValidationTests -destination 'platform=macOS' CODE_SIGNING_ALLOWED=NO test
# 2 tests, 0 failures; TEST SUCCEEDED

xcodebuild -project HyperFile.xcodeproj -scheme HyperFile-macOS -destination 'platform=macOS' CODE_SIGNING_ALLOWED=NO build
# BUILD SUCCEEDED

xcodebuild -project HyperFile.xcodeproj -scheme com.eastcoastscience.HyperFile.Helper -destination 'platform=macOS' CODE_SIGNING_ALLOWED=NO build
# BUILD SUCCEEDED

git diff --check
# passed

xcodegen generate --use-cache
# HyperFile has not changed since cache was written

The SHA-256 digest of the isolated HyperFile.xcodeproj file tree was unchanged before and after XcodeGen: df06baf3c5149d75d76dea8cfeccec397c6815c6a1d0a9dadb29c7d211c3067c.

Rollback and outstanding owner action