momo-ai 1.0.87 → 1.0.89

package/.codex/config.toml

@@ -0,0 +1,2 @@
+approval_policy = "never"
+sandbox_mode = "danger-full-access"

package/.codex-plugin/plugin.json

@@ -0,0 +1,35 @@
+{
+  "name": "r2mo-lain",
+  "version": "0.1.0",
+  "description": "Project-local Codex slash command workspace for R2MO Lain workflows.",
+  "author": {
+    "name": "R2MO"
+  },
+  "homepage": "https://gitee.com/silentbalanceyh/r2mo-lain",
+  "repository": "https://gitee.com/silentbalanceyh/r2mo-lain.git",
+  "license": "ISC",
+  "keywords": [
+    "r2mo",
+    "lain",
+    "momo",
+    "codex",
+    "slash-commands"
+  ],
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "R2MO Lain",
+    "shortDescription": "R2MO Lain Codex slash commands",
+    "longDescription": "Project-local Codex plugin package for developing reusable slash commands around R2MO Lain CLI workflows.",
+    "developerName": "R2MO",
+    "category": "Coding",
+    "capabilities": [
+      "Interactive",
+      "Write"
+    ],
+    "websiteURL": "https://gitee.com/silentbalanceyh/r2mo-lain",
+    "defaultPrompt": [
+      "Help me develop a Codex slash command for an R2MO Lain workflow"
+    ],
+    "screenshots": []
+  }
+}

package/AGENTS.md

@@ -1,307 +1,281 @@
-# AI Agents Integration (Momo CLI)
+# Codex Project Guide for r2mo-lain
 
-This document helps AI coding assistants understand the project structure and workflows. Following these conventions improves accuracy when assisting development.
+This file gives Codex the project-specific rules for working in this repository. It is derived from `CLAUDE.md` and adapted for Codex coding workflows.
 
-## Project Workflow
+## Project Identity
 
-1. **Requirements** – Define and analyze business needs
-2. **Task planning** – Break requirements into executable tasks
-3. **Role assignment** – Assign AI or human roles per task
-4. **Implementation** – Implement tasks and generate code
-5. **Verification** – Validate that outcomes meet requirements
-6. **Archive & commit** – Archive and commit completed work
+`r2mo-lain` is a Node.js RAD CLI for R2MO / Momo workflows.
 
-## Momo CLI Tools (Reference)
+- Package name: `momo-ai`
+- CLI binaries: `momo` and `lain`
+- Main entry: `src/momo.js`
+- Command metadata: `src/commander/*.json`
+- Command executors: `src/executor/execute*.js`
+- Shared utilities: `src/utils/momo-*.js`
+- Core runtime/logging helpers: `src/epic/`
 
-All tools are invoked as `momo <command> [options]`. Descriptions and options are derived from `src/commander/*.json`.
+This repository is not itself a Maven application. Do not apply Java, Spring, R2MO framework, or Zero framework coding rules unless the active task explicitly targets a generated Maven project outside this CLI or a Maven project is proven by a relevant `pom.xml`.
 
----
+## Critical Coding Rules
 
-### Basic commands
+### Module System
 
-#### `momo help [-c <command>]`
-Show help. With `-c`, show detailed help for a specific command.
+Use CommonJS only.
 
-**Options:**
-- `-c, --command`: Command name
+```js
+const Ec = require('../epic');
+const Args = require('../utils/momo-args');
 
-**Examples:**
-```bash
-momo help
-momo help -c init
+module.exports = async (options) => {
+    // implementation
+};
 ```
 
-#### `momo env`
-Check environment (Node.js, Python, and other system dependencies).
+Do not introduce ESM syntax.
 
-**Examples:**
-```bash
-momo env
+```js
+// Do not use in this project
+import Ec from '../epic';
+export default handler;
 ```
 
-#### `momo init [-d <dir>]`
-Initialize R2MO specification directory structure.
+### Core Imports
 
-**Options:**
-- `-d, --dir`: Target directory (default: current directory)
+Use the existing project modules instead of adding parallel abstractions.
 
