@aopslabs/aops 0.2.1 → 0.3.0

package/README.md

@@ -6,8 +6,9 @@ Server.
 
 ```sh
 npm install --global @aopslabs/aops
+aops
 aops --help
-aops setup
+aops setup --help
 aops setup ai
 aops setup guide
 aops setup init
@@ -38,14 +39,17 @@ operates Cockpit on port `5922`.
 
 On Windows x64, parameterless `aops` opens the bundled Rust TUI. This release
 does not include native TUI payloads for macOS or Linux; use explicit CLI
-commands such as `aops setup`, `aops server status`, or `aops --help` there.
+commands such as `aops setup init`, `aops server status`, or `aops --help` there.
 Explicit commands retain the same CLI behavior on every supported platform.
 When stdin or stdout is not an interactive terminal, parameterless `aops`
 prints short CLI guidance instead of trying to draw the TUI.
-`aops setup` always opens the installation menu, and `aops setup ai` prints a
-safe prompt that can be handed to Codex, Claude, or another terminal AI agent.
+`aops setup` prints its subcommand help instead of opening a second interactive
+menu. The Rust TUI owns the operator setup experience, while explicit setup
+subcommands remain stable engines for the TUI, agents, and automation.
+`aops setup ai` prints a safe prompt that can be handed to Codex, Claude, or another terminal AI agent.
 The prompt routes the agent to the packaged `aops-install` skill and keeps
-secrets in masked AOPS prompts instead of chat or argv.
+secrets in documented environment variables or private files instead of chat
+or argv.
 
 The default `trusted-local` server remains bound only to
 `127.0.0.1:5900`. It does not trust LAN or Tailscale interfaces. AOPS Server
@@ -87,19 +91,18 @@ role export; every migrated user must authenticate again through South.
 `aops auth logout --target remote --local-only` deliberately clears only the
 local encrypted credentials when remote revocation is unavailable.
 
-`aops setup init` is the normal cross-platform first-install wizard. It offers an
-existing PostgreSQL connection, an automatic Docker PostgreSQL 17 container,
-or a dedicated AOPS role/database created in PostgreSQL installed on this computer,
+`aops setup init` is the argument-driven cross-platform setup engine used by the
+TUI and automation. An explicit path selects an existing PostgreSQL connection,
+an automatic Docker PostgreSQL 17 container, or a dedicated AOPS role/database
+created in PostgreSQL installed on this computer,
 uses the standard `default` instance with server port `5900` and Cockpit port
 `5922`, installs all registered
 runtime pointers, reconciles the bundled signed official catalog without
 activating its skills, and leaves starter/demo user data untouched. Setup may
 reconcile only the catalog's required internal state. Managed PostgreSQL uses a
-generated strong password by default, with a masked custom-password choice in
-the interactive wizard. All
-database paths verify migrations before readiness; interactive terminals show
-animated progress and `--json` remains machine-clean. Interactive setup applies
-the chosen path immediately after collecting its required private inputs; the
+generated strong password by default. All database paths verify migrations
+before readiness and `--json` remains machine-clean. Setup applies only with an
+explicit path and `--apply --yes`; the
 verified global AOPS core/runtime gateways are automatic and have no extra
 selection or confirmation questions. Signed collaboration
 and working-discipline packages are imported as discoverable catalog choices,
@@ -139,11 +142,13 @@ aops setup init --path 4 \
 ```
 
 Setup path 3 probes loopback PostgreSQL without relying on `psql` being on
-`PATH`, then asks for an existing administrator role/password through masked
-input. The administrator password is transient; AOPS stores only its generated
-application connection in the private user server-env. If PostgreSQL is absent
-or stopped, readiness returns platform-specific Windows, macOS, or Linux
-install/start guidance instead of silently invoking an elevated package manager.
+`PATH`. The Rust TUI collects the administrator role/password for operator-led
+setup; direct CLI automation must provide the role explicitly and pass the
+password through `AOPS_LOCAL_POSTGRES_ADMIN_PASSWORD`. The administrator
+password is transient; AOPS stores only its generated application connection in
+the private user server-env. If PostgreSQL is absent or stopped, readiness
+returns platform-specific Windows, macOS, or Linux install/start guidance
+instead of silently invoking an elevated package manager.
 
 The existing-PostgreSQL path supports managed providers such as Supabase and
 Neon. Readiness compares only the migration-derived AOPS-owned table, column,
