Deferred: Traverse × Hugging Face integration (post model-refs)

## Summary

Deferred exploration: possible Hugging Face ↔ Traverse integration **after** registry decision-log entry 124 / #571 (contract-pinned model refs) lands.

## Context

We deliberately kept:
- quantized weights embedded / Release-hosted (deterministic, offline WASM)
- no required live HF calls in CI
- no runtime weight fetch from HF

HF remains provenance/marketplace; Traverse remains the governed runtime (contracts, digests, signatures, Spec 025 capability licensing + object-shaped `ai.models`).

## Pitch (from exploration)

Hugging Face is where models are born and discovered. Traverse is where a pinned model becomes a signed, redistributable, multi-host **product capability** with machine-readable rights — without making HF a runtime dependency.

## Strong fits for HF’s ecosystem

1. **Governed export path** — HF model → pinned revision → quantized WASM capability + contract (`ai.models` attribution filled)
2. **Enterprise / regulated consumers** — digests, signatures, deny-by-default rights; no live Hub fetch required at run time
3. **Multi-host product packaging** — same logic on browser / edge / device / local under one ABI
4. **Workflow composition** — VAD → transcribe → NER as a versioned graph, not a notebook
5. **License honesty for redistributors** — maintainer-declared SPDX pins where Hub metadata is dual-tagged or uneven

## Weak / don’t compete

- Replacing the Hub for discovery/social/frontier LLMs
- Training / fine-tuning / Spaces demos
- Being another Transformers.js without the governance story
- Runtime “pull latest from HF” inside capabilities

## Possible directions (not decisions)

- HF model card / Space → scaffolded Traverse capability contract + WASM package
- “Deploy with Traverse” / registry sync so app builders don’t re-quantize by hand
- Trust layer for consumers: digests, signatures, machine-readable rights

## Trigger to reopen

- #571 (FR-017 object models) merged and in use on new agent publishes
- Clear owner priority for marketplace/export UX (not just attribution pins)

## Out of scope until then

- Runtime HF downloads inside capabilities
- Required online HF validation in merge CI

## Related

- Decision-log entry 124
- https://github.com/traverse-framework/registry/issues/571
- https://github.com/traverse-framework/traverse/issues/1459
- Canvas exploration: `traverse-for-huggingface.canvas.tsx` (local Cursor canvas)

Start by reading registry issue #571 and decision-log entry 124, then review the stated Traverse and Hugging Face integration directions. The issue is ready to reopen only after #571 is merged and used for new agent publishes, with a clear owner priority for marketplace or export UX; runtime HF downloads and required online CI validation remain out of scope.

Written by the indexing model from the issue text.