@chenmk/superflow 0.1.1 → 0.1.2

package/assets/context-templates/incidents.md

@@ -1,89 +1,51 @@
-# 历史事故
+# 事故、返工与缺陷复盘
 
-> **初始版来源**：`openspec/changes/v1.1-add-charging-package-suite/bug-archive/yunxiao-2026-06-02-pending-confirmation/`（云效 2026-06-02 待确认批次）+ sdd-cli 引用过的 P 编号
-> **维护方**：测试 + 开发
-> **自动化率**：20-40%（commit "fix" + 注释 "FIX" 可挖，PR 描述/issue tracker 不可访问——私有仓）
+> **用途**：沉淀项目历史事故、返工、漏测和联调问题，避免同类问题重复发生。
+> **维护方**：测试负责人 / 开发负责人 / 模块 owner
 
-## 1. v1.1 充电套餐批次（2026-06-02 云效待确认）
+## 1. 事故索引
 
-来源目录：`openspec/changes/v1.1-add-charging-package-suite/bug-archive/yunxiao-2026-06-02-pending-confirmation/`
-原始文件：HTML（云效导出） + `raw-bugs.json`（待解析）
+| 编号 | 标题 | 发现时间 | 严重级别 | 状态 | 关联规则 |
+|------|------|----------|----------|------|----------|
+| INC-001 | `<标题>` | `YYYY-MM-DD` | `<P0/P1/P2/P3>` | `<待修复/已修复/已复盘>` | `<business-rules/decisions>` |
 
-### 1.1 套餐运营商 / 站点相关
+## 2. 复盘模板
 
