@automaton-labs/aib 0.0.6 → 0.0.7

package/dist/help/json/docs/qr.md

@@ -1,37 +0,0 @@
-# Quick Read
-
-Use qr for cross-OS quick reads of text files: ts, js, cmd, sh, json, log, txt, ndjson, etc.
-Use it for compact line windows and batching.
-qr supports AIB path aliases.
-
-It is not a replacement for inspect.
-Use it as a token-efficient way to read text data when semantic inspect is not needed.
-
-For focused text reads, prefer qr over cat/Get-Content/type, especially when aliases, line windows, or batching help.
-Use shell reads only when piping into shell tooling or qr is unavailable.
-
-Controls:
--h N    head; first N lines
--t N    tail; last N lines
--o N    offset; starting line, 1-based
--l N    limit; line count for offset reads
--a      all; whole file
-
-If no window is provided, qr uses -h 80.
-If -a is present, it wins over other window flags.
-
-Run:
-aib qr --stdin
-
-Input:
-qr @scripts/a.txt h=80
-qr @scripts/b.py o=300 l=50
-qr @scripts/c.md t=120
-qr @logs/app.log all
-
-Inline:
-aib qr @scripts/a.txt -h 80
-aib qr @scripts/b.py -o 300 -l 50
-aib qr @logs/app.log -a
-
-Use stdin for several reads.

package/dist/help/json/docs/quick-map.md

@@ -1,30 +0,0 @@
-# Quick Map
-
-Read:
-  qr              quick reads: ts, js, cmd, sh, json, log, txt, etc.
-  view            hidden/truncated output
-
-Inspect:
-  file
-  imports
-  exports
-  members
-  code
-  deps
-  usages
-  graph
-  tree
-  duplicates
-  cycles
-
-Mutate:
-  rename
-  move
-  modulePlan
-  refactor batch
-  imports normalize
-
-Other:
-  config
-  prefs
-  reveal         tsconfig and tsconfig alias discovery

package/dist/help/json/docs/refactor.batch.md

@@ -1,72 +0,0 @@
-# Refactor Batch
-
-Modes: preview/apply or execute.
-Use execute for routine changes.
-Use preview/apply when learning a mutation command or inspecting a large multi-step request before writing files.
-
-If a name is ambiguous, use selectors.
-Run help selectors to refresh selector syntax.
-
-refactor batch runs related mutation requests together.
-Use it when one workflow needs ordered steps, such as rename plus move.
-
-Use modulePlan when the main intent is only to split one large file into target modules.
-Use refactor batch when the split also includes coordinated renames or mixed mutation steps.
-
-refactor batch preview --stdin
-refactor batch execute --stdin
-refactor batch apply --stdin
-
-Use preview/apply when you want to inspect a large mixed plan before writing files.
-Use execute when you want to write immediately.
-Use --from with captured input handles when rerunning edited large batches.
-
-Example: rename and move in one request
-
-Run:
-aib refactor batch execute --stdin
-
-Input:
-{
-  "sourceFile": "src/service.ts",
-  "requests": [
-    {
-      "op": "rename",
-      "renames": {
-        "oldHelper": "newHelper",
-        "oldType": "newType"
-      }
-    },
-    {
-      "op": "move",
-      "targetFile": "src/service.helpers.ts",
-      "entities": ["newHelper"]
-    },
-    {
-      "op": "move",
-      "targetFile": "src/service.types.ts",
-      "entities": ["newType"]
-    }
-  ]
-}
-
-Use top-level sourceFile when requests operate on the same file.
-Override file/sourceFile inside a request when one request targets another file.
-
-Supported request kinds:
-rename
-move
-
-Use separate command help when the workflow only needs one mutation kind.
-
-If a large or partial refactor batch fails, edit the captured input file and rerun with --from.
-For small one-off refactor requests, write a corrected request instead.
-
-Latest refactor input:
-<session-dir>/inputs/refactor/_last.json
-
-Handle:
-aib:input:refactor:last
-
-Example:
-refactor batch execute --from aib:input:refactor:last

package/dist/help/json/docs/rename.md

