gitnexus-plus

dsh-gitnexus-plus

English · 简体中文

Current release: 0.1.7 · npm · Issues

What it does · Install · Troubleshooting · Upstream GitNexus docs

A DeepSeek Harness plugin: see what a GitNexus index covers and what it leaves out, decide whether a refresh is worth running, browse the graph, open GitNexus's own 3D view for the full picture, refresh the index from the sidebar, and search its symbols — and the source text the index recorded — by keyword.

It does not fork GitNexus, rewrite its parser, or bundle/redistribute it. gitnexus is a peer; you provide it.

What it does

• Refresh gate (Tier 0) — before offering a refresh, the panel compares the working tree with the sha256 hashes the index recorded in .gitnexus/gitnexus.json and reports what actually differs: modified / added / deleted, plus files the index's own policy excludes. A clean tree answers in milliseconds without starting the analyzer, and the button says so instead of running a minutes-long rebuild. The verdict is only called "up to date" when it is anchored to the commit the index recorded; an index that recorded none falls back to comparing the working tree with HEAD and says it cannot confirm instead of claiming freshness.
• Graph view — the index's communities drawn on a canvas, with aggregated cross-community edges; click a community to see its member symbols and the relations among them, click a symbol to open its file at the line. Node and edge budgets are applied by the host, and the view states what it left out. A Symbol view button switches to a bounded all-symbol projection when a symbol outside the current communities matters; it is explicitly truncated by file order, and the community view remains the structural overview. Single click selects a community; Expand opens a centered dialog with the same projection and a community sidebar, not a full-screen mode. The card defers its fetch until it is scrolled near the viewport.
• 3D view — the full, rotatable graph is GitNexus's own web UI, embedded instead of reimplemented. The panel starts gitnexus serve (one process per plugin host, stopped when the plugin unloads) and shows the SPA in an overlay iframe, with open in a new tab and stop the server beside it. The server is spawned with the same CLI the analyzer uses, against the GITNEXUS_HOME registry that actually holds this repository, so the URL opens this project rather than another indexed one. A failed start surfaces the process's own output — a version-mismatched index shows Trying to read a database file with a different version instead of a blank frame. An existing server on the port is adopted (and never killed) when it can see the repository. The dialog opens at 86% of the usable viewport, has 紧凑 / 标准 / 铺满 presets, and can be dragged to any size from the bottom-right corner; the size is remembered in localStorage and clamped whenever the window shrinks. Port and embedding are configurable; see webViewPort.
• AI settings, pre-filled — the SPA keeps its provider settings in sessionStorage, which a cross-origin iframe cannot be written to. The plugin therefore serves it a generated index.html (through GITNEXUS_WEB_DIST) that seeds gitnexus-llm-settings before the app boots, taking provider, key and model from GITNEXUS_PLUS_AI_PROVIDER / GITNEXUS_PLUS_AI_API_KEY / GITNEXUS_PLUS_AI_MODEL (plus optional GITNEXUS_PLUS_AI_BASE_URL for OpenAI-compatible endpoints, Azure endpoints and Ollama hosts), so chat works without pasting a key into every tab. Unset variables leave the dialog untouched; a partial or misspelled set is explained on the card (缺少 GITNEXUS_PLUS_AI_MODEL…) while the server still starts. The generated page is removed with the server, an adopted server is never touched, and the key never reaches the panel — only provider, model and endpoint.
• Refresh advice — the staleness verdict also recommends one of none / incremental / reanalyze / rebuild / init / unknown, so a worktree-only comparison never reads as "safe to incrementally refresh" and a --skip-git index is told to re-analyze instead of being offered an impossible incremental run.
• Index coverage — lists the oversized files gitnexus analyze skipped, with size, language share, and generated/minified signals.
• Index freshness — indexed commit vs HEAD, classified current / behind / diverged / unknown, plus the uncommitted-change count.
• Version consistency — compares the GitNexus CLI that wrote the index (runnerIdentity.cliVersion) with the CLI installed now. A mismatch is reported as a warning, not silently rendered as if the index and the query path agreed.
• Graph composition — nodes, edges, communities, processes, embeddings, edges per node.
• Git activity × index — recent commits, authors, branches and most-changed files, each file marked indexed, excluded by design, or missing from the index. Includes an activity × index cross-tab, a baseline review against the indexed commit (or the activity-window start when the index recorded none), a 7/14/30-day commit timeline, and a per-file timeline when a file row is clicked.
• Language distribution — bytes split into languages GitNexus can parse, formats it only recognizes, and everything else. Without GitNexus, a built-in extension map keeps the breakdown useful and marks it builtin, never "parsed".
• Keyword search — a graph query matches symbol name / filePath and returns kind, path and line; the same query asks the index's own full-text index (file_fts) for source text as well, so a term that only appears inside a file body still finds that file. Body hits are file-level and carry no line range, because only the graph knows symbol boundaries, and the footer says which of the two scopes actually ran. Clicking a symbol hit opens the file at that line, and a separate Copy button copies path:line.
• Source fallback — when the graph helper cannot start (no usable shell sandbox, DLL/ABI, busy index), a bounded line search over the indexed files returns mode: "text" instead of pretending to be the graph.
• Multiple projects in one workspace — the workspace can be a container (D:\Project holding gitnexus-plus/, viewer/, or geo/ holding frontend/, backend/). The panel discovers the workspace itself, every indexed project below it, and git repositories that have no index yet. It selects one by default and offers a header switcher when there is more than one; a selection is remembered per workspace, and an unindexed git project can be selected and initialized there.
• No-index visibility — a git project or a plain folder without an index shows a scan overview, language split and the initialize command instead of an empty panel. A folder with no .git is indexed with --skip-git.
• Maintenance — initialize, incremental refresh and full rebuild (--force) run through DSH's shell executor, with no self-escalation. When the index reports FTS as unavailable, a 修复搜索索引（FTS） action runs analyze --repair-fts — the search indexes only, without re-analysing the repository.

