@namewta/speculo 1.0.2 → 1.0.3

package/template/workflows/specdev/O-orchestrate-implementation/implementation-evidence-template.md

@@ -1,39 +0,0 @@
-# Implementation Orchestration Evidence
-
-## 1. Parent Plan and Final Revision
-
-- Parent change:
-- Final Implementation Map revision:
-- Workspace/integration strategy:
-- Lead and epoch:
-
-## 2. Member and Ticket Completion
-
-| Change | Composite Tickets | Final status | Child Evidence | Final Git result |
-|---|---|---|---|---|
-
-## 3. Dependency and Serialization Audit
-
-| Edge or pair | Required order/lock | Observed execution | Evidence |
-|---|---|---|---|
-
-## 4. Repository Integration Audit
-
-| Repository/ref | Ordered results | Stale candidates | Final checkpoint | Evidence |
-|---|---|---|---|---|
-
-## 5. Aggregate Verification
-
-| Command/check | Environment | Exit/result | Evidence |
-|---|---|---|---|
-
-## 6. Contract, Drift and Deviation Audit
-
-- Cross-change contracts:
-- Map/child drift disposition:
-- Deviations/blockers:
-
-## 7. Residual Risk and Boundary
-
-- Residual risk:
-- Not performed: archive, push, PR, remote merge, deploy, production migration unless separately authorized.

package/template/workflows/specdev/O-orchestrate-implementation/implementation-map-template.md

@@ -1,50 +0,0 @@
----
-schema_version: 1
-artifact: implementation-map
-change: <YYYY-MM-DD-parent-topic>
-status: ready
-revision: 1
-members: [<child-change-a>, <child-change-b>]
-tasks: [<child-change-a>::T-01, <child-change-b>::T-01]
-dependencies: []
-serializations: []
----
-
-# Implementation Map: <Outcome>
-
-## 1. Members and Source Authority
-
-| Change | Spec | Tickets Map | Change status | Role |
-|---|---|---|---|---|
-| `<child-change-a>` | ready | ready | active | delivery |
-| `<child-change-b>` | ready | ready | active | delivery |
-
-## 2. Composite Ticket Inventory
-
-| Composite ID | Child Ticket | Status | Ready | Writable/shared summary | Contracts |
-|---|---|---|---|---|---|
-| `<child-change-a>::T-01` | T-01 | ready | yes | pending | pending |
-| `<child-change-b>::T-01` | T-01 | ready | yes | pending | pending |
-
-## 3. Implementation Super-DAG
-
-| Edge | Kind | Source and reason | Start Gate | Evidence |
-|---|---|---|---|---|
-| none | none | independent until proven otherwise | n/a | n/a |
-
-## 4. Conflict and Serialization
-
-| Pair | Resource or overlap | Owner | Release condition |
-|---|---|---|---|
-| none | none observed | n/a | n/a |
-
-## 5. Contract and Path Coverage
-
-| Contract/shared surface | Producer task | Consumer tasks | Ordering/lock | Verification |
-|---|---|---|---|---|
-
-## 6. Revision Log
-
-| Revision | Source change | Affected tasks/edges | Reason |
-|---|---|---|---|
-| 1 | initial Ready inputs | all | parent creation |

package/template/workflows/specdev/O-orchestrate-implementation/implementation-plan-template.md