-**Examples:**
-```bash
-momo init
-momo init -d ./my-project
+```js
+const Ec = require('../epic');
+const Args = require('../utils/momo-args');
+const FS = require('../utils/momo-fs');
+const { selectSingle, selectMultiple } = require('../utils/momo-menu');
 ```
 
----
+Path depth may vary by file location, but keep the same module families:
 
-### Development & project commands
+- `../epic` for logging, metadata parsing, flow control, and shared runtime helpers.
+- `../utils/momo-*` for filesystem, menu, argument, repository, and other utility behavior.
+- `src/commander/*.json` for command declaration and option metadata.
+- `src/executor/execute*.js` for command implementation.
 
-#### `momo app -n <name>`
-Create a new R2MO/Spring or ZERO/Vertx application.
+### Interactive Input
 
-**Options:**
-- `-n, --name`: Application name (required)
+All interactive selection UI must use `src/utils/momo-menu.js`.
 
-**Examples:**
-```bash
-momo app -n my-app
-```
-
-#### `momo open [-d <dir>]`
-Open the project with a chosen AI tool (Antigravity, Trae, Cursor).
-
-**Options:**
-- `-d, --dir`: Directory to open (default: current directory)
-
-**Examples:**
-```bash
-momo open
-momo open -d ./src
-```
+- Use `selectSingle()` for one choice.
+- Use `selectMultiple()` for multiple choices.
+- Use `clearScreen()` when matching existing menu behavior.
+- Do not add raw `readline`, `inquirer`, `prompts`, or another prompt package in command executors.
+- `readline` belongs in `momo-menu.js`; do not duplicate raw terminal handling elsewhere.
 
-#### `momo domain [-d <dir>] [-e]`
-Run `r2mo_proto` to process Maven project domain model (Protobuf / DB).
+### Logging And Output
 
-**Options:**
-- `-d, --dir`: Target directory (default: current directory); must be Maven root with `pom.xml`
-- `-e, --entity`: Generate from Entity (true) or from SQL (false); default true
+Use `Ec` for normal command output.
 
-**Examples:**
-```bash
-momo domain
-momo domain -d ./my-maven-project
+```js
+Ec.info('Done');
+Ec.warn('Skipped existing file');
+Ec.error('Path not found');
+Ec.waiting('Working...');
 ```
 
-#### `momo ui -n <name> [-d <dir>] [-u]`
-Create or update a UI subproject from the r2mo-ui template (Rust/WASM + Tauri).
-
-**Options:**
-- `-n, --name`: Project name (required for create; DPA suggests `xxx-ui`)
-- `-d, --dir`: Parent directory (default: current directory)
-- `-u, --update`: Update mode: sync root MD, `src/pages/components`, `src/pages/utils`, and optionally other changed files via multi-select; target defaults to current directory when `-u` is used without `-n`
-
-**Examples:**
-```bash
-momo ui -n my-app-ui -d .
-momo ui -u
+Avoid direct `console.log()` in new business logic. Only preserve or extend direct console output when the file is already a dedicated renderer, such as detailed help output or low-level terminal UI, and the existing style requires formatted raw output.
+
+### Process Exit
+
+Executors are CLI command handlers and commonly terminate explicitly.
+
+- On success, use `process.exit(0)` when the existing command pattern does so.
+- On handled failure, log with `Ec.error()` and use `process.exit(1)`.
+- Do not silently swallow errors.
+- Keep cleanup before exit for temp directories, raw terminal mode, and copied/generated resources.
+
+## Project Architecture
+
+```text
+src/
+├── commander/          # Command configuration JSON files
+│   └── {cmd}.json
+├── executor/           # Command implementations
+│   └── execute{Cmd}.js
+├── utils/              # Shared CLI utilities
+│   ├── momo-args.js
+│   ├── momo-menu.js
+│   └── momo-*.js
+├── epic/               # Core runtime helpers and logging
+├── python/             # Python helpers invoked by CLI commands
+├── _template/          # Project, prompt, MCP, and agent templates
+├── _agent/             # Agent metadata/templates
+├── _skill/             # Skill repository metadata
+└── _mcp/               # MCP skills server
 ```
 
-#### `momo admin [-d <dir>]`
-Generate front-end page structure from project requirements (`.r2mo/requirements/project.md`). Writes module/personal pages under `src/pages/`; skips overwriting existing files (metadata, requirement, page yaml).
-
-**Options:**
-- `-d, --dir`: Target directory (default: current directory)
-
-**Examples:**
-```bash
-momo admin
-momo admin -d .
+## Command Implementation Workflow
+
+When adding a `momo` command:
+
+1. Add command metadata in `src/commander/{cmd}.json`.
+2. Implement the executor in `src/executor/execute{Cmd}.js`.
+3. Export the executor from `src/executor/index.js`.
+4. Use `Ec.parseMetadata()` / existing command loading behavior instead of custom discovery.
+5. Test with `node src/momo.js help` and the specific command path.
+
+Command config shape:
+
+```json
+{
+  "executor": "executeName",
+  "command": "name",
+  "description": "Command description",
+  "options": [
+    {
+      "name": "argument",
+      "alias": "a",
+      "type": "string",
+      "description": "Option description"
+    }
+  ]
+}
 ```
 
----
-
-### Specification & API commands
-
-#### `momo mod [-d <dir>]`
-Pull r2mo-spec into `.r2mo/repo` and copy project/OpenAPI artifacts to `.r2mo/api/`.
-
-**Options:**
-- `-d, --dir`: Project root (default: current directory)
-
-**Examples:**
-```bash
-momo mod
-momo mod -d .
+Executor pattern:
+
+```js
+const Ec = require('../epic');
+const Args = require('../utils/momo-args');
+const FS = require('../utils/momo-fs');
+const { selectSingle } = require('../utils/momo-menu');
+
+module.exports = async (options) => {
+    try {
+        const opts = Args.parseStandard(options);
+        const target = Args.parsePositional()[0];
+
+        Ec.waiting('Working...');
+
+        if (target && !FS.exists(target)) {
+            Ec.error('Path not found');
+            process.exit(1);
+        }
+
+        const item = await selectSingle([{ name: 'Go' }], 'Title');
+        if (!item) {
+            process.exit(0);
+        }
+
+        Ec.info('Done');
+        process.exit(0);
+    } catch (e) {
+        Ec.error(e.message);
+        process.exit(1);
+    }
+};
 ```
 
-#### `momo openapi [-d <dir>]`
-Extract Operation/Schema markdown from subprojects’ `src/main/resources/openapi` and copy to `-ui/.r2mo/api/` preserving structure.
+## Codex Slash Command Development
 
-**Options:**
-- `-d, --dir`: Project root (default: current directory)
+This repository is also initialized as a project-local Codex plugin workspace for `/` command development.
 
-**Examples:**
-```bash
-momo openapi
-momo openapi -d .
-```
+- Plugin manifest: `.codex-plugin/plugin.json`
+- Slash command directory: `commands/`
+- Command conventions: `commands/_conventions.md`
+- Command template: `commands/_template.md`
+- Command validator: `scripts/validate-commands.js`
 
-#### `momo docs [-d <dir>]`
-Open the docs directory with Obsidian.
+Rules for Codex slash commands:
 
-**Options:**
-- `-d, --dir`: Target directory (default: current directory)
+- Finished commands live at `commands/<name>.md` and become invokable as `/<name>`.
+- Drafts, templates, and notes must start with `_`, for example `commands/_template.md`; underscore files are meta-documents and should not be treated as runnable commands.
+- Every runnable command must include YAML frontmatter with `description`.
+- Use `$ARGUMENTS` in command files for user-provided invocation text.
+- Keep runnable command files operational: include `Arguments`, `Preflight`, `Plan`, `Commands`, `Verification`, `Summary`, and `Next Steps` sections.
+- Validate command files with `npm run validate:commands` before claiming command setup is complete.
+- Do not add a runnable slash command until its workflow is specific, safe, and verifiable.
 
-**Examples:**
-```bash
-momo docs
-momo docs -d ./specification
-```
+## Existing Utility Contracts
 
-#### `momo menu [-d <dir>]`
-Scan `src/pages` for `menu.yaml` and print the full tree menu (name, text, icon).
+Argument parsing:
 
-**Options:**
-- `-d, --dir`: Project root (default: current directory)
+```js
+const Args = require('../utils/momo-args');
 
-**Examples:**
-```bash
-momo menu
-momo menu -d .
+const opts = Args.parseStandard(options);
+const value = Args.parseOptional('flag', 'f');
+const enabled = Args.parseBool('flag', 'f');
+const args = Args.parsePositional();
 ```
 
----
+Interactive menus:
 
-### Dictionary & Flyway commands
+```js
+const { selectSingle, selectMultiple, clearScreen } = require('../utils/momo-menu');
 
-#### `momo dict [-d <dir>] [-r]`
-**Forward:** Read `.r2mo/api/components/schemas` (XTabular/XCategory), connect via `app.env`, export `X_TABULAR`/`X_CATEGORY` by TYPE to `targetDir/.r2mo/data/dbdict/` as `dict.{type}.yaml` and `tree.{type}.yaml`. When matching Flyway SQL exists, prepend metadata (sqlFile, sqlPath) in YAML front-matter.
-
-**Reverse (`-r`):** Read `.r2mo/data/dbdict` YAML (DPA: from `-ui` dir). Only process files with valid metadata (sqlPath). Ask once to overwrite; then overwrite the SQL files at recorded paths.
-
-**Options:**
-- `-d, --dir`: Project root (default: current directory)
-- `-r, --reverse`: Reverse mode: YAML as input, generate/overwrite Flyway SQL using metadata
-
-**Examples:**
-```bash
-momo dict
-momo dict -d .
-momo dict -r
+const item = await selectSingle(items, 'Title');
+const result = await selectMultiple(items, 'Title');
+clearScreen();
 ```
 
----
-
-### Spec repository codegen commands
-
-#### `momo mmr0`
-Download from r2mo-spec repository and generate Flyway SQL files (e.g. into `-domain` Flyway dir).
-
-**Examples:**
-```bash
-momo mmr0
-```
-
-#### `momo mmr2`
-Download from r2mo-spec repository and generate Entity classes.
-
-**Examples:**
-```bash
-momo mmr2
-```
-
----
-
-### Skills & MCP commands
-
-#### `momo apply [-r [repo_name]]`
-Install skills from a remote repository into the local project. Choose target path interactively.
-
-**Options:**
-- `-r, --remote`: Install from remote (optional repo name)
-
-**Install targets:**
-- Cursor (`.claude/skills/`)
-- Antigravity (`.agent/skills/`)
-- Trae CN / Trae (`.trae/skills/`)
-- Lingma (`.lingma/skills/`)
-
-**Examples:**
-```bash
-momo apply -r
-momo apply -r anthropics/skills
-```
-
-#### `momo mcp [-c]`
-Configure MCP Skills Server: merge project and global skills and generate Cursor `mcp.json`.
-
-**Options:**
-- `-c, --check`: Only check dependencies; do not configure
-
-**Behavior:**
-- Install MCP deps under `.r2mo/mcpserver`
-- Write `.cursor/mcp.json`
-- Copy config to clipboard
-
-**Examples:**
-```bash
-momo mcp
-momo mcp -c
-```
-
----
-
-### Prompt & template commands
+Core logging:
 
-#### `momo ask`
-Pick a prompt template from `src/_template/R2MO/`, extract content between `--- BEGIN` and `--- END`, copy to clipboard, and show template details (file, title, version, skills, commands). If the prompt contains a “模块：ID,NAME,PATH” placeholder, scan `src/pages/*/requirement.module.md` (with valid front-matter, no `{}` placeholders), let the user choose a module, and replace the placeholder with that module’s ID, name, and path.
+```js
+const Ec = require('../epic');
 
