wiki: bootstrap travel-as-NoETL-reference-SPA developer coverage
This wiki frames the travel repository as the operational example
of how a domain-specific single-page application is built on top
of NoETL — not "the travel app" in isolation.
Adds eight pages totaling ~1500 lines of developer-facing
documentation:
- Home.md: overview, what the repo demonstrates, table of pages.
- _Sidebar.md: navigation.
- architecture.md: the four layers (SPA shell / widgets /
playbooks / gateway integration) and how they fit. Diagram of
browser -> gateway -> noetl-server -> worker-pool flow.
- widget-contract.md: schema-driven contract between playbook
outputs and SPA UI. Five-step recipe for adding a new widget.
- playbook-itinerary-planner.md: walkthrough of the orchestrator
playbook (~16 steps). Workload contract, where each pattern
lives (LLM extractor / provider abstraction via MCP /
slot-state projection / render-decision in playbook), and
performance notes.
- gateway-integration.md: wire protocol the SPA speaks
(executePlaybook GraphQL, SSE frame families
playbook/result + playbook/state + subscription/event,
POST/DELETE /api/subscriptions/firestore).
- auth-and-session.md: Auth0-to-gateway-session model and how to
swap the identity provider.
- deployment.md: Vite build, Docker container, nginx config,
Cloudflare Pages, Wrangler.
- adapting-for-your-domain.md: fork-and-replace checklist
covering six phases — naming, widget set, orchestrator
playbook, MCP providers, auth re-branding, deployment.
Cross-links to the ephemeral_blueprints architecture doc in
noetl/docs (the foundational compute-data boundary that this
repo enforces concretely by removing the Firebase SDK from the
SPA in #50).
Every page sources from real files in repos/travel and links
back via absolute GitHub URLs into main.