@@ -1,47 +0,0 @@
-# Rename
-
-Modes: preview/apply or execute.
-Use execute for routine changes.
-Use preview/apply when learning a mutation command or inspecting a large multi-step request before writing files.
-
-If a name is ambiguous, use selectors.
-Run help selectors to refresh selector syntax.
-
-Rename is for semantic symbol renames.
-It follows TypeScript references.
-It is not plain-text replacement.
-
-Single rename:
-rename preview <file> <entity> <newName>
-rename execute <file> <entity> <newName>
-rename apply <previewId>
-
-Use preview/apply when you want to inspect the planned change before writing files.
-Use execute when you want to write immediately.
-
-Run:
-aib rename execute --stdin
-
-Input:
-{
-  "file": "src/service.ts",
-  "renames": {
-    "oldName": "newName",
-    "OldService": "NewService"
-  }
-}
-
-Rename can use plain names or selectors.
-For methods and properties, prefer JSON so you can pass parent when needed.
-
-If a large rename request fails, edit the captured input file and rerun with --from.
-For small one-off rename requests, write a corrected request instead.
-
-Latest rename input:
-<session-dir>/inputs/rename/_last.json
-
-Handle:
-aib:input:rename:last
-
-Example:
-rename preview --from aib:input:rename:last

package/dist/help/json/docs/reveal.md

@@ -1,30 +0,0 @@
-# Reveal
-
-Use reveal to inspect TypeScript config discovery used by AIB.
-
-Reveal is for config/setup diagnosis.
-Use it when aliases, sync, imports normalize, or tsconfig excludes depend on which tsconfig files AIB sees.
-
-Commands:
-aib reveal tsconfigs
-aib reveal tsaliases
-
-tsconfigs shows visible TypeScript configs and config-excluded configs.
-tsaliases shows baseUrl, paths, extends, inherited paths, duplicated inherited paths, and overridden inherited paths.
-
-Controls:
-all    show all output instead of compact output
-nec    no config excludes; ignore sync.tsconfig.exclude
-ned    no default excludes
-limit  max visible groups/items before + N more
-
-Examples:
-aib reveal tsconfigs
-aib reveal tsconfigs +all
-aib reveal tsconfigs +nec limit=20
-aib reveal tsaliases
-aib reveal tsaliases +all
-aib reveal tsaliases +nec
-
-Use tsconfigs before tuning sync.tsconfig.exclude.
-Use tsaliases before creating AIB pathAliases or configuring import normalization.

package/dist/help/json/docs/selectors.md

@@ -1,23 +0,0 @@
-# Selectors
-
-Selectors identify symbols when names are ambiguous.
-Use plain names when they are unambiguous.
-Use selectors when aib reports ambiguity or when different symbol kinds share a name.
-
-Example:
-type WsOptions
-class WsOptions
-
-If aib needs the exact entity, use:
-t-WsOptions
-c-WsOptions
-
-Selectors list:
-f-name  function
-c-Name  class
-i-Name  interface
-t-Name  type
-v-name  variable
-e-Name  enum
-m-name  method, usually with parent in JSON
-p-name  property, usually with parent in JSON

package/dist/help/json/docs/session.md

@@ -1,77 +0,0 @@
-# Session
-
-Start by creating or selecting your session.
-Create it once, then reuse it.
-Do not create a new session for every command or subtask.
-
-Session stores captured inputs, saved outputs, aliases, and prefs.
-
-Prefer short session names:
-aa, tr, qa, a2
-
-Create:
-session init --name <name>
-
-Follow the command output.
-If aib says multiple sessions exist, use the session you created explicitly:
-aib -s <name> <command>
-
-Or bind this shell:
-AIB=<name>
-
-If you want to prune session inputs/outputs, use:
-session clear
-
-After clear, keep using the same session.
-
-Check:
-session status
-
-Handles:
-Commands may return handles for hidden output or reusable indexes.
-
-Hidden output:
-aib:res_<id>
-
-Use view to fetch only the hidden part without repeating the original request:
-aib view aib:res_<id>
-
-Reusable indexes:
-aib:usages:<name>
-aib:graph:<name>
-
-Usages and graph handles store computed indexes.
-Use them with --from-file to focus or expand the saved result:
-
-inspect usages --from-file aib:usages:service-usages --focus createService --detail code
-inspect graph --from-file aib:graph:services-graph --focus src/service.ts
-
-Escape hatch for latest mutation status/result:
-aib execution status last
-
-Every JSON stdin/from request is captured.
-
-Latest input per kind:
-<session-dir>/inputs/<kind>/_last.json
-
-Handle:
-aib:input:<kind>:last
-
-Use --from when editing the captured input costs less than rebuilding the request.
-For small one-off requests, write a corrected request instead.
-Do not read input handles into context unless you specifically need to inspect the payload.
-
-Examples:
-rename preview --from aib:input:rename:last
-refactor batch <command> --from aib:input:refactor:last
-
-Prefs are stored in the session.
-Use prefs when you want repeated CLI behavior without repeating request fields.
-
-Set several prefs:
-session prefs set inspect.graph.hubs false inspect.graph.leaves false
-
-Show current overrides:
-session prefs get
-
-See help prefs for the full list.

