Release RelayX v0.5.4 usability upgrade

Author: RedteamNotes

README.md

@@ -246,6 +246,8 @@ relayx simulate-fixes    Simulate remediation impact on relay paths
 relayx quality-gate      Run local CI and release quality gates
 relayx schema            List or validate schema and evidence contracts
 relayx opsec             List or inspect OPSEC policies
+relayx discover          Search commands and topics by task or keyword
+relayx next              Suggest next useful commands from current context
 relayx modules           List execution module manifests
 relayx module-plan       Evaluate execution modules for one path
 relayx run               Run the guarded execution state machine
@@ -283,6 +285,24 @@ Human-readable help and command output display a RelayX banner with the current
 version. Use `--no-banner` for compact terminal output. JSON, CSV, HTML,
 Markdown, Mermaid, and enterprise export payloads are kept machine-clean.
 
+## Discovery And Next Steps
+
+Use `discover` when you know the task but not the command, and `next` when you
+have a RelayX result and want concrete follow-up commands.
+
+```bash
+relayx discover epa
+relayx discover jsonl
+relayx discover route --group Route/Pivot
+relayx next
+relayx next --result result.json
+relayx next --result result.json --path-id PX-0001
+```
+
+`discover` searches command names, groups, examples, output contracts, help
+topics, and safety notes. `next` is read-only: it does not validate, execute,
+probe, export, or modify files unless you run one of the suggested commands.
+
 ## Short Options
 
 Most high-use options have short aliases. Long options remain the clearest form
@@ -310,14 +330,25 @@ workflows.
 
 ```bash
 relayx console --result result.json --path-id PX-0001 --opsec-policy strict
+relayx console --history-file ~/.relayx/history
+relayx console --no-history --no-completion
 relayx completion zsh > relayx.zsh
+relayx discover epa
+relayx next --result result.json
 relayx help getting-started
 relayx --no-color help run
 ```
 
 Inside the console, use commands such as `use result <file>`, `use path
 PX-0001`, `set opsec-policy strict`, `show summary`, `show paths`, `explain`,
-`validate`, `run`, `export`, `bundle`, `help`, `back`, and `exit`.
+`validate`, `run`, `export`, `bundle`, `discover`, `next`, `menu`, `help`, `?`,
+`clear`, `cls`, `history`, `back`, and `exit`.
+
+Interactive console sessions support readline line editing, Up/Down history,
+Tab completion, persistent history, and clear-screen commands. Use
+`--no-history`, `RELAYX_NO_HISTORY=1`, or a leading space before a command when
+history should not be recorded; use `--no-completion` to disable console Tab
+completion.
 
 ## Output Formats
 

docs/CLI.md

@@ -71,7 +71,36 @@ Next steps
 - Controlled Execution: `modules`, `module-plan`, `run`
 - Enterprise: `profiles`, `report`, `export`, `bundle`, `diff`,
   `simulate-fixes`
-- Admin: `help`, `completion`, `console`, `opsec`, `schema`, `quality-gate`
+- Admin: `help`, `discover`, `next`, `completion`, `console`, `opsec`,
+  `schema`, `quality-gate`
+
+## Command Discovery And Next Steps
+
+`relayx discover` searches the CommandSpec registry, examples, output
+contracts, help topics, and safety notes. Use it when you know the task but do
+not remember the command.
+
+```bash
+relayx discover epa
+relayx discover jsonl
+relayx discover route --group Route/Pivot
+relayx discover execution --format json
+```
+
+`relayx next` suggests concrete follow-up commands. With no result, it prints a
+first-run path. With a result, it summarizes top paths and suggests review,
+evidence, route, validation, execution-planning, and enterprise handoff
+commands. With `--path-id`, it focuses the guidance on that path.
+
+```bash
+relayx next
+relayx next --result examples/tutorial/sample-result.json
+relayx next --result examples/tutorial/sample-result.json --path-id PX-0001
+relayx next -r examples/tutorial/sample-result.json -p PX-0001 -f json
+```
+
+`next` is read-only. It does not perform validation, execution, probing, export,
+or file modification.
 
 ## Operator Console
 
@@ -84,9 +113,24 @@ and guardrails as scripted workflows.
 relayx console
 relayx console --result examples/tutorial/sample-result.json --path-id PX-0001 --opsec-policy strict
 relayx console --script console.txt
+relayx console --history-file ~/.relayx/history
+relayx console --no-history --no-completion
 relayx --no-color console --result examples/tutorial/sample-result.json
 ```
 
+Interactive sessions use the terminal readline backend when available. That
+enables Up/Down command history navigation, incremental line editing, Tab completion
+for console commands, help topics, `show` targets, OPSEC policies, and
+result-file paths, plus Ctrl-L clear-screen behavior on terminals that support
+it. RelayX also provides explicit `clear` and `cls` commands.
+
+History is persisted to `RELAYX_HISTORY_FILE`, or `~/.relayx/history` by
+default. Use `--history-file` to choose a different file, `--no-history` or
+`RELAYX_NO_HISTORY=1` to disable history, and prefix a command with a leading
+space to keep that command out of persistent history. Commands containing
+obvious secret-bearing flags such as `--password` or `--token` are not saved.
+Script mode keeps deterministic text behavior and does not use readline.
+
 The prompt reflects context:
 
 ```text
