12 - full E2E connect lab

This lab verifies the complete user path:

get.ifuri.com provides the node installer.
connect.ifuri.com provides connector/install metadata.
pc1 and pc2 install and run urirun node.
host installs urirun + connectors, discovers both nodes and runs a URI flow.
registry-runtime exposes a live registry built from the node routes.
ifuri-site serves a local test page representing ifuri.com.
Connector routes are compiled into a host registry and projected to MCP tools and A2A skills.

The default test intentionally uses public installer endpoints:

https://get.ifuri.com/node.sh
https://connect.ifuri.com/install?connectors=planfile
https://ifuri.com/

You can override them for local development:

GET_BASE_URL=http://get-site CONNECT_BASE_URL=http://connect-site make test

Quick public smoke

make public-smoke

This checks public ifuri.com, get.ifuri.com and connect.ifuri.com without Docker.

make test

The scenario writes artifacts to generated/:

The connector checks execute:

httpcheck://host/http/query/status against the local ifuri-site,
data://, artifact://, check:// and log:// host SQLite routes,
task:// and planfile:// planfile-backed routes,
monitor://, dns://, flow:// and safe mock namecheap-dns routes,
browser://desktop/page/command/open and browser://desktop/page/command/screenshot

through the browser-control connector in safe no-local-browser mode,

Planned catalog entries such as mqtt are reported as skipped until their connector packages exist.

make up
make scenario
make down

To inspect a node:

docker compose exec pc1 bash
curl -fsSL http://127.0.0.1:8765/health
curl -fsSL http://127.0.0.1:8765/routes