@@ -170,11 +175,10 @@ same setup command without reset or duplicate rollback copies; same-root npm
 byte drift still requires reinstalling the package.
 
 `aops setup guide` prints the packaged agent-readable installation skill before
-the server is initialized. `aops assets` opens the registered-runtime asset
-manager. It installs or updates the verified AOPS Gateway skill, repairs global pointers, reports
+the server is initialized. `aops assets` prints its explicit subcommand catalog.
+Those commands install or update the verified AOPS Gateway skill, repair global pointers, report
 status, and can safely remove recognized pointers while retaining the local
-verified core. Interactive `aops setup init` applies directly; automation uses
-an explicit path with `--apply --yes`.
+verified core. Setup uses an explicit path with `--apply --yes`.
 The official npm package supplies an independently signed
 Gateway/client-core closure and inert official catalog snapshot, so normal
 installation does not depend on an application-image release or ask for a

package/assets/agent-assets/core/references/aops-cli-core/SKILL.md

@@ -21,12 +21,14 @@ aops server health --json
 aops cockpit
 ```
 
-`aops setup init` owns the complete first-run flow: choose an existing
-PostgreSQL, AOPS-managed PostgreSQL container, detected local PostgreSQL, or a
-remote AOPS server. Local server paths plan/apply/verify migrations, start the
-npm server, leave starter/demo user data untouched, and install verified agent
-assets. Database secrets belong only in masked prompts or private input
-files/environment; never paste them into chat or argv.
+Parameterless `aops` opens the Rust TUI for operator-led first-run choices.
+`aops setup init` is its argument-driven engine for an existing PostgreSQL,
+AOPS-managed PostgreSQL container, detected local PostgreSQL, or a remote AOPS
+server. Local server paths plan/apply/verify migrations, start the npm server,
+leave starter/demo user data untouched, and install verified agent assets. The
+CLI never opens a menu or asks a question. Database secrets belong only in TUI
+private fields or private input files/environment; never paste them into chat
+or argv.
 
 For an unattended run, inspect readiness before apply:
 
@@ -98,7 +100,7 @@ validation error and inspect full schema/OpenAPI.
 ## Guard contract
 
 - `--json`: stable automation output.
-- `--yes`: non-interactive input handling; never implies mutation approval.
+- `--yes`: compatibility/fail-fast behavior; never implies mutation approval.
 - `--preview`: validate/plan without applying when supported.
 - `--apply`: execute a guarded write.
 - `--confirm`: acknowledge destructive scope.

package/assets/agent-assets/core/references/chatv3/SKILL.md

@@ -34,7 +34,8 @@ aops agent schema --tool chatv3.channel.list --summary --json
 
 ChatV3 may keep invite, member-token, and room-key context in a private local
 session store. Never paste those values into chat, logs, source files, or raw
-shell history. Use masked CLI prompts or supported input-file/env mechanisms.
+shell history. Use supported secure-store, input-file, or environment
+mechanisms; the CLI does not collect secrets through terminal prompts.
 
 For a write not exposed by sugar, inspect the exact live schema before invoke:
 

package/assets/agent-assets/core/user-guides/aops-cli.md

@@ -8,12 +8,11 @@
 
 ## 2 En kisa kurulum akisi
 
-### 2.1 Guided npm installation
+### 2.1 TUI-guided npm installation
 
 #### 2.1.1 Overview
 
 ```bash
-aops setup init
 aops
 aops server status --json
 aops host health
@@ -24,7 +23,8 @@ AOPS-owned PostgreSQL container, create a dedicated AOPS role/database in a
 supported local PostgreSQL, or configure this CLI for an existing AOPS Server
 through path `4`. Local-server paths verify migrations and start the npm
 server. Path `4` does not install or operate local PostgreSQL or server
-processes. Use masked prompts for all database and AuthV2 secrets.
+processes. Use the Rust TUI private fields for operator-led setup, or documented
+private environment/configuration inputs for direct CLI automation.
 
 Parameterless `aops` opens the bundled Rust TUI without changing either
 service. Argument-bearing invocations retain the existing CLI behavior. AOPS