@@ -108,13 +152,20 @@ show paths                 Run paths with the selected result
 show matrix                Run matrix with the selected result
 show sources               Run sources with the selected result
 explain [query]            Explain a query or the selected path
+menu                       Show grouped console commands and tips
+next                       Suggest next commands from selected result/path
+discover <keyword>         Search commands and topics from the console
 validate [args...]         Run validate with context-filled result/path/policy
 run [args...]              Run controlled execution with context-filled inputs
 export [args...]           Run export with context-filled result
 bundle [args...]           Run bundle with context-filled result
 help [topic]               Render curated RelayX help
+?                          Alias for help
+clear / cls                Clear the interactive terminal
+history [limit]            Show recent commands from the current session
+history clear              Clear in-memory and persisted console history
 back                       Clear path first, then result
-exit                       Leave the console
+exit / quit                Leave the console
 ```
 
 Console shortcuts call the same CLI handlers and preserve the same guardrails.

docs/README.zh-CN.md

@@ -230,6 +230,8 @@ relayx simulate-fixes    模拟修复对 relay path 的影响
 relayx quality-gate      运行本地 CI 和 release quality gate
 relayx schema            列出或验证 schema 和 evidence contract
 relayx opsec             列出或查看 OPSEC policy
+relayx discover          按任务或关键词搜索命令和 topic
+relayx next              根据当前 result/path 推荐下一步命令
 relayx modules           列出 execution module manifest
 relayx module-plan       评估 execution module 是否适用于某条 path
 relayx run               运行受控 execution state machine
@@ -267,6 +269,24 @@ relayx --no-banner help
 `--no-banner`。JSON、CSV、HTML、Markdown、Mermaid 和企业 export payload 会保持
 机器可读，不插入 banner。
 
+## 发现命令与下一步
+
+知道任务但不记得命令时，用 `discover`；已有 RelayX result 后，用 `next` 获取
+具体下一步命令。
+
+```bash
+relayx discover epa
+relayx discover jsonl
+relayx discover route --group Route/Pivot
+relayx next
+relayx next --result result.json
+relayx next --result result.json --path-id PX-0001
+```
+
+`discover` 会搜索 command name、group、example、output contract、help topic 和
+safety note。`next` 是只读引导：它不会执行 validation、execution、probe、export，
+也不会修改文件；只有你手动运行建议命令时才会进入对应 workflow。
+
 ## 短选项
 
 高频参数提供短选项。共享 runbook 和脚本中，长选项通常更清晰；交互式操作时，
@@ -292,14 +312,23 @@ OPSEC policy 和 scope 上重复分析。它会在 prompt 中显示当前上下
 
 ```bash
 relayx console --result result.json --path-id PX-0001 --opsec-policy strict
+relayx console --history-file ~/.relayx/history
+relayx console --no-history --no-completion
 relayx completion zsh > relayx.zsh
+relayx discover epa
+relayx next --result result.json
 relayx help getting-started
 relayx --no-color help run
 ```
 
 console 内可使用 `use result <file>`、`use path PX-0001`、`set opsec-policy
 strict`、`show summary`、`show paths`、`explain`、`validate`、`run`、`export`、
-`bundle`、`help`、`back` 和 `exit`。
+`bundle`、`discover`、`next`、`menu`、`help`、`?`、`clear`、`cls`、`history`、
+`back` 和 `exit`。
+
+交互式 console 支持 readline 行编辑、上下键历史、Tab 补全、持久化历史和
+清屏命令。敏感终端可使用 `--no-history`、`RELAYX_NO_HISTORY=1`，或在命令前
+加一个空格避免写入历史；需要关闭 console Tab 补全时使用 `--no-completion`。
 
 ## 输出格式
 

docs/TUTORIAL.md

@@ -51,9 +51,25 @@ From the repository root:
 relayx -V
 relayx -q help workflows
 relayx -q help getting-started
+relayx discover epa
 relayx -q quality-gate -C .
 ```
 
+When you know the task but not the exact command, use discovery:
+
+```bash
+relayx discover epa
+relayx discover jsonl
+relayx discover route --group Route/Pivot
+```
+
+Once you have a result file, `next` gives concrete follow-up commands:
+
+```bash
+relayx next --result examples/tutorial/sample-result.json
+relayx next --result examples/tutorial/sample-result.json --path-id PX-0001
+```
+
 Optional shell completion can make longer RelayX commands easier to use during
 runbook development:
 
