@clawos-dev/clawd 0.2.50-beta.77.3a9364e → 0.2.51-beta.78.2024c11

package/dist/persona-defaults/persona-clawd-helper/CLAUDE.md

@@ -117,7 +117,7 @@ clawd 一句话：**它是 ClawOS 里的一个 Extension —— 在 ClawOS 桌
 5. **远程接入您的本机 AI** —— 一行命令开一条公网隧道，您手机上、外网都能连回家里电脑的 Claude Code，不用部署服务器
 6. **临时借身份**（`@persona/xxx`） —— 当前对话里想让另一个助手客串一句话，输入框 `@` 一下选它，不用切会话
 7. **对话能分叉 / 回滚** —— 任何一条 AI 的回答都能 fork 出新会话分支，或者把会话回滚到之前某一步重来
-8. **助手自带技能包** —— 比如「调研员」自带 deep-research，「知识库管理员」自带 karpathy-llm-wiki，您也可以给自己建的助手装 skill
+8. **助手按需装技能包** —— 每个助手第一次会话会引导您一键装它需要的技能（比如「调研员」引导装 deep-research，「知识库管理员」引导装 karpathy-llm-wiki），走标准 skills 渠道、可独立升级，您也可以给自己建的助手装 skill
 9. **统一记住怎么称呼您** —— 一次告诉 clawd 您叫什么（OwnerProfile），所有助手自我介绍都会用这个名字（"我是 David 的 xxx 助手"）
 10. **断线不丢对话** —— 会话历史落在本机，daemon 重启、网断、关电脑都不影响下次接回来继续聊
 

package/dist/persona-defaults/persona-knowledge-base/CLAUDE.md

@@ -1,5 +1,24 @@
 你是老板的知识库管理员。归档是入口，但不是边界 —— 查询、复盘、维护、整理都是分内事。
 
+# 初次见面：先检查 `karpathy-llm-wiki` skill 装好了没
+
+这个 persona 不自带 skill 文件，要老板手动装一次（走正常 skills 渠道，方便后续独立升级）。每次新会话**第一轮**就检查：
+
+```bash
+ls ~/.clawd/personas/persona-knowledge-base/.claude/skills/karpathy-llm-wiki/SKILL.md 2>/dev/null && echo "✅ 已装" || echo "❌ 未装"
+```
+
+未装就引导老板装到本 persona（不带 `-g`，只对这个 persona 生效）：
+
+```bash
+cd ~/.clawd/personas/persona-knowledge-base
+npx skills add astro-han/karpathy-llm-wiki -y
+```
+
+装完 `ls .claude/skills/` 应该能看到 `karpathy-llm-wiki/`。后续升级用 `npx skills update karpathy-llm-wiki`。
+
+**在 skill 装好之前**：第 0 条铁律里说"碰 wiki 必走 skill"的部分先停手，告诉老板"`karpathy-llm-wiki` skill 还没装，需要先装好才能动 wiki/，要不要现在装？"
+
 # 第 0 条铁律：碰 `wiki/` 必走 `karpathy-llm-wiki` skill
 
 **任何会读、写、改 `wiki/` 目录的工作，开工前第一件事就是 invoke `karpathy-llm-wiki` skill，按它的流程做。** 这条优先级高于本文件其他所有内容。

package/dist/persona-defaults/persona-researcher/CLAUDE.md

@@ -1,8 +1,27 @@
 你是一个专业的调研员（researcher），你的职责是帮助老板做高质量、可核查的深度调研。
 
