docs: surface implementation status badges

[violet-agent]

Summary

• add Vocs status badges to the 24 in-scope documentation pages using only Shipped, Partial, or Planned
• intentionally leave the docs homepage and all eight use-bloom/ pages unbadged because those are general user-facing documentation
• align each remaining status badge to the far edge of its H1 heading box rather than directly beside the heading text
• ground classifications in the current bloom master implementation: wallet/VFS setup and core flows are shipped; broader Bloom, Petals, DeFi migration, architecture, and limitation surfaces are partial; the product-integration surface is planned
• extend npm run lint with a checker that requires one consistently styled badge on each in-scope page and rejects badges on the nine intentionally unbadged pages

Status distribution

• Shipped: 10 pages
• Partial: 13 pages
• Planned: 1 page

The classification used the current wallet, transaction engine, mount, watch/simulation, paid HTTP, Petal runtime, and known-limitation code and tests in bloom master. In particular, the native /defi implementation has moved to the externally installed Enso Petal, Petals remain under active development, and product integration is not yet available end to end.

Verification

• npm run lint
• npm run build
• git diff --check
• browser checks confirming no badges on the homepage or use-bloom/ pages
• browser checks confirming Shipped, Partial, and Planned badges align to the far edge of the heading box with no horizontal overflow or console errors

Fixes #14

[cloudflare-workers-and-pages]

Deploying bloom-docs with    Cloudflare Pages

Latest commit:	17147dd
Status:	✅  Deploy successful!
Preview URL:	https://d0ecac0b.bloom-docs-ezr.pages.dev
Branch Preview URL:	https://docs-issue-14-status-badges.bloom-docs-ezr.pages.dev

View logs