To elaborate what happens when the buffer overflows... The official README explains that map (normally sprites) starts at 0x2000 and some other data starts at 0x3000. Therefore it will start overflowing other data, and depending on what you expect in those area, it may or may not break the game. The entirety of PICO-8 is intentionally constructed in this way to give its look and feel.
This is a clever little hack to save space which is already artificially constrained. Part of the fantasy console concept is to pick constraints like token counts in code being limited and sprite memory limits. These limits make finding ways around them fun and sometimes requires creativity like this compression scheme which needs to fit within the limited code space.
Given the other constraints of the system, the main place this code is likely to be used is in a script dedicated to assembling a "cartridge" file, and if the output overflows the target space (likely map or gfx ram) then it's just going to bail out with an error anyway, it's unlikely to care about the stomped-over RAM, given that it can't affect Lua variables or code.
Is there an implicit constant buffer size in the framework, language or device, like a single page or something?
To a C programmer, this looks extremely unsafe.
The blog post is tagged "pico-8", which I guess is [1].
1 - https://en.wikipedia.org/wiki/Pico-8