@@ -80,20 +96,33 @@ workflows.
 ```bash
 relayx -q console --result examples/tutorial/sample-result.json --path-id PX-0001 --opsec-policy strict
 relayx --no-color -q console --result examples/tutorial/sample-result.json
+relayx -q console --history-file ~/.relayx/history
+relayx -q console --no-history --no-completion
 ```
 
 Example console commands:
 
 ```text
 context
+menu
+next
+discover jsonl
 show summary
 show paths
 explain
+clear
+history
 validate --mode dry-run
 run --mode dry-run
 exit
 ```
 
+In an interactive terminal, RelayX uses readline for line editing, Up/Down
+history navigation, Tab completion, and Ctrl-L clear-screen behavior when the
+terminal backend supports it. Use `clear` or `cls` when you want an explicit
+console command. Use `--no-history`, `RELAYX_NO_HISTORY=1`, or a leading space
+before a command when the command should not be persisted.
+
 ## 1. Inspect The Result
 
 Start with a compact summary:

docs/TUTORIAL.zh-CN.md

@@ -47,9 +47,25 @@ route metadata、修复控制、enterprise output 和受控执行审计记录。
 relayx -V
 relayx -q help workflows
 relayx -q help getting-started
+relayx discover epa
 relayx -q quality-gate -C .
 ```
 
+知道任务但不确定命令时，用 discovery：
+
+```bash
+relayx discover epa
+relayx discover jsonl
+relayx discover route --group Route/Pivot
+```
+
+拿到 result file 后，用 `next` 获取具体下一步命令：
+
+```bash
+relayx next --result examples/tutorial/sample-result.json
+relayx next --result examples/tutorial/sample-result.json --path-id PX-0001
+```
+
 可选 shell completion：
 
 ```bash
@@ -75,20 +91,32 @@ CLI handler。默认 human-readable help 和 console 输出会使用 ANSI 分色
 ```bash
 relayx -q console --result examples/tutorial/sample-result.json --path-id PX-0001 --opsec-policy strict
 relayx --no-color -q console --result examples/tutorial/sample-result.json
+relayx -q console --history-file ~/.relayx/history
+relayx -q console --no-history --no-completion
 ```
 
 console 示例命令：
 
 ```text
 context
+menu
+next
+discover jsonl
 show summary
 show paths
 explain
+clear
+history
 validate --mode dry-run
 run --mode dry-run
 exit
 ```
 
+在交互式终端中，RelayX 会通过 readline 提供行编辑、上下键历史、Tab 补全，
+以及终端后端支持时的 Ctrl-L 清屏。需要显式命令时可以使用 `clear` 或 `cls`。
+敏感场景可使用 `--no-history`、`RELAYX_NO_HISTORY=1`，或在命令前加一个空格
+避免写入持久化历史。
+
 ## 1. 查看 Result
 
 先看摘要：

fixtures/enterprise_output_matrix.json

@@ -210,7 +210,7 @@
     "docs/INSTALL.md"
   ],
   "release": {
-    "version": "0.1.16",
+    "version": "0.5.4",
     "console_script": "relayx",
     "pipx_installable": true
   },

fixtures/execution_modules/lab_only_target_relay_fixture.json

@@ -1,7 +1,7 @@
 {
   "key": "lab_only_target_relay_fixture",
   "label": "Lab-only target relay adapter fixture",
-  "version": "0.1.16-fixture",
+  "version": "0.5.4-fixture",
   "supported": false,
   "lab_only": true,
   "description": "Fixture manifest for a future live target relay adapter contract. It is intentionally not registered or supported.",

fixtures/execution_modules/ntlmrelayx_compat.json

@@ -1,7 +1,7 @@
 {
   "key": "ntlmrelayx_compat",
   "label": "ntlmrelayx-inspired compatibility boundary",
-  "version": "0.1.16-fixture",
+  "version": "0.5.4-fixture",
   "supported": false,
   "lab_only": true,
   "description": "Fixture manifest for a future Impacket-style adapter boundary.",

fixtures/execution_modules/relayx_audit_record.json

@@ -1,7 +1,7 @@
 {
   "key": "relayx_audit_record",
   "label": "RelayX offline audit record adapter",
-  "version": "0.1.16-fixture",
+  "version": "0.5.4-fixture",
   "supported": true,
   "lab_only": false,
   "description": "Fixture manifest for the safe offline adapter. It records execution evidence only.",

fixtures/lab_corpus/adcs_web_enrollment_epa_matrix.json

@@ -1,14 +1,14 @@
 {
   "metadata": {
     "tool": "RelayX",
-    "version": "0.1.16",
+    "version": "0.5.4",
     "schema_version": 1,
     "mode": "lab_signature_corpus",
     "captured_at": "2026-06-05T00:00:00+00:00",
     "label": "adcs-web-enrollment-epa-policy-matrix",
     "environment": "fixture-windows-server-adcs-iis",
     "policy_state": "mixed_adcs_epa_matrix",
-    "source_result_version": "0.1.16",
+    "source_result_version": "0.5.4",
     "active_probe": true,
     "finding_count": 2
   },