adtec-core-package 3.1.9 → 3.2.0

package/src/css/elementUI/scrollbar.scss

@@ -3,6 +3,7 @@
 @use 'mixins/mixins' as *;
 @use 'mixins/var' as *;
 @use 'common/var' as *;
+@use '../../assets/style/scrollbar-classic.scss' as classic;
 
 @include b(scrollbar) {
   @include set-component-css-var('scrollbar', $scrollbar);
@@ -16,6 +17,9 @@
   @include e(wrap) {
     overflow: auto;
     height: 100%;
+    box-sizing: border-box;
+    /* 预留滚动条槽位，避免 thumb 压在正文上 */
+    padding-right: calc(var(--el-scrollbar-size, 8px) + 4px);
 
     @include m(hidden-default) {
       scrollbar-width: none;
@@ -31,7 +35,7 @@
     width: 0;
     height: 0;
     cursor: pointer;
-    border-radius: inherit;
+    border-radius: calc(var(--el-scrollbar-size, 8px) / 2);
     background-color: var(
       #{getCssVarName('scrollbar-bg-color')},
       map.get($scrollbar, 'bg-color')
@@ -56,14 +60,17 @@
 
   @include e(bar) {
     position: absolute;
-    right: 2px;
+    right: 4px;
     bottom: 2px;
     z-index: 1;
-    border-radius: 4px;
+    border-radius: calc(var(--el-scrollbar-size, 8px) / 2);
+    opacity: 0;
+    transition: opacity getCssVar('transition-duration') ease-out;
 
     @include when(vertical) {
-      width: 6px;
+      width: var(--el-scrollbar-size, 8px);
       top: 2px;
+      background-color: rgba(0, 0, 0, 0.04);
 
       > div {
         width: 100%;
@@ -71,14 +78,22 @@
     }
 
     @include when(horizontal) {
-      height: 6px;
+      height: var(--el-scrollbar-size, 8px);
       left: 2px;
+      background-color: rgba(0, 0, 0, 0.04);
 
       > div {
         height: 100%;
       }
     }
   }
+
+  &:hover,
+  &:active {
+    @include e(bar) {
+      opacity: 1;
+    }
+  }
 }
 
 .#{$namespace}-scrollbar-fade {

package/src/css/vxeTableUI/components/table.scss

@@ -1,4 +1,5 @@
 @use '../helpers/baseMixin.scss';
+@use '../../../assets/style/scrollbar-classic.scss' as classic;
 @use './icon.scss';
 @use './table-module/all.scss';
 
@@ -79,34 +80,16 @@
   overflow-x: scroll;
 }
 
-/* 仅显示外层滚动条：鼠标进入表格显示，移出隐藏 */
+/* vxe 表格：hover 时显示现代圆角滚动条 */
 .vxe-table--scroll-x-handle,
 .vxe-table--scroll-y-handle {
-  scrollbar-width: none;
-  -ms-overflow-style: none;
-  &::-webkit-scrollbar {
-    width: 8px;
-    height: 8px;
-    background: transparent;
-  }
-  &::-webkit-scrollbar-thumb {
-    background: transparent;
-    border-radius: 4px;
-  }
-  &::-webkit-scrollbar-track {
-    background: transparent;
-  }
+  @include classic.adtec-scrollbar-hidden;
 }
 
 .vxe-table:hover {
   .vxe-table--scroll-x-handle,
   .vxe-table--scroll-y-handle {
-    scrollbar-width: thin;
-    scrollbar-color: #DDDEE0 transparent;
-  }
-  .vxe-table--scroll-x-handle::-webkit-scrollbar-thumb,
-  .vxe-table--scroll-y-handle::-webkit-scrollbar-thumb {
-    background: #DDDEE0;
+    @include classic.adtec-vxe-scrollbar-active;
   }
 }
 
@@ -604,10 +587,10 @@
     }
   }
   .vxe-table--scroll-x-virtual {
-    height: 0 !important;
+    height: 0;
   }
   .vxe-table--scroll-y-virtual {
-    width: 0px !important;
+    width: 0;
   }
   .vxe-table--scroll-x-virtual,
   .vxe-table--scroll-y-virtual {
@@ -635,10 +618,10 @@
   .vxe-table--scroll-x-handle {
     overflow-y: hidden;
     overflow-x: scroll;
-    height: 8px;
+    height: var(--vxe-scrollbar-size, 8px);
   }
   .vxe-table--scroll-x-wrapper {
-    height: 8px;
+    height: 100%;
   }
   .vxe-table--scroll-y-handle,
   .vxe-table--scroll-y-wrapper {
@@ -650,7 +633,7 @@
   .vxe-table--scroll-y-handle {
     overflow-y: scroll;
     overflow-x: hidden;
-    width: 8px;
+    width: var(--vxe-scrollbar-size, 8px);
     height: 100%;
   }
   .vxe-table--scroll-x-space {
@@ -925,10 +908,20 @@
     border-collapse: separate;
     table-layout: fixed;
   }
-  .vxe-table--render-wrapper{
-    height:100%;
+  .vxe-table--render-wrapper {
+    height: 100%;
+    display: flex;
+    flex-direction: column;
+    overflow: hidden;
+
     .vxe-table--layout-wrapper {
-      height:100%
+      flex: 1;
+      min-height: 0;
+      height: auto;
+    }
+
+    .vxe-table--scroll-x-virtual {
+      flex-shrink: 0;
     }
   }
   &:not(.is--empty) {

package/src/utils/excelPreviewUtil.ts

@@ -51,6 +51,9 @@ type WorkbookStyles = {
   CellXf?: Array<Record<string, unknown>>
 }
 
+/** xlsx-js-style 运行时附带 Styles，官方 WorkBook 类型未声明 */
+type StyledWorkBook = XLSX.WorkBook & { Styles?: WorkbookStyles }
+
 /** Excel 默认主题色（Office 2013+，含 accent / hyperlink） */
 const EXCEL_THEME_COLORS: Record<number, string> = {
   0: '#FFFFFF',
@@ -392,8 +395,8 @@ export const parseExcelWorkbook = async (src: Blob | ArrayBuffer): Promise<Excel
     cellDates: true,
     cellStyles: true,
     ...(isOleXls(buffer) ? {} : {}),
-  })
-  const styles = workbook.Styles as WorkbookStyles | undefined
+  }) as StyledWorkBook
+  const styles = workbook.Styles
   const styleIndexMaps = isZipXlsx(buffer)
     ? parseXlsxStyleIndexMaps(buffer, workbook.SheetNames.length)
     : []
@@ -476,6 +479,3 @@ export const searchExcelSheets = (
   })
   return matches
 }
