@nick848/fet 1.0.1 → 1.0.3

package/README.md

@@ -14,7 +14,7 @@ FET 是一个围绕 OpenSpec 构建的前端开发工作流编排 CLI。它不
 
 FET 是 OpenSpec 的透明代理和本地编排层。用户运行 `fet apply`、`fet archive` 等命令时，FET 会先读取项目状态和 change 状态，执行必要的 pre-hook，再调用真实的 `openspec` CLI，最后根据 OpenSpec 的结果更新 FET 状态。
 
-对于 OpenSpec 1.2.x，FET 会把部分高层命令映射到真实 OpenSpec 命令。例如 `fet apply` 会调用 `openspec instructions apply --change <id>` 输出实施指令，`fet sync` 会调用 `openspec validate <change> --type change --strict` 做归档前校验。
+FET 代理命令会保留 OpenSpec 原生命令名。例如 `fet apply --change <id>` 会调用 `openspec apply --change <id>`，`fet sync --change <id>` 会在 FET verify gate 通过后调用 `openspec sync --change <id>`。
 
 ### 环境要求
 
@@ -78,19 +78,19 @@ fet archive --change my-change
 | `fet init` | `fet init [--yes]` | 初始化 FET 和 OpenSpec；生成上下文文件、状态文件、Cursor 规则和 Skill。 |
 | `fet update-context` | `fet update-context [--yes]` | 重新扫描项目并更新 `AGENTS.md` 与 `openspec/config.yaml` 的 FET 托管区域。 |
 | `fet doctor` | `fet doctor [--fix-lock]` | 诊断 OpenSpec、FET 状态、上下文文件、Cursor 集成和锁文件。 |
-| `fet explore` | `fet explore --change <id>` | 输出探索/提案相关 OpenSpec 指令，帮助 AI 讨论需求。 |
+| `fet explore` | `fet explore [...args] [--change <id>]` | 代理 OpenSpec 原生 explore 流程，保留交互式需求澄清。 |
 | `fet propose` | `fet propose <change-id>` | 创建新的 OpenSpec change；等价于 FET 高层提案入口。 |
 | `fet new` | `fet new <change-id>` | 创建新的 OpenSpec change。 |
-| `fet continue` | `fet continue [artifact] --change <id>` | 输出指定 artifact 的 OpenSpec 指令，默认 `proposal`。 |
-| `fet ff` | `fet ff --change <id>` | 查看当前 change 的 OpenSpec artifact 状态。 |
-| `fet apply` | `fet apply --change <id>` | 输出实施当前 change 的 OpenSpec apply 指令，并同步 FET 状态。 |
+| `fet continue` | `fet continue [...args] [--change <id>]` | 通过 FET 执行 OpenSpec 原生 continue。 |
+| `fet ff` | `fet ff [...args] [--change <id>]` | 通过 FET 执行 OpenSpec 原生 ff。 |
+| `fet apply` | `fet apply [...args] [--change <id>]` | 通过 FET 执行 OpenSpec 原生 apply，并同步 FET 状态。 |
 | `fet verify` | `fet verify --change <id>` | 生成 `.fet/verify-instructions.md` 手动验证指令。 |
 | `fet verify --done` | `fet verify --done --change <id>` | 声明已完成手动验证，允许后续 `sync` / `archive`。 |
 | `fet verify --auto` | `fet verify --auto [--yes]` | 生成自动验证执行计划；当前版本不执行项目脚本，`--yes` 会记录授权计划指纹。 |
-| `fet sync` | `fet sync --change <id>` | 在 FET verify gate 通过后，调用 OpenSpec 严格校验 change。 |
+| `fet sync` | `fet sync [...args] [--change <id>]` | 在 FET verify gate 通过后，执行 OpenSpec 原生 sync。 |
 | `fet archive` | `fet archive --change <id>` | 在 FET verify gate 通过后，归档 change 并更新 OpenSpec 主规范。 |
-| `fet bulk-archive` | `fet bulk-archive` | 当前 OpenSpec 1.2.x 无对应顶层命令；请逐个执行 `fet archive --change <id>`。 |
-| `fet onboard` | `fet onboard` | 输出 OpenSpec onboarding / instruction 信息。 |
+| `fet bulk-archive` | `fet bulk-archive [...args] [--change <id>]` | 通过 FET 执行 OpenSpec 原生 bulk-archive。 |
+| `fet onboard` | `fet onboard [...args] [--change <id>]` | 通过 FET 执行 OpenSpec 原生 onboard。 |
 | `fet passthrough` | `fet passthrough <command> [...args]` | 透传暂未接管的 OpenSpec 命令，不更新 FET 生命周期状态。 |
 
 ### 生成文件
@@ -133,21 +133,21 @@ MIT
 
 ## English
 
-FET is a frontend development workflow orchestration CLI built around OpenSpec. It does not generate business code directly. Instead, it proxies OpenSpec commands, maintains local workflow state, generates auditable project context, and helps AI coding tools such as Cursor load the right files.
+FET is a frontend development workflow orchestration CLI built around OpenSpec. It does not generate business code directly. Instead, it proxies OpenSpec commands, maintains local workflow state, generates auditable project context, and helps AI coding tools such as Cursor and Codex load the right files.
 
 ### What It Does
 
 - Provides one entry point through `fet <command>` for OpenSpec workflows.
 - Generates `AGENTS.md` and the `fet:` namespace in `openspec/config.yaml`.
 - Tracks local workflow state such as active changes, synced tasks, manual verification declarations, and tool adapter state.
