@stackonward/cli 1.7.0 → 1.8.0

package/dist/resources/components/nuxt/site-source/app/composables/useWebPush.ts

@@ -0,0 +1,4 @@
+/** 订阅与撤销只由真实用户动作调用；初始化只查询能力和已有状态。 */
+export function useWebPush() {
+  return useNuxtApp().$webPush;
+}

package/dist/resources/components/nuxt/site-source/app/plugins/web-push.ts

@@ -0,0 +1,52 @@
+import type { State } from "@stackonward/web-push";
+import { createBrowser, initialState } from "@stackonward/web-push";
+import { createWebPushController } from "@stackonward/composables";
+import { createApi, createStorage, readConfig } from "@stackonward/onex-web-push";
+
+export default defineNuxtPlugin({
+  name: "site:web-push",
+  setup(nuxtApp) {
+    const runtime = useRuntimeConfig();
+    const state = useState<State>("site:web-push", initialState);
+    const controller = createWebPushController(state, () => {
+      const config = readConfig(
+        runtime.public.webPush,
+        window.location.origin,
+        runtime.app.baseURL,
+        runtime.public.api.timeout,
+      );
+      return {
+        enabled: config.enabled,
+        api: createApi(config),
+        browser: createBrowser(
+          {
+            origin: config.origin,
+            workerUrl: new URL("push-sw.js", new URL(config.basePath, config.origin)).href,
+            scope: config.basePath,
+            timeout: config.timeout,
+          },
+          window,
+          navigator,
+        ),
+        storage: createStorage(
+          {
+            databaseName: runtime.public.webPush.databaseName,
+            origin: config.origin,
+            productCode: config.productCode,
+            applicationCode: config.applicationCode,
+          },
+          window.indexedDB,
+        ),
+      };
+    });
+    if (import.meta.client) {
+      onNuxtReady(() => {
+        void controller.initialize().catch(() => {
+          /* 初始化错误已进入状态；网站浏览不依赖推送服务可用。 */
+        });
+      });
+      nuxtApp.vueApp.onUnmount(() => controller.dispose());
+    }
+    return { provide: { webPush: controller } };
+  },
+});

package/dist/resources/components/nuxt/site-source/app/web-push/worker.ts

@@ -0,0 +1,8 @@
+import type { WorkerScope } from "@stackonward/web-push/worker";
+import { installWorker } from "@stackonward/web-push/worker";
+import { decodeMessage } from "@stackonward/onex-web-push";
+
+declare const self: WorkerScope;
+
+// 产品拥有品牌兜底文案；运行时实现通过公开包消费。
+installWorker(self, { fallbackTitle: "Website notification", decode: decodeMessage });

package/dist/resources/components/registry.json

@@ -147,6 +147,12 @@
     "description": "Editable Nuxt product-site source: site shell, app shell, content shell, UI primitives, composables, plugins, theme tokens, and CSS.",
     "installContext": "template",
     "files": [
+      { "path": "site-source/app/plugins/web-push.ts", "target": "app/plugins/web-push.ts" },
+      {
+        "path": "site-source/app/composables/useWebPush.ts",
+        "target": "app/composables/useWebPush.ts"
+      },
+      { "path": "site-source/app/web-push/worker.ts", "target": "app/web-push/worker.ts" },
       {
         "path": "site-source/app/app.vue",
         "target": "app/app.vue"
@@ -468,7 +474,11 @@
         "target": "app/theme/tooltip.ts"
       }
     ],
-    "dependencies": ["@stackonward/composables"],
+    "dependencies": [
+      "@stackonward/composables",
+      "@stackonward/web-push",
+      "@stackonward/onex-web-push"
+    ],
     "devDependencies": [],
     "registryDependencies": [],
     "framework": "nuxt",

package/dist/resources/registry.json

@@ -5,6 +5,18 @@
     "type": "npm",
     "version": "^0.0.3"
   },
