DevBerth v0.1.11

What changed

#35 — Fix managed launch fingerprint stabilization

What changed

• retain a strong post-spawn fingerprint candidate across intermittent incomplete ps/lsof observations
• continue resetting the candidate whenever a conflicting strong fingerprint is observed
• add regression coverage for alternating strong and incomplete samples
• document the control-authority rule in repository guidance and architecture notes

Why

The npm-managed analytics dashboard failed twice during project startup because an incomplete fingerprint inspection was treated as evidence that the process identity had changed. That reset the bounded stabilization window even though later strong observations were mutually identical.

Impact

Script launchers can complete registration despite intermittent incomplete process-path samples, while PID-reuse and executable-replacement protection remains intact. DevBerth still requires nine mutually identical strong observations and refuses any conflicting strong fingerprint.

Validation

• ProcessGroupTests: 10/10 passed
• fresh DerivedData full scheme: 219/219 passed; 0 failures, skips, or expected failures
• Scripts/build-and-install-app: installed matching Release app and MCP helper successfully
• note: shared DerivedData initially produced unrelated stale-host failures; both affected tests passed from clean DerivedData, and the final full clean run passed

Release provenance

• Merge commit: e11d6329f4147e9de9193d3a664944283ef4c1f3
• Pull request: #35
• Compare v0.1.10...v0.1.11

This is a source-project release. It does not include a signed or notarized app binary.