-
-export const cellKey = (sheetIndex: number, row: number, col: number) =>
-  `${sheetIndex}:${row}:${col}`

package/src/utils/officePreviewUtil.ts

@@ -121,19 +121,8 @@ export const isLegacyDocFile = (type?: string, name?: string, fileUrl?: string)
 export const isHeaderPreviewFile = (type?: string, name?: string, fileUrl?: string) =>
   HEADER_PREVIEW_TYPES.has(toOfficePreviewType(type, name, fileUrl))
 
-const pdfAssetBase = () => {
-  const base = import.meta.env.BASE_URL || '/'
-  return base.endsWith('/') ? base : `${base}/`
-}
-
-/** pdf.js 加载参数：CJK 预览需 cMap；缺嵌入字体时尝试系统字体 */
-export const buildPdfJsLoadOptions = (data: ArrayBuffer) => {
-  const assetBase = pdfAssetBase()
-  return {
-    data,
-    useSystemFonts: true,
-    cMapUrl: `${assetBase}pdfjs/cmaps/`,
-    cMapPacked: true,
-    standardFontDataUrl: `${assetBase}pdfjs/standard_fonts/`,
-  }
-}
+/** pdf.js 加载参数：依赖 PDF 内嵌字体与浏览器系统字体 */
+export const buildPdfJsLoadOptions = (data: ArrayBuffer) => ({
+  data,
+  useSystemFonts: true,
+})

