mapvfs: punk91 wraps punk9win.vfs on tclsfe-x64 (staying); tksfe wish-runtime experiment notes

- tclsfe-x64.exe is not a tk runtime and the tk-having sfe variants are wish-based (unsuitable), so punk91 moves off punk9win_for_tkruntime.vfs (which is intended for kits that already carry Tk) to punk9win.vfs - Tk loads as an extension per the punkbin runtime convention
- commented-out tksfe-twapi-x64 experiment recorded: the kit builds and can run tk apps (punkwish91 lib:tkhello) but the tk console does not display; noted todos - get the builtin tk console showing for exploration (unsuitable long-term: no ansi handling) and consider a textwidget-based virtual console capable of hosting the punk shell (relates to G-001 pluggable console backends)

Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com

src/runtime/mapvfs.config

@@ -47,7 +47,19 @@ tclsh902z.exe {punk9win_for_tkruntime.vfs punk902z zip}
 
 #apn's tcl-sfe
 #https://github.com/apnadkarni/tcl-sfe/releases
-tclsfe-x64.exe {punk9win_for_tkruntime.vfs punk91 zip}
+#tclsfe-x64.exe is not a tk runtime. The versions with tk are 'wish' based so unsuitable.
+#punk9win_for_tkruntime.vfs is intended for kits which already have Tk
+tclsfe-x64.exe {punk9win.vfs punk91 zip}
+
+
+#----------------------------------------------
+#experiment - what happens when we run against a 'wish' runtime? Will we have stdin stdout problems?
+#tksfe-twapi-x64.exe {punk9win.vfs punkwish91 zip}
+# result so far: the kit builds - but the tk console doesn't display.
+# we can run tk apps e.g punkwish91 lib:tkhello
+# - todo - consider if we can first get the built in tk console showing for initial exploration, although it is unsuitable for a punk console as it doesn't handle any ansi.
+# - see if we can develop a textwidget based virtual console that we can get punk shell running in.
+#----------------------------------------------
 
 #----------------------------------------------
 #testing wrong target kit type for runtime