Обновление графа текущей ветки в `graphify` должно быть ограниченным или инкрементальным

## Что это ## Резюме (RU) Обновление графа текущей ветки в `graphify` должно быть ограниченным или инкрементальным *Полный перевод тела — в работе. Английский оригинал ниже.* --- # Original (EN) ### Objective Fix the Graphify refresh path for this repo so agents can keep graph artifacts current after code changes without running an impractical full-repo update over generated/runtime/cache-heavy files. ### Source Links * GitHub issue: [https://github.com/agisota/rox.one/issues/271]() * GitHub PR: none yet * GitHub branch: `feat/rox-design-clean` * GitHub Project item: [https://github.com/users/agisota/projects/9]() (API update blocked by current PAT: `user.projectV2` not accessible) * DeepWiki/repo context: [https://deepwiki.com/agisota/rox.one]() * Local branch / cwd: `feat/rox-design-clean` / `/home/dev/craft/rox-one-terminal` * Parent Linear issue: PZD-10 * Local Graphify artifact: `/home/dev/craft/rox-one-graphify-deepwiki-2026-05-20/source/graphify-out/graph.json` ### Current State `graphify update .` was run after the docs/schema commit per AGENTS.md. It completed AST extraction over 270556 files but then continued computing without finishing. The partial output was `graphify-out/` at 4.3G with only `cache/ast` and no usable `graph.json`; it was removed to avoid committing unusable artifacts. ### Requirements Graph refresh must avoid huge generated/runtime folders and should prefer scoped paths such as changed package directories. It must not leave partial 4GB caches in the worktree. It must preserve the existing working local artifact workspace until a fresh current-branch graph is practical. ### Specification * Identify why full-repo update sees 270k files. * Add or document ignore/scoping strategy for `graphify update` in ROX.ONE. * Prefer `graphify update packages/shared/src/workbench` for this schema change, or known valid project subtrees such as `packages/server-core/src` for server-core work. * Ensure incomplete graphify outputs are not committed. * Update AGENTS/docs if command should be narrowed by default. ### Acceptance Criteria * Given only shared workbench schema changes, when Graphify refresh runs, then it targets a narrow path and finishes. * Given Graphify cannot finish, when it exits/blocks, then no partial `graphify-out` is committed. * Given future agents read AGENTS.md, when the... ## Статус Это задача из текущего backlog'а ROX.ONE (Linear). Текущий статус в Linear: `На ревью — In Review`. Метки: —. ## 🔗 Linear - [PZD-16](https://linear.app/kuhjie/issue/PZD-16/obnovlenie-grafa-tekushej-vetki-v-graphify-dolzhno-byt-ogranichennym) — backing ticket - Parent epic: [PZD-116](https://linear.app/kuhjie/issue/PZD-116)

Please authenticate to join the conversation.

Upvoters
Status

In Review

Board
🏢

Enterprise, B2B

Date

About 15 hours ago

Author

agi

Subscribe to post

Get notified by email when there are changes.