Install

Requirements:

• DSH >=0.2.0-rc.2 <0.3.0 (checked item by item against the desktop host 0.2.1-rc.3: the shell, webServer, sandboxPolicy and tools services, the sidebar.right.pane.tab slot and the client primitives this plugin uses are all still there)
• Node >=22
• GitNexus >=1.6.0 <2.0.0 (peer; not installed by this plugin)

dsh plugin add dsh-gitnexus-plus

Restart DSH after adding it. The panel is a right-sidebar tab: open the sidebar's + → guide page → GitNexus 索引.

The desktop profile is managed by Electron; the CLI cannot change it. Use the Web sidebar's Plugins page there. From a local checkout:

dsh plugin --profile web add <absolute path to this package>

GitNexus can be installed by you or by the panel. For a custom location:

GITNEXUS_CLI=/path/to/gitnexus/dist/cli/index.js

Getting GitNexus

Installing it yourself is recommended:

npm install -g gitnexus

The panel can also install it through DSH's shell:

npm install --prefix <DSH_HOME>/gitnexus-plus/gitnexus gitnexus@^1.6.12

That downloads roughly 500 MB–1 GB and needs a C++ toolchain; no registry is hardcoded. Treat the first install as unverified and fall back to the manual command if it fails.

Usage

The panel reports the projects the current workspace contains; it has no global repository list. It looks downward from the workspace: the workspace itself, every indexed descendant, and git repositories without an index are candidates; an indexed or .git directory is a project boundary. When there is more than one candidate the header path becomes a switcher, with a line naming the workspace, the project/index counts and the active path; unindexed projects are labelled. Refreshes, delta, search, graph and maintenance then target the selected project. The default is the remembered choice, then the workspace's own index, then the first indexed project, then the workspace scan; an unindexed container stays on the workspace scan and lists its git projects for initialization. The directory must exist and must not be a filesystem root; a plain folder is still scanned and can be indexed with --skip-git (no commit baseline, no incremental refresh). The route offers no way to browse or list any other path.

Inside DSH:

• tool gitnexus_coverage: { repo, includeLanguages? }
• tool gitnexus_delta: { repo } — would a refresh change anything?
• route GET /api/gitnexus/projects?root=<workspace> — the workspace's projects (indexed and unindexed git)
• route GET /api/gitnexus/coverage?repo=<project>
• route GET /api/gitnexus/search?repo=<project>&q=<keyword>&limit=20
• route GET /api/gitnexus/file-history?repo=<project>&path=<file>&days=7 — one file's bounded commit timeline
• route GET /api/gitnexus/delta?repo=<project> — Tier 0 comparison against the index
• route GET /api/gitnexus/graph?repo=<project>&view=communities|community&id=<community> — a bounded graph projection
• route POST/GET/DELETE /api/gitnexus/analyze (the only entry that changes an index; force=1 for a full rebuild, mode=repair-fts for the search indexes only)
• right-sidebar tab gitnexus