package/dist/help/json/docs/view.md

@@ -1,30 +0,0 @@
-# View Hidden Output
-
-AIB keeps large outputs compact.
-When part of a result is hidden, output may include:
-
-view: aib:res_<id>
-
-Use view to fetch the hidden part without repeating what you already saw.
-
-When a batch has several hidden results of the same kind, output may include:
-
-view all code: aib:res_<id>
-view all members: aib:res_<id>
-
-A `view all` handle covers hidden parts from all results of that kind.
-
-For code views, narrow what you fetch:
-only    show only these hidden code entities
-except  show all hidden code except these entities
-
-Run:
-aib view --stdin
-
-Input:
-view aib:res_<id_1> only=[ClassA.{bigA,bigB},bigQ,ClassB.bigB]
-view aib:res_<id_2> except=[ClassC.bigC]
-
-Inline:
-aib view aib:res_<id_1> --only bigQ --only "ClassA.{bigA,bigB}"
-aib view aib:res_<id_2> --except ClassB.bigB --except ClassC.bigC

package/dist/help/json/snippets/agents.md

@@ -1,14 +0,0 @@
-Recommended:
-For TS/JS code work, use aib. Start with {{docsPath}}.
-
-Strict:
-For TS/JS code work in this repo, prefer aib before broad file reads. Start with {{docsPath}}.
-
-Minimal:
-Use {{docsPath}} when working with TS/JS code.
-
-Help fallback:
-For TS/JS code work, use aib. Start with {{docsPath}}. If local docs are not enough, run `aib help bootstrap`.
-
-Refactor-focused:
-When changing TS/JS code, use aib for semantic discovery, usages, graph, rename, move, and modulePlan. Start with {{docsPath}}.

package/dist/help/json/topics/basics.md

@@ -1,13 +0,0 @@
-Use the active session while you work.
-Reuse captured inputs when editing them is cheaper than rebuilding large JSON.
-
-Examples are patterns, not limits.
-Feature sections show common high-value uses, not every valid use.
-Adapt requests to the task: combine features, batch related questions, and skip steps when you already have enough context.
-
-Prefer batch JSON instead of inline calls.
-One request can inspect/mutate several files/entities and save reusable outputs.
-Use one-off commands only for small checks/changes.
-
-For mutations, aib asks TS/IDE refactors to update affected references and imports.
-After a successful mutation, do not manually patch the same imports unless aib reports a follow-up or the build/checks show a real issue.

package/dist/help/json/topics/config-setup.aliases.md

@@ -1,54 +0,0 @@
-If you have not just checked the full config, check current aliases:
-
-aib config aliases
-
-pathAliases define short request aliases for paths agents repeat in AIB commands.
-Use them to reduce input tokens for repeated inspect and mutation work.
-
-Aliases are for AIB request paths.
-They do not change TypeScript imports by themselves.
-For import style after mutations, use importRules.
-
-Check TypeScript aliases for hints:
-
-aib reveal tsaliases
-
-Use this to see existing tsconfig paths and baseUrl values.
-They can reveal stable work areas, but they are not a list to copy.
-
-Add pathAliases for long paths that are likely to appear repeatedly in AIB requests.
-Prefer aliases for real work areas, package roots, or deep directories.
-
-A good alias:
-- saves meaningful path tokens;
-- points to a stable work area;
-- is easy to recognize later.
-
-A bad alias:
-- duplicates a short path like "src": "src", "packages": "packages", "scripts": "scripts";
-- points to a rarely used folder;
-- mirrors the directory tree without a workflow reason.
-
-Having 20-30 good aliases is fine for a large repo or monorepo.
-
-Example:
-
-"pathAliases": {
-  "wstore": "apps/web/src/shared/store",
-  "wapi": "apps/web/src/shared/api",
-  "whooks": "apps/web/src/shared/utils/hooks",
-  "pmail": "packages/email/src",
-  "putils": "packages/utils/src",
-  "arules": "docs/agent/rules"
-}
-
-After editing aib.json, run:
-
-aib sync
-
-Verify aliases with a small tree or inspect request:
-
-aib inspect --stdin
-
-Input:
-tree @<alias> depth=3 +onlyDirs limit=80