-- Integrates with AI tools by generating Cursor project rules and Skill instructions.
+- Integrates with AI tools by generating Cursor project rules, Cursor Skill instructions, and Codex-readable FET workflow guides.
 - Guards important stages by checking FET verification state before `sync` and `archive`.
 
 ### How It Works
 
 FET is a transparent proxy and local orchestration layer for OpenSpec. When you run commands such as `fet apply` or `fet archive`, FET loads project and change state, runs pre-hooks, calls the real `openspec` CLI, and then updates FET state based on the result.
 
-For OpenSpec 1.2.x, some high-level FET commands are mapped to the actual OpenSpec command surface. For example, `fet apply` calls `openspec instructions apply --change <id>`, and `fet sync` calls `openspec validate <change> --type change --strict`.
+FET proxy commands keep the OpenSpec command name intact. For example, `fet apply --change <id>` calls `openspec apply --change <id>`, and `fet sync --change <id>` calls `openspec sync --change <id>` after FET's verification gate passes.
 
 ### Requirements
 
@@ -208,22 +208,23 @@ fet archive --change my-change
 
 | Command | Usage | Description |
 |---------|-------|-------------|
-| `fet init` | `fet init [--yes]` | Initialize FET and OpenSpec; generate context, state, Cursor rules, and Skills. |
+| `fet init` | `fet init [--yes]` | Initialize FET and OpenSpec; generate context, state, Cursor rules and Skills, plus Codex workflow guides. |
 | `fet update-context` | `fet update-context [--yes]` | Rescan the project and update FET-managed regions in `AGENTS.md` and `openspec/config.yaml`. |
-| `fet doctor` | `fet doctor [--fix-lock]` | Diagnose OpenSpec, FET state, context files, Cursor integration, and lock files. |
-| `fet explore` | `fet explore --change <id>` | Print OpenSpec exploration/proposal instructions for discussing requirements. |
+| `fet fill-context` | `fet fill-context [--yes]` | Refresh IDE handoff commands that ask Cursor/Codex/OpenCode-style AI to replace `AGENTS.md` placeholders. |
+| `fet doctor` | `fet doctor [--fix-lock]` | Diagnose OpenSpec, FET state, context files, Cursor and Codex integration, and lock files. |
+| `fet explore` | `fet explore [...args] [--change <id>]` | Run native OpenSpec explore through FET so clarification prompts stay interactive. |
 | `fet propose` | `fet propose <change-id>` | Create a new OpenSpec change through FET's proposal entry point. |
 | `fet new` | `fet new <change-id>` | Create a new OpenSpec change. |
-| `fet continue` | `fet continue [artifact] --change <id>` | Print OpenSpec instructions for an artifact. Defaults to `proposal`. |
-| `fet ff` | `fet ff --change <id>` | Show OpenSpec artifact status for a change. |
-| `fet apply` | `fet apply --change <id>` | Print OpenSpec apply instructions and update FET state. |
+| `fet continue` | `fet continue [...args] [--change <id>]` | Run native OpenSpec continue through FET. |
+| `fet ff` | `fet ff [...args] [--change <id>]` | Run native OpenSpec ff through FET. |
+| `fet apply` | `fet apply [...args] [--change <id>]` | Run native OpenSpec apply through FET and update FET state. |
 | `fet verify` | `fet verify --change <id>` | Generate `.fet/verify-instructions.md` for manual verification. |
 | `fet verify --done` | `fet verify --done --change <id>` | Declare manual verification complete and allow `sync` / `archive`. |
 | `fet verify --auto` | `fet verify --auto [--yes]` | Generate an automatic verification plan. This version does not run project scripts; `--yes` records the plan fingerprint. |
-| `fet sync` | `fet sync --change <id>` | After FET verify gate passes, run strict OpenSpec validation for the change. |
-| `fet archive` | `fet archive --change <id>` | After FET verify gate passes, archive the change and update main OpenSpec specs. |
-| `fet bulk-archive` | `fet bulk-archive` | Not supported by OpenSpec 1.2.x as a top-level command. Archive changes one by one. |
-| `fet onboard` | `fet onboard` | Print OpenSpec onboarding / instruction information. |
+| `fet sync` | `fet sync [...args] [--change <id>]` | After FET verify gate passes, run native OpenSpec sync. |
+| `fet archive` | `fet archive --change <id>` | After FET verify gate passes, archive the change and append the change summary to `CHANGELOG.md`. |
+| `fet bulk-archive` | `fet bulk-archive [...args] [--change <id>]` | Run native OpenSpec bulk-archive through FET. |
+| `fet onboard` | `fet onboard [...args] [--change <id>]` | Run native OpenSpec onboard through FET. |
 | `fet passthrough` | `fet passthrough <command> [...args]` | Pass through unmanaged OpenSpec commands without updating FET lifecycle state. |
 
 ### Generated Files
@@ -235,8 +236,13 @@ FET may create or update:
 - `openspec/fet-state.json`
 - `openspec/changes/<change-id>/fet-state.json`
 - `openspec/changes/<change-id>/.fet/verify-instructions.md`
+- `CHANGELOG.md`
 - `.cursor/skills/fet-*/SKILL.md`
 - `.cursor/rules/fet-context.mdc`
+- `.codex/fet/context.md`
+- `.codex/fet/commands/*.md`
+- `$CODEX_HOME/prompts/fet-*.md` for Codex native slash commands. If `CODEX_HOME` is not set, FET uses `~/.codex`.
+- `.fet/fill-context.md` as a generic IDE handoff for tools without native command support.
 
 FET only owns explicitly marked managed regions. User content outside those regions should be preserved. During `fet init`, FET also adds a managed `.gitignore` block for local workflow state.