MarmotProfile.PUBLISHED is the current profile alone. The repository
publishes only the current-profile package and refuses to be asked for a
legacy one; KeyPackageEvent.build and the legacy leaf builder have no caller
and are gone. The notary republishes only what PUBLISHED names, so a legacy
bundle still active is left to be consumed and not replaced.
A legacy room still invites: the current-profile leaf advertises 0xF2EE.
RobustGroupAdminsJvmTest's legacy-room cases now join from the one package
the app publishes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>