+  "@stackonward/web-push": {
+    "name": "@stackonward/web-push",
+    "description": "Provider-neutral browser Web Push and worker primitives",
+    "type": "npm",
+    "version": "^0.0.1"
+  },
+  "@stackonward/onex-web-push": {
+    "name": "@stackonward/onex-web-push",
+    "description": "OneX anonymous Web Push protocol and recovery storage adapters",
+    "type": "npm",
+    "version": "^0.0.1"
+  },
   "@stackonward/analytics-core": {
     "name": "@stackonward/analytics-core",
     "description": "Provider-neutral analytics pipeline and browser autocapture",
@@ -21,7 +33,7 @@
     "name": "@stackonward/cli",
     "description": "StackOnward project and resource CLI",
     "type": "npm",
-    "version": "^1.7.0"
+    "version": "^1.8.0"
   },
   "@stackonward/cms-client": {
     "name": "@stackonward/cms-client",
@@ -45,7 +57,7 @@
     "name": "@stackonward/composables",
     "description": "Headless Vue composables",
     "type": "npm",
-    "version": "^0.0.2"
+    "version": "^0.1.0"
   },
   "@stackonward/device-fingerprint": {
     "name": "@stackonward/device-fingerprint",
@@ -111,7 +123,7 @@
     "name": "@stackonward/nuxt-site-shell",
     "description": "Brand-free Nuxt product-site shell",
     "type": "layer",
-    "version": "^0.3.2"
+    "version": "^0.4.0"
   },
   "@stackonward/onex-cms-client": {
     "name": "@stackonward/onex-cms-client",

package/dist/resources/templates/base/{.claude → .codex}/docs/architecture-template.md

@@ -113,7 +113,7 @@ application already contains these modules.
 
 ### 4.2 Package Split Decision
 
-{Answer the package split rules from CLAUDE.md: Which owner has two real consumers? Which types remain feature-private? Does a shared contract avoid framework or provider leakage?}
+{Answer the package split rules from AGENTS.md: Which owner has two real consumers? Which types remain feature-private? Does a shared contract avoid framework or provider leakage?}
 
 ---
 

package/dist/resources/templates/base/{.claude → .codex}/docs/architecture.md

@@ -124,7 +124,7 @@ Brand tokens, logos, locale and navigation belong to application composition. Ge
 
 Projects must run outside the source checkout. **FORBIDDEN**: developer absolute paths, dependency escapes, symlinks to external rules and commands requiring unshipped helpers.
 
-Template changes affect new projects. Existing applications receive reviewed source changes; regeneration never overwrites business code or credentials. CLAUDE and AGENTS remain synchronized complete files.
+Template changes affect new projects. Existing applications receive reviewed source changes; regeneration never overwrites business code or credentials. AGENTS remains the complete rule authority.
 
 ## 10. Architecture and Delivery
 

package/dist/resources/templates/base/{.claude → .codex}/docs/index.md

@@ -1,6 +1,6 @@
 # Application Standards Index
 
-Read [CLAUDE.md](../../CLAUDE.md) completely, then select the task boundary:
+Read [AGENTS.md](../../AGENTS.md) completely, then select the task boundary:
 
 | Task                               | Standard                                        |
 | ---------------------------------- | ----------------------------------------------- |
@@ -15,7 +15,7 @@ This directory contains current engineering rules. Product designs and implement
 
 ## Required Reading Sequence
 
-1. Read root `CLAUDE.md` or its identical full `AGENTS.md` body for the five execution phases and shared forbidden patterns.
+1. Read root `AGENTS.md` for the five execution phases and shared forbidden patterns.
 2. Read `stack.md` for the actual generated framework, environment consumers, commands and source owners.
 3. Read `architecture.md` before changing ownership, public types, dependencies or shared abstractions.
 4. Read `security-lifecycle.md` before changing external inputs, identity, credentials, requests, retries, cancellation or disposal.
@@ -39,4 +39,4 @@ Only the selected `stack.md` is installed. Base standards never overwrite it wit
 
 **MUST** update the owning rule when a real contract changes; do not append a correction beside stale instructions. Keep useful examples, forbidden patterns and checklist coverage. Do not shorten a complete standard into an index-only entry.
 
-CLAUDE and AGENTS are standalone full files and must remain equal. Relative links must resolve inside the generated project; external source-checkout paths and external symlinks are forbidden. Record source comparison and implementation evidence in ordinary project documentation, not these binding rules.
+<rule_authority>MUST keep one complete regular `AGENTS.md` per owner. NEVER maintain a second editable rule entrypoint for the same owner.</rule_authority> Relative links must resolve inside the generated project; external source-checkout paths and external symlinks are forbidden. Record source comparison and implementation evidence in ordinary project documentation, not these binding rules.

package/dist/resources/templates/base/{.claude → .codex}/docs/verification.md

@@ -79,7 +79,7 @@ Tests of services with fake dependencies do not prove actual provider permission
 
 ## 8. Distribution and Generated Projects
 
-For template changes, generate an application outside the source workspace using the packed CLI. Verify substituted variables, complete CLAUDE/AGENTS bodies, `.claude/docs`, relative links, package resolution and executable commands.
+For template changes, generate an application outside the source workspace using the packed CLI. Verify substituted variables, the complete AGENTS body, `.codex/docs`, relative links, package resolution and executable commands.
 
 Do not rely on workspace symlinks to satisfy dependencies. Inspect packed files and the consumer artifact. The generated project must not reference developer absolute paths or template placeholders.
 

package/dist/resources/templates/base/AGENTS.md

@@ -1,6 +1,6 @@
 # Application Engineering Standard
 
-> **Runtime**: Node.js ESM and TypeScript; complete installed stack in `.claude/docs/stack.md`.
+> **Runtime**: Node.js ESM and TypeScript; complete installed stack in `.codex/docs/stack.md`.
 > **Owner**: application business rules, routes, branding, configuration and release.
 > **Dependencies**: versioned public package exports; generated source belongs to this application.
 
@@ -13,7 +13,7 @@ app/ and server/                  # Nuxt presentation and server execution bound
 src/                             # MCP registrations, adapters and process startup
 package.json                     # Installed dependencies and executable commands
 .env.example                     # Configuration schema without credentials
-.claude/docs/                    # Complete engineering specifications
+.codex/docs/                    # Complete engineering specifications
 ```
 
 ---
@@ -33,29 +33,29 @@ pnpm build
 
 ## Coding Rules
 
-The selected stack has complete coding rules in `.claude/docs/stack.md`. Shared AI execution flow is defined in this file. `AGENTS.md` contains the same complete body. Nested rules add owner-specific constraints.
+The selected stack has complete coding rules in `.codex/docs/stack.md`. Shared AI execution flow is defined in this file. <rule_authority>MUST keep one complete regular `AGENTS.md` per owner. NEVER maintain a second editable rule entrypoint for the same owner.</rule_authority> Nested rules add owner-specific constraints.
 
 | File                                    | Scope                                                         |
 | --------------------------------------- | ------------------------------------------------------------- |
-| `CLAUDE.md`                             | Shared execution flow and delivery discipline                 |
-| `.claude/docs/index.md`                 | Reading order and module navigation                           |
-| `.claude/docs/stack.md`                 | Framework rules, full command and environment tables          |
-| `.claude/docs/architecture.md`          | Ownership, dependency direction, contracts and reuse          |
-| `.claude/docs/security-lifecycle.md`    | Validation, secrets, authorization, cancellation and recovery |
-| `.claude/docs/verification.md`          | Verification and delivery requirements                        |
-| `.claude/docs/architecture-template.md` | Complete design skeleton                                      |
+| `AGENTS.md`                             | Shared execution flow and delivery discipline                 |
+| `.codex/docs/index.md`                 | Reading order and module navigation                           |
+| `.codex/docs/stack.md`                 | Framework rules, full command and environment tables          |
+| `.codex/docs/architecture.md`          | Ownership, dependency direction, contracts and reuse          |
+| `.codex/docs/security-lifecycle.md`    | Validation, secrets, authorization, cancellation and recovery |
+| `.codex/docs/verification.md`          | Verification and delivery requirements                        |
+| `.codex/docs/architecture-template.md` | Complete design skeleton                                      |
 
-**Read the selected stack and applicable nested `CLAUDE.md` before writing code.**
+**Read the selected stack and applicable nested `AGENTS.md` before writing code.**
 
 ## Visual Design Standards (CRITICAL)
 
-For a stack with a visual interface, **MUST** read the design standard identified by `.claude/docs/stack.md` before choosing icons, colors, sizing or component overrides. Use that stack's installed component system, token owner and asset conventions. Icon artwork, accessible labels and interactive target size are separate responsibilities; local size changes must use the existing component contract.
+For a stack with a visual interface, **MUST** read the design standard identified by `.codex/docs/stack.md` before choosing icons, colors, sizing or component overrides. Use that stack's installed component system, token owner and asset conventions. Icon artwork, accessible labels and interactive target size are separate responsibilities; local size changes must use the existing component contract.
 
 **FORBIDDEN**: inventing a second icon library or theme implementation for an existing capability. Non-visual stacks do not acquire UI dependencies or a required design document from this rule.
 
 ## Technology Stack and Environment
 
-Read `package.json`, `.env.example`, configuration consumers and `.claude/docs/stack.md` before changing dependencies or environment variables. A sample variable does not prove that runtime code reads it. Nuxt uses `pnpm dev` / `pnpm preview`; MCP uses `pnpm start:stdio` after build. Never put private credentials in Nuxt public configuration or MCP tool output.
+Read `package.json`, `.env.example`, configuration consumers and `.codex/docs/stack.md` before changing dependencies or environment variables. A sample variable does not prove that runtime code reads it. Nuxt uses `pnpm dev` / `pnpm preview`; MCP uses `pnpm start:stdio` after build. Never put private credentials in Nuxt public configuration or MCP tool output.
 
 ## Workflow Proportionality (CRITICAL)
 
@@ -93,7 +93,7 @@ Directories, modules and packages are namespaces. Child files and symbols **MUST
 # AI Execution Standard
 
 > Mandatory workflow for every task, regardless of language or subproject.
-> Stack-specific rules are in `.claude/docs/stack.md` and applicable nested rules.
+> Stack-specific rules are in `.codex/docs/stack.md` and applicable nested rules.
 
 ---
 
@@ -104,8 +104,8 @@ Before touching code, fully understand the task and its context.
 ### 1.1 Read Project Documentation
 
 1. Read this file for shared execution rules.
-2. Read the subproject `CLAUDE.md` for stack-specific rules, starting with `.claude/docs/stack.md`.
-3. Read subproject specs, and shared specs under `.claude/docs/` that are relevant to the task.
+2. Read the subproject `AGENTS.md` for stack-specific rules, starting with `.codex/docs/stack.md`.
+3. Read subproject specs, and shared specs under `.codex/docs/` that are relevant to the task.
 4. Read existing architecture documents for affected modules.
 
 **Read specs before designing. Do not rely on memory or assumptions about project conventions.**
@@ -365,7 +365,7 @@ Violation of any rule blocks commit. No exceptions.
 | SH-E3 | Enforcement   | Fix applied as patch/workaround without proper design                                                                        | Make the fix architecturally sound                                                                                                                                                                         |
 | SH-E6 | Enum Registry | Cross-language enum metadata duplication, such as backend labels/colors/options plus frontend `constants/*.ts` copies        | The owning backend contract is the single source of truth for business enum metadata. Consume its declared API/generated types; pure UI variants stay local. Do not assume a platform enum endpoint exists |
 
-Additional forbidden patterns are defined in each subproject's `CLAUDE.md`. Identifier/reference boundaries are in `.claude/docs/security-lifecycle.md`.
+Additional forbidden patterns are defined in each subproject's `AGENTS.md`. Identifier/reference boundaries are in `.codex/docs/security-lifecycle.md`.
 
 ---
 
@@ -411,11 +411,11 @@ The principle: fail loudly, never silently skip. A production system that return
 
 | Doc                                     | Content                                                   |
 | --------------------------------------- | --------------------------------------------------------- |
-| `.claude/docs/stack.md`                 | Framework rules, real directories and executable commands |
-| `.claude/docs/architecture.md`          | Types, owner boundaries and dependency direction          |
-| `.claude/docs/security-lifecycle.md`    | Trust, identity, secrets, async lifetime and recovery     |
-| `.claude/docs/verification.md`          | Full verification and delivery requirements               |
-| `.claude/docs/architecture-template.md` | Complete Level A/B/C skeleton                             |
+| `.codex/docs/stack.md`                 | Framework rules, real directories and executable commands |
+| `.codex/docs/architecture.md`          | Types, owner boundaries and dependency direction          |
+| `.codex/docs/security-lifecycle.md`    | Trust, identity, secrets, async lifetime and recovery     |
+| `.codex/docs/verification.md`          | Full verification and delivery requirements               |
+| `.codex/docs/architecture-template.md` | Complete Level A/B/C skeleton                             |
 
 ## Project Skill Routing
 
@@ -423,7 +423,7 @@ Use only skills available in the active environment. Read the selected entry and
 
 ## Artifact Hygiene (CRITICAL)
 
-Durable standards belong in `.claude/docs/`; concrete designs and evidence belong in ordinary `docs/designs/`. Binding rules describe implemented structures and stable constraints. FORBIDDEN: conversation transcripts, repair narration, future-state assertions, dead links and invented commands.
+Durable standards belong in `.codex/docs/`; concrete designs and evidence belong in ordinary `docs/designs/`. Binding rules describe implemented structures and stable constraints. FORBIDDEN: conversation transcripts, repair narration, future-state assertions, dead links and invented commands.
 
 ## Pre-commit Checklist
 
@@ -433,5 +433,5 @@ Durable standards belong in `.claude/docs/`; concrete designs and evidence belon
 - [ ] Relevant success, validation, authorization and recovery behavior is verified.
 - [ ] Declared stack checks pass; unavailable checks are reported accurately.
 - [ ] No secrets, dead imports or deferred production code enter the diff.
-- [ ] CLAUDE.md and AGENTS.md contain the same complete standards body.
+- [ ] One complete AGENTS.md authority links the applicable .codex/docs standards.
 - [ ] Normal commits preserve unrelated work and remote history.

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/api-design.md

@@ -1,6 +1,6 @@
 # API Design Templates
 
-> Templates only. Rules are in `CLAUDE.md`.
+> Templates only. Rules are in `AGENTS.md`.
 
 ## OpenAPI Security Contract
 

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/architecture-template.md

@@ -118,7 +118,7 @@ internal/platform/{module}/
 
 ### 4.2 Package Split Decision
 
-{Answer the package split rules from CLAUDE.md: Does application/ need sub-domain splitting? Does domain/ need splitting by aggregate root?}
+{Answer the package split rules from AGENTS.md: Does application/ need sub-domain splitting? Does domain/ need splitting by aggregate root?}
 
 ---
 

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/check-list.md

@@ -1,6 +1,6 @@
 # Development Checklist
 
-> Workflow and quality gates. Rules in `CLAUDE.md`.
+> Workflow and quality gates. Rules in `AGENTS.md`.
 
 ---
 
@@ -8,7 +8,7 @@
 
 1. Design（架构评审）
 2. Implementation
-3. Self-review（对照 CLAUDE.md FORBIDDEN 表）
+3. Self-review（对照 AGENTS.md FORBIDDEN 表）
 4. Pre-commit validation
 
 ---
@@ -110,7 +110,7 @@ Pre-Commit Validation
 =====================
 Files changed: [list]
 Specs checked:
-  - CLAUDE.md FORBIDDEN table: PASS/FAIL (CRITICAL)
+  - AGENTS.md FORBIDDEN table: PASS/FAIL (CRITICAL)
   - api-design.md: PASS/FAIL
   - module-standards.md: PASS/FAIL
   - error-handling.md: PASS/FAIL

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/database.md

@@ -1,6 +1,6 @@
 # Database Reference
 
-> Templates and examples. Rules in `CLAUDE.md`.
+> Templates and examples. Rules in `AGENTS.md`.
 
 ---
 

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/error-handling.md

@@ -1,6 +1,6 @@
 # Error Handling Templates
 
-> Implementation code for errors and middleware. Rules are in `CLAUDE.md`.
+> Implementation code for errors and middleware. Rules are in `AGENTS.md`.
 
 ---
 

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/index.md

@@ -1,6 +1,6 @@
 # Specification Index
 
-Read `CLAUDE.md` completely. Files below retain the full OneX specifications and examples. Binding event, E2E and OpenAPI contracts apply according to their declared owner. Platform paths, service names, governance commands and platform tables refer to upstream OneX; generated backend commands are defined by its own `Makefile`.
+Read `AGENTS.md` completely. Files below retain the full OneX specifications and examples. Binding event, E2E and OpenAPI contracts apply according to their declared owner. Platform paths, service names, governance commands and platform tables refer to upstream OneX; generated backend commands are defined by its own `Makefile`.
 
 | File | Content | Priority |
 |------|---------|----------|

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/logging.md

@@ -1,6 +1,6 @@
 # Logging Reference
 
-> Templates and examples. Rules in `CLAUDE.md`.
+> Templates and examples. Rules in `AGENTS.md`.
 
 ---
 

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/mediagen-provider-onboarding-sop.md

@@ -5,7 +5,7 @@
 > Scope: `internal/platform/mediagen/infrastructure/providers/*` + admin runtime configuration plane
 > Audience: 任何需要新增 / 修改 / 排障 mediagen Provider Adapter 或在 admin 上线 Provider 的工程师
 > 状态：admin-integrated 锁定版（基于提交 `f2338a6d` → `211ed024`）
-> 设计权威：本文与 `backend/.claude/docs/identifier-contract.md`、`api-design.md`、`error-handling.md` 共同构成 mediagen 模块的技术契约。
+> 设计权威：本文与 `.codex/docs/identifier-contract.md`、`api-design.md`、`error-handling.md` 共同构成 mediagen 模块的技术契约。
 
 本文档目的：让"接入新 Provider"从一个**模糊的探索性任务**收敛为**一组可逐步勾选的工程操作**。每一步都有具体的文件路径、迁移编号、admin UI 入口、复制模板、验收门槛。**严格按照本 SOP 落地的新 Provider，零返工**。
 
@@ -888,7 +888,7 @@ Service: 构造一个虚拟 SubmitRequest (sample input + draft revision snapsho
 - `migrations/000473_add_generation_transport_retry_count.up.sql` —— transport_retry_count 列
 - `migrations/000483_extend_p_mediagen_execution_logs_phase_lane.up.sql` —— execution_log phase + lane_code + 复合索引
 - `migrations/000484_seed_ai_lane_dry_run_permission.up.sql` —— `ai_lane:rollback` + `ai_lane:dry_run` 权限种子
-- 短表速查：`backend/.claude/docs/mediagen-provider-quick-reference.md`
+- 短表速查：`.codex/docs/mediagen-provider-quick-reference.md`
 
 ---
 

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/mediagen-provider-quick-reference.md

@@ -192,4 +192,4 @@ bad config 在 Save / Publish 阶段直接拒收，前端按 `param` 字段路
 
 ---
 
-> **完整 SOP**: `backend/.claude/docs/mediagen-provider-onboarding-sop.md`
+> **完整 SOP**: `.codex/docs/mediagen-provider-onboarding-sop.md`

package/dist/resources/templates/go-backend/{.claude → .codex}/docs/module-standards.md

@@ -1,6 +1,6 @@
 # Module Structure Templates
 
-> Directory structures and decision tree. Rules are in `CLAUDE.md`.
+> Directory structures and decision tree. Rules are in `AGENTS.md`.
 
 ## File Creation Decision Tree
 

package/dist/resources/templates/go-backend/.dockerignore

@@ -1,6 +1,6 @@
 .git
 .github
-.claude
+.codex
 .husky
 .idea
 .vscode
@@ -22,7 +22,6 @@ tmp/
 .DS_Store
 
 AGENTS.md
-CLAUDE.md
 README.md
 deploy.config.json
 docs/

package/dist/resources/templates/go-backend/AGENTS.md

@@ -153,7 +153,7 @@ ANTHROPIC_API_KEY
 
 ## Code Rules Reference
 
-规范模板在 `backend/.claude/docs/` 目录中。
+规范模板在 `.codex/docs/` 目录中。
 
 ---
 ---
@@ -172,9 +172,9 @@ Before touching any code, fully understand the task and its context.
 ### 1.1 Read project documentation
 
 1. Read this file (execution flow + coding rules)
-2. Read `backend/.claude/docs/` specifications relevant to the task (api-design, module-standards, database, error-handling, etc.)
+2. Read `.codex/docs/` specifications relevant to the task (api-design, module-standards, database, error-handling, etc.)
 3. Read existing architecture docs in `docs/platform/` for affected modules
-4. Read the CLAUDE.md of each affected cmd/ app if applicable
+4. Read the AGENTS.md of each affected cmd/ app if applicable
 
 **Read the specs BEFORE designing. Do not rely on memory or assumptions about project conventions.**
 
@@ -263,7 +263,7 @@ Verdict: PROCEED / REJECT / REVISE
 
 ### 2.4 Determine design document level
 
-Classify the task and produce the corresponding design document. See `.claude/docs/architecture-template.md` for full skeleton.
+Classify the task and produce the corresponding design document. See `.codex/docs/architecture-template.md` for full skeleton.
 
 ```
 New module or major architecture change?
@@ -278,7 +278,7 @@ Otherwise?
 
 | Level | What to produce | Destination |
 |-------|----------------|-------------|
-| **A** | Complete architecture document following `.claude/docs/architecture-template.md` | Plan file → archive to `docs/platform/` |
+| **A** | Complete architecture document following `.codex/docs/architecture-template.md` | Plan file → archive to `docs/platform/` |
 | **B** | Impact scope, industry reference, schema/model/API changes, data flow, implementation waves | Plan file |
 | **C** | Root cause analysis, fix design, affected files, verification plan | Plan file |
 
@@ -286,7 +286,7 @@ Otherwise?
 
 ### 2.5 Decision Autonomy
 
-**Inherited from `CLAUDE.md` Phase 2.2.** AI MUST make standard technical decisions autonomously when industry consensus exists. NEVER ask the user to choose between options that have a clear industry-standard answer.
+**Inherited from `AGENTS.md` Phase 2.2.** AI MUST make standard technical decisions autonomously when industry consensus exists. NEVER ask the user to choose between options that have a clear industry-standard answer.
 
 Go-specific autonomous decisions (NEVER ask):
 
@@ -299,7 +299,7 @@ Go-specific autonomous decisions (NEVER ask):
 
 ### 2.6 Self-Review Gate (MANDATORY)
 
-**Inherited from `CLAUDE.md` Phase 2.6.** After completing ANY design or implementation, MUST self-review BEFORE presenting to user.
+**Inherited from `AGENTS.md` Phase 2.6.** After completing ANY design or implementation, MUST self-review BEFORE presenting to user.
 
 Go-specific self-review additions:
 
@@ -390,7 +390,7 @@ Re-validate against the FORBIDDEN Patterns table below with the actual implement
 
 ### 5.5 Automated review loop (Level A/B)
 
-**Inherited from `CLAUDE.md` Phase 5.5.** For Level A/B deliveries, dispatch review agents and iterate until zero findings BEFORE presenting to user.
+**Inherited from `AGENTS.md` Phase 5.5.** For Level A/B deliveries, dispatch review agents and iterate until zero findings BEFORE presenting to user.
 
 Go-specific review dimensions:
 
@@ -551,14 +551,14 @@ Violation of ANY rule blocks commit. No exceptions.
 | TX2 | Transaction | `middleware.WithTransaction` / `middleware.DBOrTx` | Use `database.TransactionManager.WithTransaction` — single mechanism |
 | TX3 | Transaction | Multiple transaction context keys | Single `database.ctxTxKey{}` — one mechanism, one key |
 | N1 | Enum | 管理端展示或选择使用的枚举值、标签、颜色在 registry 外重复维护 | 在 `internal/common/enums/register_xxx.go` 引用 owner 常量注册，并测试实际消费的值集合。私有实现类型和机器协议值不要求注册为管理端选项 |
-| N2 | Reference | `ReferenceID` / `reference_id` 字段用 `fmt.Sprintf` / 字符串拼接 ad-hoc 构造 | 在 owner domain 的 `reference.go` 定义 helper `XxxReferenceID(xxxID int64) string`，调用方 MUST 通过 helper 生成。See `backend/.claude/docs/identifier-contract.md` §3.2 |
+| N2 | Reference | `ReferenceID` / `reference_id` 字段用 `fmt.Sprintf` / 字符串拼接 ad-hoc 构造 | 在 owner domain 的 `reference.go` 定义 helper `XxxReferenceID(xxxID int64) string`，调用方 MUST 通过 helper 生成。See `.codex/docs/identifier-contract.md` §3.2 |
 | N3 | Reference | `ReferenceType` 字段使用字符串字面量（e.g. `"order"` / `"subscription"`） | 在 domain 的 `reference.go` 定义 `ReferenceTypeXxx` 常量，所有写入路径 MUST 引用常量 |
 | N4 | Validator | 写入 `p_credit_transactions` / `p_member_point_ledger` / `p_quota_transactions` 时绕过模块的 `ValidateTransactionFields` 直接调用 `db.Create` / `db.Save` | MUST 通过 repo 的 `Create` / `BatchCreate` 方法，repo 内部强制调用 `credit.ValidateTransactionFields`（或对应模块 validator）。禁止 Service/Handler 直接操作 `*gorm.DB` 写入凭证类表 |
 | LC1 | Locale | Domain model, DTO write path, persisted JSON map, or admin API accepts/stores region locale tags such as `zh-CN` / `en-US` as business locale keys | Internal business locale values MUST use OneX short codes validated by `internal/common/locale.IsShortCode`. External headers/imports may call `NormalizeCode` only at boundary adapters before entering domain/service writes |
 | LC2 | Locale | Duplicated supported-locale lists, locale enum metadata, or fallback locale arrays outside `internal/common/locale` / enum registry helpers | Use `commonlocale.SupportedCodes()`, `commonlocale.DefaultCode`, `commonlocale.AdminDefaultCode`, and shared enum helpers. Migrations may list historical external aliases only to repair old data |
 | LC3 | Locale | Localized text/channel JSON validation implemented with ad-hoc key checks or `map[string]string` loops that do not call the common locale validator | Route all localized-map write validation through `commonlocale.IsShortCode` or a module helper that delegates to it. Invalid locale keys fail fast with validation errors |
 
-`make lint-enums` / `backend/scripts/check-forbidden-patterns.sh` 运行管理端枚举合同测试及标识符、凭证写入静态检查。详细标识符契约见 `backend/.claude/docs/identifier-contract.md`。
+`make lint-enums` / `backend/scripts/check-forbidden-patterns.sh` 运行管理端枚举合同测试及标识符、凭证写入静态检查。详细标识符契约见 `.codex/docs/identifier-contract.md`。
 
 ---
 
@@ -832,7 +832,7 @@ After write operation completes →
 - 修改路由、请求、响应、认证或状态码时，同一变更内更新 owner path/component、Arazzo workflow 和生成制品。
 - registry 中全部 HTTP 服务启动时必须通过 Gin route 与内嵌 internal bundle 的精确集合校验。
 - partner/public 只能由 internal canonical source 投影生成，禁止直接编辑 `dist/`。
-- 详细规则和模板见 `.claude/docs/openapi-contract.md`。
+- 详细规则和模板见 `.codex/docs/openapi-contract.md`。
 
 ---
 
@@ -1064,9 +1064,9 @@ Modular Monolith 架构（Stripe/Shopify 标准）。统一平台 API 服务所
 
 **Outbox Relay**：platform-api 运行统一 Relay，处理所有域的 outbox 事件。admin-api 不调用 `relay.Start()`，admin 写入的 outbox 记录由 platform-api 的 Relay 投递。
 
-**Event runtime boundary**：源聚合投影监听器必须留在拥有该状态机的运行时；`worker` 只消费 durable public events 做下游副作用。`user.deleted` 这类部分公开的事件族必须使用精确白名单，禁止 `user.*` 这类宽泛通配。See `backend/.claude/docs/event-runtime-boundary.md`.
+**Event runtime boundary**：源聚合投影监听器必须留在拥有该状态机的运行时；`worker` 只消费 durable public events 做下游副作用。`user.deleted` 这类部分公开的事件族必须使用精确白名单，禁止 `user.*` 这类宽泛通配。See `.codex/docs/event-runtime-boundary.md`.
 
-**E2E contract tests**：凡是跨运行时、依赖 relay/worker、会改变最终用户可见真相的工作流，必须同时具备一个全链路 E2E 和一个 `ProvideRelayConfig()` 白名单回归测试。See `backend/.claude/docs/e2e-standards.md`.
+**E2E contract tests**：凡是跨运行时、依赖 relay/worker、会改变最终用户可见真相的工作流，必须同时具备一个全链路 E2E 和一个 `ProvideRelayConfig()` 白名单回归测试。See `.codex/docs/e2e-standards.md`.
 
 **内部服务间调用**：`/internal/v1/` 路由组，通过 IAM 服务账号凭证认证、已认证主体校验、路由资源策略授权保护。
 
@@ -1109,7 +1109,7 @@ Product-specific tables are owned by external product repositories and must not
 ## Commit Discipline
 
 - ONE module, ONE feature per commit
-- Pre-commit: validate against `backend/.claude/docs/` specs
+- Pre-commit: validate against `.codex/docs/` specs
 - MUST NOT commit with any CRITICAL/MUST violation
 
 ---
@@ -1129,11 +1129,11 @@ Product-specific tables are owned by external product repositories and must not
 
 | Doc | Content |
 |-----|---------|
-| `.claude/docs/architecture-template.md` | Plan mode mandatory skeleton (Level A/B/C) |
-| `backend/.claude/docs/api-design.md` | Handler/Service/DTO/VO templates, pagination |
-| `backend/.claude/docs/module-standards.md` | Tier decision, directory subdivision, VO naming |
-| `backend/.claude/docs/error-handling.md` | Error types, codes, decision table |
-| `backend/.claude/docs/database.md` | Model template, column types, migrations |
+| `.codex/docs/architecture-template.md` | Plan mode mandatory skeleton (Level A/B/C) |
+| `.codex/docs/api-design.md` | Handler/Service/DTO/VO templates, pagination |
+| `.codex/docs/module-standards.md` | Tier decision, directory subdivision, VO naming |
+| `.codex/docs/error-handling.md` | Error types, codes, decision table |
+| `.codex/docs/database.md` | Model template, column types, migrations |
 | Upstream OneX `.claude/docs/decisions.md` | Platform Architecture Decision Records; source revision in `docs/standards-provenance.json` |
 | `internal/platform/trade/order/` | Reference: Full DDD module |
 | `internal/platform/trade/module.go` | Reference: Module self-registration |

package/dist/resources/templates/go-backend/README.md

@@ -63,4 +63,8 @@ Outbox 保留 `schema_version` 不可变约束，产品生产者负责写入自
 
 `/metrics` 用于内部采集，不应通过公网网关发布。当前入口只有基础健康与指标接口；产品登录、业务路由、OneX 服务身份和授权策略必须通过真实契约接入，健康检查成功不代表业务验收完成。
 
-通用源码来源见 `docs/source-provenance.json`；入口、配置、部署和迁移的来源与调整见 `docs/runtime-provenance.json`。阅读 `CLAUDE.md` 和 `.claude/docs/` 后开发，新增模块复用现有所有者和 ProviderSet。
+通用源码来源见 `docs/source-provenance.json`；入口、配置、部署和迁移的来源与调整见 `docs/runtime-provenance.json`。阅读 `AGENTS.md` 和 `.codex/docs/` 后开发，新增模块复用现有所有者和 ProviderSet。
+
+## 可选 OneX 通知配置
+
+需要接入 OneX 时，使用 [通知接入说明](docs/onex-notifications.md)和随模板分发的 [原生 profile 示例](deployments/onex/product-onboarding.example.json)。产品填写自身身份、品牌和公开配置，私有连接交给 OneX 现有执行器；示例默认不激活、不发布、不发送。模板已分发通用 `internal/integrations/onex/v1/notification` 协议客户端与测试，由产品显式装配；不会自动生成产品事件、通知 BFF 或客户端接收流程。