molluskandClaude Fable 5 b9803f93fb core: retire the share at Join's session teardown, not after ticket parse ...

Gemini's review of the S2 branch found the one hole the harness had not
covered (P2, verified reachable): Join tears the old session down —
deliberately killing the share host — BEFORE validating the ticket, and
an invalid ticket exits the arm early, skipping the late
`current_sharing = None`. The killed host's stdout EOF then passed the
staleness gate and the user got a spurious "Screen share ended
unexpectedly" on top of "invalid room ticket". Pre-S2 the stale value
was toothless on this path; the fault handler gave it teeth.

The share now dies where the session does: cleared unconditionally right
after the teardown block, ahead of every early exit. The live gate grew
a third half — share, Join with a garbage ticket, then require silence
after the ticket error — and the mutant restoring the old placement is
killed by exactly that assertion (spurious re-emitted ScreenShareStopped).

Also Gemini's P3: the test's temp dir is now dropped by a guard, so an
assertion panic no longer leaks the fake-pixelpass scripts in /tmp.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-31 04:05:17 -04:00

..

fixtures

tests/fixtures: the ownership contract says exact-match, not truthy

2026-07-25 23:57:16 -04:00

file_transfer_loopback.rs

style: apply cargo fmt across the crate (A20)

2026-06-29 02:11:44 -04:00

gossip_rebootstrap.rs

feat(music): W22 shared listening + release 0.6.0

2026-06-28 06:04:31 -04:00

reconnect_eviction.rs

chat: roster-bound authorship, replay dedup, and rate limits (Phase 2)

2026-07-17 20:37:13 -04:00

screenshare_host_fault.rs

core: retire the share at Join's session teardown, not after ticket parse

2026-07-31 04:05:17 -04:00

transport_loopback.rs

chat: attachment cache, download, and transfer hardening (Phase 3)

2026-07-18 02:09:30 -04:00