[randomblocker]

The service page hid the buy box for a published DEM price such as 1.5000000000, because the check allowed at most nine decimal digits even though the
value is exactly representable in base units and the SDK accepts it. The check now accepts zeros after the ninth decimal. A price with a non-zero digit
past the ninth decimal, such as 1.0000000001, still hides the box, and so does a zero amount.

Tested by adding both amounts to test/service-page.test.ts: 1.5000000000 shows the box and 1.0000000001 does not. The first assertion failed before the
change. The service page test file passes (2 of 2), the whole directory suite passes (1696 pass, 0 fail, 1 skipped) and npm run typecheck is clean.

It does not change how other listing pages, the listing API or the SDK handle amounts; only this one display check.

Closes #219

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

[randomblocker]

Closing without merging. Review found the case it handles cannot occur: a listing's fixed price must be in canonical form, so 1.5000000000 is rejected when the listing is published (the SDK's isPricingSpec returns false for it), and the Directory's verifyListingArtifact rejects non-canonical prices before indexing. The catalog never holds a price with trailing zeros, so the service page check never sees one. The test reached the new branch only by writing a catalog summary directly.