package/.claude/skills/gitnexus/gitnexus-cli/SKILL.md

@@ -1,83 +0,0 @@
----
-name: gitnexus-cli
-description: "Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\""
----
-
-# GitNexus CLI Commands
-
-All commands work via `npx` — no global install required.
-
-## Commands
-
-### analyze — Build or refresh the index
-
-```bash
-npx gitnexus analyze
-```
-
-Run from the project root. This parses all source files, builds the knowledge graph, writes it to `.gitnexus/`, and generates CLAUDE.md / AGENTS.md context files.
-
-| Flag           | Effect                                                           |
-| -------------- | ---------------------------------------------------------------- |
-| `--force`      | Force full re-index even if up to date                           |
-| `--embeddings` | Enable embedding generation for semantic search (off by default) |
-| `--drop-embeddings` | Drop existing embeddings on rebuild. By default, an `analyze` without `--embeddings` preserves them. |
-
-**When to run:** First time in a project, after major code changes, or when `gitnexus://repo/{name}/context` reports the index is stale. In Claude Code, a PostToolUse hook detects staleness after `git commit` and `git merge` and notifies the agent to run `analyze` — the hook does not run analyze itself, to avoid blocking the agent for up to 120s and risking KuzuDB corruption on timeout.
-
-### status — Check index freshness
-
-```bash
-npx gitnexus status
-```
-
-Shows whether the current repo has a GitNexus index, when it was last updated, and symbol/relationship counts. Use this to check if re-indexing is needed.
-
-### clean — Delete the index
-
-```bash
-npx gitnexus clean
-```
-
-Deletes the `.gitnexus/` directory and unregisters the repo from the global registry. Use before re-indexing if the index is corrupt or after removing GitNexus from a project.
-
-| Flag      | Effect                                            |
-| --------- | ------------------------------------------------- |
-| `--force` | Skip confirmation prompt                          |
-| `--all`   | Clean all indexed repos, not just the current one |
-
-### wiki — Generate documentation from the graph
-
-```bash
-npx gitnexus wiki
-```
-
-Generates repository documentation from the knowledge graph using an LLM. Requires an API key (saved to `~/.gitnexus/config.json` on first use).
-
-| Flag                | Effect                                    |
-| ------------------- | ----------------------------------------- |
-| `--force`           | Force full regeneration                   |
-| `--model <model>`   | LLM model (default: minimax/minimax-m2.5) |
-| `--base-url <url>`  | LLM API base URL                          |
-| `--api-key <key>`   | LLM API key                               |
-| `--concurrency <n>` | Parallel LLM calls (default: 3)           |
-| `--gist`            | Publish wiki as a public GitHub Gist      |
-
-### list — Show all indexed repos
-
-```bash
-npx gitnexus list
-```
-
-Lists all repositories registered in `~/.gitnexus/registry.json`. The MCP `list_repos` tool provides the same information.
-
-## After Indexing
-
-1. **Read `gitnexus://repo/{name}/context`** to verify the index loaded
-2. Use the other GitNexus skills (`exploring`, `debugging`, `impact-analysis`, `refactoring`) for your task
-
-## Troubleshooting
-
-- **"Not inside a git repository"**: Run from a directory inside a git repo
-- **Index is stale after re-analyzing**: Restart Claude Code to reload the MCP server
-- **Embeddings slow**: Omit `--embeddings` (it's off by default) or set `OPENAI_API_KEY` for faster API-based embedding

package/.claude/skills/gitnexus/gitnexus-debugging/SKILL.md

@@ -1,89 +0,0 @@
----
-name: gitnexus-debugging
-description: "Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\""
----
-
-# Debugging with GitNexus
-
-## When to Use
-
-- "Why is this function failing?"
-- "Trace where this error comes from"
-- "Who calls this method?"
-- "This endpoint returns 500"
-- Investigating bugs, errors, or unexpected behavior
-
-## Workflow
-
-```
-1. gitnexus_query({query: "<error or symptom>"})            → Find related execution flows
-2. gitnexus_context({name: "<suspect>"})                    → See callers/callees/processes
-3. READ gitnexus://repo/{name}/process/{name}                → Trace execution flow
-4. gitnexus_cypher({query: "MATCH path..."})                 → Custom traces if needed
-```
-
-> If "Index is stale" → run `npx gitnexus analyze` in terminal.
-
-## Checklist
-
-```
-- [ ] Understand the symptom (error message, unexpected behavior)
-- [ ] gitnexus_query for error text or related code
-- [ ] Identify the suspect function from returned processes
-- [ ] gitnexus_context to see callers and callees
-- [ ] Trace execution flow via process resource if applicable
-- [ ] gitnexus_cypher for custom call chain traces if needed
-- [ ] Read source files to confirm root cause
-```
-
-## Debugging Patterns
-
-| Symptom              | GitNexus Approach                                          |
-| -------------------- | ---------------------------------------------------------- |
-| Error message        | `gitnexus_query` for error text → `context` on throw sites |
-| Wrong return value   | `context` on the function → trace callees for data flow    |
-| Intermittent failure | `context` → look for external calls, async deps            |
-| Performance issue    | `context` → find symbols with many callers (hot paths)     |
-| Recent regression    | `detect_changes` to see what your changes affect           |
-
-## Tools
-
-**gitnexus_query** — find code related to error:
-
-```
-gitnexus_query({query: "payment validation error"})
-→ Processes: CheckoutFlow, ErrorHandling
-→ Symbols: validatePayment, handlePaymentError, PaymentException
-```
-
-**gitnexus_context** — full context for a suspect:
-
-```
-gitnexus_context({name: "validatePayment"})
-→ Incoming calls: processCheckout, webhookHandler
-→ Outgoing calls: verifyCard, fetchRates (external API!)
-→ Processes: CheckoutFlow (step 3/7)
-```
-
-**gitnexus_cypher** — custom call chain traces:
-
-```cypher
-MATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: "validatePayment"})
-RETURN [n IN nodes(path) | n.name] AS chain
-```
-
-## Example: "Payment endpoint returns 500 intermittently"
-
-```
-1. gitnexus_query({query: "payment error handling"})
-   → Processes: CheckoutFlow, ErrorHandling
-   → Symbols: validatePayment, handlePaymentError
-
-2. gitnexus_context({name: "validatePayment"})
-   → Outgoing calls: verifyCard, fetchRates (external API!)
-
-3. READ gitnexus://repo/my-app/process/CheckoutFlow
-   → Step 3: validatePayment → calls fetchRates (external)
-
-4. Root cause: fetchRates calls external API without proper timeout
-```

package/.claude/skills/gitnexus/gitnexus-exploring/SKILL.md

@@ -1,78 +0,0 @@
----
-name: gitnexus-exploring
-description: "Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\""
----
-
-# Exploring Codebases with GitNexus
-
-## When to Use
-
-- "How does authentication work?"
-- "What's the project structure?"
-- "Show me the main components"
-- "Where is the database logic?"
-- Understanding code you haven't seen before
-
-## Workflow
-
-```
-1. READ gitnexus://repos                          → Discover indexed repos
-2. READ gitnexus://repo/{name}/context             → Codebase overview, check staleness
-3. gitnexus_query({query: "<what you want to understand>"})  → Find related execution flows
-4. gitnexus_context({name: "<symbol>"})            → Deep dive on specific symbol
-5. READ gitnexus://repo/{name}/process/{name}      → Trace full execution flow
-```
-
-> If step 2 says "Index is stale" → run `npx gitnexus analyze` in terminal.
-
-## Checklist
-
-```
-- [ ] READ gitnexus://repo/{name}/context
-- [ ] gitnexus_query for the concept you want to understand
-- [ ] Review returned processes (execution flows)
-- [ ] gitnexus_context on key symbols for callers/callees
-- [ ] READ process resource for full execution traces
-- [ ] Read source files for implementation details
-```
-
-## Resources
-
-| Resource                                | What you get                                            |
-| --------------------------------------- | ------------------------------------------------------- |
-| `gitnexus://repo/{name}/context`        | Stats, staleness warning (~150 tokens)                  |
-| `gitnexus://repo/{name}/clusters`       | All functional areas with cohesion scores (~300 tokens) |
-| `gitnexus://repo/{name}/cluster/{name}` | Area members with file paths (~500 tokens)              |
-| `gitnexus://repo/{name}/process/{name}` | Step-by-step execution trace (~200 tokens)              |
-
-## Tools
-
-**gitnexus_query** — find execution flows related to a concept:
-
-```
-gitnexus_query({query: "payment processing"})
-→ Processes: CheckoutFlow, RefundFlow, WebhookHandler
-→ Symbols grouped by flow with file locations
-```
-
-**gitnexus_context** — 360-degree view of a symbol:
-
-```
-gitnexus_context({name: "validateUser"})
-→ Incoming calls: loginHandler, apiMiddleware
-→ Outgoing calls: checkToken, getUserById
-→ Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)
-```
-
-## Example: "How does payment processing work?"
-
-```
-1. READ gitnexus://repo/my-app/context       → 918 symbols, 45 processes
-2. gitnexus_query({query: "payment processing"})
-   → CheckoutFlow: processPayment → validateCard → chargeStripe
-   → RefundFlow: initiateRefund → calculateRefund → processRefund
-3. gitnexus_context({name: "processPayment"})
-   → Incoming: checkoutHandler, webhookHandler
-   → Outgoing: validateCard, chargeStripe, saveTransaction
-4. Read src/payments/processor.ts for implementation details
-```

package/.claude/skills/gitnexus/gitnexus-guide/SKILL.md

@@ -1,64 +0,0 @@
----
-name: gitnexus-guide
-description: "Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\""
----
-
-# GitNexus Guide
-
-Quick reference for all GitNexus MCP tools, resources, and the knowledge graph schema.
-
-## Always Start Here
-
-For any task involving code understanding, debugging, impact analysis, or refactoring:
-
-1. **Read `gitnexus://repo/{name}/context`** — codebase overview + check index freshness
-2. **Match your task to a skill below** and **read that skill file**
-3. **Follow the skill's workflow and checklist**
-
-> If step 1 warns the index is stale, run `npx gitnexus analyze` in the terminal first.
-
-## Skills
-
-| Task                                         | Skill to read       |
-| -------------------------------------------- | ------------------- |
-| Understand architecture / "How does X work?" | `gitnexus-exploring`         |
-| Blast radius / "What breaks if I change X?"  | `gitnexus-impact-analysis`   |
-| Trace bugs / "Why is X failing?"             | `gitnexus-debugging`         |
-| Rename / extract / split / refactor          | `gitnexus-refactoring`       |
-| Tools, resources, schema reference           | `gitnexus-guide` (this file) |
-| Index, status, clean, wiki CLI commands      | `gitnexus-cli`               |
-
-## Tools Reference
-
-| Tool             | What it gives you                                                        |
-| ---------------- | ------------------------------------------------------------------------ |
-| `query`          | Process-grouped code intelligence — execution flows related to a concept |
-| `context`        | 360-degree symbol view — categorized refs, processes it participates in  |
-| `impact`         | Symbol blast radius — what breaks at depth 1/2/3 with confidence         |
-| `detect_changes` | Git-diff impact — what do your current changes affect                    |
-| `rename`         | Multi-file coordinated rename with confidence-tagged edits               |
-| `cypher`         | Raw graph queries (read `gitnexus://repo/{name}/schema` first)           |
-| `list_repos`     | Discover indexed repos                                                   |
-
-## Resources Reference
-
-Lightweight reads (~100-500 tokens) for navigation:
-
-| Resource                                       | Content                                   |
-| ---------------------------------------------- | ----------------------------------------- |
-| `gitnexus://repo/{name}/context`               | Stats, staleness check                    |
-| `gitnexus://repo/{name}/clusters`              | All functional areas with cohesion scores |
-| `gitnexus://repo/{name}/cluster/{clusterName}` | Area members                              |
-| `gitnexus://repo/{name}/processes`             | All execution flows                       |
-| `gitnexus://repo/{name}/process/{processName}` | Step-by-step trace                        |
-| `gitnexus://repo/{name}/schema`                | Graph schema for Cypher                   |
-
-## Graph Schema
-
-**Nodes:** File, Function, Class, Interface, Method, Community, Process
-**Edges (via CodeRelation.type):** CALLS, IMPORTS, EXTENDS, IMPLEMENTS, DEFINES, MEMBER_OF, STEP_IN_PROCESS
-
-```cypher
-MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "myFunc"})
-RETURN caller.name, caller.filePath
-```

package/.claude/skills/gitnexus/gitnexus-impact-analysis/SKILL.md

@@ -1,97 +0,0 @@
----
-name: gitnexus-impact-analysis
-description: "Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\""
----
-
-# Impact Analysis with GitNexus
-
-## When to Use
-
-- "Is it safe to change this function?"
-- "What will break if I modify X?"
-- "Show me the blast radius"
-- "Who uses this code?"
-- Before making non-trivial code changes
-- Before committing — to understand what your changes affect
-
-## Workflow
-
-```
-1. gitnexus_impact({target: "X", direction: "upstream"})  → What depends on this
-2. READ gitnexus://repo/{name}/processes                   → Check affected execution flows
-3. gitnexus_detect_changes()                               → Map current git changes to affected flows
-4. Assess risk and report to user
-```
-
-> If "Index is stale" → run `npx gitnexus analyze` in terminal.
-
-## Checklist
-
-```
-- [ ] gitnexus_impact({target, direction: "upstream"}) to find dependents
-- [ ] Review d=1 items first (these WILL BREAK)
-- [ ] Check high-confidence (>0.8) dependencies
-- [ ] READ processes to check affected execution flows
-- [ ] gitnexus_detect_changes() for pre-commit check
-- [ ] Assess risk level and report to user
-```
-
-## Understanding Output
-
-| Depth | Risk Level       | Meaning                  |
-| ----- | ---------------- | ------------------------ |
-| d=1   | **WILL BREAK**   | Direct callers/importers |
-| d=2   | LIKELY AFFECTED  | Indirect dependencies    |
-| d=3   | MAY NEED TESTING | Transitive effects       |
-
-## Risk Assessment
-
-| Affected                       | Risk     |
-| ------------------------------ | -------- |
-| <5 symbols, few processes      | LOW      |
-| 5-15 symbols, 2-5 processes    | MEDIUM   |
-| >15 symbols or many processes  | HIGH     |
-| Critical path (auth, payments) | CRITICAL |
-
-## Tools
-
-**gitnexus_impact** — the primary tool for symbol blast radius:
-
-```
-gitnexus_impact({
-  target: "validateUser",
-  direction: "upstream",
-  minConfidence: 0.8,
-  maxDepth: 3
-})
-
-→ d=1 (WILL BREAK):
-  - loginHandler (src/auth/login.ts:42) [CALLS, 100%]
-  - apiMiddleware (src/api/middleware.ts:15) [CALLS, 100%]
-
-→ d=2 (LIKELY AFFECTED):
-  - authRouter (src/routes/auth.ts:22) [CALLS, 95%]
-```
-
-**gitnexus_detect_changes** — git-diff based impact analysis:
-
-```
-gitnexus_detect_changes({scope: "staged"})
-
-→ Changed: 5 symbols in 3 files
-→ Affected: LoginFlow, TokenRefresh, APIMiddlewarePipeline
-→ Risk: MEDIUM
-```
-
-## Example: "What breaks if I change validateUser?"
-
-```
-1. gitnexus_impact({target: "validateUser", direction: "upstream"})
-   → d=1: loginHandler, apiMiddleware (WILL BREAK)
-   → d=2: authRouter, sessionManager (LIKELY AFFECTED)
-
-2. READ gitnexus://repo/my-app/processes
-   → LoginFlow and TokenRefresh touch validateUser
-
-3. Risk: 2 direct callers, 2 processes = MEDIUM
-```