Skip to content

Wire up repo drill-down and single/federated scope toggle - #17

Open
timkjr wants to merge 3 commits into
gortexhq:mainfrom
timkjr:services-scope-drilldown
Open

Wire up repo drill-down and single/federated scope toggle#17
timkjr wants to merge 3 commits into
gortexhq:mainfrom
timkjr:services-scope-drilldown

Conversation

@timkjr

@timkjr timkjr commented Aug 21, 2026

Copy link
Copy Markdown

Summary

  • Repo cards on Services and Dashboard render click to drill in copy but had no click handler — now clickable (mouse + keyboard), navigating to /graph scoped to that repo.
  • The Single repo / Federated toggle in the topbar only changed a display label (scope in lib/tweaks.ts) and was never read by any data-fetching hook — now it actually narrows the Graph page's request (useGraph({ repo }), backed by the existing /v1/graph?repo= param) and filters the Dashboard/Services repo lists to the active repo.

Known limitation

Most /v1/* payloads (kinds, languages, caveats) aren't repo-attributed, so those stay federated even in single-repo mode — narrowing them further would need a backend change.

Test plan

  • npx tsc --noEmit
  • npm run build
  • Manually verified against a running instance: clicking a Services/Dashboard repo card navigates to /graph filtered to that repo; toggling Single repo / Federated changes what's shown on Graph, Dashboard, and Services

🤖 Generated with Claude Code

timkjr added 3 commits August 10, 2026 23:04
Repo cards on Services and Dashboard were not clickable despite the
"click to drill in" copy, and the Single repo / Federated toggle only
changed a display label with no effect on any query.

- ServicesView and Dashboard repo cards now navigate to /graph scoped
  to that repo (mouse + keyboard)
- Graph page requests a single-repo subgraph from the backend
  (existing /v1/graph?repo= param) when scope is "single"
- Dashboard's Repositories card and the Services list filter to the
  active repo in single mode
- StatusBar shows which repo is active when scoped

Known limitation: dashboard kind/language/caveat rollups aren't
repo-attributed in the /v1/dashboard payload, so those stay federated
even in single-repo mode.
The server no longer auto-promotes arbitrary legacy tool names through
/v1/tools/{name} (PR zzet/gortex#649 rework). processDetail called
get_processes directly, which 404s under the core/defer surface once
generic promotion is removed. Switch to analyze(kind=processes, id=...),
which the facade routes to the get_processes handler without promotion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant