(Jump back to #fTelnet anchor when doing the click thing on
a clickable click thing to do the thing.)
Complaint courtesy of Android8675309

Execute most any top-level SSJS in an IIFE to work around whatever
context reuse thing is happening.
I'm aboot done with this shit for now I tell you what.

I'm okay with things crapping out if ftelnethelper.js can't be loaded; that'll be documented.
No need to evaluate ftelnet enabled/disabled here; sysops should hide this page or restrict it via webctrl if they don't want ftelnet on their site.

Moved stock pages into pages/.examples directory so that sysops can make customizations that won't conflict with what's in the repository.

Use IsWebSocketServiceEnabled() (not RLogin-specific function)
Paste in WS/WSS setup instructions from 000-Home.xjs.

Apply a WebSocketUrlPath option to the ftelnet client, where ?Port= the rlogin port, via ftelnethelper, from sbbs.ini.
Untested. Not sure if this will do what I expect it to.
Removed 'template' related lines; copy/paste from the stock web UI, I think.

Work with the latest fTelnet release, probably stop working with earlier ones. Reload the page on fTelnet disconnect to avoid various problems.

Reinit fTelnet on disconnect.  List all xtrn sections and programs whose internal codes are not in xtrn_blacklist.

If rlogin_port is specified in modopts.ini [web], use that port; otherwise, use WebSocketRLogin port specified in services.ini