133 lines
7.3 KiB
HTML
133 lines
7.3 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="zh-CN">
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<title>Day 2 - 任务规则中心联调</title>
|
||
<link rel="stylesheet" href="./styles.css">
|
||
</head>
|
||
<body>
|
||
<div class="shell">
|
||
<div class="topbar">
|
||
<a class="brand" href="./index.html"><span class="brand-mark">D2</span><span>Day 2 View</span></a>
|
||
<div class="quick-links">
|
||
<a class="pill" href="./index.html">返回总览</a>
|
||
<a class="pill" href="../agent%20week%20plan/day_2_rule_center_integration.md">周计划原文</a>
|
||
<a class="pill" href="../agent%20week%20plan/day_2_rule_center_integration.md">合并文档原文</a>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="day-nav">
|
||
<a class="pill" href="./day-1.html">Day 1</a>
|
||
<a class="pill active" href="./day-2.html">Day 2</a>
|
||
<a class="pill" href="./day-3.html">Day 3</a>
|
||
<a class="pill" href="./day-4.html">Day 4</a>
|
||
<a class="pill" href="./day-5.html">Day 5</a>
|
||
<a class="pill" href="./day-6.html">Day 6</a>
|
||
<a class="pill" href="./day-7.html">Day 7</a>
|
||
</div>
|
||
|
||
<section class="hero">
|
||
<div class="hero-badge">Integration</div>
|
||
<h1>Day 2 任务规则中心联调</h1>
|
||
<p>Day 2 的核心不是“把页面做漂亮”，而是让规则、技能、MCP、任务这四类资产第一次脱离本地假数据，真正连到 Day 1 的数据库和 API。最关键的能力是 Markdown、版本、审核和上线约束闭环。</p>
|
||
<div class="hero-meta">
|
||
<div class="meta-card"><div class="meta-label">上游依赖</div><div class="meta-value">Day 1 的资产模型、版本模型、审核模型、资产 API。</div></div>
|
||
<div class="meta-card"><div class="meta-label">下游交接</div><div class="meta-value">Day 3 要复用资产数据，Day 4 要查询 active 技能 / MCP / 任务。</div></div>
|
||
<div class="meta-card"><div class="meta-label">当天关键</div><div class="meta-value">前端联调不是硬编码演示，而是可对接真实后端。</div></div>
|
||
</div>
|
||
</section>
|
||
|
||
<div class="section-kicker">Three-Layer Mapping</div>
|
||
<h2 class="section-title">三层文档映射</h2>
|
||
<div class="grid three">
|
||
<section class="card tone-warm">
|
||
<h3>路线图</h3>
|
||
<p>周计划要求把任务规则中心从静态 UI 升级到真实数据对接，覆盖规则、技能、MCP、任务四类资产。</p>
|
||
<div class="card-links"><a class="link-chip" href="../agent%20week%20plan/day_2_rule_center_integration.md">day_2_rule_center_integration.md</a></div>
|
||
</section>
|
||
<section class="card tone-teal">
|
||
<h3>执行细则</h3>
|
||
<p>执行层拆成 API Client、四类列表、规则详情、Markdown 编辑、版本卡片、审核与上线、技能详情、MCP 详情、任务详情、前端质量和当天验收。</p>
|
||
<div class="card-links"><a class="link-chip" href="../agent%20week%20plan/day_2_rule_center_integration.md">agent week plan/day_2</a></div>
|
||
</section>
|
||
<section class="card tone-olive">
|
||
<h3>架构依据</h3>
|
||
<p>这一天主要受能力注册、规则形成生命周期和数据治理约束，重点在四类资产的统一展示方式和规则上线前审核拦截。</p>
|
||
<div class="card-links">
|
||
<a class="link-chip" href="../agent%20plan/07_capability_registry.md">07</a>
|
||
<a class="link-chip" href="../agent%20plan/13_rule_formation_lifecycle.md">13</a>
|
||
<a class="link-chip" href="../agent%20plan/06_data_contracts_and_governance.md">06</a>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
|
||
<div class="section-kicker">Build Order</div>
|
||
<h2 class="section-title">推荐开发顺序</h2>
|
||
<div class="timeline">
|
||
<div class="timeline-step"><strong>Step 1</strong>先补 API Client：列表、详情、版本、保存、审核、上线、运行日志。</div>
|
||
<div class="timeline-step"><strong>Step 2</strong>把四个页签的真实数据接起来，覆盖筛选、搜索、状态、空态和加载态。</div>
|
||
<div class="timeline-step"><strong>Step 3</strong>把规则详情的 Hero 区、Markdown 编辑器、版本卡片和审核信息拉通。</div>
|
||
<div class="timeline-step"><strong>Step 4</strong>补技能 / MCP / 任务的差异化详情，不复用规则编辑器。</div>
|
||
<div class="timeline-step"><strong>Step 5</strong>最后收 UI 细节、错误态、禁用态、确认弹窗和构建验证。</div>
|
||
</div>
|
||
|
||
<div class="section-kicker">Must Deliver</div>
|
||
<h2 class="section-title">今天必须产出的东西</h2>
|
||
<div class="grid two">
|
||
<section class="card">
|
||
<h3>规则中心四页签</h3>
|
||
<ul class="list">
|
||
<li>规则、技能、MCP、任务都能切换。</li>
|
||
<li>每个页签都来自真实接口，不再只读本地常量。</li>
|
||
<li>搜索和状态筛选同时生效。</li>
|
||
</ul>
|
||
</section>
|
||
<section class="card">
|
||
<h3>规则详情闭环</h3>
|
||
<ul class="list">
|
||
<li>能读取当前 Markdown。</li>
|
||
<li>能保存并刷新版本列表。</li>
|
||
<li>能展示审核者、审核状态、上线条件。</li>
|
||
</ul>
|
||
</section>
|
||
<section class="card">
|
||
<h3>版本与上线约束</h3>
|
||
<ul class="list">
|
||
<li>最近 5 个版本可见。</li>
|
||
<li>切换旧版本必须弹确认框。</li>
|
||
<li>未审核规则不能上线，拒绝原因要可见。</li>
|
||
</ul>
|
||
</section>
|
||
<section class="card">
|
||
<h3>详情差异化</h3>
|
||
<ul class="list">
|
||
<li>技能详情展示输入输出与依赖。</li>
|
||
<li>MCP 详情展示服务地址、鉴权、降级策略。</li>
|
||
<li>任务详情展示 cron、执行 Agent、最近执行结果。</li>
|
||
</ul>
|
||
</section>
|
||
</div>
|
||
|
||
<div class="section-kicker">Acceptance Snapshot</div>
|
||
<h2 class="section-title">验收快照</h2>
|
||
<div class="table-like">
|
||
<div class="row"><div class="row-label">真实数据</div><div class="row-value">四个页签都能用真实后端数据渲染，后端不可用时有明确错误提示。</div></div>
|
||
<div class="row"><div class="row-label">规则编辑</div><div class="row-value">Markdown 保存后刷新页面仍在，保存失败不丢输入。</div></div>
|
||
<div class="row"><div class="row-label">版本卡片</div><div class="row-value">最近 5 个版本可切换，当前版本标识清楚但不造成布局位移。</div></div>
|
||
<div class="row"><div class="row-label">审核上线</div><div class="row-value"><code>pending</code> / <code>rejected</code> 规则都无法上线，<code>approved</code> 才能放行。</div></div>
|
||
</div>
|
||
|
||
<div class="section-kicker">Common Misses</div>
|
||
<h2 class="section-title">这一天最容易漏掉的点</h2>
|
||
<ul class="list">
|
||
<li>只把规则页签接成真实数据，技能、MCP、任务仍然靠假数据撑场面。</li>
|
||
<li>只做版本列表展示，不做确认弹窗和拒绝风险提示。</li>
|
||
<li>把任务写成“定时任务”暴露给用户，违背文档里 UI 名称统一成“任务”的约束。</li>
|
||
</ul>
|
||
|
||
<div class="footer">Day 2 的完成标准不是“页面能打开”，而是“规则中心第一次成为真实的资产入口”。</div>
|
||
</div>
|
||
</body>
|
||
</html>
|