* test: add reload fallback for sidebar-focus-onboarding flake
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* fix: update sidebar-focus-onboarding test strategy to use runIndex and simplify artifact naming
* test: retry the reload fallback once more for sidebar-focus-onboarding
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* fix: update sidebar-focus-onboarding test strategy to use sharding and restore previous run state
---------
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
## Summary
- Replaces the madge-based `check-cycle-references` with a `dependency-cruiser`-based check, cruised once per npm workspace package.
- Keeps the checker, dependency-cruiser config, and known-cycle baseline together under `scripts/circular-references/`.
- Uses a committed baseline to grandfather existing cycles while failing on new cycles and stale baseline entries.
- Cleans the existing `insomnia-inso` type cycle by using `insomnia-data`'s `AllTypes` instead of importing the database container type.
- CI explicitly uses Bash for correct `tee`/pipeline failure propagation, safely handles skipped checks, and posts a PR report.
- Dropped `madge`/`.madgerc`, added `dependency-cruiser`.
add initial settings for legacy test
add initial check for legacy unit test suites
show dropdown
remove spec route and merged with default debug page
showing document as collection
remove document term in UI
fix lint issue
fix ut failures
## Problem
In the environment editor, double-clicking an environment name (sidebar or header) to rename it and pressing Enter could freeze the entire page: nothing responded to clicks or keyboard until pressing Escape. Root cause found empirically (instrumented focus trace + CPU profile + pause stacks) and confirmed against the installed library source.
## Root cause
Committing the rename unmounts the focused input **while the Enter keypress is still in flight**. `FocusScope`'s `restoreFocus` (async rAF) then raced the RAC collection correction and landed DOM focus on a draggable row — the KV editor's trailing blank row — before the same keypress's keyup fired. `@react-aria/dnd`'s keyboard-drag handler (`useDrag.mjs` `onKeyUpCapture`: `if (target === currentTarget && key === 'Enter') startDragging(...)`) read that keyup as a drag release and started a `DragSession`, which:
- `ariaHideOutside`-hides everything on the page except the drag source/drop targets, and
- capture-phase `preventDefault`s every `focusin`/`focusout`/`mousedown`/`keydown`.
Result: the whole app is inert until Escape (the session's only user-facing exit). CPU profile showed the renderer ~92% idle — the page wasn't busy, it was locked.
## Fix
- **`EditableInput`**: drop `restoreFocus` from the `FocusScope`. On commit, focus settles on `document.body`, the collection stays unfocused, and the keyboard drag can never be armed (mechanism removed, not mitigated).
- **`EditableInput`**: `settledRef` guard so Enter/Escape/blur commit exactly once — the unmount blur previously fired `onSubmit` a second time (double mutation + double revalidation per rename). Side effect: **Escape now truly cancels** — previously the unmount blur committed the typed value after Escape.
- **`OneLineEditor`**: the `ensureFocus` rAF loop bails when the CodeMirror wrapper is detached from the DOM, so a stale loop from a remount cannot steal focus into a mid-teardown editor.
## Known behavior change
After committing/canceling a rename, focus settles on the document body instead of returning to the trigger element. Keyboard users need to Tab back into the tree/list. `restoreFocus` could not be kept without re-arming the freeze (the drag is armed precisely by focus landing on a draggable row mid-keypress); a safe follow-up would be restoring collection position only after the keyup completes.
* feat(sync): allow deleting unsynced remote files from the project dashboard
Unsynced workspace cards now reveal a trash icon on hover that opens a
confirmation dialog before permanently archiving the remote backend project.
Adds archiveBackendProject(backendProjectId) to insomnia-vcs so a project can be
archived without being pulled locally first, exposes it through the global sync
IPC bridge, and reuses it from VCS.archiveProject. The local meta.json cleanup is
now guarded by hasItem, since a never-pulled project has no local meta file.
* test(smoke): disambiguate Delete dropdown locator in cloud-sync test
* test(smoke): cover deleting an unsynced remote file from the project dashboard
Builds each hint row with createElement/textContent/title assignment
rather than a templated HTML string, treating hint values as text
content rather than markup.
[INS-3702](https://konghq.atlassian.net/browse/INS-3702)
## Summary
- Extracts a JSONPath from each streaming SSE message and concatenates it into one readable transcript, shown in a new "Summary" tab next to Events — useful for debugging LLM streaming APIs (OpenAI, Anthropic, Gemini) without scrolling through raw chunks.
- Auto-infers the JSONPath from the request URL for known provider endpoints (OpenAI Chat Completions/legacy Completions/Responses, Anthropic Messages, Google Gemini streamGenerateContent), matched by pathname only (not full URL/host), so self-hosted or reverse-proxied endpoints that keep the same path shape still match. Falls back to a manually-editable path otherwise.
- Handles curl's SSE event log being chunk-granular rather than frame-granular (a JSON payload can span multiple raw network reads, or multiple SSE frames can land in one chunk) by reconstructing the raw wire text and re-parsing `data:` frames properly.
- Handles Gemini's default `streamGenerateContent` response (no `?alt=sse`), which is a single top-level JSON array with no `data:` frames and no blank lines between elements, by scanning the array's bracket/brace depth by hand and pulling out whichever elements have fully closed so far — including mid-stream, before the array's closing `]` (or even the last element's own closing `}`) has arrived — so the summary renders progressively instead of only after the full response finishes.
- Summary tab defaults to selected when the URL matches a known provider, otherwise Events stays default. Plain text/Markdown render toggle for the summary output.
- Scoped to `curl` (SSE) responses only — WebSocket, `socketIO`, and `mcp` responses are untouched.
## Problem
When editing a project environment in Table View with no key/value entries, the trailing blank row could freeze the UI after renaming the environment in the header and immediately clicking the blank `Input Name` field.
The blank row was simultaneously managed by React Aria's `ListBox autoFocus="last"`, an imperative `ListBoxItem.onFocus` handoff, and `OneLineEditor` autofocus/retry logic. In the single-item boundary case these focus owners could race with `FocusScope` restoration and async environment revalidation.
## Fix
- Keep the trailing blank row inside the existing React Aria `ListBox` so row semantics, styling, keyboard navigation, drag-and-drop, and state behavior remain unchanged.
- Remove `ListBox autoFocus="last"` and the blank-row `ListBoxItem` focus handoff.
- Give the blank row's `OneLineEditor` one-shot autofocus on initial editor mount. This works for both empty and non-empty lists and is cleared after the initial autofocus.
- Track editor refs by distinct name/value editor ids.
- Restore focus once to the editor that was active when a blank row was converted into a persisted pair, after the persisted data update has mounted the new editor.
This prevents repeated focus stealing while preserving focus through the blank-row-to-persisted-row transition.
## Summary
- Splits the single "Manage Environments" popover into two independent dropdowns — project-level and collection-level — each with a scope tooltip and an inheritance-order hint (folder overrides collection, which overrides project).
- Replaces the hidden "+" menu in the collection environment editor and the project-level full-page environment editor with explicit, always-visible "Add Sub Environment" / "Add Private Sub Environment" buttons.
- Adds an "Add Project Environment" action to the project dropdown (does not auto-select the new environment).
- Adds a keyboard shortcut for the project dropdown (Cmd/Ctrl+Alt+E), alongside the existing collection-environment shortcut (Cmd/Ctrl+Shift+E).
- Fixes smoke tests broken by removing the old single-picker trigger, and adds new coverage for the split dropdowns and create flows.
The madge-based check-cycle-references never had a committed .madgerc,
so real CI silently resolved without tsconfig path aliases and only
ever saw 10 cycles instead of the ~200 that actually exist once `~/`
imports resolve correctly. Also replaces the base-branch-diff CI
mechanism (checkout base branch, compare cycle counts, never fails)
with a per-package dependency-cruiser cruise gated by a committed
baseline: existing cycles are grandfathered in, any genuinely new
cycle anywhere in the repo now fails CI.
[INS-2791](https://konghq.atlassian.net/browse/INS-2791)
## Summary
- Switching a request's project environment (activeGlobalEnvironment) left the request pane's template values stale, since its remount `key` only tracked the workspace environment (activeEnvironment).
- Added the project environment id/modified timestamp to the URL bar's remount key so it also refreshes on project environment switch.
## Background
- In the latest vite up gradation, the log is `VITE v7.3.1 ready in 1145 ms` instead of `VITE ready in`
- Playwright SIGKILLs the process by default, which leaves a stale .vite-port file
## Changes
- Update the wait pattern
- Use gracefulShutdown
- Always try to cleanup when receive any exit event
actions/checkout steps across CI workflows leaves GITHUB_TOKEN persisted in git config after checkout. None of these steps perform a git push using that persisted credential, disable credential persistence on the actions.
## Background
- Cloud Sync workspace uses local workspace id as its id, which may duplicate with the workspace id in the local db. (Clone a github repo -> convert to cloud sync -> clone it again)
## Changes
- Use team project id + project id as the unique id
* fix(main): compare full origin, not string prefix, for renderer nav guard (INS-3622)
Use isTrustedAppOrigin (parsed origin comparison) instead of
url.startsWith(appUrl) for will-navigate and will-redirect on the main
window.
* fix(main): restrict trusted-origin check to http/https schemes (INS-3622)
blob:/data: URLs report an origin derived from embedded text, not
actual creation context, so they could spoof isTrustedAppOrigin.
[INS-3637](https://konghq.atlassian.net/browse/INS-3637)
## Summary
- SSE ("Event Stream") sends re-fetched the raw, unrendered request from the database instead of using the already-rendered/de-duplicated/interpolated request the renderer had computed, so headers/authentication/body reaching curl could diverge from what the user configured.
- `openCurlConnection` now takes one fully-rendered request object (`{ workspaceId, renderedRequest, initialPayload? }`) instead of piecemeal fields, drops the redundant DB read, and computes the auth header in-process via `getAuthHeader` instead of a separate IPC round trip.
- Fixed `createConfiguredCurlInstance`'s manual-proxy branch, which resolved protocol/hostname from the raw stored URL instead of the request's actual URL.
- Added `curl.test.ts` and `libcurl-promise.test.ts`; patched shared test infra (`setup-vitest.ts`, `src/__mocks__/electron.ts`) so named imports from `electron` resolve under the mock and `electron.app.on(...)` doesn't throw.
## Test plan
- [x] `npx tsc --noEmit` clean on changed files
- [x] `npx eslint` clean on changed files
- [x] `npx vitest run` — full suite: 162 files / 2244 passed, 15 pre-existing skips
- [x] Manually verify an SSE request (e.g. POST with `Accept: text/event-stream` to a streaming API) sends the expected single Accept header and correct body/auth
[INS-3637]: https://konghq.atlassian.net/browse/INS-3637?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
* fix(cloud-sync): surface stale/reverted staged changes instead of silently committing them
status() diffed the working tree against HEAD only, so a key whose content
returned to HEAD while still staged (or was staged-then-deleted before ever
being committed) was invisible to both the staged and unstaged views —
takeSnapshot() would then commit the stale staged content unnoticed
(INS-3520).
- status() now diffs against the index (HEAD with the stage overlaid via a
new applyStageToState helper, also reused by takeSnapshot()) so these
cases surface as actionable unstaged entries, with explicit branches for
every stage/entry combination instead of a single blobId comparison that
was tautological for deletions.
- stage() drops an entry instead of storing it when the incoming content is
a no-op relative to HEAD, keeping the sparse stage map from accumulating
entries that would otherwise still show as staged and produce empty
commits.
- Removed the unused key field from status()'s return (and the Status
type), which was computed but never read anywhere.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Fix type check
* rm doc
---------
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
* chore: support dynamic port
* fix: handle missing .vite-port and prevent stale file race
- window-utils.ts: wrap .vite-port read in try/catch with fallback to
default port 3334, preventing crash when file is missing
- esbuild.entrypoints.ts: delete .vite-port at start of dev build so
wait-on doesn't pick up a stale port from a previous run
* fix: derive smoke-test webServer port from per-worktree .vite-port
Hardcoded url: 'http://localhost:3334' made playwright's webServer
reuse-detection cross-worktree: if another worktree's dev server was
already answering on 3334, this worktree's tests silently reused it
instead of starting their own. Read the worktree's own .vite-port file
(written by vite.config.ts) instead, falling back to plain stdout-regex
readiness when no port file exists yet.
Bingbing