Curious if this work on proof-witnesses for #Twelf’s totality checker ever landed upstream: https://al.radbox.org/doi/10.1145/2503887.2503893
Towards extracting explicit proofs from totality checking in twelf

The Edinburgh Logical Framework (LF) is a dependently type lambda calculus that can be used to encode formal systems. The versatility of LF allows specifications to be constructed also about the encoded systems. The Twelf system exploits the correspondence between formulas and types to give specifications in LF a logic programming interpretation. By interpreting particular arguments as input and others as output, specifications can be seen as describing non-deterministic functions. We can then prove meta-theorems about the encoded systems by showing particular such functions to be total. Twelf provides tools for establishing totality. However, the resulting proofs of meta-theorems are implicit in that they do not yield a certificate that can be given to a proof checker. We begin the process here of making these proofs explicit. We treat the restricted situation in Twelf where context definitions (regular worlds), mutually recursive definitions and lemmas are not used. In this setting we describe and prove correct a translation of the steps in totality checking into an actual proof in the companion logic M2.

May your encodings be adequate and your abstract syntax higher-order

#Twelf #benediction

I figured the #twelf logo needed to be in the "About..." box, and what more natural format than a PICT resource. Turns out a PICT is not (necessarily) a raster image, but a sequence of postcript-esque (and rescalable!) drawing opcodes. No problem, just potrace to polylines in geojson format, reassemble the layers, write some javascript to emit the right headers and flip the y-coordinates, remember to allocate a 256-color drawing port, and...
now we're cookin'
#twelf
Ok, this actually works now, it is really #twelf executing on m68k
Getting closer... #classicmac #twelf
it's not a useful #twelf LSP server yet, but I do have a twelf.wasm emitting some basic data coming out of the actual twelf parser, enough of which is read by an nodejs lsp implementation to enable a fake "jump to definition" that jumps to the previous constructor declaration.
Switched #twelf sandbox from ace to codemirror, which means I get slightly better support for parsing and errors
In continuation of implementing modern features for #twelf that nobody really asked for, (except in the capacity that @simrob mentioned he was thinking of doing it at some point, thereby nerdsniping me into seeing how hard it would be) I got the regression suite running all CI-style with github actions and a custom docker image, and added the metadata that puts the groups of tests in little hierarchical groups in the logs.
Syntax highlighting for #twelf sandbox! Very primitive, just comments and pragmas, but proof of concept.