docs: publish business instruction 0.5.127
This commit is contained in:
inman
@@ -29,7 +29,7 @@ Authenticated employee manual or account-bound AgentBus input is routed through
|
||||
- Each enabled AgentBus channel owns one active non-admin employee account. Inbound work uses that account and route allowlist, persists the same account as immutable task assignee, and is returned only to that account's executable feed. A team-lead channel may additionally carry its leader's lower-priority proactive summary outbox; those rows use explicit destination/conversation routing and never become executable task traffic.
|
||||
- Each employee account has one expected ERP identity and at most one fresh browser execution worker. The extension accepts ERP identity only from exactly one `#Lable_UserName` login node and normalized full equality; missing, duplicate, blank, substring-only, or unrelated body-text matches fail closed without returning the observed identity. Concurrent fresh workers, unbound channels, or unassigned tasks also fail closed. Browser claims, active-execution checks, and confirmed FIFO are serialized per immutable task assignee, so one account cannot block or occupy another account's queue.
|
||||
- Administrators have no task read or execution model. Task lists/details, attachments, artifacts, lifecycle mutations, SSE history/live events, browser claims, plugin-result ingestion, and browser cleanup commands require a `team_lead` or `user` session matching `assigned_user_id`; the team-lead dashboard and notification outbox remain separate read projections.
|
||||
- Extension `0.5.170` is the current manually published plugin baseline, Program parser `v1.0.7` owns the new shared-child batch directive, and the five Skills plus operator instruction DOCX remain at `0.5.126`. The batch adapter enumerates and validates every matching shared-plan parent before the first write, executes in date/tid order, and stops without retry at the first blocked, failed, or uncertain result. The extension retains an idle-proof and guarded-reload message protocol, but the active control plane has no extension-release tables, ECS host mapping, OSS publication endpoint, Cloud Assistant dispatcher, or platform trigger; required migration is 023.
|
||||
- Extension `0.5.170` is the current manually published plugin baseline, Program parser `v1.0.7` owns the new shared-child batch directive, the five Skills remain at `0.5.126`, and the operator instruction DOCX is `0.5.127`. The batch adapter enumerates and validates every matching shared-plan parent before the first write, executes in date/tid order, and stops without retry at the first blocked, failed, or uncertain result. The extension retains an idle-proof and guarded-reload message protocol, but the active control plane has no extension-release tables, ECS host mapping, OSS publication endpoint, Cloud Assistant dispatcher, or platform trigger; required migration is 023.
|
||||
- Creator and manual input-turn attribution remain durable while business input stays encrypted at rest. Routine removal is reversible archive/restore. Separately confirmed force delete physically removes an authorized task regardless of lifecycle state, retains only a minimal non-content deletion audit marker, and cannot undo an ERP write that already occurred.
|
||||
- Unknown, ambiguous, unverified, or post-write-uncertain states fail closed; automatic retries must not create duplicate writes.
|
||||
- PostgreSQL is the sole required durable database/state middleware, and the production artifact provider is OSS. Redis, message queues, MongoDB, and search services are not runtime dependencies.
|
||||
|
||||
@@ -4,6 +4,7 @@ This file is the integrated default-branch snapshot. Feature tasks record progre
|
||||
|
||||
## Integrated Through
|
||||
|
||||
- Integration task `20260909-business-instruction-batch-child-7e3c1a94` synchronized operator input catalog/DOCX `0.5.127` with all 19 system routes, adding the copyable `散拼团多个新增子单` entry while keeping that route Program-only and leaving the five Skills at `0.5.126`.
|
||||
- Source commit `be17f6c` from feature task `20260908-leader-webhook-api-7c4e9a12`, integrated as merge commit `295409b`, for organization-level external Webhook delivery of privacy-bounded leader summaries, migration `023_leader_summary_webhook_delivery`, and AUTH-005's one-attempt accepted-versus-delivered boundary.
|
||||
- Source commit `6ac90f8` from feature task `20260908-shared-child-batch-create-4e7c2a91`, integrated as merge commit `0d20544`, for Program-only `shared_child_order_batch_create`, parser `v1.0.7`, migration `022_shared_child_order_batch_create`, complete pre-write target enumeration, deterministic stop-on-first-non-success execution, and extension `0.5.170`.
|
||||
- Commit `bb115a3` from integration task `20260908-remove-maintain-project-docs-requirement-6d8a31f2` removed the deleted external project-document Skill/task-registry dependency and retained repository-local worktree and project-memory gates.
|
||||
@@ -42,7 +43,7 @@ This file is the integrated default-branch snapshot. Feature tasks record progre
|
||||
|
||||
## Current Focus
|
||||
|
||||
Operate the repository's current extension `0.5.170`, Program parser `v1.0.7`, Skill/business-instruction `0.5.126`, roster normalizer `v1.4.0`, and migrations through `023_leader_summary_webhook_delivery` safely. The machine registry contains 19 routes; the external Agent remains limited to its original 18 and the two passenger-list routes plus shared-child batch creation are Program-only. Administrators manage accounts, channels, employee grants, parser routing, automation settings, and audit but never enter the task data plane. Team leads/users own normal task operations through immutable assignment; same-account work remains FIFO and single-active while distinct accounts are independent. Team leads alone receive the read-only assignee-based dashboard. Future privacy-bounded organization summaries use one protected external Webhook and a separate encrypted one-attempt outbox, not a leader AgentBus route. Database migration, extension reload, route grants, service rollout, live ERP validation, and any external Webhook canary remain separately authorized runtime work. Server-side automatic extension updating is not part of the active main line.
|
||||
Operate the repository's current extension `0.5.170`, Program parser `v1.0.7`, Skills `0.5.126`, business-instruction `0.5.127`, roster normalizer `v1.4.0`, and migrations through `023_leader_summary_webhook_delivery` safely. The machine registry and operator input catalog contain 19 routes; the external Agent remains limited to its original 18 and the two passenger-list routes plus shared-child batch creation are Program-only. Administrators manage accounts, channels, employee grants, parser routing, automation settings, and audit but never enter the task data plane. Team leads/users own normal task operations through immutable assignment; same-account work remains FIFO and single-active while distinct accounts are independent. Team leads alone receive the read-only assignee-based dashboard. Future privacy-bounded organization summaries use one protected external Webhook and a separate encrypted one-attempt outbox, not a leader AgentBus route. Database migration, extension reload, route grants, service rollout, live ERP validation, and any external Webhook canary remain separately authorized runtime work. Server-side automatic extension updating is not part of the active main line.
|
||||
|
||||
## Recently Completed
|
||||
|
||||
@@ -77,6 +78,7 @@ Operate the repository's current extension `0.5.170`, Program parser `v1.0.7`, S
|
||||
- 2026-09-08: Added Program-only shared-child batch creation across an inclusive departure-date range. Every product-matching parent is enumerated and validated before the first write; execution is ordered by date/tid, stops at the first blocked/failed/uncertain result, and never retries a write automatically. Parser `v1.0.7`, migration 022, and extension `0.5.170` are synchronized.
|
||||
- 2026-09-08: Replaced only the leader-summary AgentBus transport with an organization-level external Webhook. AUTH-005 and migration 023 retain future-only encrypted/privacy-bounded projection, mark only strict gateway success as accepted rather than delivered, and terminate rejected or uncertain attempts without automatic retry.
|
||||
- 2026-09-08: Removed the deleted external project-document Skill and task-registry requirement; repository-local Git worktree checks and `.project-docs/` remain the active collaboration and memory boundary.
|
||||
- 2026-09-09: Advanced the operator input catalog and generated DOCX to `0.5.127`, covering all 19 routes with a new copyable Program-only `散拼团多个新增子单` section while leaving Agent Prompt and Skill packages unchanged.
|
||||
|
||||
## In Progress
|
||||
|
||||
|
||||
@@ -0,0 +1,63 @@
|
||||
# Task: Update business instruction table for batch shared-child creation
|
||||
|
||||
## Identity
|
||||
|
||||
- Task ID: 20260909-business-instruction-batch-child-7e3c1a94
|
||||
- Mode: Integration
|
||||
- Branch: main
|
||||
- Worktree: /Users/inmanx/Documents/lwltAPI
|
||||
- Base commit: 75b9f2ede991c3f8d37465f80d4856f771e54051
|
||||
- Owner: codex
|
||||
- Status: Ready for push verification
|
||||
|
||||
## Scope
|
||||
|
||||
- Add the integrated Program-only `散拼团多个新增子单` route to the canonical operations input template.
|
||||
- Bump the business-input contract and DOCX delivery version without changing any Skill or external-Agent route.
|
||||
- Rebuild the versioned DOCX, synchronize the release manifest and README, visually inspect every rendered page, and place the verified current copy on the user's Desktop.
|
||||
- Commit the verified release and push `main` to `origin/main` without force after confirming the remote remains at the selected base.
|
||||
|
||||
## Worktree Safety
|
||||
|
||||
- Existing changes in this worktree: none.
|
||||
- Relevant concurrent worktree: `/Users/inmanx/Documents/lwltAPI-shared-child-batch-create-4e7c2a91`, clean and already integrated into `main`.
|
||||
- Overlap result: Clear.
|
||||
|
||||
## Constraints
|
||||
|
||||
- Preserve `shared_child_order_batch_create` as Program-only.
|
||||
- Do not add it to the Agent prompt, external-Agent directive registry, or any Skill package.
|
||||
- Keep the Markdown template as the sole editable source and generate the DOCX only through `tools/build_business_instruction_docx.py`.
|
||||
- Use bundled workspace dependencies and complete render-to-PNG inspection before delivery.
|
||||
|
||||
## Outcome
|
||||
|
||||
- Advanced the canonical operator input catalog and generated DOCX from `0.5.126`/18 items to `0.5.127`/19 items.
|
||||
- Added section 5, `散拼团多个新增子单`, with a directly copyable template and example while preserving `shared_child_order_batch_create` as Program-only and absent from the external Agent prompt, Agent/Skill registry table, and all Skill packages.
|
||||
- Synchronized the route contract constant, repository documentation, release gate, README, regression expectations, and `dist/release-manifest.json`.
|
||||
- Corrected the canonical architecture snapshot so it distinguishes the unchanged five Skills at `0.5.126` from the operator instruction DOCX at `0.5.127`.
|
||||
- Archived the former `0.5.126` DOCX and its exact release-manifest snapshot under `archive/releases/2026-09-09/`, generated `dist/老挝联泰AI指令表-0.5.127.docx`, and copied the verified artifact to the user's Desktop. The superseded Desktop copy was moved to Trash and remains recoverable.
|
||||
|
||||
## Verification
|
||||
|
||||
- Rebuilt the DOCX from `agent设计规范/templates/business-input-templates.md` with the governed builder and bundled workspace dependencies.
|
||||
- Rendered the final DOCX to 13 PNG pages with the bundled LibreOffice/Poppler stack and configured Chinese fonts; visually inspected every page with no clipping, missing glyphs, orphaned explanatory text, or broken hierarchy.
|
||||
- Parsed the DOCX package to confirm all operation headings 1 through 19, the new template/example fields, version/scope text, and absence of unresolved document tokens.
|
||||
- Verified source SHA-256 `652af8ef645ae56af2dd9990f74b8078de230cb9b87acd13c289d1f4dae0738a`, builder SHA-256 `c162884210da22e3b78368749b66f1f177df5e9fc6155f4fd9954bd516d187f1`, and DOCX SHA-256 `e1b8ae5a98d550ab0785692a01cf1c87b99e4edfaea39e4edbbab7341e585f29`; the Desktop copy is byte-identical to `dist`.
|
||||
- `node --test tools/business-input-templates.test.mjs` — 16/16 passed.
|
||||
- `node --run check:repo` — 10/10 passed.
|
||||
- `node --run check` — passed.
|
||||
- `node --run test:control-plane` — 183/183 passed.
|
||||
- `node --run test:legacy` — 278/278 passed.
|
||||
- `node --run build` — passed.
|
||||
- A fresh release-push gate reran all required checks. The initial repository-hygiene pass found only two generated `.DS_Store` files; both were moved out of the repository, after which `node --run check:repo` passed 10/10 and `node --run test:legacy` passed 278/278.
|
||||
- `git diff --check` — passed after the final project-memory edits.
|
||||
- Remote push and final remote-tip verification are pending the release commit.
|
||||
|
||||
## Follow-ups
|
||||
|
||||
- No documentation follow-up is required. Deployment, extension reload, route grants, and live ERP writes remain separate explicitly authorized runtime work.
|
||||
|
||||
## Promotion Candidates
|
||||
|
||||
- Promote the operator input catalog/DOCX `0.5.127` and its 19-item scope into the integrated current-state snapshot; no Agent/Skill behavior changes are promoted.
|
||||
@@ -15,7 +15,7 @@
|
||||
## 当前发布基线
|
||||
|
||||
- Chrome 扩展制品版本由 [发布清单](dist/release-manifest.json) 定义；运行中的浏览器版本必须通过实时握手确认，不写入静态交接文档。
|
||||
- 五个业务 Skill：`0.5.126`；运营 DOCX：`0.5.126`。
|
||||
- 五个业务 Skill：`0.5.126`；运营 DOCX：`0.5.127`。
|
||||
- Agent Prompt：`ltjt-agent-prompt-v1.8-independent-headcount-categories`。
|
||||
- 控制面确定性解析器：`ltjt-program-parser-v1.0.7`；19 项路由中三项固定为 Program-only（两项名单及散拼批量子单），其余路由由操作台逐项晋级；新增批量子单不进入外部 Agent 路由。
|
||||
- 独立团/散拼子单名单固定为 Program-only：文字用于业务定位，名单由单个 `.xls`/`.xlsx` 附件确定性规范化；附件到齐前任务保持等待。
|
||||
|
||||
@@ -8,7 +8,7 @@
|
||||
4. [运营业务 AI 输入模板总表](templates/business-input-templates.md)：业务人员可直接复制的“模板 + 示例”双段式输入目录；模板首行是业务指令，后续逐行业务字段。
|
||||
5. [业务适配模板](templates/business-adaptation-template.md)：新增业务的一页式交接模板。
|
||||
6. [AgentBus 用户回复契约](agentbus-reply-contract.md)：执行完成后的受理通知、成功回执、失败回传和文件交付边界。
|
||||
7. [确定性业务路由注册表](../control-plane/src/business-routes.ts)：手工与 AgentBus 共用的 18 项程序解析路由、兼容指令、唯一完整字段签名、必填项、类型、action、对象类型和版本的唯一机器源。
|
||||
7. [确定性业务路由注册表](../control-plane/src/business-routes.ts)：手工与 AgentBus 共用的 19 项程序解析路由、兼容指令、唯一完整字段签名、必填项、类型、action、对象类型和版本的唯一机器源。
|
||||
|
||||
第一个已真实验证的参考业务是[独立团批量下单](businesses/team_order_batch_create.md)。
|
||||
|
||||
@@ -18,7 +18,7 @@
|
||||
|
||||
- `agent-prompt.md`：云端 Agent 的业务识别、字段提取和标准 JSON 返回提示词。
|
||||
- `business-behavior-registry.md`：维护人员使用的业务行为与内部实现映射参考，不直接作为云端 Agent Prompt 内容。
|
||||
- `templates/business-input-templates.md`：当前 18 项运营输入的统一契约；每项都有相邻的模板和示例，按“最小必填 + 其余选填”区分字段。独立团信息修改和安排变更归入修改类；暂缓需求与测试删除不进入当前生产用户入口。
|
||||
- `templates/business-input-templates.md`：当前 19 项运营输入的统一契约；每项都有相邻的模板和示例，按“最小必填 + 其余选填”区分字段。散拼团多个新增子单和两项名单固定走 Program Parser，不进入外部 Agent；独立团信息修改和安排变更归入修改类，暂缓需求与测试删除不进入当前生产用户入口。
|
||||
- `skills/lwlt-newbooking/SKILL.md`：解析独立团批量/单个下单、散拼母团计划和散拼具体子单输入。
|
||||
- `skills/lwlt-updating/SKILL.md`：解析三类修改输入中的全部用户明确业务目标；插件按已验证能力自动执行或转人工复核。
|
||||
- `skills/lwlt-arrangement/SKILL.md`：解析五类新增安排和酒店离店日/房间数变更输入。
|
||||
@@ -29,7 +29,7 @@
|
||||
|
||||
## 边界
|
||||
|
||||
云端 Agent Prompt 及对应 Skill 与业务系统确定性解析器通常是并列的解析实现，均只输出解析态 operation。两项名单 route 是明确例外：固定走 Program Parser，原始 Excel 先由控制面程序规范化，不进入 AI Prompt。两类解析共享最终契约，不查询业务对象，不读取当前值，不生成内部引用，也不描述任务如何执行。控制面在任务创建时固化解析策略；后续执行层负责对象解析、候选匹配和实际操作。本目录不负责调用或操作业务系统。
|
||||
云端 Agent Prompt 及对应 Skill 与业务系统确定性解析器通常是并列的解析实现，均只输出解析态 operation。两项名单 route 和散拼团多个新增子单是明确例外，固定走 Program Parser；其中原始 Excel 先由控制面程序规范化，不进入 AI Prompt。两类解析共享最终契约，不查询业务对象，不读取当前值，不生成内部引用，也不描述任务如何执行。控制面在任务创建时固化解析策略；后续执行层负责对象解析、候选匹配和实际操作。本目录不负责调用或操作业务系统。
|
||||
|
||||
运行时 Skill 包只保留 `SKILL.md`、必要的 `agents/openai.yaml` 和按需加载的业务 references；宿主接入说明、示例和维护路线放在 `test-fixtures/` 或维护文档中。
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# 业务适配登记表
|
||||
|
||||
这是跨会话和交付的 Agent/Skill 业务入口。它回答三个问题：业务人员怎么输入、ERP 怎么执行、Skill 在哪里维护。运营统一复制入口见[运营业务 AI 输入模板总表](templates/business-input-templates.md)，AI 业务路由参考见 [business-behavior-registry.md](business-behavior-registry.md)，19 项确定性解析的指令、字段、action 和版本唯一机器源见 [`control-plane/src/business-routes.ts`](../control-plane/src/business-routes.ts)。其中下表与外部 Agent 继续覆盖原 18 项；新增的散拼批量子单只由 Program 入口接受，不加入 Agent/Skill 指令登记。该机器路由、任务级解析模式快照和组织全自动化规则对获授权员工的手工与 AgentBus 新任务全局共用，来源只负责输入和回执适配；AgentBus 渠道必须绑定一个员工平台账号，并使用该账号的业务白名单、任务归属、唯一云电脑 worker 和唯一登录节点精确 ERP 身份门禁。ERP 领取队列按不可变的任务归属账号分别保持 FIFO 与单活跃执行，不同账号互不阻塞；管理员只进入账号、渠道、解析策略、自动化设置和审计管理面，不创建、查看、修改、领取或删除业务任务。
|
||||
这是跨会话和交付的 Agent/Skill 业务入口。它回答三个问题：业务人员怎么输入、ERP 怎么执行、Skill 在哪里维护。运营统一复制入口见[运营业务 AI 输入模板总表](templates/business-input-templates.md)，其中覆盖全部 19 项系统输入；AI 业务路由参考见 [business-behavior-registry.md](business-behavior-registry.md)，19 项确定性解析的指令、字段、action 和版本唯一机器源见 [`control-plane/src/business-routes.ts`](../control-plane/src/business-routes.ts)。下表与外部 Agent 继续覆盖原 18 项；新增的散拼批量子单只由 Program 入口接受，不加入 Agent/Skill 指令登记。该机器路由、任务级解析模式快照和组织全自动化规则对获授权员工的手工与 AgentBus 新任务全局共用，来源只负责输入和回执适配；AgentBus 渠道必须绑定一个员工平台账号，并使用该账号的业务白名单、任务归属、唯一云电脑 worker 和唯一登录节点精确 ERP 身份门禁。ERP 领取队列按不可变的任务归属账号分别保持 FIFO 与单活跃执行，不同账号互不阻塞；管理员只进入账号、渠道、解析策略、自动化设置和审计管理面，不创建、查看、修改、领取或删除业务任务。
|
||||
|
||||
## 状态定义
|
||||
|
||||
@@ -20,13 +20,13 @@
|
||||
| `team_order_create` | 独立团单个下单 | [`lwlt-newbooking`](skills/lwlt-newbooking/SKILL.md) / `team_order_create` | [业务入口](businesses/team_order_create.md) | [ERP 流程](businesses/team_order_create.md) | [Skill actions](skills/lwlt-newbooking/references/actions-and-fields.md) | 已真实验证 |
|
||||
| `shared_plan_create` | 散拼团新增计划 | [`lwlt-newbooking`](skills/lwlt-newbooking/SKILL.md) / `shared_plan_create` | [业务入口](businesses/shared_plan_create.md) | [ERP 流程](businesses/shared_plan_create.md) | [Skill actions](skills/lwlt-newbooking/references/actions-and-fields.md) | 单个/批量母团已重复验证；E2E3/E2E4 均证明批量每日期具体子单、客户与 15+1，统一发布仍待批准 |
|
||||
| `shared_child_order_create` | 散拼团单个新增子单/计划 | [`lwlt-newbooking`](skills/lwlt-newbooking/SKILL.md) / `shared_child_order_create` | [业务入口](businesses/shared_child_order_create.md) | [ERP 流程](businesses/shared_child_order_create.md) | [Skill actions](skills/lwlt-newbooking/references/actions-and-fields.md) | 已重复真实创建并完成后续全生命周期；仍受统一发布门槛约束 |
|
||||
| `passenger_list_import` | 独立团/散拼子单名单导入/补充 | [`lwlt-lifecycle`](skills/lwlt-lifecycle/SKILL.md) / `passenger_list_import`（Program-only） | [统一输入模板 §5—6](templates/business-input-templates.md)；文字定位 + 单个 `.xls/.xlsx` 附件；程序在前 100 行自动定位唯一 ERP 字段表头，按精确语义从任意表头行和列顺序中只选择必需字段，并读取其下连续名单数据；身份证、年龄、源证件类型和其他普通额外列忽略且不输出 | 识别 route 后等待附件 → 程序规范化为加密 13 列 TSV，并从唯一严格`领队`备注行提取姓名/电话 → 读取 ERP 游客位 → 未确认的占用序号要求覆盖确认；确认后所有指定序号强制覆写（同值也写）→ `DaoRuDones` → 原生游客位不足时返回“名单 N 人超过 ERP 最多 M 人”且不保存 → 恢复未指定行 → 投影领队联系人 → 完整写前投影 → 父页原生保存；ERP 明确返回成功即完成，不再逐行写后回查 | 用户模板 `.xls` 已只读通过 25 行规范化及单一领队行结构核验；解析阶段不以初始 16/31 行作统一静态上限，5000 为技术上限；执行时以精确 ERP 页面实际物化游客位为准。2026-08-28 一笔散拼子单 25 行及领队联系人已持久化全等；另一次独立团 25 人只物化 16 位并在保存前安全阻断 | 名单与领队联系人真实写入已有一笔证据；`0.5.155` 起确认覆盖同值也写，`0.5.156` 起容量不足使用人数/上限业务提示并仅在技术详情保留原始 blocker；其他对象/边界继续按发布门槛分级 |
|
||||
| `passenger_list_import` | 独立团/散拼子单名单导入/补充 | [`lwlt-lifecycle`](skills/lwlt-lifecycle/SKILL.md) / `passenger_list_import`（Program-only） | [统一输入模板 §6—7](templates/business-input-templates.md)；文字定位 + 单个 `.xls/.xlsx` 附件；程序在前 100 行自动定位唯一 ERP 字段表头，按精确语义从任意表头行和列顺序中只选择必需字段，并读取其下连续名单数据；身份证、年龄、源证件类型和其他普通额外列忽略且不输出 | 识别 route 后等待附件 → 程序规范化为加密 13 列 TSV，并从唯一严格`领队`备注行提取姓名/电话 → 读取 ERP 游客位 → 未确认的占用序号要求覆盖确认；确认后所有指定序号强制覆写（同值也写）→ `DaoRuDones` → 原生游客位不足时返回“名单 N 人超过 ERP 最多 M 人”且不保存 → 恢复未指定行 → 投影领队联系人 → 完整写前投影 → 父页原生保存；ERP 明确返回成功即完成，不再逐行写后回查 | 用户模板 `.xls` 已只读通过 25 行规范化及单一领队行结构核验；解析阶段不以初始 16/31 行作统一静态上限，5000 为技术上限；执行时以精确 ERP 页面实际物化游客位为准。2026-08-28 一笔散拼子单 25 行及领队联系人已持久化全等；另一次独立团 25 人只物化 16 位并在保存前安全阻断 | 名单与领队联系人真实写入已有一笔证据；`0.5.155` 起确认覆盖同值也写，`0.5.156` 起容量不足使用人数/上限业务提示并仅在技术详情保留原始 blocker；其他对象/边界继续按发布门槛分级 |
|
||||
| `order_update_shared_plan` / `order_update_shared_child` | 散拼母团容量/散拼子单住宿说明 | [`lwlt-updating`](skills/lwlt-updating/SKILL.md) | [统一输入模板：修改](templates/business-input-templates.md) | `DoInfoSP` / `DoInfo_order`；写前读取当前值 | 母团容量、子单住宿说明通过；用户只填目标值；无年份定位日期取任务日后的下一次发生日 | Skill 全量解析；仅已验证字段自动执行，其他字段保留并转人工复核 |
|
||||
| `order_update_independent` | 独立团信息修改 | [`lwlt-updating`](skills/lwlt-updating/SKILL.md) / `order_update_independent` | [统一输入模板 §14](templates/business-input-templates.md) | `DoInfoJH`；写前读取当前值；SGL/TWN 分别映射 `frenshu0`/`frenshu1`，成人/占床儿童/不占床儿童/领队分别映射 `darenshu`/`xiaorenshu`/`ertrenshu`/`quanrenshu` | 标间数 `8→9→8` 已有明确响应和 fresh GET；无年份定位/目标日期取下一次发生日；SGL/TWN 与四类人数待新版本授权 ERP 实写复测 | Skill 全量解析；当前插件执行标间数、SGL/TWN 与四类人数，其他目标保留并转人工复核 |
|
||||
| `arrangement_guide` / `arrangement_vehicle` / `arrangement_hotel` / `arrangement_transport` / `arrangement_other` | 安排导游/用车/酒店/大交通/其他备案 | [`lwlt-arrangement`](skills/lwlt-arrangement/SKILL.md) | [统一输入模板 §7—11](templates/business-input-templates.md) | 五类 action-specific `DoInfo_*`，全类 `create|clear`；酒店另有窄 `update` | 两类团队共 10 create + 10 clear；酒店资源/房型由唯一 ERP 模糊匹配结果带入；大交通和其他/备案的结算单位组合候选按下拉顺序首条原生联动，其他/备案数量可选，省略时保留 ERP 默认值；散拼母团无子单时 ERP 禁止安排酒店并隐藏提交入口，插件在三项页面证据同时成立时提示先新增子单 | 已真实验证；非酒店 update 和酒店其他字段阻断 |
|
||||
| `arrangement_hotel` | 安排变更 | [`lwlt-arrangement`](skills/lwlt-arrangement/SKILL.md) / `arrangement_hotel` | [统一输入模板 §15](templates/business-input-templates.md) | fresh 查询 → 精确未安排或未确认酒店行 → `DoInfo_jiudian` → 双回查 | `2026-09-12/8 → 2026-09-13/9`，备注与资源保持；无年份目标离店日取下一次发生日 | 窄能力已真实验证；其他目标转人工复核 |
|
||||
| `order_cancel` / `order_restore` | 取消与恢复 | [`lwlt-lifecycle`](skills/lwlt-lifecycle/SKILL.md) | [统一输入模板 §16—17](templates/business-input-templates.md) | 列表取消或编辑页状态；列表恢复禁用 | 三类对象及母子传播共 7 次状态验证通过；无年份定位日期取任务日后的下一次发生日 | 已接入分段执行链；统一发布待批准 |
|
||||
| `confirmation_export` | 导出团队文件 | [`lwlt-confirmation`](skills/lwlt-confirmation/SKILL.md) / `confirmation_export` | [统一输入模板 §18](templates/business-input-templates.md)；`游客名单`=独立团/散拼具体子单，`整团游客信息`=散拼母团 | 唯一解析业务对象后取得 ERP 文件源内容 + SHA-256；游客文件按 kind 分流：独立团/子单 `orders_Visitor.asp?did&tid`，散拼母团整团游客 `orders_Visitor.asp?tid`；整团类型必须单独导出且不得携带子单 did。游客源保留原始 `.xls` 归档并生成真实 `.xlsx` 供移动端/AgentBus；其余类型转 PDF，失败回退源文件 | 独立团/具体子单 ERP 源读取已有 40/40 证据；散拼母团 tid-only 源有历史真实只读证据，本次已接入严格 Program/Schema/validator/插件分流，仍待新版运行态只读复测；后台附件、XLSX/PDF 转换、鉴权下载和 OSS provider 已接入 | 已接入；母团整团游客新分支待授权运行态只读复测，外发仍延后 |
|
||||
| `order_update_independent` | 独立团信息修改 | [`lwlt-updating`](skills/lwlt-updating/SKILL.md) / `order_update_independent` | [统一输入模板 §15](templates/business-input-templates.md) | `DoInfoJH`；写前读取当前值；SGL/TWN 分别映射 `frenshu0`/`frenshu1`，成人/占床儿童/不占床儿童/领队分别映射 `darenshu`/`xiaorenshu`/`ertrenshu`/`quanrenshu` | 标间数 `8→9→8` 已有明确响应和 fresh GET；无年份定位/目标日期取下一次发生日；SGL/TWN 与四类人数待新版本授权 ERP 实写复测 | Skill 全量解析；当前插件执行标间数、SGL/TWN 与四类人数，其他目标保留并转人工复核 |
|
||||
| `arrangement_guide` / `arrangement_vehicle` / `arrangement_hotel` / `arrangement_transport` / `arrangement_other` | 安排导游/用车/酒店/大交通/其他备案 | [`lwlt-arrangement`](skills/lwlt-arrangement/SKILL.md) | [统一输入模板 §8—12](templates/business-input-templates.md) | 五类 action-specific `DoInfo_*`，全类 `create|clear`；酒店另有窄 `update` | 两类团队共 10 create + 10 clear；酒店资源/房型由唯一 ERP 模糊匹配结果带入；大交通和其他/备案的结算单位组合候选按下拉顺序首条原生联动，其他/备案数量可选，省略时保留 ERP 默认值；散拼母团无子单时 ERP 禁止安排酒店并隐藏提交入口，插件在三项页面证据同时成立时提示先新增子单 | 已真实验证；非酒店 update 和酒店其他字段阻断 |
|
||||
| `arrangement_hotel` | 安排变更 | [`lwlt-arrangement`](skills/lwlt-arrangement/SKILL.md) / `arrangement_hotel` | [统一输入模板 §16](templates/business-input-templates.md) | fresh 查询 → 精确未安排或未确认酒店行 → `DoInfo_jiudian` → 双回查 | `2026-09-12/8 → 2026-09-13/9`，备注与资源保持；无年份目标离店日取下一次发生日 | 窄能力已真实验证；其他目标转人工复核 |
|
||||
| `order_cancel` / `order_restore` | 取消与恢复 | [`lwlt-lifecycle`](skills/lwlt-lifecycle/SKILL.md) | [统一输入模板 §17—18](templates/business-input-templates.md) | 列表取消或编辑页状态；列表恢复禁用 | 三类对象及母子传播共 7 次状态验证通过；无年份定位日期取任务日后的下一次发生日 | 已接入分段执行链；统一发布待批准 |
|
||||
| `confirmation_export` | 导出团队文件 | [`lwlt-confirmation`](skills/lwlt-confirmation/SKILL.md) / `confirmation_export` | [统一输入模板 §19](templates/business-input-templates.md)；`游客名单`=独立团/散拼具体子单，`整团游客信息`=散拼母团 | 唯一解析业务对象后取得 ERP 文件源内容 + SHA-256；游客文件按 kind 分流：独立团/子单 `orders_Visitor.asp?did&tid`，散拼母团整团游客 `orders_Visitor.asp?tid`；整团类型必须单独导出且不得携带子单 did。游客源保留原始 `.xls` 归档并生成真实 `.xlsx` 供移动端/AgentBus；其余类型转 PDF，失败回退源文件 | 独立团/具体子单 ERP 源读取已有 40/40 证据；散拼母团 tid-only 源有历史真实只读证据，本次已接入严格 Program/Schema/validator/插件分流，仍待新版运行态只读复测；后台附件、XLSX/PDF 转换、鉴权下载和 OSS provider 已接入 | 已接入；母团整团游客新分支待授权运行态只读复测，外发仍延后 |
|
||||
|
||||
测试对象的 `order_delete` 回收能力仍保留在 Schema、插件和生命周期测试夹具中，但不属于生产运营业务，不登记为用户输入入口。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
这是业务行为名称与内部 Skill 的参考映射表。业务人员通常把业务行为放在第一行，方便 Agent 快速定位；这不是必须严格遵守的命令格式，也不要求业务人员知道 `lwlt-newbooking`、`lwlt-updating`、`lwlt-arrangement` 或 `lwlt-confirmation` 这些内部 Skill 名称。
|
||||
|
||||
运营可直接复制的标准输入见[运营业务 AI 输入模板总表](templates/business-input-templates.md)。业务的完整三项交付（用户输入模板与示例、ERP 操作流程、Skill 适配）见 [业务适配登记表](business-adaptation-registry.md)；本表只负责路由，不替代业务适配包。
|
||||
运营可直接复制的 19 项系统输入见[运营业务 AI 输入模板总表](templates/business-input-templates.md)。其中`散拼团多个新增子单`固定走 Program Parser，不进入本表或外部 Agent；其余业务的完整三项交付（用户输入模板与示例、ERP 操作流程、Skill 适配）见 [业务适配登记表](business-adaptation-registry.md)。本表只负责 Agent/Skill 路由，不替代业务适配包。
|
||||
|
||||
## 识别原则
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
# 运营业务 AI 输入模板总表
|
||||
|
||||
交付版本：0.5.126
|
||||
适用范围：当前 18 项运营业务输入；执行能力以生命周期发布门槛为准。
|
||||
交付版本：0.5.127
|
||||
适用范围：当前 19 项运营业务输入；执行能力以生命周期发布门槛为准。
|
||||
|
||||
本文件用于向系统提交 ERP 业务需求。复制对应模板填写；示例只供参考，不要直接用于生产业务。
|
||||
|
||||
@@ -15,6 +15,7 @@
|
||||
6. 人数可写 `15+1`；用房可写 `8标1单`。
|
||||
7. 客户、产品、导游、酒店和供应商只填写名称或搜索关键词；需要唯一匹配时，信息不足会要求补充。
|
||||
8. 名单业务必须随文字发送一份 `.xls` 或 `.xlsx` 附件；附件到齐前不会解析或执行，且只走程序解析，不走 AI。
|
||||
9. `散拼团多个新增子单`固定走程序解析，不走 AI；系统逐日查找日期范围内所有产品匹配的散拼母团，再为每个母团创建一个相同子单。
|
||||
|
||||
字段统一写`预订客户`；历史写法`预定客户`仍可识别。
|
||||
|
||||
@@ -124,6 +125,31 @@
|
||||
人数：15+1
|
||||
```
|
||||
|
||||
### 5. 散拼团多个新增子单
|
||||
|
||||
#### 模板
|
||||
|
||||
```text
|
||||
散拼团多个新增子单
|
||||
预订客户（必填）：<具体子单客户名称或唯一搜索关键词>
|
||||
出发日期（必填）：<YYYY-MM-DD到YYYY-MM-DD>
|
||||
产品名称（必填）：<散拼母团产品名称或唯一搜索关键词>
|
||||
领队（选填）：<领队姓名或唯一搜索关键词>
|
||||
人数（必填）：<每个子单使用的x+x人数格式>
|
||||
特殊要求（选填）：<每个子单使用的其他业务要求>
|
||||
```
|
||||
|
||||
#### 示例
|
||||
|
||||
```text
|
||||
散拼团多个新增子单
|
||||
预订客户：广东衡阳
|
||||
出发日期：11-01到11-30
|
||||
产品名称：广东衡阳6D
|
||||
领队：张三
|
||||
人数：15+1
|
||||
```
|
||||
|
||||
## 三、游客名单
|
||||
|
||||
名单只通过一份 `.xls` 或 `.xlsx` 附件提交，不再粘贴到文字输入框。系统识别名单业务后会等待附件，附件到齐后只走程序解析。
|
||||
@@ -132,7 +158,7 @@
|
||||
|
||||
若游客是领队，在该行`备注`只填`领队`，并确保同一行`姓名`和`电话`已填写；一份名单最多一位。系统会把这两个值同步到 ERP `联系人/领队人`和`电话`。其他备注不触发联系人写入；没有领队标记时保留 ERP 原信息。正文里的`领队`仍只是选填的查单关键词。
|
||||
|
||||
### 5. 导入独立团名单
|
||||
### 6. 导入独立团名单
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -159,7 +185,7 @@
|
||||
|
||||
示例同时附一份名单工作簿。
|
||||
|
||||
### 6. 导入散拼子单名单
|
||||
### 7. 导入散拼子单名单
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -190,7 +216,7 @@
|
||||
|
||||
以下操作只新增团队安排，不维护客户、导游、酒店或供应商资料。
|
||||
|
||||
### 7. 安排导游
|
||||
### 8. 安排导游
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -210,7 +236,7 @@
|
||||
备注：首日机场接团
|
||||
```
|
||||
|
||||
### 8. 安排用车
|
||||
### 9. 安排用车
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -233,7 +259,7 @@
|
||||
数量：1
|
||||
```
|
||||
|
||||
### 9. 安排酒店
|
||||
### 10. 安排酒店
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -260,7 +286,7 @@
|
||||
|
||||
酒店搜索可填写酒店名，也可包含房型关键词；离店日期必须晚于入住日期。
|
||||
|
||||
### 10. 安排大交通
|
||||
### 11. 安排大交通
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -283,7 +309,7 @@
|
||||
交通日期：11-03
|
||||
```
|
||||
|
||||
### 11. 安排其他/备案
|
||||
### 12. 安排其他/备案
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -312,7 +338,7 @@
|
||||
|
||||
## 五、修改
|
||||
|
||||
### 12. 修改散拼母团计划收客数
|
||||
### 13. 修改散拼母团计划收客数
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -335,7 +361,7 @@
|
||||
目标计划收客数：30
|
||||
```
|
||||
|
||||
### 13. 追加散拼子单订房说明
|
||||
### 14. 追加散拼子单订房说明
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -360,7 +386,7 @@
|
||||
追加内容：领队单住
|
||||
```
|
||||
|
||||
### 14. 独立团信息修改
|
||||
### 15. 独立团信息修改
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -388,7 +414,7 @@
|
||||
|
||||
只填写需要修改的目标。人数中未出现的类别保持原值；需要清零时单独写明，例如`婴儿改为0`。
|
||||
|
||||
### 15. 安排变更
|
||||
### 16. 安排变更
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -413,7 +439,7 @@
|
||||
|
||||
## 六、取消与恢复
|
||||
|
||||
### 16. 取消订单
|
||||
### 17. 取消订单
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -435,7 +461,7 @@
|
||||
产品名称：老挝好时光
|
||||
```
|
||||
|
||||
### 17. 恢复订单
|
||||
### 18. 恢复订单
|
||||
|
||||
#### 模板
|
||||
|
||||
@@ -464,7 +490,7 @@
|
||||
|
||||
## 七、导出团队文件
|
||||
|
||||
### 18. 导出团队文件
|
||||
### 19. 导出团队文件
|
||||
|
||||
#### 模板
|
||||
|
||||
|
||||
@@ -5,14 +5,15 @@
|
||||
- Chrome 插件：`0.5.170`
|
||||
- Agent Prompt：`ltjt-agent-prompt-v1.8-independent-headcount-categories`
|
||||
- 生命周期契约：`ltjt-lifecycle-v2.9-roster-leader-contact-2026-08`
|
||||
- 五个 Skill：`0.5.126`；运营 DOCX：`0.5.126`
|
||||
- 五个 Skill：`0.5.126`；运营 DOCX：`0.5.127`
|
||||
- 发布状态：核心窄能力已有真实证据；一笔名单附件 Program-only 任务已把 25 行及唯一领队联系人正确保存到 ERP，后续只读逐字段核验全等。两种写后逐行读取方式都曾在真实成功写入后产生假阴性；名单在全部写前门禁通过后，以父表单 ERP 明确成功响应作为终结证据，不再执行写后逐行回查或自动名单对账。`0.5.155` 规定确认覆盖的指定序号同值也写；`0.5.156` 把原生游客位不足统一映射为包含名单人数和 ERP 实际上限的业务提示，原技术 blocker 仅留技术详情。`0.5.157` 新增散拼母团“整团游客信息”的 `shared_plan + visitor-list + tid-only` 窄分支，静态契约与回归已通过，仍待授权后的新版运行态只读复测。`0.5.158` 把正式控制面 `https://lwlt.nianxx.cn` 同步加入 Popup、后台、Manifest 权限和 content script 精确白名单；其他 HTTPS origin 仍保持阻断。`0.5.159` 修复 MV3 后台恢复被中断后持久化 `running` 永久阻断插件派发的问题：仅在内存恢复 Promise 已不存在时收敛为 `interrupted`，真实活动恢复仍保持阻断，下一次成功只读保活把状态归零为 `idle`。`0.5.160` 为独立团单个下单写前漂移增加仅字段名诊断，并把数字后缀动态应收字段纳入保护。`0.5.161` 等待客户、跟单人和销售人原生 lookup 数据就绪后才开始单团预检；生产反馈证明仅检查 lookup 数据仍不足。`0.5.162` 进一步要求页面 jQuery Ajax 在预检前归零，并在 `GetProduct` 后等待原生 `ajaxStop` 再应用最终业务字段。`0.5.163` 按生产操作方明确要求恢复 `0.5.156` 的实际校验范围：核心订单字段继续写前阻断，带编号的动态 `ys_*` 应收行不再纳入保护哈希，允许 ERP 原生回调在预检后调整这些字段。`0.5.164` 新增平台账号、AgentBus 渠道、唯一云电脑 worker 与 ERP 登录身份四方一致门禁；旧未绑定渠道和历史未归属 AgentBus 任务默认不执行。`0.5.165` 让散拼新增计划和独立团批量下单在本地候选未命中时先使用表单原生非空产品检索，实测两类表单均能由完整关键词唯一返回目标产品；本轮未勾选或保存，自动选择与写入仍由原门禁保护。新增独立团房型/人数映射仍待实写；未验证宽能力继续失败关闭。
|
||||
|
||||
- `0.5.166` 在散拼母团列表入口加入立即检查、100ms 条件轮询和 15 秒总超时；每次探测都重新取得当前主 iframe document，按钮一旦可用便立即继续。该等待只发生在点击前，不固定拖慢快速页面，也不触发业务写入重试。
|
||||
- `0.5.167` 保留插件侧的空闲证明和受控重载安全协议，并继续包含 `0.5.166` 的散拼入口自适应等待。中央服务私有 OSS/ECS 云助手编排及迁移 019 已按用户决定从主线撤回，因此这些插件更新消息在当前主线没有服务端触发方，属于休眠能力；插件仍按现有人工发布/加载流程使用。
|
||||
- `0.5.168` 将 ERP 身份门禁从整页子串搜索收紧为唯一 `#Lable_UserName` 登录节点的规范化精确全等；缺失、重复、空白、子串或其他页面文字命中均不再让云电脑进入可执行状态，观察到的账号文本不离开扩展。
|
||||
- `0.5.170` 保留全部执行门禁，并新增 Program-only 散拼批量子单的“完整只读枚举后逐单执行、首错停止、不自动重试”门禁；ERP 写入不确定后的人工只读核验责任仍明确绑定到任务归属账号，管理员仍完全不进入任务数据面。
|
||||
- 名单工作簿 normalizer `v1.4.0` 与业务输入/Skill `0.5.126` 改为只选择 12 个必需源字段；身份证、年龄、源证件类型及其他普通额外列不参与行识别、字段校验或 canonical 输出。必需字段完整性、宏/外链、全局超链接和外部公式等安全门槛保持失败关闭。
|
||||
- 运营输入/DOCX `0.5.127` 补齐第 19 项`散拼团多个新增子单`的可复制模板与示例；该入口仍固定为 Program-only，不进入 Agent Prompt 或 Skill。
|
||||
- 名单工作簿 normalizer `v1.4.0`、Skill `0.5.126` 与业务输入 `0.5.127` 继续只选择 12 个必需源字段；身份证、年龄、源证件类型及其他普通额外列不参与行识别、字段校验或 canonical 输出。必需字段完整性、宏/外链、全局超链接和外部公式等安全门槛保持失败关闭。
|
||||
|
||||
运行中的浏览器版本必须实时握手确认。当前制品文件名和 SHA-256 只看 [`../../../dist/release-manifest.json`](../../../dist/release-manifest.json)，不从历史日志推断。
|
||||
|
||||
|
||||
6
archive/releases/2026-09-09/README.md
Normal file
6
archive/releases/2026-09-09/README.md
Normal file
@@ -0,0 +1,6 @@
|
||||
# 2026-09-09 发布归档
|
||||
|
||||
本目录只保存被新版本替代的历史发布物，不定义当前运行规则。当前制品文件名和 SHA-256 只以根目录 [`../../../dist/release-manifest.json`](../../../dist/release-manifest.json) 为准。
|
||||
|
||||
- `release-manifest-0.5.170-skills-0.5.126-docx-0.5.126.json`：补齐散拼团多个新增子单运营模板前的历史清单快照。
|
||||
- `老挝联泰AI指令表-0.5.126.docx`：被 `0.5.127` 的 19 项完整运营输入表替代；旧版缺少`散拼团多个新增子单`。
|
||||
@@ -0,0 +1,69 @@
|
||||
{
|
||||
"manifest_version": 1,
|
||||
"generated_on": "2026-09-08",
|
||||
"baselines": {
|
||||
"chrome_extension": "0.5.170",
|
||||
"skills": "0.5.126",
|
||||
"business_instruction_docx": "0.5.126",
|
||||
"agent_prompt": "ltjt-agent-prompt-v1.8-independent-headcount-categories"
|
||||
},
|
||||
"artifacts": [
|
||||
{
|
||||
"kind": "chrome_extension",
|
||||
"version": "0.5.170",
|
||||
"path": "dist/ltjt-order-assistant-0.5.170.zip",
|
||||
"source": "chrome-extension/ltjt-order-assistant",
|
||||
"sha256": "c041d13f468f46f1130668ae67701342b0dd920c5be20c5b47b97732384f48d8"
|
||||
},
|
||||
{
|
||||
"kind": "skill",
|
||||
"name": "lwlt-arrangement",
|
||||
"version": "0.5.126",
|
||||
"path": "dist/lwlt-arrangement-0.5.126.skill",
|
||||
"source": "agent设计规范/skills/lwlt-arrangement",
|
||||
"sha256": "83770befe3a8e4048eacaeacb567c5139bf8a0b3a49f2b1513c26383422f2a9c"
|
||||
},
|
||||
{
|
||||
"kind": "skill",
|
||||
"name": "lwlt-confirmation",
|
||||
"version": "0.5.126",
|
||||
"path": "dist/lwlt-confirmation-0.5.126.skill",
|
||||
"source": "agent设计规范/skills/lwlt-confirmation",
|
||||
"sha256": "543507ed8b68c183d2df6722061b0e927ebb728de4bf254d15f83311c9264018"
|
||||
},
|
||||
{
|
||||
"kind": "skill",
|
||||
"name": "lwlt-lifecycle",
|
||||
"version": "0.5.126",
|
||||
"path": "dist/lwlt-lifecycle-0.5.126.skill",
|
||||
"source": "agent设计规范/skills/lwlt-lifecycle",
|
||||
"sha256": "fff3879d9a4143c34ae51e091b91411e55382ad3f5d77c99d6202a005b1ddbd9"
|
||||
},
|
||||
{
|
||||
"kind": "skill",
|
||||
"name": "lwlt-newbooking",
|
||||
"version": "0.5.126",
|
||||
"path": "dist/lwlt-newbooking-0.5.126.skill",
|
||||
"source": "agent设计规范/skills/lwlt-newbooking",
|
||||
"sha256": "5eb6a7bf5649a0fcee3fbee488a124e1b1d018a642a3a49ebb5439ccf20ccc2f"
|
||||
},
|
||||
{
|
||||
"kind": "skill",
|
||||
"name": "lwlt-updating",
|
||||
"version": "0.5.126",
|
||||
"path": "dist/lwlt-updating-0.5.126.skill",
|
||||
"source": "agent设计规范/skills/lwlt-updating",
|
||||
"sha256": "3bd665207649cbb8e0e5ebb012c916720201fe160eea62bccdf1c3a1f0275d1d"
|
||||
},
|
||||
{
|
||||
"kind": "business_instruction_docx",
|
||||
"version": "0.5.126",
|
||||
"path": "dist/老挝联泰AI指令表-0.5.126.docx",
|
||||
"source": "agent设计规范/templates/business-input-templates.md",
|
||||
"builder": "tools/build_business_instruction_docx.py",
|
||||
"sha256": "052611d9b700afe66b02a9b3e3b456fc245ac46541d338980f2fa4ff2e41de14",
|
||||
"source_sha256": "3ea8efd5174c0d4ab59972fb30fac2f8c6dfe7308f4e3fdb6e5b5e7c9c76258b",
|
||||
"builder_sha256": "c162884210da22e3b78368749b66f1f177df5e9fc6155f4fd9954bd516d187f1"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -76,7 +76,7 @@ export function effectiveParserModeForRoute(route: BusinessRouteDefinition, conf
|
||||
}
|
||||
|
||||
const PROGRAM_VERSION = 'ltjt-program-parser-v1.0.7';
|
||||
export const BUSINESS_INPUT_CONTRACT_VERSION = 'business-input-templates-0.5.126';
|
||||
export const BUSINESS_INPUT_CONTRACT_VERSION = 'business-input-templates-0.5.127';
|
||||
|
||||
const lookupFields = ({ customerRequired = true } = {}): ProgramFieldDefinition[] => [
|
||||
{ key: 'order_no', label: '单号', aliases: ['团号', '订单号'], kind: 'text' },
|
||||
|
||||
@@ -170,11 +170,10 @@ test('machine routes stay synchronized with their declared Program or Agent boun
|
||||
for (const route of BUSINESS_ROUTES) {
|
||||
const directivePattern = new RegExp(route.directive.replace(/[.*+?^${}()|[\]\\]/g, '\\$&'));
|
||||
const actionPattern = new RegExp(route.action.replace(/[.*+?^${}()|[\]\\]/g, '\\$&'));
|
||||
assert.match(template, directivePattern, route.routeId);
|
||||
if (route.routeId === 'shared_child_order_batch_create') {
|
||||
assert.doesNotMatch(template, directivePattern, 'Program-only batch route must not be added to the Agent/operator template');
|
||||
assert.doesNotMatch(registry, actionPattern, 'Program-only batch route must not be added to the Agent adaptation registry');
|
||||
} else {
|
||||
assert.match(template, directivePattern, route.routeId);
|
||||
assert.match(registry, actionPattern, route.routeId);
|
||||
}
|
||||
assert.match(`${initialMigration}\n${batchMigration}`, new RegExp(`'${route.routeId}'`), route.routeId);
|
||||
|
||||
12
dist/release-manifest.json
vendored
12
dist/release-manifest.json
vendored
@@ -1,10 +1,10 @@
|
||||
{
|
||||
"manifest_version": 1,
|
||||
"generated_on": "2026-09-08",
|
||||
"generated_on": "2026-09-09",
|
||||
"baselines": {
|
||||
"chrome_extension": "0.5.170",
|
||||
"skills": "0.5.126",
|
||||
"business_instruction_docx": "0.5.126",
|
||||
"business_instruction_docx": "0.5.127",
|
||||
"agent_prompt": "ltjt-agent-prompt-v1.8-independent-headcount-categories"
|
||||
},
|
||||
"artifacts": [
|
||||
@@ -57,12 +57,12 @@
|
||||
},
|
||||
{
|
||||
"kind": "business_instruction_docx",
|
||||
"version": "0.5.126",
|
||||
"path": "dist/老挝联泰AI指令表-0.5.126.docx",
|
||||
"version": "0.5.127",
|
||||
"path": "dist/老挝联泰AI指令表-0.5.127.docx",
|
||||
"source": "agent设计规范/templates/business-input-templates.md",
|
||||
"builder": "tools/build_business_instruction_docx.py",
|
||||
"sha256": "052611d9b700afe66b02a9b3e3b456fc245ac46541d338980f2fa4ff2e41de14",
|
||||
"source_sha256": "3ea8efd5174c0d4ab59972fb30fac2f8c6dfe7308f4e3fdb6e5b5e7c9c76258b",
|
||||
"sha256": "e1b8ae5a98d550ab0785692a01cf1c87b99e4edfaea39e4edbbab7341e585f29",
|
||||
"source_sha256": "652af8ef645ae56af2dd9990f74b8078de230cb9b87acd13c289d1f4dae0738a",
|
||||
"builder_sha256": "c162884210da22e3b78368749b66f1f177df5e9fc6155f4fd9954bd516d187f1"
|
||||
}
|
||||
]
|
||||
|
||||
BIN
dist/老挝联泰AI指令表-0.5.127.docx
vendored
Normal file
BIN
dist/老挝联泰AI指令表-0.5.127.docx
vendored
Normal file
Binary file not shown.
@@ -69,12 +69,18 @@ const deferredDirectives = [
|
||||
'团队文件上传'
|
||||
];
|
||||
|
||||
const allDirectives = [
|
||||
const agentDirectives = [
|
||||
...executableDirectives.slice(0, 13),
|
||||
...narrowModificationDirectives,
|
||||
...executableDirectives.slice(13)
|
||||
];
|
||||
|
||||
const allDirectives = [
|
||||
...agentDirectives.slice(0, 4),
|
||||
'散拼团多个新增子单',
|
||||
...agentDirectives.slice(4)
|
||||
];
|
||||
|
||||
const skillContracts = {
|
||||
'agent设计规范/skills/lwlt-newbooking/references/input-contract.md': [
|
||||
'独立团单个下单',
|
||||
@@ -116,6 +122,7 @@ const minimumLabels = {
|
||||
独立团批量下单: ['发团日期', '预订客户', '产品搜索', '预估人数', '用房数量', '发团周期'],
|
||||
散拼团新增计划: ['发团日期', '产品搜索', '计划收客数', '用房数量'],
|
||||
散拼团单个新增子单: ['预订客户', '出发日期', '人数'],
|
||||
散拼团多个新增子单: ['预订客户', '出发日期', '产品名称', '人数'],
|
||||
导入独立团名单: ['预订客户', '出发日期'],
|
||||
导入散拼子单名单: ['预订客户', '出发日期'],
|
||||
安排导游: ['团号', '导游搜索'],
|
||||
@@ -178,10 +185,10 @@ const assertTwoBlockContract = (document, directives, source) => {
|
||||
}
|
||||
};
|
||||
|
||||
test('catalog has exactly 18 ordered operations with adjacent template and example blocks', () => {
|
||||
test('catalog has exactly 19 ordered operations with adjacent template and example blocks', () => {
|
||||
assert.deepEqual(
|
||||
operationSections.map((section) => section.number),
|
||||
Array.from({ length: 18 }, (_, index) => index + 1)
|
||||
Array.from({ length: 19 }, (_, index) => index + 1)
|
||||
);
|
||||
assert.deepEqual(operationSections.map((section) => section.directive), allDirectives);
|
||||
|
||||
@@ -348,8 +355,8 @@ test('user templates never request ERP internal identifiers and use canonical cu
|
||||
}
|
||||
});
|
||||
|
||||
test('all current directives are routed to their Skill contract in the same two-block format', () => {
|
||||
for (const directive of allDirectives) {
|
||||
test('all Agent directives are routed to their Skill contract in the same two-block format', () => {
|
||||
for (const directive of agentDirectives) {
|
||||
assert.ok(registry.includes(`\`${directive}\``), `registry missing ${directive}`);
|
||||
}
|
||||
|
||||
@@ -358,6 +365,16 @@ test('all current directives are routed to their Skill contract in the same two-
|
||||
}
|
||||
});
|
||||
|
||||
test('shared-child batch stays Program-only while remaining copyable from the operator catalog', () => {
|
||||
const directive = '散拼团多个新增子单';
|
||||
const section = sectionByDirective.get(directive);
|
||||
assert.ok(section, `${directive}: missing operator template`);
|
||||
assert.match(catalog, /`散拼团多个新增子单`固定走程序解析，不走 AI/);
|
||||
assert.doesNotMatch(registry, /^\|[^\n]*`散拼团多个新增子单`[^\n]*\|$/m);
|
||||
assert.equal(skillRuntimeText.includes('shared_child_order_batch_create'), false);
|
||||
assert.equal(mainPrompt.includes('shared_child_order_batch_create'), false);
|
||||
});
|
||||
|
||||
test('the four detailed business pages use adjacent template and example blocks', () => {
|
||||
for (const [relativePath, directive] of Object.entries(businessPages)) {
|
||||
const document = read(relativePath);
|
||||
@@ -481,7 +498,7 @@ test('independent-order updates preserve broad parser targets while arrangement
|
||||
assert.doesNotMatch(catalog, /需求登记：/);
|
||||
});
|
||||
|
||||
test('deferred items 19 to 21 are absent from current user and Skill input contracts', () => {
|
||||
test('deferred items 20 to 22 are absent from current user and Skill input contracts', () => {
|
||||
const currentInputSurface = [
|
||||
catalog,
|
||||
...Object.keys(skillContracts).map((relativePath) => read(relativePath))
|
||||
@@ -491,7 +508,7 @@ test('deferred items 19 to 21 are absent from current user and Skill input contr
|
||||
assert.doesNotMatch(currentInputSurface, new RegExp(directive));
|
||||
}
|
||||
|
||||
assert.doesNotMatch(catalog, /^### (?:19|20|21)\./m);
|
||||
assert.doesNotMatch(catalog, /^### (?:20|21|22)\./m);
|
||||
});
|
||||
|
||||
test('new business adaptation template enforces the two-block writing convention', () => {
|
||||
|
||||
@@ -304,8 +304,9 @@ test('single-source and generated-output boundaries remain explicit', async () =
|
||||
const diagnoseServer = await readFile(path.join(ROOT, 'infra/diagnose-server.sh'), 'utf8');
|
||||
const gitignore = await readFile(path.join(ROOT, '.gitignore'), 'utf8');
|
||||
|
||||
assert.match(template, /^交付版本：0\.5\.126\s*$/mu);
|
||||
assert.match(template, /^适用范围：当前 18 项运营业务输入；执行能力以生命周期发布门槛为准。\s*$/mu);
|
||||
assert.match(template, /^交付版本：0\.5\.127\s*$/mu);
|
||||
assert.match(template, /^适用范围：当前 19 项运营业务输入；执行能力以生命周期发布门槛为准。\s*$/mu);
|
||||
assert.match(template, /^### 5\. 散拼团多个新增子单\s*$/mu);
|
||||
assert.doesNotMatch(template, /^事实基线：/mu);
|
||||
assert.equal(tsconfig.compilerOptions.outDir, '.build');
|
||||
assert.match(packageJson.scripts.start, /\.build\/control-plane/u);
|
||||
|
||||
Reference in New Issue
Block a user