package/dist/help/json/topics/config-setup.excludes.md

@@ -1,43 +0,0 @@
-Tree excludes affect directory and file discovery output.
-Graph excludes affect graph counts, hubs, entrypoints, leaves, edges, imports, importedBy, and saved graph views.
-
-Built-in excludes already skip common noise such as node_modules, .git, dist, build, out, and .tmp.
-Add config excludes for repository-specific noise.
-
-For example, if the user often creates hard-copy directories or backup files before risky edits, those copies can make tree and graph output noisy.
-Exclude them explicitly:
-
-"inspect.tree.onlyDirs.exclude": [
-  "**/*copy",
-  "**/*copy/**"
-],
-"inspect.tree.files.exclude": [
-  "**/* copy.ts",
-  "**/*.generated.ts"
-],
-"inspect.graph.exclude": [
-  "**/* copy.ts",
-  "**/*.generated.ts",
-  "src/generated/**"
-]
-
-Prefer narrow patterns for known noise:
-- generated files;
-- local copy/backup folders;
-- build artifacts not already skipped by defaults;
-- vendored or checked-in output.
-
-These are common cases, not mandatory rules.
-If the repository needs one of these areas for reasoning or mutation impact checks, do not exclude it.
-
-Do not exclude broad source areas to make output smaller.
-If output is too large, use scope, depth, limit, graph view, or graph toggles first.
-
-After editing aib.json, run:
-
-aib sync
-
-Then verify with a compact tree request and the graph view that was noisy.
-
-If excluded paths still appear, check the glob pattern against repo-relative paths.
-If important source disappeared, narrow or remove the exclude.

package/dist/help/json/topics/config-setup.import-normalize.md

@@ -1,84 +0,0 @@
-Configure import normalization intent.
-
-importNormalize defines default normalization rules for explicit aib imports normalize commands.
-Use it before broad or important import cleanup so the scope, target style, preferred alias, and excludes are stored in aib.json instead of repeated in command arguments.
-
-It does not run automatically during move/modulePlan.
-Use importRules for mutation-time import cleanup.
-
-Set importNormalize when the intended cleanup has project meaning:
-- adopting a new tsconfig alias across a project area;
-- converting an area to aliases;
-- converting scripts/tools or extracted modules to relative imports;
-- excluding generated or bundled output from normalization.
-
-For tiny one-file checks, inline options are fine.
-Before wider cleanup, put the intended rule in config and preview the smallest useful scope.
-
-Fields:
-scope        repo-relative file or directory scope; most specific scope wins
-to           relative|alias|shortestAlias
-preferAlias  tsconfig paths pattern used when to=alias
-exclude      files, directories, or glob-like patterns to skip
-
-to:
-relative       rewrite resolved local imports to relative paths
-alias          rewrite resolved local imports to a matching tsconfig alias
-shortestAlias  rewrite to the shortest valid alias specifier
-
-preferAlias:
-@shared/*      prefer one alias pattern when several aliases can resolve the same file
-
-Alias cleanup:
-
-"importNormalize": [
-  {
-    "scope": "src",
-    "to": "shortestAlias",
-    "preferAlias": "@/*",
-    "exclude": [
-      "src/generated",
-      "src/**/dist"
-    ]
-  }
-]
-
-Relative cleanup for scripts/tools:
-
-"importNormalize": [
-  {
-    "scope": "scripts",
-    "to": "relative",
-    "exclude": [
-      "scripts/**/*.cjs",
-      "scripts/**/*.mjs"
-    ]
-  }
-]
-
-If you have not just checked config rules, run:
-
-aib config rules
-
-After editing aib.json, run:
-
-aib sync
-
-Then preview the smallest useful scope before applying:
-
-aib imports normalize preview <scope>
-
-Preview shows counts, sample import rewrites, a planId, and the apply command.
-It does not change project files.
-
-If preview changes imports outside the intended area, narrow scope or add exclude.
-
-If preview does not use the expected alias, check tsconfig aliases:
-
-aib reveal tsaliases
-
-If the config and aliases look correct but preview still looks stale or strange, run:
-
-aib sync
-
-Then preview again.

