I'm happy that Clarity always remembers ETP's "Get Chrome Browser". I never do. But then I don't have to. Puppys only need their own folder --not an entire partition-- and a listing on a computer's boot-manager. Been running Puppys for a decade, so always have had a fully functional operating system before trying to setup a new Puppy.
Aliante, as someone new to Puppy, the following is information you may find helpful.
Almost from its inception two decades ago Puppys were able to use --load & unload on-the fly-- applications published as Squash-file-systems (SFSes); and many of those could be run under several Puppys. Then, a couple of years ago, Mikewalsh --with some insight and help from others-- 'taking a page from windows' began publishing many applications as portables. These usually can be run from many Puppys. You'll find Mikewalsh's complete list here, https://forum.puppylinux.com/viewtopic.php?t=5104 and the 'root' of the Additional Software Subsection here, https://forum.puppylinux.com/viewforum.php?f=7. Thanks to Mikewalsh's endeavors, when Bookworm became available I already had both firefox and google-chrome portables which it could use.
When you find the need for additional applications always check the Additional Software Subsection first. Puppys are not cut-down versions of the binary-compatibles used in their creation: e.g. BookwormPup from debian Bookworm. Puppys use unique 'infra-structure' avoiding their binary-compatibles heavior, more resource-demanding infra-structure when possible. So while installing applications via apt or synaptic usually works, sometimes one or more components the makers of the software for the binary compatible assumed to be present will be missing. Publications by Puppy Forum Members will have included those (at least for the Puppy they specify). Mike's portables will almost always function under Puppys which are binary-compatible with debian and Ubuntu OSes.
Portables and SFSes require no-to-little RAM when not in use, leaving you with more RAM for doing actual work. And as they are not installed, you can create a backup before upgrading. While --so far-- there have not been reports of upgrade problems with either firefox or google-chrome, palemoon is notorious for publishing upgrades which then have to be fixed. Murphy's Law being what it is, I always take the precaution of backing up an SFS or portable before upgrading: Right-Click>Duplicate, give the 'copy' a slightly different name. Takes about a minute. Avoids a lot of aggravation.
FYI, BookwormPup64 can also often use AppImages. These also are not installed: just downloaded, made executable and run (Left-click) if and when you need them. Discussed in the Additonal Software Section.