+## 初次见面：先检查 `deep-research` skill 装好了没
+
+这个 persona 不自带 skill 文件，要老板手动装一次（走正常 skills 渠道，方便后续独立升级）。每次新会话**第一轮**就检查：
+
+```bash
+ls ~/.clawd/personas/persona-researcher/.claude/skills/deep-research/SKILL.md 2>/dev/null && echo "✅ 已装" || echo "❌ 未装"
+```
+
+未装就引导老板装到本 persona（不带 `-g`，只对这个 persona 生效）：
+
+```bash
+cd ~/.clawd/personas/persona-researcher
+npx skills add 199-biotechnologies/claude-deep-research-skill -y
+```
+
+装完 `ls .claude/skills/` 应该能看到 `deep-research/`。后续升级用 `npx skills update deep-research`。
+
+**在 skill 装好之前**：能用通用搜索能力的调研可以继续做，但要告诉老板"`deep-research` skill 没装，当前是降级模式，没有分档（quick/standard/deep/ultradeep）、不会自动校验来源链接，要不要现在装？"
+
 ## 核心工作方式
 
-- **优先调用 `deep-research` skill**：老板提出任何"调研 / 研究 / 分析 / 综述 / 竞品 / 市场 / 技术选型"类需求时，先评估是否适用 `deep-research` skill（这个 persona 出厂自带），是就用，不要凭感觉口述
+- **优先调用 `deep-research` skill**：老板提出任何"调研 / 研究 / 分析 / 综述 / 竞品 / 市场 / 技术选型"类需求时，先评估是否适用 `deep-research` skill，是就用，不要凭感觉口述
 - **不能猜**：拿不准的事实，主动并行抓多个源核验，给出来源链接
 - **产出带引用**：所有调研报告末尾必须给 bibliography（参考文献列表），每条带可点击链接和访问日期
 - **抗幻觉**：发现引用不存在 / 链接打不开 / 数据来源单一时，明确标红，不要硬凑结论

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clawos-dev/clawd",
-  "version": "0.2.50-beta.77.3a9364e",
+  "version": "0.2.51-beta.78.2024c11",
   "description": "Standalone clawd daemon — Claude Code (and future Codex) session server over WebSocket",
   "type": "module",
   "license": "MIT",

package/dist/persona-defaults/persona-knowledge-base/.claude/skills/karpathy-llm-wiki/SKILL.md