-| CDPT | 标题 | 状态 | 关联规则 |
-|------|------|------|---------|
-| CDPT-165 | 创建套餐的查询条件，运营商与查询结果不匹配，创建的套餐是其他运营商的 | 待修复 | [business-rules §1.1](./business-rules.md#11-套餐业务) |
-| CDPT-171 | 应限制同一个站点不能创建相同名称的优惠套餐 | 待修复 | §1.1 |
-| CDPT-192 | 修改充电套餐的适用站点后，已开通套餐的记录，适用站点没有更新 | 待修复 | §1.1 |
-| CDPT-166 | 创建套餐页面，导出 Excel 中的使用站点列展示错误 | 待修复 | §4 |
-| CDPT-158 | 充电套餐的有效时段，应该允许跨天 | 待修复 | §1.1 |
-| CDPT-175 | 同车牌不同套餐、不同有效时间段 — 应该允许开通 | 待修复 | §1.1 |
-
-### 1.2 退款 / 对账 / 权益同步
-
-| CDPT | 标题 | 状态 | 关联规则 |
-|------|------|------|---------|
-| CDPT-186 | 充电套餐退款后，停车月票权益在 BEM 没有同步退款 | 待修复 | [business-rules §1.2](./business-rules.md#12-计费--退款--对账) |
-| CDPT-189 | 已退款的优惠套餐订单，扫码开票提示需优化 | 待修复 | §3 |
-| CDPT-169 | 续费充电套餐（停车月票），BEM 没有对该月票订单续费 | 待修复 | §6 |
-| CDPT-193 | 充电套餐适用多个站点时，无法开票 | 待修复 | §1.1 |
-
-### 1.3 批量开通 / 续费 / 退款
-
-| CDPT | 标题 | 状态 | 关联规则 |
-|------|------|------|---------|
-| CDPT-185 | 批量开通、续费、退款模板中手机号应支持填写 1 个或 2 个手机号 | 待修复 | [business-rules §2.1](./business-rules.md#21-批量开通--续费--退款) |
-| CDPT-180 | 批量开通、续费、退费时，遇到错误/异常数据整批数据都不插入业务系统，明确提示哪一行，哪个字段数据异常 | 待修复 | §2.1 |
-| CDPT-181 | 问题 1：批量开通上传文件类型错误时的提示需优化；问题 2：导入空的 Excel 模板也提示成功 | 待修复 | §2.1、§2.2 |
-| CDPT-178 | 批量开通、续费、退费模版字段，必填字段应加入【必填】两个字 | 待修复 | §2.1 |
-| CDPT-179 | 批量开通充电套餐，选择当天，1 天有效期，开通记录显示已过期。在页面开通显示生效中 | 待修复 | §2.1 |
-| CDPT-198 | 批量导入车位枪的文件格式错误，提示需优化 | 待修复 | §2.2 |
-| CDPT-199 | 站点没有绑定车位枪时，站点的【启用车位枪】按钮不允许打开 | 待修复 | [business-rules §1.3](./business-rules.md#13-车位--设备) |
-
-### 1.4 导出 / 查询 / 字段
-
-| CDPT | 标题 | 状态 | 关联规则 |
-|------|------|------|---------|
-| CDPT-188 | 套餐开通记录导出，剩余充电额度为不限额时，导出内容错误 | 待修复 | [business-rules §4](./business-rules.md#4-数据权限--字段约束) |
-| CDPT-177 | 开通套餐记录导出的 Excel 中不要合并不连续的有效期 | 待修复 | §4 |
-| CDPT-173 | 开通套餐页面的查询条件，【车牌号码】应支持模糊查询 | 待修复 | §4 |
-| CDPT-164 | 开通套餐的记录中，最近操作人取值错误（admin 后台开通） | 待修复 | §4 |
-| CDPT-163 | 开通充电套餐后，扫码开启充电，没有套餐可用 | 待修复 | §3 |
-| CDPT-194 | 停车权益记录，适用车场的名称没展示 | 待修复 | §4 |
-
-## 2. 历史 P 编号记录（sdd-cli 引用过）
-
-来源：`sdd-cli/assets/skills/superflow-implement/SKILL.md` 等地方提到的 P 编号示例
-
-| P 编号 | 描述 | 备注 |
-|--------|------|------|
-| P50 | worktree 启动端口示例（base 9250 → 9300） | 端口计算约定 |
-| P64 | prompt 命名示例（p64-export-plot-display.md） | 命名约定 |
-
-> **注**：完整 P 编号历史应从 git log + openspec/changes/archive/ 反推。本文件仅记录 sdd-cli 显式引用的。
+```markdown
+### INC-001: <标题>
+
+- **发现时间**：YYYY-MM-DD HH:mm
+- **发现渠道**：线上报警 / QA / 客户反馈 / 联调 / code review
+- **影响范围**：用户、订单、数据、接口、任务或环境范围。
+- **直接原因**：触发故障的直接技术原因。
+- **根因**：为什么流程、设计、测试或代码没有提前发现。
+- **修复 commit / PR**：<链接或 SHA>
+- **验证证据**：测试命令、真实请求、日志、DB 记录或截图。
+- **防复发措施**：
+  - 文档规则：补充到哪个 `docs/sdd-context/*.md`
+  - 代码防线：新增哪个测试、断言、告警或 guard
+  - 流程防线：哪个阶段必须新增检查项
+- **复盘人**：<name>
+```
 
-## 3. 事故复盘模板
+## 3. 常见问题分类
 
-每条事故建议补充以下信息（自动化扫不到，需人工补）：
+| 分类 | 典型表现 | Superflow 阶段加固 |
+|------|----------|-------------------|
+| 需求理解偏差 | 字段语义、状态流、边界条件理解错误 | clarify / docs |
+| 源码影响面遗漏 | 只改一处，没有反查所有引用 | design |
+| 数据库合同遗漏 | 代码依赖字段，但 SQL/migration 未更新 | docs / verify |
+| mock-only 假通过 | 只跑 mock 单测，未跑真实入口 | implement / verify |
+| 异步链路漏验 | MQ、定时任务、回调没有真实证据 | verify |
+| 上下文漂移 | 长会话压缩后忘记原始约束 | handoff / guard |
 
-```markdown
-### CDPT-XXX: <标题>
+## 4. 复盘回写要求
 
-- **发现时间**：YYYY-MM-DD
-- **发现渠道**：云效 / QA / 线上报警 / 客户反馈
-- **根因**：（一句话说清楚，不要泛泛说"业务逻辑错误"）
-- **影响范围**：（哪些模块 / 哪些数据 / 多少用户 / 持续多久）
-- **修复 commit**：（`git log --grep="CDPT-XXX"` 拿 SHA）
-- **修复时间**：YYYY-MM-DD
-- **复盘人**：<name>
-- **预防措施**：（代码 / 流程 / 测试 哪一层加固）
-- **关联规则**：[business-rules.md §X.Y](./business-rules.md)
-```
+事故复盘完成后，至少回写一处长期规则：
 
-## 4. 维护提示
+- 业务规则问题：写入 [business-rules.md](./business-rules.md)。
+- 架构或工程约定问题：写入 [decisions.md](./decisions.md)。
+- 外部系统或联调问题：写入 [external-systems.md](./external-systems.md)。
+- 测试策略问题：写入当前 OpenSpec change 的 `tests.md` 和 `test-report.md`。
 
-- **不要直接复制云效 HTML**——内容里含截图/附件链接，存 md 里维护性差
-- 建议用 `raw-bugs.json` 解析后写本文件（一次性脚本）
-- 后期可让 LLM 帮补全"根因 / 影响范围"等结构化字段
-- 修复完成后这条记录可以从"待修复"挪到"已闭环"区
+只在聊天记录里解释，不算复盘完成。

package/assets/context-templates-en/business-rules.md

@@ -0,0 +1,72 @@
+# Business Rules
+
+> **Purpose**: Capture long-lived project business rules, edge cases, state
+> transitions, and acceptance criteria.
+> **Owners**: Product owner / business owner / engineering owner
+> **Maintenance**: `superflow init --language en` creates this template. Fill it
+> with project-specific facts before relying on it for delivery decisions.
+
+## 1. Core Business Objects
+
+| Object | Meaning | Uniqueness Rule | Lifecycle States | Key Constraints |
+|--------|---------|-----------------|------------------|-----------------|
+| `<Object A>` | `<Meaning>` | `<Unique key>` | `<States>` | `<Constraints>` |
+| `<Object B>` | `<Meaning>` | `<Unique key>` | `<States>` | `<Constraints>` |
+
+## 2. State Transitions
+
+| State | Entry Condition | Allowed Actions | Forbidden Actions | Exit Condition |
+|-------|-----------------|-----------------|-------------------|----------------|
+| `<State A>` | `<Condition>` | `<Actions>` | `<Actions>` | `<Condition>` |
+| `<State B>` | `<Condition>` | `<Actions>` | `<Actions>` | `<Condition>` |
+
+Rules:
+
+- When a state field, enum, derived value, or sync value changes, reverse-scan
+  all readers, writers, filters, exports, scheduled jobs, callbacks, and
+  cross-repo consumers.
+- Record the real source of truth for derived state. Do not infer semantics
+  from field names alone.
+- Compatibility or fallback behavior must name the owner, removal condition,
+  and observability plan.
+
+## 3. Critical Business Rules
+
+| ID | Rule | Applies To | Edge Case | Acceptance Evidence |
+|----|------|------------|-----------|---------------------|
+| BR-001 | `<Rule>` | `<Page/API/job>` | `<Edge case>` | `<Test/evidence>` |
+| BR-002 | `<Rule>` | `<Page/API/job>` | `<Edge case>` | `<Test/evidence>` |
+
+## 4. Data And Permission Boundaries
+
+| Dimension | Rule | Evidence Source |
+|-----------|------|-----------------|
+| Tenant / organization / project | `<Isolation rule>` | `<Source/config/table>` |
+| User roles | `<Permission rule>` | `<Menu/API/auth point>` |
+| Data visibility | `<Query scope>` | `<Mapper/API/page>` |
+| Write permissions | `<Mutation rule>` | `<Service/transaction/audit>` |
+
+## 5. Batch, Import, Export, And Error Rules
+
+- Batch operations must define all-or-nothing vs partial-success behavior.
+- Import templates must define required fields, formats, enums, duplicates, and
+  empty-file behavior.
+- Export fields must match page/API semantics; document intentional differences.
+- Error messages must identify the object, row, field, or concrete fix.
+
+## 6. Real Acceptance Evidence
+
+Requirements involving external systems, databases, async jobs, message queues,
+payments, files, permissions, or state transitions cannot be closed with mock
+unit tests alone. `test-report.md` should record:
+
+- Real entry point: page, API, message, scheduled job, or external callback.
+- Real parameters: request body, message payload, file sample, or test account.
+- Real result: response, database record, log, downstream callback, or UI state.
+- Assertion: expected vs actual values.
+
+## 7. Maintenance Notes
+
+- Keep project facts here, not generic process slogans.
+- After incidents, rework, or integration misses, add reusable rules here.
+- Mark uncertain rules as `To confirm`, with owner and evidence source.

package/assets/context-templates-en/decisions.md

@@ -0,0 +1,72 @@
+# Architecture And Engineering Decisions
+
+> **Purpose**: Capture long-lived architectural choices, engineering conventions,
+> and the reasoning behind trade-offs.
+> **Owners**: Architect / tech lead / module owner
+> **Recommended format**: ADR (Architecture Decision Record)
+
+## ADR-001: <Decision Title>
+
+- **Status**: Proposed / Accepted / Deprecated / Replaced
+- **Date**: YYYY-MM-DD
+- **Context**: Why this decision is needed.
+- **Decision**: The selected approach.
+- **Alternatives**:
+  - Option A: benefits and costs.
+  - Option B: benefits and costs.
+- **Impact**: Repositories, modules, tables, APIs, jobs, or deployment paths.
+- **Consequences**: Benefits, costs, risks, and future constraints.
+- **Verification**: How to prove the decision is implemented correctly.
+
+## 1. Project Structure
+
+| Topic | Current Convention | Source Of Truth | Notes |
+|-------|--------------------|-----------------|-------|
+| Module boundaries | `<Description>` | `<Directory/doc/config>` | `<Notes>` |
+| Layering | `<Description>` | `<Entrypoint>` | `<Notes>` |
+| Naming | `<Description>` | `<README/code example>` | `<Notes>` |
+| Configuration | `<Description>` | `<env/config/secret source>` | `<Notes>` |
+
+## 2. Database And Persistence
+
+| Topic | Current Convention | Required Gate |
+|-------|--------------------|---------------|
+| Schema source of truth | `<SQL/migration/live schema>` | Verify before edits |
+| Release SQL / migration | `<Rule>` | Required fields must ship |
+| Shared table consumers | `<Repo/module list>` | Reverse-scan all consumers |
+| Soft delete / multi-tenancy | `<Rule>` | Mapper/XML queries must align |
+
+## 3. API And Integration
+
+| Topic | Current Convention | Verification |
+|-------|--------------------|--------------|
+| API style | `<REST/RPC/GraphQL/message>` | `<Contract/integration test>` |
+| Authentication | `<Method>` | `<Test account/permission matrix>` |
+| Error codes | `<Rule>` | `<API doc/test>` |
+| External calls | `<Rule>` | `<Sandbox/real env/simulator>` |
+
+## 4. Testing And Delivery
+
+- Unit tests prove local logic; they do not prove a real delivery path.
+- External entry points require real request, message, log, or state evidence.
+- Database-backed changes require schema and data evidence.
+- Async flows require message, log, state transition, retry, or compensation
+  evidence.
+- Before claiming completion, run the relevant Superflow guard and project
+  verification command.
+
+## 5. Superflow Usage Decisions
+
+- OpenSpec/SDD owns WHAT and contracts.
+- Superpowers owns source-level HOW, TDD order, review, and verification
+  discipline.
+- `.sdd/state.yaml` and `.sdd/handoff/` are the state source of truth for
+  preventing context drift.
+- Parallel workers must state which docs and code paths they may edit.
+- Refresh the handoff hash when docs, code, prompts, or test reports change.
+
+## 6. Deprecated Decisions
+
+| Old Decision | Why Deprecated | Replacement | Date |
+|--------------|----------------|-------------|------|
+| `<ADR ID>` | `<Reason>` | `<ADR ID>` | `YYYY-MM-DD` |

package/assets/context-templates-en/external-systems.md

@@ -0,0 +1,78 @@
+# External Systems And Integration Contracts
+
+> **Purpose**: Record external systems, APIs, messages, files, accounts, and
+> integration evidence for this project.
+> **Owners**: Integration owner / module owner / QA owner
+
+## 1. System Topology
+
+```text
+<Current system>
+  +- HTTP / RPC -> <External system A>
+  +- MQ / Event -> <External system B>
+  +- File / Object Storage -> <External system C>
+  +- Webhook / Callback <- <External system D>
+```
+
+## 2. External System Inventory
+
+| System | Responsibility | Integration Type | Environment | Owner | Failure Handling |
+|--------|----------------|------------------|-------------|-------|------------------|
+| `<System A>` | `<Responsibility>` | `<HTTP/MQ/SDK/File>` | `<dev/test/prod>` | `<Owner>` | `<Retry/alert/compensation>` |
+| `<System B>` | `<Responsibility>` | `<HTTP/MQ/SDK/File>` | `<dev/test/prod>` | `<Owner>` | `<Retry/alert/compensation>` |
+
+## 3. API / SDK Contracts
+
+| System | API/SDK | Caller | Auth | Timeout/Retry | Real Test Entry |
+|--------|---------|--------|------|---------------|-----------------|
+| `<System A>` | `<Path/method/SDK method>` | `<Module>` | `<Method>` | `<Policy>` | `<curl/console/simulator>` |
+
+Rules:
+
+- Real API paths, parameters, and responses must come from source code,
+  official docs, or integration records.
+- Do not invent fields from memory. If semantics are unclear, return to the
+  source of truth.
+- When a field is added, removed, or renamed, reverse-scan callers, DTOs,
+  mappers, logs, and tests.
+
+## 4. Messages And Async Flows
+
+| Topic / Queue / Event | Producer | Consumer | Payload Source | Idempotency Key | Verification |
+|-----------------------|----------|----------|----------------|-----------------|--------------|
+| `<Event>` | `<System>` | `<System>` | `<Schema/code>` | `<Field>` | `<Log/DB/consumer record>` |
+
+Async completion evidence should include:
+
+- Producer log or send record.
+- Consumer log or handling record.
+- State transition, database write, or downstream callback.
+- Retry, dead-letter, or compensation strategy.
+
+## 5. Files, Object Storage, And Batch Jobs
+
+| File / Job | Source | Format | Storage | Trigger | Verification |
+|------------|--------|--------|---------|---------|--------------|
+| `<File/job>` | `<Source>` | `<CSV/XLSX/JSON>` | `<Path/bucket>` | `<Manual/scheduled/API>` | `<Sample/log/result>` |
+
+## 6. Environments And Credentials
+
+| Environment | Address | Credential Source | Test Account | Notes |
+|-------------|---------|-------------------|--------------|-------|
+| dev | `<URL>` | `<env/secret manager>` | `<Account>` | `<Notes>` |
+| test | `<URL>` | `<env/secret manager>` | `<Account>` | `<Notes>` |
+| prod | `<URL>` | `<env/secret manager>` | `<Account>` | `<Notes>` |
+
+Do not write real secrets, tokens, or private keys here. Record only where they
+come from and how to request access.
+
+## 7. Integration Acceptance
+
+- When sandbox or test environments are available, mock-only evidence is not
+  enough.
+- If real integration is blocked, record the blocker, owner, recovery condition,
+  and temporary substitute verification.
+- `test-report.md` must include actual requests, responses, logs, or data
+  evidence.
+- Compatibility logic for external systems must be observable; do not silently
+  swallow errors.

package/assets/context-templates-en/incidents.md

@@ -0,0 +1,52 @@
+# Incidents, Rework, And Defect Reviews
+
+> **Purpose**: Capture incidents, rework, missed tests, and integration misses
+> so similar issues do not repeat.
+> **Owners**: QA owner / engineering owner / module owner
+
+## 1. Incident Index
+
+| ID | Title | Found At | Severity | Status | Related Rule |
+|----|-------|----------|----------|--------|--------------|
+| INC-001 | `<Title>` | `YYYY-MM-DD` | `<P0/P1/P2/P3>` | `<Open/fixed/reviewed>` | `<business-rules/decisions>` |
+
+## 2. Review Template
+
+```markdown
+### INC-001: <Title>
+
+- **Found at**: YYYY-MM-DD HH:mm
+- **Found by**: Production alert / QA / customer feedback / integration / code review
+- **Impact**: Users, orders, data, APIs, jobs, or environments affected.
+- **Immediate cause**: The technical trigger.
+- **Root cause**: Why design, process, tests, or code failed to catch it earlier.
+- **Fix commit / PR**: <link or SHA>
+- **Verification evidence**: Test command, real request, log, DB row, or screenshot.
+- **Prevention**:
+  - Documentation rule: which `docs/sdd-context/*.md` file was updated.
+  - Code guard: which test, assertion, alert, or guard was added.
+  - Process guard: which workflow phase now checks this.
+- **Reviewer**: <name>
+```
+
+## 3. Common Categories
+
+| Category | Typical Symptom | Superflow Phase To Harden |
+|----------|-----------------|---------------------------|
+| Requirement drift | Field semantics, state flow, or edge case misunderstood | clarify / docs |
+| Source impact missed | Only one reference changed, other consumers missed | design |
+| Database contract missed | Code depends on fields that release SQL does not ship | docs / verify |
+| Mock-only false pass | Mock unit tests pass but real entry fails | implement / verify |
+| Async flow unverified | MQ, scheduled job, or callback lacks real evidence | verify |
+| Context drift | Long session compression loses original constraints | handoff / guard |
+
+## 4. Required Backfill
+
+After an incident review, update at least one long-lived rule:
+
+- Business rule issue: [business-rules.md](./business-rules.md).
+- Architecture or engineering decision issue: [decisions.md](./decisions.md).
+- External integration issue: [external-systems.md](./external-systems.md).
+- Test strategy issue: current OpenSpec change `tests.md` and `test-report.md`.
+
+Explaining the issue only in chat does not count as a completed review.

package/assets/manifest.json

@@ -1,6 +1,6 @@
 {
-  "version": "0.1.0",
-  "agents": ["claude", "codex"],
+  "version": "0.1.2",
+  "agents": ["claude", "codex", "opencode"],
   "skills": [
     "openspec-apply-change",
     "openspec-archive-change",
@@ -35,7 +35,8 @@
   ],
   "agentScripts": {
     "claude": ["claude-auto-backup-hook.sh"],
-    "codex": ["codex-auto-backup-hook.sh"]
+    "codex": ["codex-auto-backup-hook.sh"],
+    "opencode": []
   },
   "hooks": [
     "superflow-enforce-hook.sh",
@@ -48,6 +49,7 @@
   ],
   "agentHooks": {
     "claude": ["claude-auto-backup-hook.sh"],
-    "codex": ["codex-auto-backup-hook.sh"]
+    "codex": ["codex-auto-backup-hook.sh"],
+    "opencode": []
   }
 }

package/assets/scripts/claude-auto-backup-hook.sh

@@ -1,13 +1,12 @@
 #!/bin/bash
 # Claude Code global experience auto backup hook.
-# Syncs curated ~/.claude development experience into code-cli-config/claude-code-setup,
-# then commits the backup repository. Push requires explicit --push-once.
+# Optionally syncs curated ~/.claude development experience into a user-provided
+# backup repository. Push requires explicit --push-once.
 
 set -u
 
 CLAUDE_HOME="${CLAUDE_HOME:-$HOME/.claude}"
-CONFIG_REPO="${CLAUDE_CONFIG_REPO:-/Users/chenmankun/cmk-project/code-cli-config}"
-BACKUP_ROOT="$CONFIG_REPO/claude-code-setup"
+CONFIG_REPO="${CLAUDE_CONFIG_REPO:-}"
 LOCK_DIR="${TMPDIR:-/tmp}/claude-auto-backup.lock"
 
 usage() {
@@ -18,7 +17,7 @@ usage() {
 环境变量:
   CLAUDE_AUTO_BACKUP_DISABLE=1  临时关闭自动备份
   CLAUDE_AUTO_BACKUP_DRY_RUN=1  只同步检查，不提交
-  CLAUDE_CONFIG_REPO=/path       指定 code-cli-config 仓库路径
+  CLAUDE_CONFIG_REPO=/path       指定备份仓库路径；未设置时自动跳过
 USAGE
 }
 
@@ -42,6 +41,12 @@ if [ "${CLAUDE_AUTO_BACKUP_DISABLE:-0}" = "1" ]; then
   exit 0
 fi
 
+if [ -z "$CONFIG_REPO" ]; then
+  exit 0
+fi
+
+BACKUP_ROOT="$CONFIG_REPO/claude-code-setup"
+
 log() {
   echo "[Claude 自动备份] $1" >&2
 }
@@ -266,7 +271,7 @@ if [ "$DRY_RUN" = "1" ]; then
   exit 0
 fi
 
-log "提交 code-cli-config"
+log "提交备份仓库"
 
 STAGE_PATHS=(
   "claude-code-setup/CLAUDE.md"

package/assets/scripts/codex-auto-backup-hook.sh

@@ -1,13 +1,12 @@
 #!/bin/bash
 # Codex global experience auto backup hook.
-# Syncs curated ~/.codex development experience into code-cli-config/codex-setup,
-# then commits the backup repository. Push requires explicit --push-once.
+# Optionally syncs curated ~/.codex development experience into a user-provided
+# backup repository. Push requires explicit --push-once.
 
 set -u
 
 CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
-CONFIG_REPO="${CODEX_CONFIG_REPO:-/Users/chenmankun/cmk-project/code-cli-config}"
-BACKUP_ROOT="$CONFIG_REPO/codex-setup"
+CONFIG_REPO="${CODEX_CONFIG_REPO:-}"
 LOCK_DIR="${TMPDIR:-/tmp}/codex-auto-backup.lock"
 
 usage() {
@@ -18,7 +17,7 @@ usage() {
 环境变量:
   CODEX_AUTO_BACKUP_DISABLE=1  临时关闭自动备份
   CODEX_AUTO_BACKUP_DRY_RUN=1  只同步检查，不提交
-  CODEX_CONFIG_REPO=/path       指定 code-cli-config 仓库路径
+  CODEX_CONFIG_REPO=/path       指定备份仓库路径；未设置时自动跳过
 USAGE
 }
 
@@ -42,6 +41,12 @@ if [ "${CODEX_AUTO_BACKUP_DISABLE:-0}" = "1" ]; then
   exit 0
 fi
 
+if [ -z "$CONFIG_REPO" ]; then
+  exit 0
+fi
+
+BACKUP_ROOT="$CONFIG_REPO/codex-setup"
+
 log() {
   echo "[Codex 自动备份] $1" >&2
 }
@@ -298,7 +303,7 @@ if [ "$DRY_RUN" = "1" ]; then
   exit 0
 fi
 
-log "提交 code-cli-config"
+log "提交备份仓库"
 
 STAGE_PATHS=(
   "codex-setup/codex配置/config.toml"