@staff0rd/assist 0.722.0 → 0.722.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -255,7 +255,7 @@ The Config tab of the sessions web dashboard never receives secret values: `GET
255
255
  - `assist refactor rename file <source> <destination>` - Rename/move a TypeScript file and update all imports (`--apply` to execute)
256
256
  - `assist refactor rename symbol <file> <oldName> <newName>` - Rename a symbol across the project (`--apply` to execute)
257
257
  - `assist refactor extract <file> <functionName> <destination>` - Extract a function and its private dependencies to a new file (`--apply` to execute)
258
- - `assist refactor restructure [root]` - Place every file under `root` (default `src`) by its import graph alone, so re-running on the result makes no moves. Roots (no importers in scope, or imported from outside) sit at `root`; a single-importer file nests in `<importer dir>/<importer basename>/`; a shared file sits directly in the lowest folder common to its importers; cycles stay together; tests sit next to their subject. Dry-run prints the moves, resulting tree, depth statistics and basename collisions. `--apply` moves the files, rewrites imports (including `import()`, `import("…")` types and `vi.mock` paths) and removes emptied folders; `--check` lists files that drift from the plan and exits non-zero. Files matching `restructure.ignore` globs are never moved. Modules named in `restructure.pin` (basename without extension) move up out of deep import chains into the folder of the nearest root or pinned module above them, taking their subtrees with them. When the plan places files deeper than `restructure.maxDepth` (default 10), or puts more files in any folder below the root than `restructure.maxFolderPercent` of all files (default 15, capped at `restructure.maxFolderFiles`, default 150), every mode lists the deep chains and oversized folders with guidance for adjusting pins, and `--check` exits non-zero
258
+ - `assist refactor restructure [root]` - Place every file under `root` (default `src`) by its import graph alone, so re-running on the result makes no moves. Roots (no importers in scope, or imported from outside) sit at `root`; a single-importer file nests in `<importer dir>/<importer basename>/`; a shared file sits directly in the lowest folder common to its importers; cycles stay together; tests sit next to their subject. Dry-run prints the moves, resulting tree, depth statistics and basename collisions. `--apply` moves the files, rewrites imports (including `import()`, `import("…")` types and `vi.mock` paths) and removes emptied folders; `--check` lists files that drift from the plan and exits non-zero. Files matching `restructure.ignore` globs are never moved. Modules named in `restructure.pin` (basename without extension) move up out of deep import chains into the folder of the nearest root or pinned module above them, taking their subtrees with them. When the plan places files deeper than `restructure.maxDepth` (default 10), every mode lists the deep chains with guidance for choosing feature-boundary pins, and `--check` exits non-zero
259
259
 
260
260
  ### Rules
261
261