[GH-ISSUE #56] Replace temporal Hopper cleanup with explicit process ownership #43

New issue

Closed

opened 2026-10-15 18:20:24 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:20:24 +00:00

Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/56

Problem

Verifier cleanup based on processes appearing after a snapshot can terminate an unrelated Hopper instance launched concurrently.

Outcome

Own and clean up Hopper through explicit run IDs, PIDs, parentage, and process groups.

Scope

Generate a verifier/session run ID.
Record the exact launched PID and descendant lineage in an owned manifest.
Verify command identity and parentage before signaling.
Ask normal runtime shutdown to clean up first.
Escalate only within the owned process group.
Verify socket, process, and temporary-root cleanup.
Preserve bounded sanitized diagnostics.

Acceptance criteria

An unrelated concurrently launched Hopper process survives success, cancellation, timeout, verifier failure, and forced cleanup tests. Missing or stale ownership metadata fails closed. Cleanup is idempotent and cannot target PID reuse without identity validation.

Dependencies

Parent: #48. Blocks trustworthy semantic conformance.

Non-goals

General system-wide process management.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/56 ## Problem Verifier cleanup based on processes appearing after a snapshot can terminate an unrelated Hopper instance launched concurrently. ## Outcome Own and clean up Hopper through explicit run IDs, PIDs, parentage, and process groups. ## Scope - Generate a verifier/session run ID. - Record the exact launched PID and descendant lineage in an owned manifest. - Verify command identity and parentage before signaling. - Ask normal runtime shutdown to clean up first. - Escalate only within the owned process group. - Verify socket, process, and temporary-root cleanup. - Preserve bounded sanitized diagnostics. ## Acceptance criteria An unrelated concurrently launched Hopper process survives success, cancellation, timeout, verifier failure, and forced cleanup tests. Missing or stale ownership metadata fails closed. Cleanup is idempotent and cannot target PID reuse without identity validation. ## Dependencies Parent: #48. Blocks trustworthy semantic conformance. ## Non-goals General system-wide process management.

bsakaguchi

2026-10-15 18:20:24 +00:00