@@ -39,7 +39,7 @@ closing that terminal stops the foreground server. The matching
 background mode. These scripts accept `--instance` and `--data-root`, not
 database credentials.
 
-### 2.2 Interactive auth
+### 2.2 Browser-approved auth
 
 #### 2.2.1 Overview
 
@@ -99,9 +99,10 @@ aops target use remote --apply
 ### 4.1 Overview
 
 `aops setup server-env` owns the private PostgreSQL connection used by local
-server paths. Enter the URL through its masked prompt. Automation may pass
-`AOPS_PG_URL` through the private process environment; never put a PostgreSQL
-URL or password in argv, chat, or committed files.
+server paths. The TUI may pass the URL through a private child-process
+environment. Direct CLI automation must use `AOPS_PG_URL` or an existing
+owner-only environment file; never put a PostgreSQL URL or password in argv,
+chat, or committed files.
 
 The default provider is `trusted-local`. Before an explicit non-loopback host,
 generate the complete AuthV2 runtime closure in the same owner-only file:
@@ -119,11 +120,9 @@ provider and secrets when rerun without `--auth`.
 ### 5.1 Overview
 
 Use `aops setup first-admin --target <target-name>` only while AuthV2 reports
-that no first admin exists. Interactive mode collects the password and admin
-key through masked prompts and stores the verified target-bound session.
-Non-interactive automation may use `AOPS_AUTH_EMAIL`, `AOPS_AUTH_PASSWORD`, and
-`AOPS_ADMIN_KEY` in its private process environment. Secret command arguments
-are refused.
+that no first admin exists. The TUI owns operator input. Direct CLI automation
+may use `AOPS_AUTH_EMAIL`, `AOPS_AUTH_PASSWORD`, and `AOPS_ADMIN_KEY` in its
+private process environment. Secret command arguments are refused.
 
 ## 6 User yonetimi
 
@@ -148,8 +147,8 @@ Login stores encrypted credentials bound to the selected target endpoint.
 Normal logout revokes the remote session before clearing the local copy. If the
 server is unavailable and the explicit intent is local cleanup, use
 `aops auth logout --target remote --local-only`. Passwords and tokens belong
-only in masked prompts or documented private environment variables, never
-argv.
+only in TUI private fields, secure stores, browser-approved flows, or documented
+private environment variables, never argv.
 
 ## 8 Diagnostik
 
@@ -791,7 +790,7 @@ Retrieval notes:
 High-signal operator notes:
 
 1. First cold hosted calls can take around 20 seconds; use `--timeout-ms 120000` for schema, doc, skill, or file smoke commands.
-2. `--yes` means non-interactive/fail-fast. It is not a magic fix for validation errors.
+2. `--yes` is a compatibility/fail-fast flag. The CLI never prompts, and the flag is not a magic fix for validation errors.
 3. In PowerShell, quote file pointers for multiline or quote-heavy content: `--content '@file'` or `--input '@file.json'`.
 4. If sugar returns validation errors, stop retrying guessed flags. Read `<command> --help`; for raw invokes, read `agent schema`.
 5. If command help and skill text disagree, command help wins.
@@ -876,7 +875,7 @@ Guard flags are consistent across AOPS sugar:
 | `--confirm` | Confirm destructive actions such as delete, restore overwrite, cleanup, or reset. |
 | `--idempotency-key <key>` | Make write retries deterministic when the command supports it. |
 | `--json` | Return scriptable structured output. |
-| `--yes` | Non-interactive/fail-fast mode for prompts and missing choices. |
+| `--yes` | Compatibility/fail-fast mode; missing required choices remain errors. |
 
 Read commands need no guard. Normal writes require `--apply`. Destructive writes require `--apply --confirm`. `--preview` without `--apply` should not mutate; if a command mutates during preview, file an issue.
 

package/assets/skills/aops-install/SKILL.md

@@ -27,7 +27,8 @@ detail is needed.
 
 Never place any PostgreSQL URL, application password, path 3 administrator
 password, AuthV2 password, admin key, or token in argv, logs, committed files,
