Scarpet apps are more maintainable given they don't depend on the game source directly (so only the language has to be updated once for all apps to work) and having Carpet functionality as scarpet apps also works as tests for the scarpet API.

I propose /info to be reimplemented as a Scarpet app, given it is quite a simple concept if scarpet has access to all the data /info provides, and if it doesn't, this can be a good tracking issue for adding them.

Properties that can be queried from scarpet:

• Material
• Map color
• Sound name
• Full cube
• Normal cube (redstone conductor) (solid)
• Liquid (note that it also returns waterlogging)
• Light
• Brightness (though it is deprecated in the game's source and comes from a method named the same as light)
• Solid (!transparent)
• Blocks light
• Causes suffocation
• Blocks movement
  • On land (this is the parameter used by blocks_movement)
  • In air
  • In liquids
• Can burn (flammable)
• "Requires a tool"
• Hardness
• Blast resistance
• Ticks randomly
• Can provide power
• Strong power level
• Redstone power level (power)

yes. This just shows the gap in the API. There are more 'exotic' measures, like random wandering chances, but that could be measured in scanning the area for blocks, so not a biggie..

Another vector would be informative aspects of /spawn - could also be scarpet only.