CLI:

npm run build
node lib/bin/gitnexus-coverage.js <repo-path>
node lib/bin/gitnexus-coverage.js -r material-ui         # by registry alias
node lib/bin/gitnexus-coverage.js --all --json           # every indexed repository
node lib/bin/gitnexus-coverage.js <repo> --fail-on-large # CI gate, exit 2
npm run check
npm test

npm test builds and runs the engine, plugin and client suites — at 0.1.7 that is 852 checks (562 engine, 60 plugin, 230 client). The suite no longer depends on a developer's D: drive: the format test builds a disposable repository, and the real-repository smoke test defaults to this checkout (or GITNEXUS_SMOKE_REPO) and skips when it has no index. .github/workflows/ci.yml runs npm ci, npm run check and npm test on Windows and Ubuntu with Node 22 and 24.

Search has two modes:

• graph — the normal path. The host does not load native lbug itself; it starts lib/bin/search-helper.js under system Node, which matches a symbol's name and file path against the graph and returns the exact symbol and line range. Separately, the helper asks the index's own FTS (file_fts) for source text, so a query also finds files whose body mentions the term. Body matches arrive as file-level hits with no line range, because only the graph knows symbol boundaries. When the index was built with --skip-fts, or the FTS extension cannot load, the helper still answers with names and paths and the panel says which of the two scopes ran; the graph query is retried once without FTS before the run fails.
• text — the fallback when the graph query cannot start. It reads the files listed in the index manifest, matches lines, searches code before docs, and caps files/bytes/ matches. The panel labels it 源码关键词（回退）.

Clicking a hit calls ctx.sidebarRight.openResourceIn(sessionId, address, { params: { line } }) to open the platform file viewer at that line; without that service it falls back to copying the path.

Troubleshooting

Start with the state the panel reports: GitNexus absent, no index, index stale, FTS unavailable. The rows below cover this plugin's boundary; the linked upstream GitNexus path owns the rest.

