Skip to content

Feat(hub): add ui native setup wizard - #192

Merged
theyashasvipandey merged 9 commits into
mainfrom
feat/add-hub-setup-wizard
Sep 11, 2026
Merged

Feat(hub): add ui native setup wizard#192
theyashasvipandey merged 9 commits into
mainfrom
feat/add-hub-setup-wizard

Conversation

@architdhamija

Copy link
Copy Markdown
Contributor

What

Why

Type of change

  • Bug fix
  • New feature
  • Refactor
  • Docs
  • CI/Tooling

How to test

Checklist

  • Tests pass (npm test)
  • No breaking changes (or documented below)
  • Tested locally with a real project

Code-graph changes

  • This PR targets main
  • A linked issue agrees on the bounded extractor/resolver scope
  • The change follows the frozen LanguageExtractor or FrameworkResolver interface
  • A focused fixture and assertions for the expected node/edge shape are included
  • Any new grammar WASM, extension mapping, extractor, or resolver is registered
  • No graph identity, reconciliation, schema, or drift-semantics changes are included, or a core / discuss-first issue is linked above

architdhamija and others added 5 commits September 10, 2026 17:37
Share setup phases and provider commands between CLI and Hub, run Claude
Code and Codex population in owned background sessions, and stream bounded
assistant text with compact tool activity.

Add exact setup-file diff review and local commits that preserve unrelated
staging, reject stale reviews, and promote the existing session into Hub.
Render readable numbered additions/deletions with bounded raw fallback.

Cover setup, streaming, Git transactions, browser flows and packaged assets;
document the explicit local-commit policy and retain separate setup budgets.
…ze errors

Hub setup populated scaffolds without grounding and then failed at finalize:

- Headless Claude ran with acceptEdits only, so every `mex graph` call was
  denied at an approval prompt no one could answer. Pre-approve only the
  read-only graph, impact, and event-log commands, for both the Bash and
  PowerShell tools (Windows sessions use PowerShell).
- The population prompt showed its anchor example as a live Markdown link and
  told agents to retain the rule in AGENTS.md. A verbatim copy left
  mex://<exact-node-id>, which grounding capture rejects. Show the example as
  inline code instead.
- The Hub replaced every finalize failure with a generic message. Finalize now
  throws SetupFinalizationError with authored text naming the unverifiable
  reference, and the runner shows it.
…tory

The headless allow-list comment claimed Git commands need a person. A probe with
the original launch arguments showed `git log`, `git show`, and `git blame`
already run; only `mex` commands were denied.
…ommitted

The setup commit review returned every file's diff inline, capped at 128 Ki
characters in total. A normally populated scaffold for a small app is about
185 KB, so the guided commit fell back to manual on ordinary projects.

The preview now lists only per-file metadata (status, line counts, diff size).
Each diff is served on expand by POST /api/v1/setup/commit/diff from the text
retained with the reviewed snapshot; it runs no Git and answers only for the
current, unexpired revision. Per-file review text is 128 Ki characters and the
retained review total is 1 Mi. A truncated diff still blocks the in-app commit,
and a blocked review stays readable to guide the manual commit. The file,
count, and Git-output caps are unchanged.
The setup page's grid tracks defaulted to min-width auto, so an open diff with
long unwrapped lines widened the whole card. The card clips overflow, which hid
the right-aligned Refresh review and Commit setup and open Hub buttons until
every diff was closed. Constrain the page, body, and review grids to
minmax(0, 1fr) so wide rows scroll inside their own diff instead.

The browser test now opens every diff with a long line in the fixture and
checks that the card has no hidden overflow and both actions stay inside it.
@theyashasvipandey
theyashasvipandey merged commit bb1466e into main Sep 11, 2026
9 checks passed
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.

3 participants