@vodmal/vdx-cli 0.35.0 → 0.37.0

package/README.md

@@ -50,11 +50,15 @@ vdx push [project-path] [--dry-run]   # default: cwd
 
 # Environment self-check (Node / git / mise / npm auth / docker / Claude Code plugin; git hooks of the project; the GitHub token vdx asks with)
 vdx doctor [project-path] [--format=ansi|markdown|json]   # default: cwd
-vdx doctor --check [project-path]   # one line per hook declared but not running here — the plugin's SessionStart hook tells the agent
-vdx doctor --fix                    # write the profile's personal hooks (git.hooks) into ~/.gitconfig
+vdx doctor --check [project-path]   # one line per hook declared but not running here, and one when the memory is
+                                    # not inside — the plugin's SessionStart hook tells the agent
+vdx doctor --fix [project-path]     # write the profile's personal hooks (git.hooks) into ~/.gitconfig, and put
+                                    # the project's Claude Code memory inside it: .claude/memory/ (after a
+                                    # folder move, its path and conversations follow)
 
 # Start your agent in a project per your profile (~/.vdx-environment.yaml or $VDX_ENVIRONMENT)
-vdx ai[@host] [project-path] [--new | --conversation <id>] [--focused] [--restart] [--detach] [--dry-run]   # default: cwd; @host: over ssh, in tmux there
+vdx ai[@host] [project-path] [--new | --conversation <id>] [--focused | --intercom] [--restart] [--detach] [--dry-run]   # default: cwd; @host: over ssh, in tmux there; --intercom: the project's mail session
+vdx ai --close [--waiting <n>]   # inside the mail session: it ends itself; n questions to you still unanswered show on the project's other tmux sessions
 vdx ai --check [project-path]   # this session against the profile and the installed Claude Code and plugins — what the plugin's SessionStart hook tells the agent
 
 # What a command does and takes; nothing runs (ai: also where launch flags live)
@@ -79,6 +83,7 @@ vdx test            # → mise run test (which calls `vitest run` or whatever wa
 
 # 3. Ship a new minor release of a Node lib
 vdx publish minor   # npm login if expired → bump package.json + lock → npm publish (OTP or browser) → commit + tag → push → wait for the registry
+                    # in your own terminal: without one it releases nothing (--force goes on)
 
 # 4. Start the agent here, continuing its last conversation (--new: a new one,
 #    next to a running agent; another machine's conversation is continued on
@@ -143,6 +148,9 @@ the one git keeps for that host (`git credential fill`, never a prompt — log i
 once with `git ls-remote https://<host>/scm/<project>/<repo>.git`, a personal
 access token as the password), or `BITBUCKET_TOKEN` when the host is
 `BITBUCKET_HOST`. Branch restrictions are visible to a repository admin only.
+A login the server refuses (a revoked token) is unknown with the command that
+erases it: vdx leaves git's store alone, and sends the login again each audit
+until it is gone.
 Not met comes with the reason; another hosting, no network or no token
 where one is needed leave the axis unknown, with the reason too;
 `VDX_OFFLINE=1` does not ask at all.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vodmal/vdx-cli",
-  "version": "0.35.0",
+  "version": "0.37.0",
   "description": "vdx — unified lifecycle interface (up/down/build/test/check/fix) + versioned maturity audit with drift detection. Pairs with the vdx Claude Code plugin.",
   "keywords": [
     "vdx",

package/rubric/vdx-rubric.yaml

@@ -11,7 +11,7 @@ schema_version: "0.3"
 
 metadata:
   name: vdx-rubric-vodmal
-  version: "1.5.0"
+  version: "1.7.0"
   description: "Personal maturity rubric for multi-stack projects (vodmal)"
   owner: vodmal
   homepage: "https://github.com/vodmal/vdx-rubric"
@@ -260,8 +260,9 @@ axes:
     default_target: L4
     fact_sources: [hosting API]
     # Гейт — свойство L3 общей лестницы; ниже ось ничего не требует и уровень
-    # не ограничивает. Знает о защите только хостинг: пока расширения для него
-    # нет, L3 — «неизвестно» у всех. L4 — позже: force-push, удаление ветки,
+    # не ограничивает. Знает о защите только хостинг: vdx спрашивает GitHub
+    # (с CLI 0.29), GitLab (0.33) и Bitbucket Server (0.34), у другого хостинга
+    # L3 — «неизвестно» с причиной. L4 — позже: force-push, удаление ветки,
     # ревью (как Branch-Protection у Scorecard).
     levels:
       L1: { not_required: true }