feat(loop): scaffold WF1 reference app across seven OS clients

[enricopiovesan]

Summary

Scaffold apps/loop/ WF1 (ingest → extract → normalize → authorize) across all seven OS clients, composed via digest-pinned registry_ref capabilities and an in-app loop.wf1 workflow overlay. Extends bundle sync materialize for core.* WF1 caps and registers CI/nightly/docs touchpoints.

Governing Spec

• docs/specs/003-loop-wf1-reference-app/spec.md (Approved)
• ADR docs/adr/0003-loop-wasm-from-registry-only.md
• Specs 001/002 event-UI conformance (presentation + capability progress)
• Registry pins: docs/loop-registry-deps.md
• Public embedder surfaces only; UI remains a rendering layer

Project Item

• Ticket ID: loop-wf1-multi-os
• Item: PVTI_lADOEbiBt84BbzAzzg2Jmec
• Status: In Progress (Cursor)

Definition of Done

• apps/loop/ clients for web, iOS, macOS, Android, Windows, Linux GTK, CLI
• App + four registry_ref component manifests + in-app WF1 workflow
• Sync wrappers + materialize mapping for WF1 capability digests
• Spec 001/002 presentation wiring on shells
• Human-review chrome when presentation is blocked (web)
• README / design-language / repository checks / CI + nightly registration

Validation

• bash scripts/ci/repository_checks.sh
• npm run test -w apps/loop/web-react
• npm run typecheck -w apps/loop/web-react
• cargo test -p loop-core-rs -p loop-cli (under apps/loop)
• Native sync: scripts/ci/sync_{web,android,swift,winui}_loop_bundle.sh with TRAVERSE_REPO set

Checklist

Traceability

• Project 2 ticket updated (Agent + Status); Ticket ID cited above
• Updated README.md / docs/design-language.md platform rows if shipping status changed
• Updated AGENTS.md blocked-work summary only if Project 2 Blocked set changed

Production baseline (platform / runtime-client PRs)

• Embedded mode — production path uses in-process public embedder (no required traverse-cli serve)
• Digest pin / sync — runtime/runtime-release.json pin followed; ran the relevant scripts/ci/sync_*_bundle.sh (see docs/runtime-bundle-sync.md)
• SDK test doubles — unit tests use public embedder doubles (EmbedderTestDouble / InMemoryTraverseEmbedder); no faked business fields in app code
• Docs touchpoints — platform README Runtime mode + any getting-started / playbook links updated when behavior changed
• CI commands — listed under Validation; embedded_smoke / repository checks covered when the slice is Linux-runnable

Architecture

• No business logic added to UI layer (title / tags / note type / next action / status come from runtime)
• No private Traverse internals imported
• CI gates pass locally where applicable

Made with Cursor