-or chat. Use AOPS masked prompts or the documented private process environment.
+or chat. Use the AOPS TUI private fields or the documented private process
+environment/configuration files.
 
 ## Route by need
 
@@ -35,7 +36,8 @@ or chat. Use AOPS masked prompts or the documented private process environment.
 | --- | --- |
 | inspect choices and readiness | `aops setup init --yes --json` |
 | give any terminal AI agent a safe setup handoff | `aops setup ai` |
-| normal operator installation | `aops setup init` |
+| normal operator installation | `aops` (Rust TUI) |
+| headless setup/automation | `aops setup init --path <1|2|3|4> ...` |
 | use an existing database URL | path `1`, then `aops setup server-env` |
 | let AOPS manage Docker PostgreSQL | path `2` |
 | create AOPS DB in PostgreSQL on this computer | path `3` |
@@ -46,21 +48,21 @@ or chat. Use AOPS masked prompts or the documented private process environment.
 Load only the section needed for the selected path. The current nested `--help`
 owns exact flags.
 
-## Normal interactive installation
+## Normal TUI installation
 
-Prefer the normal setup menu:
+Prefer the TUI for operator-led setup:
 
 ```sh
-aops setup init
+aops
 ```
 
 All local-server paths use the normal `default` instance, API port `5900`, and
 independently supervised Cockpit port `5922`, verify
 migrations, install the verified Gateway for registered runtimes, reconcile the inert signed
-official catalog, and leave starter/demo user data untouched. Interactive
-setup applies after collecting the selected path's required private inputs; it
-does not ask redundant continue, asset-selection, or asset-confirmation
-questions. It automatically installs or repairs the verified AOPS core and
+official catalog, and leave starter/demo user data untouched. The TUI collects
+the selected path's required private inputs and calls only explicit CLI commands.
+The CLI itself never opens a menu or asks a question. Setup automatically
+installs or repairs the verified AOPS core and
 gateway for every registered runtime. The core supplies a small neutral router,
 rich on-demand mounted-domain user guides, and public-safe collaboration and
 working-discipline references. Setup makes disciplines available but does not
@@ -77,7 +79,7 @@ For automatic Docker PostgreSQL, the container port is loopback-only and dynamic
 
 ```sh
 aops server reset --remove-managed-postgres --confirm-data-loss --confirm-instance default
-aops setup init
+aops
 ```
 
 Global AOPS skills and pointers are shared installation assets and remain installed after server reset.
@@ -95,30 +97,29 @@ the rewrite removes retired local-auth assignments without printing them.
 Git clone is a secondary development path. The optional application image is
 built from the same exact public npm CLI/server closure and runs the normal
 `aops server setup` lifecycle inside the container. It is a distribution path,
-not a fifth interactive `setup init` path. Path `2` manages only its namespaced,
+not a fifth TUI setup path. Path `2` manages only its namespaced,
 label-verified PostgreSQL resources; unrelated Docker resources remain
 operator-owned.
 
 For path `1`, PostgreSQL is operator-owned and may be local, remote, managed,
-or separately containerized. Run interactive `aops setup init` and select path
-`1`; it asks for the PostgreSQL URL using masked input, then immediately tests
-the connection with TLS `require`. A saved URL is offered as a masked default
-on retry and can be kept or replaced. The TLS-policy menu appears only when the
-default encrypted connection fails. Use `verify-full` with a trusted CA and
-matching hostname; use `disable` only when the operator explicitly accepts
-unencrypted transport. For
-non-interactive work, inject `AOPS_PG_URL` privately or prepare it with
+or separately containerized. Select path `1` in the TUI; it collects the
+PostgreSQL URL privately and immediately tests the connection with TLS
+`require`. A saved URL can be kept or replaced. Use `verify-full` with a trusted
+CA and matching hostname; use `disable` only when the operator explicitly
+accepts unencrypted transport. For direct CLI work, inject `AOPS_PG_URL`
+privately or prepare it with
 `aops setup server-env`, then inspect `aops setup init --path 1
 --postgres-tls <policy> --yes --json`.
 
