Generate FOC Platform admin and reconciliation surfaces #81

Goal

Add generated FOC Platform admin/read surfaces around object receipts, account usage, datasets, coordinator state, and reconciliation status.

Parent tracker: FIL-Builders/foc-platform#3
Platform spec source: FIL-Builders/foc-platform spec.md section 10 and section 17.

Scope

Generate or scaffold UI/read surfaces for:

• user object browser
• upload request/object detail
• compact receipt and copy receipt detail
• account usage and quota view
• dataset/provider/copy attribution
• coordinator allowlist/status view
• FOC account runway view
• reconciliation mismatch/status view

The first implementation may read from generated prototype collections or from an ABI-bound hand-written FocPlatformRegistry, but it must label prototype data clearly.

Non-Goals

• Do not implement the registry lifecycle itself.
• Do not store sensitive PII in generated views or examples.
• Do not require production reconciliation automation before exposing read/admin scaffolding.

Milestones

1. Define the manifest/schema inputs needed by the generated UI.
2. Add minimal generated pages/components for the FOC Platform admin/read surface.
3. Wire a demo schema or fixture to exercise the pages.
4. Add tests/snapshots that cover generated routes and manifest behavior.
5. Document limitations and source-of-truth assumptions.

Required Evidence

• Generated UI tests or build artifact tests for the new pages/routes.
• Fixture/demo showing object, usage, dataset, copy, and coordinator data shapes.
• Documentation explaining whether the view reads generated prototype state or a hand-written registry ABI.

Completion Criteria

This issue is complete when a Token Host-generated app can provide the minimum useful FOC Platform operator/read UI without overclaiming that the underlying protocol module is complete.