-**Examples:**
-```bash
-momo ask
+Ec.info('Information message');
+Ec.warn('Warning message');
+Ec.error('Error message');
+Ec.waiting('Processing...');
 ```
 
----
-
-## Tool summary (by command)
-
-| Command   | Description (short) |
-|----------|----------------------|
-| `help`   | Show help; optional `-c` for command-specific help |
-| `env`    | Environment check |
-| `init`   | Initialize R2MO spec directory |
-| `app`    | Create R2MO/Spring or ZERO/Vertx app |
-| `open`   | Open project in AI tool (Antigravity/Trae/Cursor) |
-| `domain` | Run r2mo_proto for domain/Protobuf |
-| `ui`     | Create/update UI subproject from r2mo-ui; `-u` update mode |
-| `admin`  | Generate front-end page structure from requirements (skip existing) |
-| `mod`    | Pull r2mo-spec, copy OpenAPI to `.r2mo/api/` |
-| `openapi`| Extract OpenAPI md to `-ui/.r2mo/api/` |
-| `docs`   | Open docs in Obsidian |
-| `menu`   | Print tree menu from `src/pages` menu.yaml |
-| `dict`   | Export dict to `.r2mo/data/dbdict` (with metadata); `-r` reverse to Flyway SQL |
-| `mmr0`   | Generate Flyway SQL from r2mo-spec |
-| `mmr2`   | Generate Entity classes from r2mo-spec |
-| `apply`  | Install skills from remote (Cursor/Agent/Trae/Lingma) |
-| `mcp`    | Configure MCP Skills Server and `mcp.json` |
-| `ask`    | Select prompt template, optional module substitution, copy to clipboard |
-
----
-
-## Key paths
-
-- **Spec / requirements:** `.r2mo/requirements/`, `src/_template/R2MO/`
-- **Schemas / API:** `.r2mo/api/components/schemas`, `-ui/.r2mo/api/`
-- **Dictionary:** `.r2mo/data/dbdict/` (dict.*.yaml, tree.*.yaml; optional front-matter sqlFile/sqlPath)
-- **Flyway SQL:** `-domain/src/main/resources/plugins/<artifactId>/flyway/MYSQL/`
-- **Skills:** `.claude/skills/`, `.agent/skills/`, `.trae/skills/`, `.lingma/skills/`
-- **MCP:** `.r2mo/mcpserver/`, `.cursor/mcp.json`
-
----
-
-## Conventions
-
-1. **DPA vs ONE:** DPA = Domain + Provider + Api (+ `-ui`); target dir for UI/dbdict is `-ui`; app.env from `-api`. ONE = single project; target dir is project root.
-2. **momo dict:** Forward writes YAML with optional metadata from matching Flyway SQL; reverse only processes YAML with valid metadata and overwrites SQL after user confirmation.
-3. **momo admin:** Does not overwrite existing metadata, requirement, or page yaml files.
-4. **momo ask:** Modules with `{}` placeholders in front-matter are excluded from the module list.
-5. **momo ui -u:** Without `-n`, target is current directory; Rust/Tauri and listed root files are not updated in “other files” multi-select.
+## Testing And Verification
+
+There is no broad test suite configured beyond the package script. Prefer targeted CLI verification.
+
+- Run `node src/momo.js version` after changes touching startup or package metadata.
+- Run `node src/momo.js help` after changes touching command metadata, executor registration, or help behavior.
+- Run `node src/momo.js help -c <command>` after adding or changing one command.
+- Run the changed command with a safe temp directory or fixture when it writes files.
+- Run `npm test` only if the current task requires the package script; note that it maps directly to `src/index.test.js`.
+
+Do not claim verification succeeded unless the command was actually run and completed successfully.
+
+## Momo CLI Context
+
+Common user-facing commands are:
+
+- `momo help [-c <command>]`
+- `momo env`
+- `momo init [-d <dir>]`
+- `momo app -n <name>`
+- `momo open [-d <dir>]`
+- `momo domain [-d <dir>] [-e]`
+- `momo ui -n <name> [-d <dir>] [-u]`
+- `momo admin [-d <dir>]`
+- `momo mod [-d <dir>]`
+- `momo openapi [-d <dir>]`
+- `momo docs [-d <dir>]`
+- `momo menu [-d <dir>]`
+- `momo dict [-d <dir>] [-r]`
+- `momo mmr0`
+- `momo mmr2`
+- `momo apply [-r [repo_name]]`
+- `momo mcp [-c]`
+- `momo ask`
+- `momo task`
+- `momo run`
+- `momo team`
+- `momo focus`
+
+When command details are needed, prefer reading the corresponding `src/commander/{cmd}.json` and `src/executor/execute{Cmd}.js` instead of relying on this summary.
+
+## Editing Discipline
+
+- Keep changes small and aligned with the existing style.
+- Do not introduce new dependencies for behavior already covered by `src/utils` or `src/epic`.
+- Do not rewrite unrelated command executors while implementing a specific command.
+- Preserve existing generated/template assets unless the task explicitly targets them.
+- Respect dirty worktree changes that were not made for the current task.
+- Update templates under `src/_template/` only when the user asks for template behavior changes.
+
+## Repository Metadata
+
+- Repository: `https://gitee.com/silentbalanceyh/r2mo-lain.git`
+- Keywords: `r2mo`, `rad`, `lain`, `nodejs`, `cli`, `momo`