-For path `3`, prefer interactive setup. It probes loopback PostgreSQL, asks for
-an existing administrator role/password through masked input, creates a new
+For path `3`, prefer the TUI. It probes loopback PostgreSQL, collects an existing
+administrator role/password privately, creates a new
 dedicated login and database with a generated application password, stores only
 the application URL in the private user server-env, and runs the normal external
 migrations. The administrator password is never stored. If PostgreSQL is absent
 or stopped, return the platform-specific install/start actions reported by
-readiness; do not silently run an elevated package manager. Automation may use
-the private `AOPS_LOCAL_POSTGRES_ADMIN_PASSWORD` environment variable.
+readiness; do not silently run an elevated package manager. Direct CLI use must
+provide the administrator role explicitly and may use the private
+`AOPS_LOCAL_POSTGRES_ADMIN_PASSWORD` environment variable.
 `--local-postgres-admin-no-password` works only with PostgreSQL TCP trust auth;
 it does not bypass authentication or make Linux peer/socket auth work over
 loopback TCP. If the administrator password is unknown, stop and ask the

package/dist/commands/agent.js

@@ -3,7 +3,6 @@ import { Command } from 'commander';
 import { banner, logError, logInfo, logSuccess } from '@aopslabs/xf-cli-ui';
 import { applyCommonOptions, compactPayload, normalizeNonEmpty } from '../utils/command.js';
 import { buildAgentContextHeaders, invokeHostedToolWithApiState, parseJsonInput, requireApiState, unwrapHostedToolResult, } from '../utils/agent-gateway.js';
