railiance-fabric/workplans/archived/260702-ADHOC-2026-06-03.md

---
id: RAIL-FAB-WP-ADHOC-2026-06-03
type: workplan
title: "Ad Hoc Fixes 2026-06-03"
domain: railiance
repo: railiance-fabric
status: finished
owner: codex
topic_slug: railiance
created: "2026-06-03"
updated: "2026-06-03"
state_hub_workstream_id: "786f6b47-d0a2-52fc-badf-79dd629fed06"
---

> **Terminology note:** Historical text in this archived workplan may use the legacy term "workstream". The fleet term is **workplan** (`canon/standards/workplan-terminology-fleet_v0.1.md`).

# RAIL-FAB-WP-ADHOC-2026-06-03 - Ad Hoc Fixes

## Add Graph Explorer Make Target

```task
id: RAIL-FAB-WP-ADHOC-2026-06-03-T01
status: done
priority: medium
state_hub_task_id: "120820db-ab85-58c5-a8b1-62d933db9fa3"
```

The graph explorer is served by the registry HTTP service, but starting it
currently requires remembering the full registry command and database path.

Add a Makefile target that starts the registry-backed graph explorer from the
repo root with defaults for the local database, host, and port. Calling `make`
without an explicit target should list available targets rather than start a
long-running service. Document the target and available overrides.

Result: Added `make graph-explorer`, with `registry` as an alias, defaulting to
`.railiance-fabric/registry.sqlite3`, `127.0.0.1`, and port `8765`. Plain
`make` now prints the available targets instead of starting the service. The
target uses `python3 -m railiance_fabric.server`, so it works from the checkout
without requiring an installed console script. Updated the README and graph
explorer operations guide with the target and override examples.

Verification:

- Confirmed plain `make` lists available targets.
- Started `make graph-explorer PORT=9877 REGISTRY_DB=/tmp/railiance-fabric-make-test.sqlite3`.
- Confirmed `GET http://127.0.0.1:9877/status` returned `status: ok`.
- Stopped the temporary verification server on port `9877`.