@@ -1,61 +0,0 @@
----
-schema_version: 1
-artifact: implementation-plan
-change: <YYYY-MM-DD-parent-topic>
-status: ready
-source_map_revision: 1
-orchestration: lead-directed
-lead: <owner-or-session-locator>
-implementation_agent_limit: 3
-integration_attempt_limit: 3
-ticket_workspace_policy: current
-integration_gate: direct-parent
-ready_for_execution: true
----
-
-# Implementation Plan: <Outcome>
-
-## 1. Outcome and Authority
-
-- Outcome: <aggregate implementation outcome>
-- Lead: <recoverable owner/session locator>
-- False completion: <what must not be called done>
-- Authority: child Spec/Tickets for behavior and implementation; parent Map/Plan for cross-change execution only.
-
-## 2. Ready Frontier and Waves
-
-| Wave | Composite tasks | Dependency Gate | Serialization/resource Gate | Status |
-|---|---|---|---|---|
-| 1 | pending | dependencies satisfied | locks available | ready |
-
-## 3. Workspace and Dispatch Contract
-
-- Ticket workspace policy: current / required.
-- Dispatch IDs use `<member-change>::<ticket-id>`.
-- The implementation agent limit is global across all members; the Lead is not counted.
-- Read-only review/research/test-observation agents do not consume the implementation limit.
-
-## 4. Repository Integration Queue
-
-| Repository/ref | Ordered composite tasks | Current parent checkpoint | Active candidate | Owner |
-|---|---|---|---|---|
-| current repository/current ref | pending | pending-read | none | Lead |
-
-## 5. Gates and Aggregate Verification
-
-| Gate | Required tasks | Verification | Evidence | Status |
-|---|---|---|---|---|
-| child completion | all child Tickets | child completion contract | child Evidence | pending |
-| aggregate | all members completed | full suite and applicable E2E | parent Evidence | pending |
-
-## 6. Conflict, Drift and Recovery
-
-- Re-read Map revision, Lead epoch, child Tickets, Git HEAD, active dispatches and locks before every action.
-- Any parent advance makes older candidates stale and requires reconstruction.
-- On pause, persist last accepted task, stale candidates, blockers, next legal task and required reads.
-
-## 7. Progress and Decisions
-
-| Time | Composite task | Dispatch/result | Child Evidence | Parent checkpoint | Next recomputation |
-|---|---|---|---|---|---|
-| pending | none | not started | none | pending-read | compute frontier |

package/template/workflows/specdev/R-review-architecture/architecture-report-contract.md