-import { promptInput } from '../utils/prompts.js';
 function augmentAgentInvokeErrorMessage(toolId, message) {
     const normalized = String(message ?? '').toLowerCase();
     if (normalized.includes('apply_required')) {
@@ -506,10 +505,7 @@ export async function runAgentInvoke(options = {}) {
     const apiState = await requireApiState(options);
     if (!apiState)
         return;
-    let toolId = normalizeNonEmpty(options.tool)?.toLowerCase();
-    if (!toolId && interactive) {
-        toolId = normalizeNonEmpty(await promptInput({ message: 'Tool id:' }))?.toLowerCase();
-    }
+    const toolId = normalizeNonEmpty(options.tool)?.toLowerCase();
     if (!toolId) {
         logError('Missing tool id. Provide --tool <id>.');
         process.exitCode = 1;

package/dist/commands/api.js

@@ -3,16 +3,12 @@ import { banner, logError, logInfo, logSuccess } from '@aopslabs/xf-cli-ui';
 import { appendQueryToPath, buildDomainApiPath, parseJsonInput, } from '../utils/operator-runtime.js';
 import { applyCommonOptions, normalizeNonEmpty, } from '../utils/command.js';
 import { buildAgentContextHeaders, requireApiState } from '../utils/agent-gateway.js';
-import { promptInput } from '../utils/prompts.js';
 export async function runApiCall(options = {}) {
     const interactive = !options.yes && !options.json;
     const apiState = await requireApiState(options);
     if (!apiState)
         return;
-    let domain = normalizeNonEmpty(options.domain);
-    if (!domain && interactive) {
-        domain = normalizeNonEmpty(await promptInput({ message: 'Domain (e.g. docman):' }));
-    }
+    const domain = normalizeNonEmpty(options.domain);
     if (!domain) {
         logError('Missing domain. Provide --domain <id>.');
         process.exitCode = 1;

package/dist/commands/assets.js

@@ -2,7 +2,6 @@ import { createHash } from 'node:crypto';
 import { readFileSync } from 'node:fs';
 import path from 'node:path';
 import { Command } from 'commander';
-import { banner, logError, logInfo, logSuccess } from '@aopslabs/xf-cli-ui';
 import { AgentAssetsError, agentAssetsFailure, agentAssetsSuccess, assertBoundedDiscoveryEnvelope, } from '../lib/agent-assets/envelope.js';
 import { resolveAgentAssetsMutationGuard } from '../lib/agent-assets/guards.js';
 import { discoverHostedSkills } from '../lib/agent-assets/hosted-discovery.js';
@@ -14,10 +13,8 @@ import { resolveAgentAssetsRoots } from '../lib/agent-assets/roots.js';
 import { inspectRuntimeGatewayBindings } from '../lib/agent-assets/runtime-binding-reader.js';
 import { readAgentAssetsStoreStatus, readAgentAssetsRollbackTarget, readAgentAssetsPrunePlan, readResolvedAgentAssetPackage, resolveAgentAsset, } from '../lib/agent-assets/store-reader.js';
 import { applyVerifiedCommunityCore, applyVerifiedHostedSkillPackage, cleanupAgentAssetsStaging, pinAgentAssetsExactVersion, pruneAgentAssets, repairAgentAssetRuntimeBindings, rollbackAgentAssets, } from '../lib/agent-assets/store-writer.js';
-import { createSetupAgentAssetsProvider, } from '../lib/setup-agent-assets-bridge.js';
 import { resolveSetupAgentAssetsReleaseV1 } from '../lib/setup-agent-assets-release.js';
-import { AGENT_ASSET_RUNTIME_IDS, AGENT_ASSET_RUNTIME_REGISTRY, collectAgentAssetTarget, resolveAgentAssetTargetSelection, selectAgentAssetRuntimeHomes, } from '../lib/agent-assets/runtime-targets.js';
-import { promptConfirm, promptMultiSelect, promptSelect } from '../utils/prompts.js';
+import { collectAgentAssetTarget, resolveAgentAssetTargetSelection, selectAgentAssetRuntimeHomes, } from '../lib/agent-assets/runtime-targets.js';
 function stableRootId(kind, absolutePath) {
     const canonicalPath = process.platform === 'win32'
         ? path.normalize(absolutePath).toLowerCase()
@@ -1108,135 +1105,6 @@ Notes:
         .action(action('assets.migrate.legacy-pointers', runner));
     return command;
 }
-export const AGENT_ASSETS_HOME = `AOPS Agent Assets
-
-Global Gateway skill pointers:
-  Status                 aops assets status --verify full
-  Install                aops assets install --apply
-  Update                 aops assets update --apply
-  Repair pointers        aops assets repair --repair-bindings --apply
-  Remove pointers        aops assets uninstall --apply --confirm
-
-Targets: --target codex | --target claude | --target codex,claude | --target all
-`;
-function menuStatusData(status) {
-    return (status.data ?? {});
-}
-function showAgentAssetsStatus(status) {
-    const data = menuStatusData(status);
-    logInfo(status.summary);
-    logInfo(`Core: ${data.store?.state ?? 'unknown'}`);
-    logInfo(`Codex pointer: ${data.runtimeBindings?.codex?.state ?? 'unknown'}`);
-    logInfo(`Claude pointer: ${data.runtimeBindings?.claude?.state ?? 'unknown'}`);
-}
-async function selectAgentAssetsTarget() {
-    const selected = await promptMultiSelect({
-        message: 'Registered runtime targets:',
-        choices: AGENT_ASSET_RUNTIME_REGISTRY.map((runtime) => ({
-            name: runtime.label,
-            value: runtime.id,
-            checked: true,
-        })),
-    });
-    if (selected.length === 0) {
-        throw new AgentAssetsError('schema_incompatible', 'Select at least one registered runtime.', {
-            nextActions: ['Select one or more runtimes, or leave every registered runtime checked for all.'],
-        });
-    }
-    return resolveAgentAssetTargetSelection(selected.length === AGENT_ASSET_RUNTIME_IDS.length ? 'all' : selected);
-}
-function selectedRuntimeHomes(roots, target) {
-    return selectAgentAssetRuntimeHomes(target, {
-        codex: roots.runtimeHomes.codex.absolutePath,
-        claude: roots.runtimeHomes.claude.absolutePath,
-    });
-}
-async function resolveAgentAssetsReleaseForMenu(provider) {
-    const resolved = await provider.resolveRelease?.({});
-    if (!resolved?.fromRelease) {
-        throw new Error('agent_assets_bundled_source_unavailable:reinstall_the_official_aops_cli_package');
-    }
-    logInfo(resolved.source === 'bundled-npm'
-        ? 'Using the verified Gateway assets bundled with this AOPS CLI installation.'
-        : `Using verified Gateway assets from ${resolved.source}.`);
-    return resolved.fromRelease;
-}
-export async function runAgentAssetsMenu(provider = createSetupAgentAssetsProvider()) {
-    if (!process.stdin.isTTY || !process.stdout.isTTY) {
-        process.stdout.write(AGENT_ASSETS_HOME);
-        return;
-    }
-    banner('AOPS Agent Assets');
-    logInfo('Manage the verified AOPS Gateway skill pointers for registered agent runtimes.');
-    while (true) {
-        const status = await provider.status();
-        showAgentAssetsStatus(status);
-        const storeReady = menuStatusData(status).store?.state === 'ready';
-        const action = await promptSelect({
-            message: 'Agent assets action:',
-            choices: [
-                { name: 'Inspect status', value: 'status' },
-                { name: storeReady ? 'Update verified Gateway core' : 'Install verified Gateway core', value: 'install-update' },
-                { name: 'Repair global pointers', value: 'repair' },
-                { name: 'Remove global pointers', value: 'uninstall' },
-                { name: 'Quick command help', value: 'help' },
-                { name: 'Back', value: 'back' },
-            ],
-            pageSize: 6,
-        });
-        if (action === 'back')
-            return;
-        if (action === 'status')
-            continue;
-        if (action === 'help') {
-            process.stdout.write(AGENT_ASSETS_HOME);
-            continue;
-        }
-        try {
-            const target = await selectAgentAssetsTarget();
-            if (action === 'uninstall') {
-                const confirmed = await promptConfirm({
-                    message: 'Remove only the selected recognized AOPS global pointer files?',
-                    default: false,
-                });
-                if (!confirmed)
-                    continue;
-                const roots = resolveAgentAssetsRoots({});
-                const removed = removeAopsGatewayPointers({
-                    assetRoot: roots.assetRoot,
-                    runtimeHomes: selectedRuntimeHomes(roots, target),
-                });
-                logSuccess(removed.removed.length > 0
-                    ? `Removed: ${removed.removed.join(', ')}. Verified core and receipts were retained.`
-                    : 'Selected global pointers were already absent.');
-                continue;
-            }
-            if (!provider.apply)
-                throw new Error('agent_assets_apply_unavailable');
-            if (action === 'repair') {
-                if (!await promptConfirm({ message: 'Repair the selected managed AOPS pointers now?', default: true }))
-                    continue;
-                const repaired = await provider.apply({ action: 'repair', target: target.selector });
-                showAgentAssetsStatus(repaired);
-                logSuccess('Gateway pointer repair completed.');
-                continue;
-            }
-            const operation = storeReady ? 'update' : 'install';
-            const fromRelease = await resolveAgentAssetsReleaseForMenu(provider);
-            if (!await promptConfirm({
-                message: `${operation === 'install' ? 'Install' : 'Update'} the verified Gateway core for ${target.selector}?`,
-                default: true,
-            }))
-                continue;
-            const applied = await provider.apply({ action: operation, fromRelease, target: target.selector });
-            showAgentAssetsStatus(applied);
-            logSuccess(`Gateway ${operation} completed.`);
-        }
-        catch (error) {
-            logError(error instanceof Error ? error.message : String(error));
-        }
-    }
-}
 export function makeAssetsCommand(runner = defaultAgentAssetsCommandRunner) {
     const command = new Command('assets')
         .description(`Install, inspect, update, repair, remove pointers, and roll back verified AOPS client assets in
@@ -1409,6 +1277,6 @@ Notes:
 `)
         .action(action('assets.prune', runner));
     command.addCommand(makeMigrateCommand(runner));
-    command.action(() => runAgentAssetsMenu());
+    command.action(() => command.outputHelp());
     return command;
 }

package/dist/commands/community-auth.js

@@ -16,7 +16,7 @@ export function guardCommunitySecretArgv(argv) {
     for (const token of argv.slice(2)) {
         const flag = token.split('=', 1)[0]?.toLowerCase();
         if (SECRET_ARGV.has(flag)) {
-            throw new Error(`community_secret_argv_refused:${flag}:use_interactive_prompt_secure_store_or_environment`);
+            throw new Error(`community_secret_argv_refused:${flag}:use_secure_store_browser_or_environment`);
         }
     }
 }