Package toolbox is the directory of moul's small gno.land utilities: one page listing every tool, each tool a realm of its own at `r/moul/toolbox/<slug>`.
It holds no logic. A tool composes other contracts (resolve a username, read a DAO, decode a denom) and renders the answer; this realm only says which tools exist and where they are. The model, the rendering and the query-form builder are p/moul/toolbox(/p/moul/toolbox/v0).
Why the catalog is compiled in and not registered
The obvious design is the opposite one: each tool calls `Register` on this realm from its own init, and the directory assembles itself. That design is unavailable here, and the reason is worth stating because it is not a preference.
`private = true` buys redeploy-in-place at the same path and costs the ability to be imported: the type checker refuses any realm importing a private one (`ImportPrivateError`, `gnovm/pkg/gnolang/gotypecheck.go`). So a private hub cannot be imported by its tools, and a hub that accepts registration has to be public. A public realm can never be redeployed, which would freeze this path at v0 and move the directory's URL on the first bug in it.
A stable URL is the whole point of a directory, so the trade goes the other way: everything here is private and redeployable, and adding a tool is one entry in [tools] plus a redeploy. The catalog is rebuilt from source every time, so the redeploy wipe costs nothing: there is no state to lose.
p/moul/toolbox.Catalog stays mutable for whoever wants the other trade.