feature: incorporate plan1 foundation for peersky parity

[tylerchilds]

heyo- ty from sillyz.computer here-- i'm stepping back from open source being my full time gig, but want to decentralize my research before i go-- a two weeks notice hand-off of sorts.

to date, sillyz has been about bridging systems through user experience, which in practice is javascript for writing hypertext, what i lovingly refer to as "my elves"; tiny hypertext helpers.

my overall hypothesis is that the key to interoperable systems are portable, re-mixable components.

this PR adds baseline compatibility between sillyz.computer, plan98 systems, peersky-browser as of yesterday, which unlocks any of these unstable elves (plan1) and any of these more stable elves (plan98).

by incorporating this pr, it'll be possible to begin to bridge client experiences from within peersky, agregore, and sillyz.

one of my personal favorites is a shared bulletin-board (still experimental), currently powered by https://gun.eco, but we can agree on any state synchronization engine for {x,y,z,width,height} and it'll work across environments. We also don't need to incorporate this elf, but this PR opens up new potential experimental avenues, leveraging my library of elves to date.

the most documented demonstration of plan98 to date is in this https://braid.org meeting from last month.

[RangerMauve]

TY for the PR. This is interesting but I'm not sure what the advantage is in packaging the apps directly in the agregore protocol handler. Is there a reason we couldn't publish it as a static site onto hypercore? I'd be open to donating my distributed.press instance and adding a link to the published site under the explore page that's linked on the welcome screen.