$ rm -rf db &&
super -version &&
super db -q -db db init &&
super db -q -db db create foo &&
super db -db db ls
Version: v0.3.0-208-gddb2268fe
type "ksuid.KSUID"=bytes
type "order.Which"=string
type "field.Path"=[string]
type "field.List"=["field.Path"]
type "order.SortKey"={order:"order.Which",keys:"field.List"}
type "pools.Config"={ts:time,name:string,id:"ksuid.KSUID",layout:"order.SortKey",seek_stride:int64,threshold:int64}
{ts:2026-06-27T18:05:31.900881Z,name:"foo",id:0x16cdc2eb779fe59576225323126cf10144ca5122,layout:{order:"desc",keys:[["ts"]]},seek_stride:65536,threshold:524288000}::pools.Config
$ rm -rf db &&
super -version &&
super db -q -db db init &&
super db -q -db db create foo &&
super db -db db ls
Version: v0.3.0-207-g6b4c403aa
foo 3FjLc8kzBZ8Pp8kXXCwfbh0oMiW key ts order desc
Details
Repro is with super commit ddb2268.
The appearance of this symptom is correlated with the merge of #7050, as the normal formatting of the db metadata output was intact at commit 6b4c403 just prior to the merge of #7050.