@@ -1,123 +0,0 @@
-# HTML 报告格式
-
-架构审查渲染为一个独立的 HTML 文件，存放在操作系统临时目录中。Tailwind 和 Mermaid 均来自 CDN。Mermaid 处理图形状的图表；手工构建的 div 和内联 SVG 处理更具编辑性的可视化（质量图、横截面图）。混合使用两者 — 不要所有事情都依赖 Mermaid，否则会变得千篇一律。
-
-## 脚手架
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="utf-8" />
-    <title>Architecture review — {{repo name}}</title>
-    <script src="https://cdn.tailwindcss.com"></script>
-    <script type="module">
-      import mermaid from "https://cdn.jsdelivr.net/npm/mermaid@11/dist/mermaid.esm.min.mjs";
-      mermaid.initialize({ startOnLoad: true, theme: "neutral", securityLevel: "loose" });
-    </script>
-    <style>
-      /* Tailwind 无法很好覆盖的小型自定义层：
-         虚线接缝线、手绘感箭头等。 */
-      .seam { stroke-dasharray: 4 4; }
-      .leak { stroke: #dc2626; }
-      .deep { background: linear-gradient(135deg, #0f172a, #1e293b); }
-    </style>
-  </head>
-  <body class="bg-stone-50 text-slate-900 font-sans">
-    <main class="max-w-5xl mx-auto px-6 py-12 space-y-12">
-      <header>...</header>
-      <section id="candidates" class="space-y-10">...</section>
-      <section id="top-recommendation">...</section>
-    </main>
-  </body>
-</html>
-```
-
-## 页头
-
-仓库名称、日期和一个紧凑的图例：实线框 = 模块，虚线 = 接缝，红色箭头 = 泄漏，粗黑框 = 深模块。无介绍段落 — 直接进入候选。
-
-## 候选卡片
-
-图表承担主要分量。文字稀疏、平实，并使用来自 `<Path>{roots.workflows}/specdev/common/rules/codebase-design.md</Path>` 的术语，不刻意修饰。
-
-每个候选是一个 `<article>`：
-
-- **标题** — 简短，命名深化方案（例如"Collapse the Order intake pipeline"）。
-- **徽章行** — 推荐强度（`Strong` = 翡翠绿，`Worth exploring` = 琥珀色，`Speculative` = 石板灰），外加一个依赖类别标签（`in-process`、`local-substitutable`、`ports & adapters`、`mock`）。
-- **文件** — 等宽字体列表，`font-mono text-sm`。
-- **Before / After 图表** — 核心。两列，并排。参见下方模式。
-- **Problem** — 一句话。痛点是什么。
-- **Solution** — 一句话。改变了什么。
-- **Wins** — 要点，每个不超过 6 个词。例如 "Tests hit one interface"、"Pricing logic stops leaking"、"Delete 4 shallow wrappers"。
-- **ADR 标注**（如适用）— 一行，放在琥珀色调的框中。
-
-无需解释段落。如果图表需要一段文字才能理解，重新画图。
-
-## 图表模式
-
-选择适合候选的模式。混合使用它们。不要让每个图表看起来都一样 — 多样性本身就是目的的一部分。
-
-### Mermaid 图表（依赖/调用流的常用工具）
-
-当重点是"X 调用 Y 调用 Z，看看这有多混乱"时，使用 Mermaid `flowchart` 或 `graph`。用 Tailwind 风格卡片包裹它，这样不会显得突兀。使用 classDef 将泄漏边缘着红色，深模块着深色。序列图适合展示"before：6 个往返；after：1 个"。
-
-```html
-<div class="rounded-lg border border-slate-200 bg-white p-4">
-  <pre class="mermaid">
-    flowchart LR
-      A[OrderHandler] --> B[OrderValidator]
-      B --> C[OrderRepo]
-      C -.leak.-> D[PricingClient]
-      classDef leak stroke:#dc2626,stroke-width:2px;
-      class C,D leak
-  </pre>
-</div>
-```
-
-### 手工绘制的框线图（当 Mermaid 的布局难以驾驭时）
-
-模块用带边框和标签的 `<div>` 表示。箭头用绝对定位在相对容器上的内联 SVG `<line>` 或 `<path>` 元素表示。当你希望"after"图表看起来像一个粗边的深模块，内部元素灰显时使用 — Mermaid 不会以合适的权重渲染这种效果。
-
-### 横截面图（适合分层浅度）
-
-堆叠水平条（`h-12 border-l-4`）来展示调用经过的各层。Before：6 个薄层，每个都不做什么。After：一个厚条，标注合并后的职责。
-
-### 质量图（适合"接口与实现一样宽"的场景）
-
-每个模块两个矩形 — 一个表示接口表面积，一个表示实现。Before：接口矩形几乎和实现矩形一样高（浅）。After：接口矩形短，实现矩形高（深）。
-
-### 调用图坍缩
-
-Before：嵌套框呈现的函数调用树。After：同一棵树坍缩成一个框，内部调用在其内部以淡化形式显示。
-
-## 样式指导
-
-- 偏向编辑风格，而非企业仪表盘风格。宽松的留白。标题可选择衬线字体（`font-serif` 与 stone/slate 搭配效果很好）。
-- 色彩使用克制：一种强调色（翠绿或靛蓝），加上红色用于泄漏，琥珀色用于警告。
-- 保持图表约 320px 高，使 before/after 能够舒适地并排放置而无需滚动。
-- 使用 `text-xs uppercase tracking-wider` 用于图表内的模块标签 — 它们应读起来像示意图，而非 UI。
-- 唯一的脚本是 Tailwind CDN 和 Mermaid ESM 导入。除此之外报告是静态的 — 没有应用代码，除了 Mermaid 自身的渲染之外没有交互。
-
-## 顶部推荐部分
-
-一张更大的卡片。候选名称，一句话说明为什么，指向其卡片的锚链接。这就够了。
-
-## 语气
-
-平实的英语，简洁 — 但架构名词和动词直接来自 `<Path>{roots.workflows}/specdev/common/rules/codebase-design.md</Path>`。简洁不是偏离的借口。
-
-**完全使用：** module、interface、implementation、depth、deep、shallow、seam、adapter、leverage、locality。
-
-**绝不替代：** component、service、unit（代替 module）· API、signature（代替 interface）· boundary（代替 seam）· layer、wrapper（代替 module，当你的意思是 module 时）。
-
-**符合风格的表达方式：**
-
-- "Order intake module is shallow — interface nearly matches the implementation."
-- "Pricing leaks across the seam."
-- "Deepen: one interface, one place to test."
-- "Two adapters justify the seam: HTTP in prod, in-memory in tests."
-
-**Wins 要点**用术语表命名收益：*"locality: bugs concentrate in one module"*、*"leverage: one interface, N call sites"*、*"interface shrinks; implementation absorbs the wrappers"*。不要写 *"easier to maintain"* 或 *"cleaner code"* — 这些术语不在术语表中，不值得留下。
-
-不模糊其词，不清喉咙，不说"值得注意的是……"。如果一句话可以变成一个要点，就变成要点。如果一个要点可以删除，就删除它。如果一个术语不在 `<Path>{roots.workflows}/specdev/common/rules/codebase-design.md</Path>` 中，在发明新术语之前先用术语表中已有的。

package/template/workflows/specdev/R-review-architecture/architecture-review-report-template.html

@@ -1,106 +0,0 @@
-<!doctype html>
-<html lang="zh-CN">
-  <head>
-    <meta charset="utf-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1">
-    <title>Architecture review - {{repo name}}</title>
-    <script src="https://cdn.tailwindcss.com"></script>
-    <script type="module">
-      import mermaid from "https://cdn.jsdelivr.net/npm/mermaid@11/dist/mermaid.esm.min.mjs";
-      mermaid.initialize({ startOnLoad: true, theme: "neutral", securityLevel: "loose" });
-    </script>
-    <style>
-      * { letter-spacing: 0 !important; }
-      .seam { stroke-dasharray: 4 4; }
-      .leak { stroke: #dc2626; }
-      .module-label { font-size: 0.72rem; text-transform: uppercase; }
-      .quality-bar { min-height: 2.75rem; }
-      code { overflow-wrap: anywhere; }
-    </style>
-  </head>
-  <body class="bg-stone-50 text-slate-900 font-sans">
-    <main class="mx-auto max-w-5xl space-y-12 px-4 py-10 sm:px-6 sm:py-12">
-      <header class="space-y-4 border-b border-slate-300 pb-6">
-        <div class="flex flex-col gap-2 sm:flex-row sm:items-end sm:justify-between">
-          <div>
-            <p class="text-sm font-semibold text-emerald-700">{{repo name}} / {{date}}</p>
-            <h1 class="mt-1 font-serif text-3xl font-semibold sm:text-4xl">Architecture review</h1>
-          </div>
-          <p class="text-sm text-slate-600">{{review scope}}</p>
-        </div>
-        <div class="flex flex-wrap gap-x-5 gap-y-2 text-xs text-slate-600" aria-label="图例">
-          <span><span class="mr-1 inline-block h-3 w-5 border border-slate-700 align-middle"></span>module</span>
-          <span><span class="mr-1 inline-block h-3 w-5 border border-dashed border-slate-700 align-middle"></span>seam</span>
-          <span><span class="mr-1 inline-block h-0 w-5 border-t-2 border-red-600 align-middle"></span>leak</span>
-          <span><span class="mr-1 inline-block h-3 w-5 border-4 border-slate-900 align-middle"></span>deep module</span>
-        </div>
-        <p class="text-xs text-slate-500">
-          Decision record: <code><Path>{roots.state}/specdev/changes/{change}/architecture-review.md</Path></code>
-        </p>
-      </header>
-
-      <section id="candidates" class="space-y-10">
-        <article id="ar-001" class="rounded-lg border border-slate-300 bg-white p-5 shadow-sm sm:p-7">
-          <div class="flex flex-col gap-3 sm:flex-row sm:items-start sm:justify-between">
-            <div>
-              <p class="text-sm font-semibold text-emerald-700">AR-001</p>
-              <h2 class="mt-1 font-serif text-2xl font-semibold">Collapse the Order intake pipeline</h2>
-            </div>
-            <div class="flex flex-wrap gap-2 text-xs font-semibold">
-              <span class="rounded border border-emerald-700 bg-emerald-50 px-2 py-1 text-emerald-800">Strong</span>
-              <span class="rounded border border-slate-400 bg-slate-50 px-2 py-1 text-slate-700">in-process</span>
-            </div>
-          </div>
-
-          <div class="mt-5 border-y border-slate-200 py-3">
-            <p class="text-xs font-semibold uppercase text-slate-500">Files</p>
-            <p class="mt-1 font-mono text-sm">src/order/handler.ts · src/order/validator.ts · test/order.test.ts</p>
-          </div>
-
-          <div class="mt-6 grid gap-6 lg:grid-cols-2">
-            <section aria-labelledby="before-title">
-              <h3 id="before-title" class="text-sm font-semibold">Before</h3>
-              <div class="mt-2 min-h-80 rounded-lg border border-slate-200 bg-stone-50 p-4">
-                <pre class="mermaid">
-flowchart LR
-  A[OrderHandler] --> B[OrderValidator]
-  B --> C[OrderRepo]
-  C -. leak .-> D[PricingClient]
-  classDef leaking stroke:#dc2626,stroke-width:2px
-  class C,D leaking
-                </pre>
-              </div>
-            </section>
-            <section aria-labelledby="after-title">
-              <h3 id="after-title" class="text-sm font-semibold">After</h3>
-              <div class="mt-2 flex min-h-80 flex-col justify-center rounded-lg border-4 border-slate-900 bg-white p-5">
-                <p class="module-label font-semibold text-slate-500">Interface</p>
-                <div class="quality-bar mt-2 flex items-center rounded border border-emerald-700 bg-emerald-50 px-4 text-sm font-semibold text-emerald-900">one narrow interface</div>
-                <p class="module-label mt-6 font-semibold text-slate-500">Hidden implementation</p>
-                <div class="mt-2 space-y-2 text-sm text-slate-500">
-                  <div class="rounded border border-slate-200 bg-slate-50 p-3">validation</div>
-                  <div class="rounded border border-slate-200 bg-slate-50 p-3">pricing protocol</div>
-                  <div class="rounded border border-slate-200 bg-slate-50 p-3">persistence</div>
-                </div>
-              </div>
-            </section>
-          </div>
-
-          <dl class="mt-6 grid gap-5 border-t border-slate-200 pt-5 sm:grid-cols-3">
-            <div><dt class="text-xs font-semibold uppercase text-slate-500">Problem</dt><dd class="mt-1 text-sm">Callers coordinate three shallow modules and absorb the failure order.</dd></div>
-            <div><dt class="text-xs font-semibold uppercase text-slate-500">Solution</dt><dd class="mt-1 text-sm">Move the intake policy behind one deep module.</dd></div>
-            <div><dt class="text-xs font-semibold uppercase text-slate-500">Wins</dt><dd class="mt-1 text-sm">One test surface · Local failure policy · Fewer leaking seams</dd></div>
-          </dl>
-
-          <p class="mt-5 rounded border border-amber-500 bg-amber-50 px-4 py-3 text-sm text-amber-950">ADR note: {{none or conflict explanation}}</p>
-        </article>
-      </section>
-
-      <section id="top-recommendation" class="border-t-4 border-emerald-700 pt-6">
-        <p class="text-sm font-semibold text-emerald-700">Best recommendation</p>
-        <h2 class="mt-1 font-serif text-2xl font-semibold"><a class="underline decoration-emerald-600 decoration-2 underline-offset-4" href="#ar-001">Collapse the Order intake pipeline</a></h2>
-        <p class="mt-2 max-w-3xl text-slate-700">It removes the hottest coordination seam while preserving the domain language and existing behavior.</p>
-      </section>
-    </main>
-  </body>
-</html>