Cross-repo analysis - 2026-06-20

Scope: app, get, ifuri-com, urirun, and the current urirun-connector-* repositories.

Executive findings

1. The program needs one root planning layer.

urirun already has a local .planfile, but /home/tom/github/if-uri did not have a cross-repo planfile. Roadmap and planfile should track the whole product: runtime, app, installer, sites and connectors.

1. Install/release trust is the first blocker.

urirun has multiple version sources: root VERSION and root package.json are 0.3.12, while adapters/python/VERSION and adapters/python/pyproject.toml are 0.3.14. The JavaScript adapter is still 0.1.0.

1. Old urihandler paths are still active in installer smoke scripts.

get/scripts/smoke-node.sh and get/scripts/smoke-service.sh still point to ../../tellmesh/urihandler/adapters/python. Historical changelog references are acceptable; runnable scripts must use if-uri/urirun or a released artifact.

1. CI coverage is uneven.

app and urirun have workflows. get, ifuri-com, and the connector repositories rely on local Makefiles only. Connector docker-test targets exist, but they are not enforced in CI.

1. urirun core still mixes runtime, host/app and connector concerns.

The runtime package includes mesh.py, host_dashboard.py, host_db.py, task_planner.py, domain_monitor.py, namecheap_dns.py and planfile_adapter.py. That makes the core harder to release and makes connector packaging less clear.

1. The app has a likely execute-path bug.

app/src/ifuri_app/cli.py contains an ifuri-app run path that calls dry_run_flow(...) in both branches. This should become a real execution path or be explicitly documented as dry-run only.

1. Connectors have a good local shape but need a stable public contract.

Existing connectors have Makefile, tests and Docker compose files. The next step is a stable decorator/API style (@urirun.command), entry-point discovery and generated registry artifacts that the hub and app can consume.

1. The user-facing sites need deployment/test parity.

ifuri-com has PHP/static content and Docker compose, but no Makefile or GitHub workflow. connect.ifuri.com has a workflow, while the core public marketing site needs the same test/deploy discipline.

P0 - make the system installable and testable end to end

• Align urirun versions into one source of truth and update release docs.
• Replace active tellmesh/urihandler paths in get smoke scripts.
• Add CI workflows for get, ifuri-com, and all connector repositories.
• Run connector docker-test in CI, including registry generation, MCP/A2A

projection and a two-node host/node smoke where practical.

• Fix or explicitly gate the app ifuri-app run execute path.
• Normalize connector .gitignore files so local .venv/, venv/,

.pytest_cache/, dist/, build/ and *.egg-info/ never enter commits.

P1 - simplify architecture for people adding capabilities

• Split urirun into a small runtime core plus external connector/app packages.
• Move app/host modules (mesh, dashboard, host DB, planner) out of core or

behind optional extras.

• Move domain-specific modules (namecheap_dns, domain_monitor,

planfile_adapter) into connector packages.

• Standardize connector declaration around:

@urirun.command(...) -> generated binding -> generated registry.

• Add one command that installs connectors and regenerates the local registry.
• Teach the app GUI to show installed connectors, routes, devices, processes and

available URI flows.

P2 - improve adoption, search and broader demos

• Add connector detail pages with route lists, schemas, install commands,

examples and machine-readable JSON-LD.

• Add Namecheap DNS, planfile, SQLite/context, domain monitor and LLM connectors.
• Add a noVNC GUI test matrix for desktop app scenarios.
• Publish a status page or generated catalog that shows tested versions across

app, get, urirun and connectors.

Recommended sequencing

1. Release/install integrity: version alignment, old path cleanup, CI.
2. Runtime contract: stable urirun public API and connector entry points.
3. Full-network smoke: host + two nodes + registry + connector commands.
4. App operator view: discover routes, run flows, inspect logs/results.
5. Connector marketplace polish: detail pages, search, schema previews and

install scripts.

Synced from GitHub · last update 2026-07-17 04:24 UTC · source: cache. Edit on GitHub; this page refreshes once a day.