package/dist/help/json/topics/config-setup.import-rules.md

@@ -1,94 +0,0 @@
-Use this when move/modulePlan creates imports that do not match the repository style.
-
-Do not keep fixing the same generated import style by hand.
-Tune importRules, sync config, then retry the smallest useful mutation before continuing larger mutation work.
-
-Check current config:
-
-aib config rules
-
-importRules control imports created or expanded by move/modulePlan mutation cleanup.
-They do not rewrite the whole project.
-
-AIB starts from IDE/TS import preferences.
-For mutation cleanup, matching importRules in aib.json take priority.
-Do not assume IDE/TS defaults match the repo style.
-
-Fields:
-scope      repo-relative file or directory scope; most specific scope wins
-specifier  relative|shortest|project-relative|non-relative
-ending     auto|minimal|index|js
-builtin    node|bare
-unusedImports  remove|preserve
-
-Defaults:
-specifier omitted      IDE/TS decides
-ending omitted         IDE/TS decides
-builtin omitted        keep TS/project builtin style
-unusedImports omitted  keep unused imports
-
-specifier:
-relative          best for local relative imports
-shortest          best for shortest valid alias/path output
-project-relative  best for root-relative project imports
-non-relative      best for package or alias imports
-
-ending:
-minimal  best for extensionless TS imports
-js       best for ESM-style TS projects that require .js
-auto     leaves the decision to TypeScript
-index    best for explicit index import style
-
-builtin:
-node        path -> node:path; best for explicit Node builtin imports
-bare        node:path -> path; best for bare Node builtin imports
-omit field  keeps TypeScript/project output; add builtin if agents keep fixing this manually
-
-unusedImports:
-remove    clean unused imports in mutation-touched files
-preserve  keep unused imports
-omit      same as preserve
-
-Mutation-touched files are files where TS produced edits: source/target files and any reference/update files TS changed.
-Recommended value: remove
-
-If the repository has one import style, use one broad rule:
-
-"importRules": [
-  {
-    "scope": ".",
-    "specifier": "shortest",
-    "ending": "auto",
-    "builtin": "node",
-    "unusedImports": "remove"
-  }
-]
-
-Use scoped rules only when areas differ by style, for example packages use aliases but scripts use relative imports:
-
-"importRules": [
-  {
-    "scope": "packages",
-    "specifier": "shortest",
-    "ending": "auto",
-    "builtin": "node",
-    "unusedImports": "remove"
-  },
-  {
-    "scope": "scripts",
-    "specifier": "relative",
-    "ending": "auto",
-    "builtin": "node",
-    "unusedImports": "remove"
-  }
-]
-
-Use the most specific scope that matches the real convention.
-Do not add scoped rules just because directories exist.
-
-After editing aib.json, run:
-
-aib sync
-
-Then rerun the smallest affected move/modulePlan preview or execute request.
-If imports are still wrong, update importRules again before doing more manual cleanup.

package/dist/help/json/topics/config-setup.tsconfigs.md

@@ -1,31 +0,0 @@
-AIB syncs and watches visible tsconfigs.
-Keep real app/package configs visible.
-Exclude nested workspaces, seed projects, snapshots, backups, copied apps, or other non-primary projects.
-
-Do not exclude real package/app configs just to reduce output.
-
-Check which TypeScript configs AIB will sync and watch:
-
-aib reveal tsconfigs +all
-
-If output includes non-primary projects, exclude them:
-
-"sync.tsconfig.exclude": [
-  "dev-seed/**",
-  "snapshots/**"
-]
-
-After editing aib.json, run:
-
-aib sync
-
-Then check again:
-
-aib reveal tsconfigs +all
-
-Visible tsconfigs should describe the active project surface.
-Excluded tsconfigs should be things the agent should not use for setup decisions.
-
-Use +nec only when you need to compare visible configs with config-excluded configs:
-
-aib reveal tsconfigs +nec