Delivers the migrate Guide UX roadmap item: progress %, resumable in the browser, clearer errors.
The guide's browser wizard now runs migrate with --progress json and reads the structured event stream (start/account/end) instead of regex-scraping the human log:
Progress % — a real progress bar with a running count and percentage while a preview or move runs, driven by the account events (robust to log truncation; the count comes from the event's own n/total).
Clearer errors — when a run ends the page says how many accounts didn't finish and points at the report, whose failed rows are already marked. Setup-failure wording unchanged.
Resumable in the browser — the guide process outlives the browser, so a reload reconnects to a run in progress and now says so. A run that stopped part way still starts again from where each account left off.
Backend: stdout (JSON events) and stderr (human log) are kept apart in the job and exposed separately in api/state; directory runs are unaffected (only plan runs get --progress json). Frontend changes are in guide.js/guide.css; no HTML structure change.
Tests: mock_guide now asserts the event stream is present and the end counts are right (done/unfinished) for both a clean preview and a partial run. fmt/clippy/cargo test --locked green; guide.js syntax-checked. Docs + CHANGELOG updated.
Note: the live browser render couldn't be screenshotted from here (the guide serves on this host's 127.0.0.1, which the Chrome extension can't reach without the bench ssh tunnel); the event wiring is covered end-to-end by the integration test.
Delivers the migrate **Guide UX** roadmap item: progress %, resumable in the browser, clearer errors.
The guide's browser wizard now runs `migrate` with `--progress json` and reads the structured event stream (`start`/`account`/`end`) instead of regex-scraping the human log:
- **Progress %** — a real progress bar with a running count and percentage while a preview or move runs, driven by the `account` events (robust to log truncation; the count comes from the event's own `n`/`total`).
- **Clearer errors** — when a run ends the page says how many accounts didn't finish and points at the report, whose failed rows are already marked. Setup-failure wording unchanged.
- **Resumable in the browser** — the guide process outlives the browser, so a reload reconnects to a run in progress and now says so. A run that stopped part way still starts again from where each account left off.
Backend: stdout (JSON events) and stderr (human log) are kept apart in the job and exposed separately in `api/state`; directory runs are unaffected (only plan runs get `--progress json`). Frontend changes are in `guide.js`/`guide.css`; no HTML structure change.
Tests: `mock_guide` now asserts the event stream is present and the `end` counts are right (done/unfinished) for both a clean preview and a partial run. fmt/clippy/`cargo test --locked` green; `guide.js` syntax-checked. Docs + CHANGELOG updated.
Note: the live browser render couldn't be screenshotted from here (the guide serves on this host's 127.0.0.1, which the Chrome extension can't reach without the bench ssh tunnel); the event wiring is covered end-to-end by the integration test.
Run the guide's preview and move with --progress json and drive the page
off the structured event stream instead of scraping the log. While a run
is going the page shows a real progress bar with a running count and
percentage; when it ends it says how many accounts didn't finish and
points at the report's marked rows. The guide process outlives the
browser, so a reload reconnects to a run in progress and now says so.
stdout now carries the JSON events and stderr the human log, kept apart
in the job so each is rendered for what it is.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delivers the migrate Guide UX roadmap item: progress %, resumable in the browser, clearer errors.
The guide's browser wizard now runs
migratewith--progress jsonand reads the structured event stream (start/account/end) instead of regex-scraping the human log:accountevents (robust to log truncation; the count comes from the event's ownn/total).Backend: stdout (JSON events) and stderr (human log) are kept apart in the job and exposed separately in
api/state; directory runs are unaffected (only plan runs get--progress json). Frontend changes are inguide.js/guide.css; no HTML structure change.Tests:
mock_guidenow asserts the event stream is present and theendcounts are right (done/unfinished) for both a clean preview and a partial run. fmt/clippy/cargo test --lockedgreen;guide.jssyntax-checked. Docs + CHANGELOG updated.Note: the live browser render couldn't be screenshotted from here (the guide serves on this host's 127.0.0.1, which the Chrome extension can't reach without the bench ssh tunnel); the event wiring is covered end-to-end by the integration test.