Repository navigation
分步录入向导(wizard/steps)要不要成为一等作者面?假教材已删,需求本体待裁 #13342
Description
Activity
zhuangjianguo commented
on Aug 30, 2026 CollaboratorMore actions⚖️ RULED — 维护者,2026-08-30,第 5 场总监席决裁批 #6,verbatim「13342 A」
裁定:采选项 A —— 分步录入向导(wizard)成为平台一等作者面:新的一等 view 形,带步序、进度模型、「上一步过校验才能进下一步」的闸。⛔ 不采 B(tabbed 近似教材)、不采 C(defer)。
执行形状(照卡面裁后执行段 + #12183 先例,契约先行分解;本卡转为 Feature 父单/协调节点):
- spec 形先行(
domain:spec席):设计 wizard view 的一等 schema 形(步序 / 进度 / 每步校验闸的键与语义)。⚠️ 具体契约形状定稿后回决策箱过维护者一次——方向已裁(要做),形状是公开契约新面(条款②预期 yes),⛔ 不由席位定稿即派实现。设计输入:与 tabbed form view 的分界(它能分页、无闸)、ui#6237 已裁的「拆FormSectionConfig」(WizardForm 侧刻意无谓词槽——wizard 一等形若引入步级显隐,须与该裁决调和而非旁路)。 - objectui 渲染子卡随后,带
Blocked-by:指向 spec 半;⛔ 两半永不同批。 - ⛔ 最贵失败形围栏(本板已裁过):声明与实现同波次落地——绝不先声明 schema 后缓实现渲染,那会重开「AI 照教材写、校验全绿、渲染骨架」通道(docs(objectui): layout-dsl teaches only shapes the live schemas accept #13337+[finding] YAML doc fences are validated by nothing —
check:skill-examplesreads onlyts/tsxfences, and only opt-in, so every metadata example incontent/docs/**is unverifiable by construction #13086 刚关掉的正是它);文档教材只在两半都落地后回写。 - 假教材已删(PR docs(objectui): layout-dsl teaches only shapes the live schemas accept #13337)、门禁已钉([finding] YAML doc fences are validated by nothing —
check:skill-examplesreads onlyts/tsxfences, and only opt-in, so every metadata example incontent/docs/**is unverifiable by construction #13086)——现状保持到新形落地,⛔ 不提前写新教材。
席位边界(裁不派):录裁 + 转
pm:queue(domain:spec,Feature 父单);type 归分诊补(预期Feature)。同笔摘needs-user-decision。裁决入本场追认摘要表。
Generated by Claude Code
- spec 形先行(
Coordination update (domain:spec seat,
session_01PBjwYLS6BciTQW3c9xQiD2): the ruled spec-half design is DELIVERED on sub-card #13622 and staged back to the decision inbox per this card's ruling (「具体契约形状定稿后回决策箱过维护者一次」). One repricing fact for this coordination node: the proposal's re-measurement found the wizard form view already exists end-to-end (spec enum member'wizard'atview.zod.ts:2906, live WizardForm chain, the gate and progress model implemented, a real showcase author) — the ruling's direction stands, but v1 is a declaration-and-refusal TIGHTENING with zero new keys, and the future Card R (objectui half) shrinks accordingly. Next state transitions happen on #13622 (maintainer pass) → then the implementation cards are filed contract-first as ruled. This parent stays the coordination node; nothing is dispatched from it.
Generated by Claude Code
关卡(completed):本协调节点的两半均已落地——
- Card S(Wizard view v1 — declaration-and-refusal tightening of FormViewSchema type:'wizard' (Card S, ruled shape of #13622) #13704 → PR feat(spec): wizard view v1 — declaration-and-refusal tightening of FormViewSchema type:'wizard' (Card S) #13733,wizard v1 声明与拒绝收紧,Design the first-class wizard view schema shape — the ruled spec half of #13342 (proposal returns to the decision box before any implementation) #13622 裁定 D1–D8):MERGED 13:27Z(维护者词放行)。
- Card R(objectui#6985 → objectui PR fix(spec,rest,cli): validation diagnostics reach the real defect — named view-union branches +
invalid_key/invalid_elementdescent (#7025) #7042,objectui 对齐 + 消费侧 pins + metadata-admin create 种子修复):MERGED ~16:5xZ(席内复核 PASS 放行)。
wizard 需求本体按 #13622 的裁定落定:sections 即 steps、步门为默认语义、
allowSkip为导航自由、进度为派生态、步骤键家族在 wizard 上拒绝、空 wizard 拒绝。#13337/#13086 教材围栏随两半落地解除——教学卡(rich-text/wizard 编写指南类)由后续按需另立,⛔ 不在本节点上挂。假教材已删(本卡开卡时的现场),需求本体已裁并实施。
Generated by Claude Code
作者想做一个分步的录入向导——第一步填基本信息、第二步填明细、最后确认提交——平台今天没有任何一层能表达它,而文档曾经教的写法全部是平台拒收的假形。
背景
layout-dsl.mdx曾在两节教steps:分步写法(Wizard Template、Multi-Step Wizard)。#13266 实测:steps在任何一层 schema 都不存在,两节已随 PR #13337 删除/替换,门禁(#13086 的os:check-yaml)现在钉住该页只教真形。删的是假教材;需求本体(要不要有向导)从未裁过,本卡裁它。前提(带 re-check 命令)
最近的两个已声明形:tabbed form view(能分页,但无进度模型、无「上一步必须过校验才能进下一步」的闸)、flow(自动化流程,不是录入 UI)。
具体问题
分步录入向导要不要成为平台的一等作者面?
选项 × 真实代价
业务直译:A = 像 Salesforce Screen Flow / Typeform 那样的分步表单;B = 「分页可以,防跳步不行」;C = 「这个面暂时没有,别用没有的词」。
<!-- os-decision-facets -->
推荐:C(defer,记录在案;真实客户需求出现时回炉按 A 走契约先行分解);回退:B(一页文档教 tabbed 近似,零声明)。
置信缺口:本分析看不见客户/hotcrm 侧是否已有真实分步录入需求(语料未扫),也看不见 flow 引擎的产品路线图——若 flow 已计划长出录入步,A/B 都该并入它。
裁后执行段(裁后我会怎么执行,你不用管)
layout-dsl维持现状。nav:menu/global:search/global:notifications/app:launcheras "Component Placeholder" — four spec-declared PageComponentType members with no renderer #12183 先例。相关单与 PR
出处:#13266(escalation ①)、PR #13337(删假教材)、#13086/PR #13267(门禁机制)。
Generated by Claude Code