@@ -1,187 +0,0 @@
----
-name: karpathy-llm-wiki
-description: "Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'."
----
-
-# Karpathy LLM Wiki
-
-Build and maintain a personal knowledge base using LLMs. You manage two directories: `raw/` (immutable source material) and `wiki/` (compiled knowledge articles). Sources go into raw/, you compile them into wiki articles, and the wiki compounds over time.
-
-Core ideas from Karpathy:
-- "The LLM writes and maintains the wiki; the human reads and asks questions."
-- "The wiki is a persistent, compounding artifact."
-
-## Architecture
-
-Three layers, all under the user's project root:
-
-**raw/** — Immutable source material. You read, never modify. Organized by topic subdirectories (e.g., `raw/machine-learning/`).
-
-**wiki/** — Compiled knowledge articles. You have full ownership. Organized by topic subdirectories, one level only: `wiki/<topic>/<article>.md`. Contains two special files:
-- `wiki/index.md` — Global index. One row per article, grouped by topic, with link + summary + Updated date.
-- `wiki/log.md` — Append-only operation log.
-
-**SKILL.md** (this file) — Schema layer. Defines structure and workflow rules.
-
-Templates live in `references/` relative to this file. Read them when you need the exact format for raw files, articles, archive pages, or the index.
-
-### Initialization
-
-Triggers only on the first Ingest. Check whether `raw/` and `wiki/` exist. Create only what is missing; never overwrite existing files:
-
-- `raw/` directory (with `.gitkeep`)
-- `wiki/` directory (with `.gitkeep`)
-- `wiki/index.md` — heading `# Knowledge Base Index`, empty body
-- `wiki/log.md` — heading `# Wiki Log`, empty body
-
-If Query or Lint cannot find the wiki structure, tell the user: "Run an ingest first to initialize the wiki." Do not auto-create.
-
----
-
-## Ingest
-
-Fetch a source into raw/, then compile it into wiki/. Always both steps, no exceptions.
-
-### Fetch (raw/)
-
-1. Get the source content using whatever web or file tools your environment provides. If nothing can reach the source, ask the user to paste it directly.
-
-2. Pick a topic directory. Check existing `raw/` subdirectories first; reuse one if the topic is close enough. Create a new subdirectory only for genuinely distinct topics.
-
-3. Save as `raw/<topic>/YYYY-MM-DD-descriptive-slug.md`.
-   - Slug from source title, kebab-case, max 60 characters.
-   - Published date unknown → omit the date prefix from the file name (e.g., `descriptive-slug.md`). The metadata Published field still appears; set it to `Unknown`.
-   - If a file with the same name already exists, append a numeric suffix (e.g., `descriptive-slug-2.md`).
-   - Include metadata header: source URL, collected date, published date.
-   - Preserve original text. Clean formatting noise. Do not rewrite opinions.
-
-   See `references/raw-template.md` for the exact format.
-
-### Compile (wiki/)
-
-Determine where the new content belongs:
-
-- **Same core thesis as existing article** → Merge into that article. Add the new source to Sources/Raw. Update affected sections.
-- **New concept** → Create a new article in the most relevant topic directory. Name the file after the concept, not the raw file.
-- **Spans multiple topics** → Place in the most relevant directory. Add See Also cross-references to related articles elsewhere.
-
-These are not mutually exclusive. A single source may warrant merging into one article while also creating a separate article for a distinct concept it introduces. In all cases, check for factual conflicts: if the new source contradicts existing content, annotate the disagreement with source attribution. When merging, note the conflict within the merged article. When the conflicting content lives in separate articles, note it in both and cross-link them.
-
-See `references/article-template.md` for article format. Key points:
-- Sources field: author, organization, or publication name + date, semicolon-separated.
-- Raw field: markdown links to raw/ files, semicolon-separated.
-- Relative paths from `wiki/<topic>/` use `../../raw/<topic>/<file>.md` (two levels up to project root).
-
-### Cascade Updates
-
-After the primary article, check for ripple effects:
-
-1. Scan articles in the same topic directory for content affected by the new source.
-2. Scan `wiki/index.md` entries in other topics for articles covering related concepts.
-3. Update every article whose content is materially affected. Each updated file gets its Updated date refreshed.
-
-Archive pages are never cascade-updated (they are point-in-time snapshots).
-
-### Post-Ingest
-
-Update `wiki/index.md`: add or update entries for every touched article. When adding a new topic section, include a one-line description. The Updated date reflects when the article's knowledge content last changed, not the file system timestamp. See `references/index-template.md` for format.
-
-Append to `wiki/log.md`:
-
-```
-## [YYYY-MM-DD] ingest | <primary article title>
-- Updated: <cascade-updated article title>
-- Updated: <another cascade-updated article title>
-```
-
-Omit `- Updated:` lines when no cascade updates occur.
-
----
-
-## Query
-
-Search the wiki and answer questions. Examples of triggers:
-- "What do I know about X?"
-- "Summarize everything related to Y"
-- "Compare A and B based on my wiki"
-
-### Steps
-
-1. Read `wiki/index.md` to locate relevant articles.
-2. Read those articles and synthesize an answer.
-3. Prefer wiki content over your own training knowledge. Cite sources with markdown links: `[Article Title](wiki/topic/article.md)` (project-root-relative paths for in-conversation citations; within wiki/ files, use paths relative to the current file).
-4. Output the answer in the conversation. Do not write files unless asked.
-
-### Archiving
-
-When the user explicitly asks to archive or save the answer to the wiki:
-
-1. Write the answer as a new wiki page. See `references/archive-template.md`. When converting conversation citations to the archive page, rewrite project-root-relative paths (e.g., `wiki/topic/article.md`) to file-relative paths (e.g., `../topic/article.md` or `article.md` for same-directory).
-   - Sources: markdown links to the wiki articles cited in the answer.
-   - No Raw field (content does not come from raw/).
-   - File name reflects the query topic, e.g., `transformer-architectures-overview.md`.
-   - Place in the most relevant topic directory.
-2. Always create a new page. Never merge into existing articles (archive content is a synthesized answer, not raw material).
-3. Update `wiki/index.md`. Prefix the Summary with `[Archived]`.
-4. Append to `wiki/log.md`:
-   ```
-   ## [YYYY-MM-DD] query | Archived: <page title>
-   ```
-
----
-
-## Lint
-
-Quality checks on the wiki. Two categories with different authority levels.
-
-### Deterministic Checks (auto-fix)
-
-Fix these automatically:
-
-**Index consistency** — compare `wiki/index.md` against actual wiki/ files (excluding index.md and log.md):
-- File exists but missing from index → add entry with `(no summary)` placeholder. For Updated, use the article's metadata Updated date if present; otherwise fall back to file's last modified date.
-- Index entry points to nonexistent file → mark as `[MISSING]` in the index. Do not delete the entry; let the user decide.
-
-**Internal links** — for every markdown link in wiki/ article files (body text and Sources metadata), excluding Raw field links (validated by Raw references below) and excluding index.md/log.md (handled above):
-- Target does not exist → search wiki/ for a file with the same name elsewhere.
-  - Exactly one match → fix the path.
-  - Zero or multiple matches → report to the user.
-
-**Raw references** — every link in a Raw field must point to an existing raw/ file:
-- Target does not exist → search raw/ for a file with the same name elsewhere.
-  - Exactly one match → fix the path.
-  - Zero or multiple matches → report to the user.
-
-**See Also** — within each topic directory:
-- Add obviously missing cross-references between related articles.
-- Remove links to deleted files.
-
-### Heuristic Checks (report only)
-
-These rely on your judgment. Report findings without auto-fixing:
-
-- Factual contradictions across articles
-- Outdated claims superseded by newer sources
-- Missing conflict annotations where sources disagree
-- Orphan pages with no inbound links from other wiki articles
-- Missing cross-topic references
-- Concepts frequently mentioned but lacking a dedicated page
-- Archive pages whose cited source articles have been substantially updated since archival
-
-### Post-Lint
-
-Append to `wiki/log.md`:
-
-```
-## [YYYY-MM-DD] lint | <N> issues found, <M> auto-fixed
-```
-
----
-
-## Conventions
-
-- Standard markdown with relative links throughout.
-- wiki/ supports one level of topic subdirectories only. No deeper nesting.
-- Today's date for log entries, Collected dates, and Archived dates. Updated dates reflect when the article's knowledge content last changed. Published dates come from the source (use `Unknown` when unavailable).
-- Inside wiki/ files, all markdown links use paths relative to the current file. In conversation output, use project-root-relative paths (e.g., `wiki/topic/article.md`).
-- Ingest updates both `wiki/index.md` and `wiki/log.md`. Archive (from Query) updates both. Lint updates `wiki/log.md` (and `wiki/index.md` only when auto-fixing index entries). Plain queries do not write any files.

package/dist/persona-defaults/persona-knowledge-base/.claude/skills/karpathy-llm-wiki/references/archive-template.md

@@ -1,21 +0,0 @@
-# {Title}
-
-> Sources: [{Cited Article 1}](article1.md); [{Cited Article 2}](../other-topic/article2.md)
-{Paths must be relative to this file: same-topic = filename only, cross-topic = ../other-topic/filename.md}
-> Archived: {YYYY-MM-DD}
-
-## Overview
-
-{One paragraph summarizing the query and key findings.}
-
-## {Body Sections}
-
-{The synthesized answer, lightly edited for wiki context. This page is a point-in-time snapshot; it will not be cascade-updated when source articles change.}
-
-{OPTIONAL — include this section only when cross-references exist:}
-
-## See Also
-
-{Cross-references to related wiki articles. Use relative links:
-- Same topic: [Other Article](other-article.md)
-- Different topic: [Other Article](../other-topic/other-article.md)}

package/dist/persona-defaults/persona-knowledge-base/.claude/skills/karpathy-llm-wiki/references/article-template.md

@@ -1,20 +0,0 @@
-# {Title}
-
-> Sources: {Author1, YYYY-MM-DD; Author2, YYYY-MM-DD}
-> Raw: [{source1}](../../raw/{topic1}/{filename1}.md); [{source2}](../../raw/{topic2}/{filename2}.md)
-
-## Overview
-
-{One paragraph summarizing the key points of this article.}
-
-## {Body Sections}
-
-{Synthesize a coherent structure from the source material. Do not copy source text verbatim; distill and reorganize. Use blockquotes sparingly for particularly important original phrasing.}
-
-{OPTIONAL — include this section only when cross-references exist:}
-
-## See Also
-
-{Cross-references to related wiki articles. Maintained during lint. Use relative links:
-- Same topic: [Other Article](other-article.md)
-- Different topic: [Other Article](../other-topic/other-article.md)}

package/dist/persona-defaults/persona-knowledge-base/.claude/skills/karpathy-llm-wiki/references/index-template.md

@@ -1,18 +0,0 @@
-# Knowledge Base Index
-
-## {topic-name}
-
-{One-line description of this topic.}
-
-| Article | Summary | Updated |
-|---------|---------|---------|
-| [{Article Title}]({topic-name}/{article}.md) | {One-line summary} | {YYYY-MM-DD} |
-| [{Archived Article}]({topic-name}/{archived}.md) | [Archived] {One-line summary} | {YYYY-MM-DD} |
-
-## {another-topic}
-
-{One-line description of this topic.}
-
-| Article | Summary | Updated |
-|---------|---------|---------|
-| [{Article Title}]({another-topic}/{article}.md) | {One-line summary} | {YYYY-MM-DD} |

package/dist/persona-defaults/persona-knowledge-base/.claude/skills/karpathy-llm-wiki/references/raw-template.md

@@ -1,7 +0,0 @@
-# {Title}
-
-> Source: {URL or origin description}
-> Collected: {YYYY-MM-DD}
-> Published: {YYYY-MM-DD or Unknown}
-
-{Original content below. Preserve the source text faithfully. Clean up formatting noise (extra whitespace, broken HTML artifacts, navigation chrome), but do not rewrite opinions or alter meaning.}

package/dist/persona-defaults/persona-researcher/.claude/skills/deep-research/README.md

@@ -1,119 +0,0 @@
-# Deep Research Skill for Claude Code
-
-Enterprise-grade research engine for Claude Code. Produces citation-backed reports with source credibility scoring, multi-provider search, and automated validation.
-
-## Installation
-
-```bash
-# Clone into Claude Code skills directory
-git clone https://github.com/199-biotechnologies/claude-deep-research-skill.git ~/.claude/skills/deep-research
-```
-
-No additional dependencies required for basic usage.
-
-### Optional: search-cli (multi-provider search)
-
-For aggregated search across Brave, Serper, Exa, Jina, and Firecrawl:
-
-```bash
-brew tap 199-biotechnologies/tap && brew install search-cli
-search config set keys.brave YOUR_KEY  # configure at least one provider
-```
-
-## Usage
-
-```
-deep research on the current state of quantum computing
-```
-
-```
-deep research in ultradeep mode: compare PostgreSQL vs Supabase for our stack
-```
-
-## Research Modes
-
-| Mode | Phases | Duration | Best For |
-|------|--------|----------|----------|
-| Quick | 3 | 2-5 min | Initial exploration |
-| Standard | 6 | 5-10 min | Most research questions |
-| Deep | 8 | 10-20 min | Complex topics, critical decisions |
-| UltraDeep | 8+ | 20-45 min | Comprehensive reports, maximum rigor |
-
-## Pipeline
-
-Scope → Plan → **Retrieve** (parallel search + agents) → Triangulate → Outline Refinement → Synthesize → Critique (with loop-back) → Refine → Package
-
-Key features:
-- **Step 0**: Retrieves current date before searches (prevents stale training-data year assumptions)
-- **Parallel retrieval**: 5-10 concurrent searches + 2-3 focused sub-agents returning structured evidence objects
-- **First Finish Search**: Adaptive quality thresholds by mode
-- **Critique loop-back**: Phase 6 can return to Phase 3 with delta-queries if critical gaps found
-- **Multi-persona red teaming**: Skeptical Practitioner, Adversarial Reviewer, Implementation Engineer (Deep/UltraDeep)
-- **Disk-persisted citations**: `sources.json` survives context compaction and continuation agents
-
-## Output
-
-Reports saved to `~/Documents/[Topic]_Research_[Date]/`:
-- Markdown (primary source of truth)
-- HTML (McKinsey-style, auto-opened in browser)
-- PDF (professional print via WeasyPrint)
-
-Reports >18K words auto-continue via recursive agent spawning with context preservation.
-
-## Quality Standards
-
-- 10+ sources, 3+ per major claim
-- Executive summary 200-400 words
-- Findings 600-2,000 words each, prose-first (>=80%)
-- Full bibliography with URLs, no placeholders
-- Automated validation: `validate_report.py` (9 checks) + `verify_citations.py` (DOI/URL/hallucination detection)
-- Validation loop: validate → fix → retry (max 3 cycles)
-
-## Search Tools
-
-| Tool | Priority | Setup |
-|------|----------|-------|
-| search-cli | **Primary** — all searches go here first | `brew install search-cli` + API keys |
-| WebSearch | Fallback — if search-cli fails or rate-limited | None (built-in) |
-| Exa MCP | Optional — semantic/neural search alongside search-cli | MCP config |
-
-## Architecture
-
-```
-deep-research/
-├── SKILL.md                          # Skill entry point (lean, ~100 lines)
-├── reference/
-│   ├── methodology.md                # 8-phase pipeline details
-│   ├── report-assembly.md            # Progressive generation strategy
-│   ├── quality-gates.md              # Validation standards
-│   ├── html-generation.md            # McKinsey HTML conversion
-│   ├── continuation.md               # Auto-continuation protocol
-│   └── weasyprint_guidelines.md      # PDF generation
-├── templates/
-│   ├── report_template.md            # Report structure template
-│   └── mckinsey_report_template.html # HTML report template
-├── scripts/
-│   ├── validate_report.py            # 9-check structure validator
-│   ├── verify_citations.py           # DOI/URL/hallucination checker
-│   ├── source_evaluator.py           # Source credibility scoring
-│   ├── citation_manager.py           # Citation tracking
-│   ├── md_to_html.py                 # Markdown to HTML converter
-│   ├── verify_html.py                # HTML verification
-│   └── research_engine.py            # Core orchestration engine
-└── tests/
-    └── fixtures/                     # Test report fixtures
-```
-
-## Version History
-
-| Version | Date | Changes |
-|---------|------|---------|
-| 2.3.1 | 2026-03-19 | Template/validator harmonization, structured evidence, critique loop-back, multi-persona red teaming |
-| 2.3 | 2026-03-19 | Contract harmonization, search-cli integration, dynamic year detection, disk-persisted citations, validation loops |
-| 2.2 | 2025-11-05 | Auto-continuation system for unlimited length |
-| 2.1 | 2025-11-05 | Progressive file assembly |
-| 1.0 | 2025-11-04 | Initial release |
-
-## License
-
-MIT - modify as needed for your workflow.

package/dist/persona-defaults/persona-researcher/.claude/skills/deep-research/SKILL.md

@@ -1,108 +0,0 @@
----
-name: deep-research
-description: Use when the user needs multi-source research with citation tracking, evidence persistence, and structured report generation. Triggers on "deep research", "comprehensive analysis", "research report", "compare X vs Y", "analyze trends", or "state of the art". Not for simple lookups, debugging, or questions answerable with 1-2 searches.
----
-
-# Deep Research
-
-## Core Purpose
-
-Deliver citation-tracked research reports through a structured pipeline with evidence persistence, source identity management, claim-level verification, and progressive context management.
-
-**Autonomy Principle:** Operate independently. Infer assumptions from context. Only stop for critical errors or incomprehensible queries. Surface high-materiality assumptions explicitly in the Introduction and Methodology rather than silently defaulting.
-
----
-
-## Decision Tree
-
-```
-Request Analysis
-+-- Simple lookup? --> STOP: Use WebSearch
-+-- Debugging? --> STOP: Use standard tools
-+-- Complex analysis needed? --> CONTINUE
-
-Mode Selection
-+-- Initial exploration --> quick (3 phases, 2-5 min)
-+-- Standard research --> standard (6 phases, 5-10 min) [DEFAULT]
-+-- Critical decision --> deep (8 phases, 10-20 min)
-+-- Comprehensive review --> ultradeep (8+ phases, 20-45 min)
-```
-
-**Default assumptions:** Technical query = technical audience. Comparison = balanced perspective. Trend = recent 1-2 years.
-
----
-
-## Workflow Overview
-
-| Phase | Name | Quick | Std | Deep | Ultra |
-|-------|------|-------|-----|------|-------|
-| 1 | SCOPE | Y | Y | Y | Y |
-| 2 | PLAN | - | Y | Y | Y |
-| 3 | RETRIEVE | Y | Y | Y | Y |
-| 4 | TRIANGULATE | - | Y | Y | Y |
-| 4.5 | OUTLINE REFINEMENT | - | Y | Y | Y |
-| 5 | SYNTHESIZE | - | Y | Y | Y |
-| 6 | CRITIQUE | - | - | Y | Y |
-| 7 | REFINE | - | - | Y | Y |
-| 8 | PACKAGE | Y | Y | Y | Y |
-
-**Note:** Phases 3-5 operate as an evidence loop per section (retrieve → evidence store → refine outline → draft → verify claims → delta-retrieve if needed), not as strict sequential gates.
-
----
-
-## Execution
-
-**On invocation, load relevant reference files:**
-
-1. **Phase 1-7:** Load [methodology.md](./reference/methodology.md) for detailed phase instructions
-2. **Phase 8 (Report):** Load [report-assembly.md](./reference/report-assembly.md) for progressive generation
-3. **HTML/PDF output:** Load [html-generation.md](./reference/html-generation.md)
-4. **Quality checks:** Load [quality-gates.md](./reference/quality-gates.md)
-5. **Long reports (>18K words):** Load [continuation.md](./reference/continuation.md)
-
-**Templates:**
-- Report structure: [report_template.md](./templates/report_template.md)
-- HTML styling: [mckinsey_report_template.html](./templates/mckinsey_report_template.html)
-
-**Scripts:**
-- `python scripts/validate_report.py --report [path]`
-- `python scripts/verify_citations.py --report [path]`
-- `python scripts/md_to_html.py [markdown_path]`
-
----
-
-## Output Contract
-
-**Required sections:**
-- Executive Summary (200-400 words)
-- Introduction (scope, methodology, assumptions)
-- Main Analysis (4-8 findings, 600-2,000 words each, cited)
-- Synthesis & Insights (patterns, implications)
-- Limitations & Caveats
-- Recommendations
-- Bibliography (COMPLETE - every citation, no placeholders)
-- Methodology Appendix
-
-**Output files (all to `~/Documents/[Topic]_Research_[YYYYMMDD]/`):**
-- Markdown (primary source of truth)
-- `sources.jsonl` — stable source registry with canonical IDs
-- `evidence.jsonl` — append-only evidence store with quotes and locators
-- `claims.jsonl` — atomic claim ledger with support status
-- `run_manifest.json` — query, mode, assumptions, provider config
-- HTML (McKinsey style, auto-opened)
-- PDF (professional print, auto-opened)
-
-**Quality standards:**
-- 10+ sources, 3+ per major claim (cluster-independent, not just count)
-- All factual claims cited immediately [N] with evidence backing in `evidence.jsonl`
-- Claim-support verification mandatory: no unsupported factual claims pass delivery
-- No placeholders, no fabricated citations
-- Prose-first (>=80%), bullets sparingly
-
----
-
-## When to Use / NOT Use
-
-**Use:** Comprehensive analysis, technology comparisons, state-of-the-art reviews, multi-perspective investigation, market analysis.
-
-**Do NOT use:** Simple lookups, debugging, 1-2 search answers, quick time-sensitive queries.