package/README.md

@@ -69,8 +69,8 @@ momo help
 | 命令 | 说明 | 示例 |
 |:---|:---|:---|
 | `momo ask` | 从模板目录中选择提示词并复制到剪切板 | `momo ask` |
-| `momo run` | 从 `.r2mo/task` 中选择任务，生成提示词到剪贴板 | `momo run` |
-| `momo task` | 在 `.r2mo/task/` 下使用五槽位创建任务，写入提示词到剪贴板 | `momo task` |
+| `momo run` | 从项目根或 `.r2mo` 目录下的 `task/` 中选择任务，生成提示词到剪贴板 | `momo run` |
+| `momo task` | 按项目根或 `.r2mo` 目录下的 `task/thread` 配置对齐任务槽位；thread 缺失时默认 20，满队列时交互选择要转历史的任务 | `momo task` |
 
 <hr/>
 
@@ -88,4 +88,4 @@ momo help
 - Maven 统一版本管理：<https://gitee.com/silentbalanceyh/rachel-momo>
 - Rapid快速开发框架：<https://gitee.com/silentbalanceyh/r2mo-rapid>
 - Zero Epoch：<https://www.zerows.io>
-- Zero Demo：<https://gitee.com/zero-ws/zero-rachel-momo>
+- Zero Demo：<https://gitee.com/zero-ws/zero-rachel-momo>

package/commands/_README.md

@@ -0,0 +1,28 @@
+# R2MO Lain Codex Slash Commands
+
+This directory is the project-local workspace for Codex `/` command development.
+
+Only finished command files should be exposed as slash commands. Keep work-in-progress notes, templates, and conventions prefixed with `_` so they remain meta-documents instead of user-invocable commands.
+
+## Current State
+
+No runnable slash command is registered yet. The environment is initialized for later command development.
+
+## File Rules
+
+- Use `commands/<name>.md` for a finished command that should be invokable as `/<name>`.
+- Use `commands/_<name>.md` for conventions, drafts, templates, and notes.
+- Use lower-case kebab-case names, for example `run-task.md`.
+- Include YAML frontmatter with at least `description`.
+- Use `$ARGUMENTS` in the command body when the command needs user-provided arguments.
+- Keep command text operational and verifiable: preflight, plan, commands, verification, summary, next steps.
+
+## Validation
+
+Run:
+
+```bash
+npm run validate:commands
+```
+
+The validator ignores underscore-prefixed Markdown files and checks finished command files for required structure.