Symptom	What to do here	Upstream GitNexus path
The panel says GitNexus is absent	Install it yourself, or use the panel's install. For a non-standard location set GITNEXUS_CLI=/path/to/gitnexus/dist/cli/index.js.	gitnexus/README.md — Requirements, Quick Start
The project has no index	Use 初始化索引 in the panel, or run gitnexus analyze --index-only <repo>. For a folder that is not a git repository the panel's command adds --skip-git (upstream requires it); the resulting index has no commit baseline and no incremental refresh.	README.md — CLI Reference, RUNBOOK.md — Index out of date
A subdirectory has an index but the switcher does not list it	The search only goes down from the current workspace, never up or to siblings. It skips hidden directories, node_modules and build output, and has depth/count/time limits. Confirm <workspace>/<child>/.gitnexus/gitnexus.json; if the index is in a skipped or very deep directory, open that directory as the workspace. Multiple projects appear in the header switcher, including git projects without an index; a truncated search is labelled as such.	This plugin's discovery; no upstream GitNexus path.
Refresh fails, spawn EPERM, or the index stays incremental-in-progress	The panel's command already sets GITNEXUS_MEMORY=off, NODE_OPTIONS=--max-old-space-size=8192, GITNEXUS_HOME=<repo>/.gitnexus/plugin-home and --index-only. If the sandbox still refuses, run the copied command in your own shell; the plugin will not escalate.	RUNBOOK.md — LadybugDB / lock errors, Memory / analyze crashes
Refresh fails with EPERM … mkdir or rmdir '<repo>\.gitnexus\parsedfile-store'	GitNexus deletes this run-scoped store at the start of every parse, and a parse worker creates it again during the parse — both directions can be refused. Two causes, both addressed in 0.1.4: the plugin no longer pre-creates the directory (that was 0.1.3's rmdir), and the analyzer's shell call now carries the repository as its sandbox workspace root. A panel route has no session, so the sandbox used to fall back to the DSH application directory, whose write capability is a different identity — the repository's write grant never applied. If it still fails, the deployment's mode is read-only: run the copied command in a normal terminal.	RUNBOOK.md — LadybugDB / lock errors, RUNBOOK.md — Clean slate
Windows reports windows-acl-run: SetNamedSecurityInfoW failed (Win32 5): grantWrite(D:\Program Files\DSH Desktop)	The ACL sandbox failed to grant write on the workspace root; D:\Program Files\DSH Desktop is the DSH application directory, not a project. Since 0.1.5 the search/graph helpers use <repo>/.gitnexus as the policy root, and the installer uses the plugin prefix; a failed install returns the copyable command. If an ordinary shell command still fails this way, the session workspace itself is the install directory: open a writable project. Do not add ACL grants to Program Files.	This plugin's policy-root fix; the DSH sandbox itself has no upstream GitNexus path.
Incremental analyze hangs, or the database reports Maximum database size … has been reached	Use 全量重建 (--force), or the clean-slate steps.	RUNBOOK.md — Clean slate, gitnexus/README.md — Troubleshooting
Refresh fails with EPERM … open '<repo>\.gitnexus\lbug.init.lock' or unable to acquire init lock	A transient file lock, not a permissions problem: the ACL for .gitnexus was checked on the machine that reported it and came back healthy. GitNexus's first write is that lock, and a scanner, the indexer, or a crashed run can hold it. The plugin clears a stale lock and retries once automatically (the run shows attempts: 2). If it still fails, wait a moment and retry, or run the copied command in a normal terminal.	This plugin's retry plus the analyzer's own lock file; no upstream GitNexus path.
Search fails with A dynamic link library (DLL) initialization routine failed / lbugjs.node	Graph search runs in lib/bin/search-helper.js, never in the Electron host. Restart DSH after upgrading and keep node on the shell PATH. If the helper cannot start at all, search falls back to source text.	gitnexus/README.md — Troubleshooting
Windows search returns very few hits, or the panel warns FTS is unavailable	Read capabilities.fts in .gitnexus/meta.json first: status: "unavailable" is a record written when the index was built, and it can be stale — measured here, the record said unavailable while gitnexus doctor reported Full-text search: available and the extension files were present. 修复搜索索引（FTS） (analyze --repair-fts) rewrites that record and the search indexes without touching the graph; the panel then reports what it actually searched instead of repeating the manifest. Other causes, in order: the index was built with --skip-fts; the repair could not run out of process because the sandbox refuses the spawn (spawn EPERM — run the copied command in a terminal); or the extension genuinely cannot load, which is a missing Windows runtime (VC++ 2015-2022 x64 and OpenSSL 3) — the rarest of the four, and worth confirming rather than assuming.	gitnexus/README.md — Windows: full-text search unavailable, Analyze warns about unavailable FTS
The refresh button says 无需刷新 and is disabled	That is the Tier 0 verdict, not a failure: every file the index recorded still hashes the same, so re-running the analyzer would change nothing. 仍然刷新 forces it anyway (useful after a schema or GitNexus upgrade). If the index recorded no commit baseline, the panel does not claim 无需刷新 — it says it cannot confirm and leaves the button enabled.	This plugin's delta engine; no upstream GitNexus path.
The gate says 无法确认 instead of 无需刷新	The index recorded no commit, so the comparison can only see the working tree. A confined analyze cannot start git, which is how the manifest ends up with an empty lastCommit — measured here: the same command writes it in a normal terminal and leaves it empty under the sandbox. Run the copied command outside the sandbox once if you want the stronger verdict; the refresh button stays usable either way.	This plugin's delta engine plus the analyzer's git access; no upstream GitNexus path.
The graph card is empty, or fails with 404	A 404 means the host predates /api/gitnexus/graph — restart DSH, not just the page. An empty canvas with a message means the index has no communities yet (an old index), or the store is busy: refresh the index. Nodes are capped by design; the card states how much it left out.	This plugin's host route; graph data itself comes from the GitNexus index.
The graph loads for some projects but spins or returns 504 for others	On Windows the ACL sandbox's first workspace grant propagates an inheritable ACE across the whole repository, which can exceed the 25 s helper timeout on a large tree; a project whose grant is already cached is fast. Since 0.1.5 the search/graph helpers root the policy at <repo>/.gitnexus, so the grant covers only the index; restart DSH. If it still fails, confirm .gitnexus/lbug exists and that no analyze is holding the index.	This plugin's sandbox policy root; graph data itself comes from the GitNexus index.
The 3D view will not open, or its overlay stays blank	Read the card first: unavailable means the host has no shell executor or the machine has no gitnexus CLI (the card prints the install command); failed carries the child process's own output, where a busy port (EADDRINUSE) and an index written by another CLI version (database file version) are the two common cases. 服务在跑，但索引对不上 means the server on that port does not list this repository in its registry: refresh this repository's index, or stop the server you started yourself. A missing card or a 404 means the host never mounted the route — restart DSH.	This plugin's web-view lifecycle; the SPA is the web/ directory inside the GitNexus package.
The AI settings inside the 3D view are still empty	The AI 设置 line on the card names the reason: no GITNEXUS_PLUS_AI_* variables set (export them and restart DSH or press 重新启动), a partial set (缺少 GITNEXUS_PLUS_AI_MODEL / 缺少 GITNEXUS_PLUS_AI_API_KEY), or 外部启动的服务 — that server was not started by the plugin, so its page cannot be seeded and the dialog has to be filled once by hand. The variables are read from the DSH process environment, so a restart is required after changing them.	This plugin's generated page (GITNEXUS_WEB_DIST); the SPA keeps its own settings in sessionStorage.
Clicking a search hit does not open a file	The click uses ctx.sidebarRight.openResourceIn; a profile without that service falls back to copying path:line. Restart DSH; if it persists, use the Copy button.	This panel/DSH boundary; no upstream GitNexus path.
The file timeline fails with 404/401	The client hot-reloaded before the host did, so /api/gitnexus/file-history is not mounted yet. Restart DSH (not just refresh the page).	This plugin's host route; no upstream GitNexus path.
Analyze runs out of memory	Keep the panel's NODE_OPTIONS / GITNEXUS_MEMORY settings, or raise the heap manually; the index may need a full rebuild.	gitnexus/README.md — Analysis runs out of memory, RUNBOOK.md — Memory / analyze crashes
A large file is missing from the graph	This is what the panel reports: size/share, generated/minified heuristics, binary detection. Raising the cap is an upstream analyze option; this plugin only reports the skip.	gitnexus/README.md — Large files are being skipped
Native install fails (@ladybugdb/core, tree-sitter-*)	The plugin runs npm install --prefix …; it needs a C++ toolchain and a reachable registry. Run the manual command from Getting GitNexus to see the compiler error.	gitnexus/README.md — Installation fails with native module errors
The panel does not appear at all	Check that dsh plugin add succeeded and DSH was restarted; open it from the sidebar's + guide page. For the desktop profile, use the Web Plugins page.	This plugin's install path; no upstream GitNexus path.

Upstream GitNexus documentation

This README describes the plugin, not GitNexus. GitNexus behavior follows its source docs. Repository: abhigyanpatwari/GitNexus (branch main).

Topic	Path
Install, CLI, environment variables, MCP	README.md
CLI package, requirements, full Troubleshooting	gitnexus/README.md
Index stale, clean slate, locks, memory	RUNBOOK.md
Architecture and data flow	ARCHITECTURE.md
Tests and guardrails	TESTING.md, GUARDRAILS.md
CLI command reference	gitnexus/skills/gitnexus-cli.md
Language-specific notes	docs/languages/

Local .docs/ notes are gitignored; the links above are the published source of truth.

Maintenance commands

The panel shows and runs more than a bare gitnexus analyze:

$env:GITNEXUS_MEMORY='off'; $env:NODE_OPTIONS='--max-old-space-size=8192'; `
  $env:GITNEXUS_HOME='<repo>/.gitnexus/plugin-home'; `
  gitnexus analyze --index-only '<repo>'

Add --force for a full rebuild, or --repair-fts alone to rebuild the search indexes without touching the graph (the panel offers that as 修复搜索索引（FTS） when the index reports FTS as unavailable). A folder without .git also gets --skip-git.

• --skip-git — GitNexus refuses a directory without .git even when its path is explicit; this flag indexes the folder directly. The index then has no commit baseline, no incremental refresh and no Git activity, and the panel says so.

• GITNEXUS_MEMORY=off — stops the CLI from re-spawning itself over piped stdio, which a confined sandbox denies (spawn EPERM).

• NODE_OPTIONS=--max-old-space-size=8192 — supplies the heap that respawn wanted.

• GITNEXUS_HOME — redirects the global registry write into the project, so a failed write to ~/.gitnexus cannot leave the index stuck at incremental-in-progress.

• --index-only — otherwise analyze rewrites AGENTS.md, CLAUDE.md and skill files inside the repository.

--skip-fts is adaptive per index: no flag when the manifest says FTS is available, and the flag when it is not. skipFts: true can force the flag; there is no config that forces FTS on, because enabling it is a repair (gitnexus analyze --repair-fts), not an incremental refresh — so the panel exposes it as its own action, and a repair run never carries --skip-fts (the CLI accepts that pair and exits 0 having done nothing).

AI settings for the embedded web UI

The embedded GitNexus SPA has its own chat, and its AI settings are stored per tab. Export these in the environment DSH starts from, and the panel seeds them whenever it starts the server:

Variable	Meaning
GITNEXUS_PLUS_AI_PROVIDER	One of openai, gemini, anthropic, azure-openai, ollama, openrouter, minimax, glm, deepseek. Common aliases are accepted (google, claude, azure, z.ai, open-ai).
GITNEXUS_PLUS_AI_API_KEY	The provider key. Not needed for ollama.
GITNEXUS_PLUS_AI_MODEL	Model id as the provider spells it, e.g. gpt-4o-mini, gemini-2.0-flash, llama3.2.
GITNEXUS_PLUS_AI_BASE_URL	Optional. OpenAI-compatible endpoint, Azure endpoint (required for azure-openai), or Ollama host.

Nothing is sent over the network to configure this: the page the server hands out seeds sessionStorage inline, before the SPA's module script runs. With none of the variables set the dialog is left exactly as it was, and the card says so. A partial set (say, provider and model but no key) is reported on the card and the server still starts, so a typo never costs you the 3D view.

License (read before commercial use)

This plugin is MIT (see LICENSE).

GitNexus is PolyForm-Noncommercial-1.0.0: noncommercial use is granted, commercial use is restricted. gitnexus is a peer; this package does not install, bundle or redistribute it. But using this plugin's GitNexus-backed features (reading an index, refreshing it, installing it) puts your use of GitNexus under GitNexus's license; commercial use needs a separate grant from GitNexus's author:

https://github.com/abhigyanpatwari/GitNexus/blob/main/LICENSE

In one line: MIT covers this plugin's code; GitNexus's license covers GitNexus, and using the related features puts that use under it.

Boundaries

• Coverage and search are read-only; maintenance is a separately confirmed write and never starts by itself.
• The refresh gate compares content hashes of the files the index recorded. It cannot see a change the analyzer would make for its own reasons (a schema upgrade, a new feature mode); 仍然刷新 exists for exactly that case.
• The graph view draws communities by default, not every symbol: the overview is the community graph, and a drill-down shows at most the configured node budget of one community's members. The Symbol view is a bounded all-symbol projection ordered by file and explicitly truncated, not a claim of completeness. Both say when they are truncated.
• The 3D view is a second process, started on demand: it needs the gitnexus CLI on the machine and, on a host with no shell executor, only the manual command is offered. Embedding is display-only — the iframe is another origin, so the panel cannot script into it; select things in the SPA itself, or open it in its own tab.
• A server started by hand on the configured port is adopted only when its registry lists this repository; otherwise the plugin tries the next port rather than killing it. The card says which case it is in. An adopted server keeps its own page, so the AI settings cannot be seeded into it — fill the dialog once by hand there.
• The seeded AI settings live in sessionStorage, exactly like hand-entered ones: the SPA clears them when the tab closes, and the plugin re-seeds them on the next start. Nothing is written to the repository or to ~/.dsh beyond the generated page, which is deleted when the server stops.
• The plugin reports facts about a GitNexus index; it does not rewrite the parser or reimplement the graph database.
• Graph search answers with two scopes: symbol names and file paths from the graph, and source text from the index's own FTS. Body hits are file-level and carry no line range, and the footer states which scope ran. The text fallback matches lines and is capped.
• The source fallback only covers files in the index manifest; refresh the index for new files.
• An index built with --skip-git has no commit baseline: the gate can only say it cannot confirm, a refresh re-analyses the whole folder, and the Git activity cards do not appear.
• The workspace search is bounded: 12 levels, 4000 directories and 2 seconds by default; it skips node_modules, build output and every hidden directory, and does not follow symlinks. Indexed projects are preferred by default; unindexed git projects are listed and can be initialized. An indexed or .git directory stops the descent. When a bound stops the search the panel says it may have missed a project.
• Deeper design/build notes are kept out of the public README; this file stays at the "what it does" and "how to fix it" level.