# tela - Doramagic AI Context Pack

> 定位：安装前体验与判断资产。它帮助宿主 AI 有一个好的开始，但不代表已经安装、执行或验证目标项目。

## 充分原则

- **充分原则，不是压缩原则**：AI Context Pack 应该充分到让宿主 AI 在开工前理解项目价值、能力边界、使用入口、风险和证据来源；它可以分层组织，但不以最短摘要为目标。
- **压缩策略**：只压缩噪声和重复内容，不压缩会影响判断和开工质量的上下文。

## 给宿主 AI 的使用方式

你正在读取 Doramagic 为 tela 编译的 AI Context Pack。请把它当作开工前上下文：帮助用户理解适合谁、能做什么、如何开始、哪些必须安装后验证、风险在哪里。不要声称你已经安装、运行或执行了目标项目。

## Claim 消费规则

- **事实来源**：Repo Evidence + Claim/Evidence Graph；Human Wiki 只提供显著性、术语和叙事结构。
- **事实最低状态**：`supported`
- `supported`：可以作为项目事实使用，但回答中必须引用 claim_id 和证据路径。
- `weak`：只能作为低置信度线索，必须要求用户继续核实。
- `inferred`：只能用于风险提示或待确认问题，不能包装成项目事实。
- `unverified`：不得作为事实使用，应明确说证据不足。
- `contradicted`：必须展示冲突来源，不得替用户强行选择一个版本。

## 它最适合谁

- **正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**：README 或插件配置提到多个宿主 AI。 证据：`README.md` Claim：`clm_0002` supported 0.86

## 它能做什么

- **命令行启动或安装流程**（需要安装后验证）：项目文档中存在可执行命令，真实使用需要在本地或宿主环境中运行这些命令。 证据：`README.md` Claim：`clm_0001` supported 0.86

## 怎么开始

- `git clone https://github.com/zcag/tela.git` 证据：`README.md` Claim：`clm_0003` supported 0.86
- `claude mcp add --transport http tela https://telawiki.com/api/mcp` 证据：`README.md` Claim：`clm_0004` supported 0.86

## 继续前判断卡

- **当前建议**：需要管理员/安全审批
- **为什么**：继续前可能涉及密钥、账号、外部服务或敏感上下文，建议先经过管理员或安全审批。

### 30 秒判断

- **现在怎么做**：需要管理员/安全审批
- **最小安全下一步**：先跑 Prompt Preview；若涉及凭证或企业环境，先审批再试装
- **先别相信**：角色质量和任务匹配不能直接相信。
- **继续会触碰**：角色选择偏差、命令执行、宿主 AI 配置

### 现在可以相信

- **适合人群线索：正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0002` supported 0.86
- **能力存在：命令行启动或安装流程**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`README.md` Claim：`clm_0001` supported 0.86
- **存在 Quick Start / 安装命令线索**（supported）：可以相信项目文档出现过启动或安装入口；不要因此直接在主力环境运行。 证据：`README.md` Claim：`clm_0003` supported 0.86

### 现在还不能相信

- **角色质量和任务匹配不能直接相信。**（unverified）：角色库证明有很多角色，不证明每个角色都适合你的具体任务，也不证明角色能产生高质量结果。
- **不能把角色文案当成真实执行能力。**（unverified）：安装前只能判断角色描述和任务画像是否匹配，不能证明它能在宿主 AI 里完成任务。
- **真实输出质量不能在安装前相信。**（unverified）：Prompt Preview 只能展示引导方式，不能证明真实项目中的结果质量。
- **宿主 AI 版本兼容性不能在安装前相信。**（unverified）：Claude、Cursor、Codex、Gemini 等宿主加载规则和版本差异必须在真实环境验证。
- **不会污染现有宿主 AI 行为，不能直接相信。**（inferred）：Skill、plugin、AGENTS/CLAUDE/GEMINI 指令可能改变宿主 AI 的默认行为。 证据：`CLAUDE.md`
- **可安全回滚不能默认相信。**（unverified）：除非项目明确提供卸载和恢复说明，否则必须先在隔离环境验证。
- **真实安装后是否与用户当前宿主 AI 版本兼容？**（unverified）：兼容性只能通过实际宿主环境验证。
- **项目输出质量是否满足用户具体任务？**（unverified）：安装前预览只能展示流程和边界，不能替代真实评测。

### 继续会触碰什么

- **角色选择偏差**：用户对任务应该由哪个专家角色处理的判断。 原因：选错角色会让 AI 从错误专业视角回答，浪费时间或误导决策。
- **命令执行**：包管理器、网络下载、本地插件目录、项目配置或用户主目录。 原因：运行第一条命令就可能产生环境改动；必须先判断是否值得跑。 证据：`README.md`
- **宿主 AI 配置**：Claude/Codex/Cursor/Gemini/OpenCode 等宿主的 plugin、Skill 或规则加载配置。 原因：宿主配置会改变 AI 后续工作方式，可能和用户已有规则冲突。 证据：`CLAUDE.md`
- **本地环境或项目文件**：安装结果、插件缓存、项目配置或本地依赖目录。 原因：安装前无法证明写入范围和回滚方式，需要隔离验证。 证据：`README.md`
- **环境变量 / API Key**：项目入口文档明确出现 API key、token、secret 或账号凭证配置。 原因：如果真实安装需要凭证，应先使用测试凭证并经过权限/合规判断。 证据：`CLAUDE.md`, `README.md`, `docs/architecture.md`, `docs/atlas.md` 等
- **宿主 AI 上下文**：AI Context Pack、Prompt Preview、Skill 路由、风险规则和项目事实。 原因：导入上下文会影响宿主 AI 后续判断，必须避免把未验证项包装成事实。

### 最小安全下一步

- **先跑 Prompt Preview**：先用交互式试用验证任务画像和角色匹配，不要先导入整套角色库。（适用：任何项目都适用，尤其是输出质量未知时。）
- **只在隔离目录或测试账号试装**：避免安装命令污染主力宿主 AI、真实项目或用户主目录。（适用：存在命令执行、插件配置或本地写入线索时。）
- **先备份宿主 AI 配置**：Skill、plugin、规则文件可能改变 Claude/Cursor/Codex 的默认行为。（适用：存在插件 manifest、Skill 或宿主规则入口时。）
- **不要使用真实生产凭证**：环境变量/API key 一旦进入宿主或工具链，可能产生账号和合规风险。（适用：出现 API、TOKEN、KEY、SECRET 等环境线索时。）
- **安装后只验证一个最小任务**：先验证加载、兼容、输出质量和回滚，再决定是否深用。（适用：准备从试用进入真实工作流时。）

### 退出方式

- **保留安装前状态**：记录原始宿主配置和项目状态，后续才能判断是否可恢复。
- **准备移除宿主 plugin / Skill / 规则入口**：如果试装后行为异常，可以把宿主 AI 恢复到试装前状态。
- **保留原始角色选择记录**：如果输出偏题，可以回到任务画像阶段重新选择角色，而不是继续沿着错误角色推进。
- **记录安装命令和写入路径**：没有明确卸载说明时，至少要知道哪些目录或配置需要手动清理。
- **准备撤销测试 API key 或 token**：测试凭证泄露或误用时，可以快速止损。
- **如果没有回滚路径，不进入主力环境**：不可回滚是继续前阻断项，不应靠信任或运气继续。

## 哪些只能预览

- 解释项目适合谁和能做什么
- 基于项目文档演示典型对话流程
- 帮助用户判断是否值得安装或继续研究

## 哪些必须安装后验证

- 真实安装 Skill、插件或 CLI
- 执行脚本、修改本地文件或访问外部服务
- 验证真实输出质量、性能和兼容性

## 边界与风险判断卡

- **把安装前预览误认为真实运行**：用户可能高估项目已经完成的配置、权限和兼容性验证。 处理方式：明确区分 prompt_preview_can_do 与 runtime_required。 Claim：`clm_0005` inferred 0.45
- **命令执行会修改本地环境**：安装命令可能写入用户主目录、宿主插件目录或项目配置。 处理方式：先在隔离环境或测试账号中运行。 证据：`README.md` Claim：`clm_0006` supported 0.86
- **待确认**：真实安装后是否与用户当前宿主 AI 版本兼容？。原因：兼容性只能通过实际宿主环境验证。
- **待确认**：项目输出质量是否满足用户具体任务？。原因：安装前预览只能展示流程和边界，不能替代真实评测。
- **待确认**：安装命令是否需要网络、权限或全局写入？。原因：这影响企业环境和个人环境的安装风险。

## 开工前工作上下文

### 加载顺序

- 先读取 how_to_use.host_ai_instruction，建立安装前判断资产的边界。
- 读取 claim_graph_summary，确认事实来自 Claim/Evidence Graph，而不是 Human Wiki 叙事。
- 再读取 intended_users、capabilities 和 quick_start_candidates，判断用户是否匹配。
- 需要执行具体任务时，优先查 role_skill_index，再查 evidence_index。
- 遇到真实安装、文件修改、网络访问、性能或兼容性问题时，转入 risk_card 和 boundaries.runtime_required。

### 任务路由

- **命令行启动或安装流程**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`README.md` Claim：`clm_0001` supported 0.86

### 上下文规模

- 文件总数：2533
- 重要文件覆盖：40/2533
- 证据索引条目：80
- 角色 / Skill 条目：42

### 证据不足时的处理

- **missing_evidence**：说明证据不足，要求用户提供目标文件、README 段落或安装后验证记录；不要补全事实。
- **out_of_scope_request**：说明该任务超出当前 AI Context Pack 证据范围，并建议用户先查看 Human Manual 或真实安装后验证。
- **runtime_request**：给出安装前检查清单和命令来源，但不要替用户执行命令或声称已执行。
- **source_conflict**：同时展示冲突来源，标记为待核实，不要强行选择一个版本。

## Prompt Recipes

### 适配判断

- 目标：判断这个项目是否适合用户当前任务。
- 预期输出：适配结论、关键理由、证据引用、安装前可预览内容、必须安装后验证内容、下一步建议。

```text
请基于 tela 的 AI Context Pack，先问我 3 个必要问题，然后判断它是否适合我的任务。回答必须包含：适合谁、能做什么、不能做什么、是否值得安装、证据来自哪里。所有项目事实必须引用 evidence_refs、source_paths 或 claim_id。
```

### 安装前体验

- 目标：让用户在安装前感受核心工作流，同时避免把预览包装成真实能力或营销承诺。
- 预期输出：一段带边界标签的体验剧本、安装后验证清单和谨慎建议；不含真实运行承诺或强营销表述。

```text
请把 tela 当作安装前体验资产，而不是已安装工具或真实运行环境。

请严格输出四段：
1. 先问我 3 个必要问题。
2. 给出一段“体验剧本”：用 [安装前可预览]、[必须安装后验证]、[证据不足] 三种标签展示它可能如何引导工作流。
3. 给出安装后验证清单：列出哪些能力只有真实安装、真实宿主加载、真实项目运行后才能确认。
4. 给出谨慎建议：只能说“值得继续研究/试装”“先补充信息后再判断”或“不建议继续”，不得替项目背书。

硬性边界：
- 不要声称已经安装、运行、执行测试、修改文件或产生真实结果。
- 不要写“自动适配”“确保通过”“完美适配”“强烈建议安装”等承诺性表达。
- 如果描述安装后的工作方式，必须使用“如果安装成功且宿主正确加载 Skill，它可能会……”这种条件句。
- 体验剧本只能写成“示例台词/假设流程”：使用“可能会询问/可能会建议/可能会展示”，不要写“已写入、已生成、已通过、正在运行、正在生成”。
- Prompt Preview 不负责给安装命令；如用户准备试装，只能提示先阅读 Quick Start 和 Risk Card，并在隔离环境验证。
- 所有项目事实必须来自 supported claim、evidence_refs 或 source_paths；inferred/unverified 只能作风险或待确认项。

```

### 角色 / Skill 选择

- 目标：从项目里的角色或 Skill 中挑选最匹配的资产。
- 预期输出：候选角色或 Skill 列表，每项包含适用场景、证据路径、风险边界和是否需要安装后验证。

```text
请读取 role_skill_index，根据我的目标任务推荐 3-5 个最相关的角色或 Skill。每个推荐都要说明适用场景、可能输出、风险边界和 evidence_refs。
```

### 风险预检

- 目标：安装或引入前识别环境、权限、规则冲突和质量风险。
- 预期输出：环境、权限、依赖、许可、宿主冲突、质量风险和未知项的检查清单。

```text
请基于 risk_card、boundaries 和 quick_start_candidates，给我一份安装前风险预检清单。不要替我执行命令，只说明我应该检查什么、为什么检查、失败会有什么影响。
```

### 宿主 AI 开工指令

- 目标：把项目上下文转成一次对话开始前的宿主 AI 指令。
- 预期输出：一段边界明确、证据引用明确、适合复制给宿主 AI 的开工前指令。

```text
请基于 tela 的 AI Context Pack，生成一段我可以粘贴给宿主 AI 的开工前指令。这段指令必须遵守 not_runtime=true，不能声称项目已经安装、运行或产生真实结果。
```

## 角色 / Skill 索引

- 共索引 42 个角色 / Skill / 项目文档条目。

- **Submission assets**（project_doc）：Widget screenshots + app icon for the Claude / ChatGPT directory submissions. Rendered from the real widget bundles backend/internal/api/widgets/ .html with demo-account data, cropped to just the app response per both forms' guidance . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/submission-assets/README.md`
- **tela**（project_doc）：The wiki that writes itself — from the code you already ship. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`README.md`
- **deck — Slidev render sidecar**（project_doc）：A tela deck is a page whose body is Slidev markdown whole page — a page is either a deck or a doc, set by deck: true . Two output paths off the same parse + theme-injection core: 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`deck/README.md`
- **tela — frontend**（project_doc）：React 19 + TypeScript + Vite SPA for tela ../README.md . Tailwind v4 + Radix + Milkdown editor + TanStack Query/Router + Orama + cmdk + Lucide + Storybook. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`frontend/README.md`
- **tela landing**（project_doc）：The standalone marketing landing page for tela — a separate Astro static site, in the same repo as the app but built and deployed independently. backend/ and frontend/ are untouched by this. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`landing/README.md`
- **tela-mcp**（project_doc）：A thin stdio↔HTTP proxy to a Tela https://telawiki.com instance's built-in MCP server. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`mcp/README.md`
- **internal/rag — semantic retrieval**（project_doc）：Self-contained hybrid retrieval over pages : heading-aware markdown chunking, pluggable embeddings, and RRF-fused lexical + vector chunk search on Postgres + pgvector. Agent-first — no answer-LLM; every hit carries a citation page id + heading path . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/internal/rag/README.md`
- **JWK Set JSON Web Key Set**（project_doc）：! Go Reference https://pkg.go.dev/badge/github.com/MicahParks/jwkset.svg https://pkg.go.dev/github.com/MicahParks/jwkset 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/MicahParks/jwkset/README.md`
- **keyfunc**（project_doc）：! Go Reference https://pkg.go.dev/badge/github.com/MicahParks/keyfunc/v3.svg https://pkg.go.dev/github.com/MicahParks/keyfunc/v3 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/MicahParks/keyfunc/v3/README.md`
- **xxhash**（project_doc）：! Go Reference https://pkg.go.dev/badge/github.com/cespare/xxhash/v2.svg https://pkg.go.dev/github.com/cespare/xxhash/v2 ! Test https://github.com/cespare/xxhash/actions/workflows/test.yml/badge.svg https://github.com/cespare/xxhash/actions/workflows/test.yml 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/cespare/xxhash/v2/README.md`
- **websocket**（project_doc）：! Go Reference https://pkg.go.dev/badge/github.com/coder/websocket.svg https://pkg.go.dev/github.com/coder/websocket ! Go Coverage https://coder.github.io/websocket/coverage.svg https://coder.github.io/websocket/coverage.html 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/coder/websocket/README.md`
- **Go JOSE**（project_doc）：! godoc https://pkg.go.dev/badge/github.com/go-jose/go-jose/v4.svg https://pkg.go.dev/github.com/go-jose/go-jose/v4 ! godoc https://pkg.go.dev/badge/github.com/go-jose/go-jose/v4/jwt.svg https://pkg.go.dev/github.com/go-jose/go-jose/v4/jwt ! license https://img.shields.io/badge/license-apache 2.0-blue.svg?style=flat https://raw.githubusercontent.com/go-jose/go-jose/master/LICENSE 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/go-jose/go-jose/v4/README.md`
- **Safe JSON**（project_doc）：This repository contains a fork of the encoding/json package from Go 1.6. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/go-jose/go-jose/v4/json/README.md`
- **jwt-go**（project_doc）：! build https://github.com/golang-jwt/jwt/actions/workflows/build.yml/badge.svg https://github.com/golang-jwt/jwt/actions/workflows/build.yml ! Go Reference https://pkg.go.dev/badge/github.com/golang-jwt/jwt/v5.svg https://pkg.go.dev/github.com/golang-jwt/jwt/v5 ! Coverage Status https://coveralls.io/repos/github/golang-jwt/jwt/badge.svg?branch=main https://coveralls.io/github/golang-jwt/jwt?branch=main 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/golang-jwt/jwt/v5/README.md`
- **pgpassfile**（project_doc）：! https://godoc.org/github.com/jackc/pgpassfile?status.svg https://godoc.org/github.com/jackc/pgpassfile ! Build Status https://travis-ci.org/jackc/pgpassfile.svg https://travis-ci.org/jackc/pgpassfile 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/jackc/pgpassfile/README.md`
- **pgservicefile**（project_doc）：! Go Reference https://pkg.go.dev/badge/github.com/jackc/pgservicefile.svg https://pkg.go.dev/github.com/jackc/pgservicefile ! Build Status https://github.com/jackc/pgservicefile/actions/workflows/ci.yml/badge.svg https://github.com/jackc/pgservicefile/actions/workflows/ci.yml 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/jackc/pgservicefile/README.md`
- **pgx - PostgreSQL Driver and Toolkit**（project_doc）：! Go Reference https://pkg.go.dev/badge/github.com/jackc/pgx/v5.svg https://pkg.go.dev/github.com/jackc/pgx/v5 ! Build Status https://github.com/jackc/pgx/actions/workflows/ci.yml/badge.svg https://github.com/jackc/pgx/actions/workflows/ci.yml 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/jackc/pgx/v5/README.md`
- **pgio**（project_doc）：Package pgio is a low-level toolkit building messages in the PostgreSQL wire protocol. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/jackc/pgx/v5/internal/pgio/README.md`
- **pgconn**（project_doc）：Package pgconn is a low-level PostgreSQL database driver. It operates at nearly the same level as the C library libpq. It is primarily intended to serve as the foundation for higher level libraries such as https://github.com/jackc/pgx. Applications should handle normal queries with a higher level library and only use pgconn directly when required for low-level access to PostgreSQL functionality. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/jackc/pgx/v5/pgconn/README.md`
- **pgproto3**（project_doc）：Package pgproto3 is an encoder and decoder of the PostgreSQL wire protocol version 3. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/jackc/pgx/v5/pgproto3/README.md`
- **Puddle**（project_doc）：! Go Reference https://pkg.go.dev/badge/github.com/jackc/puddle/v2.svg https://pkg.go.dev/github.com/jackc/puddle/v2 ! Build Status https://github.com/jackc/puddle/actions/workflows/ci.yml/badge.svg 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/jackc/puddle/v2/README.md`
- **PDF Reader**（project_doc）：! Built with WeBuild https://raw.githubusercontent.com/webuild-community/badge/master/svg/WeBuild.svg https://webuild.community 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/ledongthuc/pdf/README.md`
- **Readme**（project_doc）：See ! Go Reference https://pkg.go.dev/badge/github.com/prometheus/client golang/prometheus.svg https://pkg.go.dev/github.com/prometheus/client golang/prometheus . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/prometheus/client_golang/prometheus/README.md`
- **procfs**（project_doc）：This package provides functions to retrieve system, kernel, and process metrics from the pseudo-filesystems /proc and /sys. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/prometheus/procfs/README.md`
- **encoding/json ! GoDoc https://godoc.org/github.com/segmentio/encoding/json?status.svg https://godoc.org/github.com/segm…**（project_doc）：encoding/json ! GoDoc https://godoc.org/github.com/segmentio/encoding/json?status.svg https://godoc.org/github.com/segmentio/encoding/json 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/segmentio/encoding/json/README.md`
- **go-mail - Easy to use, yet comprehensive library for sending mails with Go**（project_doc）：<!-- SPDX-FileCopyrightText: The go-mail Authors 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/wneessen/go-mail/README.md`
- **Parser options**（project_doc）：goldmark ========================================== 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/yuin/goldmark/README.md`
- **defterparse — Tier-1 pure-text Go layer for Defter**（project_doc）：defterparse — Tier-1 pure-text Go layer for Defter 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/zcag/defter/go/README.md`
- **YAML support for the Go language**（project_doc）：The yaml package enables Go programs to comfortably encode and decode YAML values. It was developed within Canonical https://www.canonical.com as part of the juju https://juju.ubuntu.com project, and is based on a pure Go port of the well-known libyaml http://pyyaml.org/wiki/LibYAML C library to parse and generate YAML data quickly and reliably. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/go.yaml.in/yaml/v2/README.md`
- **OAuth2 for Go**（project_doc）：! Go Reference https://pkg.go.dev/badge/golang.org/x/oauth2.svg https://pkg.go.dev/golang.org/x/oauth2 ! Build Status https://travis-ci.org/golang/oauth2.svg?branch=master https://travis-ci.org/golang/oauth2 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/golang.org/x/oauth2/README.md`
- **Building sys/unix**（project_doc）：The sys/unix package provides access to the raw system call interface of the underlying operating system. See: https://godoc.org/golang.org/x/sys/unix 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/golang.org/x/sys/unix/README.md`
- **YAML support for the Go language**（project_doc）：The yaml package enables Go programs to comfortably encode and decode YAML values. It was developed within Canonical https://www.canonical.com as part of the juju https://juju.ubuntu.com project, and is based on a pure Go port of the well-known libyaml http://pyyaml.org/wiki/LibYAML C library to parse and generate YAML data quickly and reliably. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/gopkg.in/yaml.v3/README.md`
- **tela Claude Desktop extension .dxt**（project_doc）：A one-click Desktop Extension https://github.com/anthropics/dxt that wraps the tela-mcp stdio proxy. Installing it in Claude Desktop prompts for your tela base URL + API token — no hand-edited claude desktop config.json . 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`mcp/dxt/README.md`
- **CLAUDE.md — tela**（project_doc）：Working context for tela. Read before contributing. Full architecture is in docs/ docs/ and the deepest subsystem detail in docs/architecture.md docs/architecture.md ; this file is the conventions + hard rules + the things that bite. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`CLAUDE.md`
- **tela — Architecture**（project_doc）：1. Backend Go — REST API over PostgreSQL; auth, collab WebSocket, business logic. 2. Frontend React + TS — SPA, Milkdown editor, talks to the backend over REST + a WebSocket for live collab. 3. MCP server TypeScript — exposes tela to AI agents over the Model Context Protocol; a thin bearer-authed client over the REST API. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/architecture.md`
- **tela — Decisions ADR-lite**（project_doc）：Each entry: context → decision → consequence. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/decisions.md`
- **CLAUDE.md**（project_doc）：This file provides guidance to Claude Code claude.ai/code when working with code in this repository. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/jackc/pgx/v5/CLAUDE.md`
- **Contributing**（project_doc）：If you would like to contribute code to go-jose you can do so through GitHub by forking the repository and sending a pull request. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/go-jose/go-jose/v4/CONTRIBUTING.md`
- **Contributing**（project_doc）：Before you invest a significant amount of time on a change, please create a discussion or issue describing your proposal. This will help to ensure your proposed change has a reasonable chance of being merged. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/jackc/pgx/v5/CONTRIBUTING.md`
- **Contributing**（project_doc）：Prometheus uses GitHub to manage reviews of pull requests. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/prometheus/procfs/CONTRIBUTING.md`
- **How to contribute**（project_doc）：<!-- SPDX-FileCopyrightText: The go-mail Authors 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/github.com/wneessen/go-mail/CONTRIBUTING.md`
- **Contributing to Go**（project_doc）：It is the work of hundreds of contributors. We appreciate your help! 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`backend/vendor/golang.org/x/oauth2/CONTRIBUTING.md`

## 证据索引

- 共索引 80 条证据。

- **Submission assets**（documentation）：Widget screenshots + app icon for the Claude / ChatGPT directory submissions. Rendered from the real widget bundles backend/internal/api/widgets/ .html with demo-account data, cropped to just the app response per both forms' guidance . 证据：`docs/submission-assets/README.md`
- **tela**（documentation）：The wiki that writes itself — from the code you already ship. 证据：`README.md`
- **deck — Slidev render sidecar**（documentation）：A tela deck is a page whose body is Slidev markdown whole page — a page is either a deck or a doc, set by deck: true . Two output paths off the same parse + theme-injection core: 证据：`deck/README.md`
- **tela — frontend**（documentation）：React 19 + TypeScript + Vite SPA for tela ../README.md . Tailwind v4 + Radix + Milkdown editor + TanStack Query/Router + Orama + cmdk + Lucide + Storybook. 证据：`frontend/README.md`
- **tela landing**（documentation）：The standalone marketing landing page for tela — a separate Astro static site, in the same repo as the app but built and deployed independently. backend/ and frontend/ are untouched by this. 证据：`landing/README.md`
- **tela-mcp**（documentation）：A thin stdio↔HTTP proxy to a Tela https://telawiki.com instance's built-in MCP server. 证据：`mcp/README.md`
- **internal/rag — semantic retrieval**（documentation）：Self-contained hybrid retrieval over pages : heading-aware markdown chunking, pluggable embeddings, and RRF-fused lexical + vector chunk search on Postgres + pgvector. Agent-first — no answer-LLM; every hit carries a citation page id + heading path . 证据：`backend/internal/rag/README.md`
- **JWK Set JSON Web Key Set**（documentation）：! Go Reference https://pkg.go.dev/badge/github.com/MicahParks/jwkset.svg https://pkg.go.dev/github.com/MicahParks/jwkset 证据：`backend/vendor/github.com/MicahParks/jwkset/README.md`
- **keyfunc**（documentation）：! Go Reference https://pkg.go.dev/badge/github.com/MicahParks/keyfunc/v3.svg https://pkg.go.dev/github.com/MicahParks/keyfunc/v3 证据：`backend/vendor/github.com/MicahParks/keyfunc/v3/README.md`
- **xxhash**（documentation）：! Go Reference https://pkg.go.dev/badge/github.com/cespare/xxhash/v2.svg https://pkg.go.dev/github.com/cespare/xxhash/v2 ! Test https://github.com/cespare/xxhash/actions/workflows/test.yml/badge.svg https://github.com/cespare/xxhash/actions/workflows/test.yml 证据：`backend/vendor/github.com/cespare/xxhash/v2/README.md`
- **websocket**（documentation）：! Go Reference https://pkg.go.dev/badge/github.com/coder/websocket.svg https://pkg.go.dev/github.com/coder/websocket ! Go Coverage https://coder.github.io/websocket/coverage.svg https://coder.github.io/websocket/coverage.html 证据：`backend/vendor/github.com/coder/websocket/README.md`
- **Go JOSE**（documentation）：! godoc https://pkg.go.dev/badge/github.com/go-jose/go-jose/v4.svg https://pkg.go.dev/github.com/go-jose/go-jose/v4 ! godoc https://pkg.go.dev/badge/github.com/go-jose/go-jose/v4/jwt.svg https://pkg.go.dev/github.com/go-jose/go-jose/v4/jwt ! license https://img.shields.io/badge/license-apache 2.0-blue.svg?style=flat https://raw.githubusercontent.com/go-jose/go-jose/master/LICENSE 证据：`backend/vendor/github.com/go-jose/go-jose/v4/README.md`
- **Safe JSON**（documentation）：This repository contains a fork of the encoding/json package from Go 1.6. 证据：`backend/vendor/github.com/go-jose/go-jose/v4/json/README.md`
- **jwt-go**（documentation）：! build https://github.com/golang-jwt/jwt/actions/workflows/build.yml/badge.svg https://github.com/golang-jwt/jwt/actions/workflows/build.yml ! Go Reference https://pkg.go.dev/badge/github.com/golang-jwt/jwt/v5.svg https://pkg.go.dev/github.com/golang-jwt/jwt/v5 ! Coverage Status https://coveralls.io/repos/github/golang-jwt/jwt/badge.svg?branch=main https://coveralls.io/github/golang-jwt/jwt?branch=main 证据：`backend/vendor/github.com/golang-jwt/jwt/v5/README.md`
- **pgpassfile**（documentation）：! https://godoc.org/github.com/jackc/pgpassfile?status.svg https://godoc.org/github.com/jackc/pgpassfile ! Build Status https://travis-ci.org/jackc/pgpassfile.svg https://travis-ci.org/jackc/pgpassfile 证据：`backend/vendor/github.com/jackc/pgpassfile/README.md`
- **pgservicefile**（documentation）：! Go Reference https://pkg.go.dev/badge/github.com/jackc/pgservicefile.svg https://pkg.go.dev/github.com/jackc/pgservicefile ! Build Status https://github.com/jackc/pgservicefile/actions/workflows/ci.yml/badge.svg https://github.com/jackc/pgservicefile/actions/workflows/ci.yml 证据：`backend/vendor/github.com/jackc/pgservicefile/README.md`
- **pgx - PostgreSQL Driver and Toolkit**（documentation）：! Go Reference https://pkg.go.dev/badge/github.com/jackc/pgx/v5.svg https://pkg.go.dev/github.com/jackc/pgx/v5 ! Build Status https://github.com/jackc/pgx/actions/workflows/ci.yml/badge.svg https://github.com/jackc/pgx/actions/workflows/ci.yml 证据：`backend/vendor/github.com/jackc/pgx/v5/README.md`
- **pgio**（documentation）：Package pgio is a low-level toolkit building messages in the PostgreSQL wire protocol. 证据：`backend/vendor/github.com/jackc/pgx/v5/internal/pgio/README.md`
- **pgconn**（documentation）：Package pgconn is a low-level PostgreSQL database driver. It operates at nearly the same level as the C library libpq. It is primarily intended to serve as the foundation for higher level libraries such as https://github.com/jackc/pgx. Applications should handle normal queries with a higher level library and only use pgconn directly when required for low-level access to PostgreSQL functionality. 证据：`backend/vendor/github.com/jackc/pgx/v5/pgconn/README.md`
- **pgproto3**（documentation）：Package pgproto3 is an encoder and decoder of the PostgreSQL wire protocol version 3. 证据：`backend/vendor/github.com/jackc/pgx/v5/pgproto3/README.md`
- **Puddle**（documentation）：! Go Reference https://pkg.go.dev/badge/github.com/jackc/puddle/v2.svg https://pkg.go.dev/github.com/jackc/puddle/v2 ! Build Status https://github.com/jackc/puddle/actions/workflows/ci.yml/badge.svg 证据：`backend/vendor/github.com/jackc/puddle/v2/README.md`
- **PDF Reader**（documentation）：! Built with WeBuild https://raw.githubusercontent.com/webuild-community/badge/master/svg/WeBuild.svg https://webuild.community 证据：`backend/vendor/github.com/ledongthuc/pdf/README.md`
- **Readme**（documentation）：See ! Go Reference https://pkg.go.dev/badge/github.com/prometheus/client golang/prometheus.svg https://pkg.go.dev/github.com/prometheus/client golang/prometheus . 证据：`backend/vendor/github.com/prometheus/client_golang/prometheus/README.md`
- **procfs**（documentation）：This package provides functions to retrieve system, kernel, and process metrics from the pseudo-filesystems /proc and /sys. 证据：`backend/vendor/github.com/prometheus/procfs/README.md`
- **encoding/json ! GoDoc https://godoc.org/github.com/segmentio/encoding/json?status.svg https://godoc.org/github.com/segm…**（documentation）：encoding/json ! GoDoc https://godoc.org/github.com/segmentio/encoding/json?status.svg https://godoc.org/github.com/segmentio/encoding/json 证据：`backend/vendor/github.com/segmentio/encoding/json/README.md`
- **go-mail - Easy to use, yet comprehensive library for sending mails with Go**（documentation）：<!-- SPDX-FileCopyrightText: The go-mail Authors 证据：`backend/vendor/github.com/wneessen/go-mail/README.md`
- **Parser options**（documentation）：goldmark ========================================== 证据：`backend/vendor/github.com/yuin/goldmark/README.md`
- **defterparse — Tier-1 pure-text Go layer for Defter**（documentation）：defterparse — Tier-1 pure-text Go layer for Defter 证据：`backend/vendor/github.com/zcag/defter/go/README.md`
- **YAML support for the Go language**（documentation）：The yaml package enables Go programs to comfortably encode and decode YAML values. It was developed within Canonical https://www.canonical.com as part of the juju https://juju.ubuntu.com project, and is based on a pure Go port of the well-known libyaml http://pyyaml.org/wiki/LibYAML C library to parse and generate YAML data quickly and reliably. 证据：`backend/vendor/go.yaml.in/yaml/v2/README.md`
- **OAuth2 for Go**（documentation）：! Go Reference https://pkg.go.dev/badge/golang.org/x/oauth2.svg https://pkg.go.dev/golang.org/x/oauth2 ! Build Status https://travis-ci.org/golang/oauth2.svg?branch=master https://travis-ci.org/golang/oauth2 证据：`backend/vendor/golang.org/x/oauth2/README.md`
- **Building sys/unix**（documentation）：The sys/unix package provides access to the raw system call interface of the underlying operating system. See: https://godoc.org/golang.org/x/sys/unix 证据：`backend/vendor/golang.org/x/sys/unix/README.md`
- **YAML support for the Go language**（documentation）：The yaml package enables Go programs to comfortably encode and decode YAML values. It was developed within Canonical https://www.canonical.com as part of the juju https://juju.ubuntu.com project, and is based on a pure Go port of the well-known libyaml http://pyyaml.org/wiki/LibYAML C library to parse and generate YAML data quickly and reliably. 证据：`backend/vendor/gopkg.in/yaml.v3/README.md`
- **tela Claude Desktop extension .dxt**（documentation）：A one-click Desktop Extension https://github.com/anthropics/dxt that wraps the tela-mcp stdio proxy. Installing it in Claude Desktop prompts for your tela base URL + API token — no hand-edited claude desktop config.json . 证据：`mcp/dxt/README.md`
- **Package**（package_manifest）：{ "name": "tela-deck-render", "version": "0.0.1", "private": true, "type": "module", "description": "Slidev render-only sidecar for tela — deck markdown in, per-slide PNGs + PDF/PPTX out.", "scripts": { "start": "node server.mjs" }, "dependencies": { "@defterjs/core": "^0.1.5", "@defterjs/formula": "^0.1.5", "@slidev/cli": "^52.16.0", "@slidev/parser": "^52.16.0", "echarts": "^5.5.0", "playwright-chromium": "1.60.0", "sharp": "^0.33.0", "slidev-theme-tahta": "^0.13.1" } } 证据：`deck/package.json`
- **Package**（package_manifest）：{ "name": "frontend", "private": true, "version": "0.0.0", "type": "module", "scripts": { "dev": "vite", "build": "tsc -b && vite build", "lint": "eslint .", "test:unit": "vitest run --project unit", "preview": "vite preview", "storybook": "storybook dev -p 6006", "build-storybook": "storybook build" }, "dependencies": { "@defterjs/core": "^0.2.0", "@defterjs/formula": "^0.2.0", "@defterjs/react": "^0.2.0", "@defterjs/xlsx": "^0.2.0", "@defterjs/yjs": "^0.2.0", "@excalidraw/excalidraw": "^0.18.1", "@mermaid-js/layout-elk": "^0.2.2", "@milkdown/kit": "^7.21.1", "@milkdown/plugin-prism": "^7.21.1", "@milkdown/react": "^7.21.1", "@orama/orama": "^3.1.18", "@prosemirror-adapter/react": "^0.5.3"… 证据：`frontend/package.json`
- **Package**（package_manifest）：{ "name": "tela-landing", "type": "module", "version": "0.0.1", "private": true, "description": "tela marketing landing — standalone Astro + Tailwind v4 OKLCH tokens + self-hosted Geist. Separate static build; backend/ + frontend/ untouched.", "engines": { "node": " =20.0.0" }, "scripts": { "dev": "astro dev", "build": "astro build", "preview": "astro preview", "astro": "astro", "gate:tokens": "playwright test token-conformance && stylelint \"src/ / .css\"", "gate:a11y": "playwright test a11y", "gate:motion": "playwright test reduced-motion", "gate:lh": "lhci autorun --config=lighthouserc.cjs", "gate:lh:mobile": "lhci autorun --config=lighthouserc.mobile.cjs", "gate:lh:showcase": "lhci auto… 证据：`landing/package.json`
- **Package**（package_manifest）：{ "name": "tela-mcp", "mcpName": "io.github.zcag/tela", "version": "0.7.4", "description": "MCP server for Tela — a self-hostable, markdown-native team wiki. Lets Claude, Cursor, and other agents search, read, and write your wiki pages. A stdio↔HTTP proxy to a Tela instance's built-in MCP server {TELA BASE URL}/api/mcp for hosts that can't speak HTTP transport directly.", "keywords": "mcp", "model-context-protocol", "wiki", "knowledge-base", "markdown", "documentation", "ai-agents", "claude", "cursor", "self-hosted", "tela" , "homepage": "https://telawiki.com", "repository": { "type": "git", "url": "git+https://github.com/zcag/tela.git", "directory": "mcp" }, "bugs": { "email": "tela@telawi… 证据：`mcp/package.json`
- **CLAUDE.md — tela**（documentation）：Working context for tela. Read before contributing. Full architecture is in docs/ docs/ and the deepest subsystem detail in docs/architecture.md docs/architecture.md ; this file is the conventions + hard rules + the things that bite. 证据：`CLAUDE.md`
- **tela — Architecture**（documentation）：1. Backend Go — REST API over PostgreSQL; auth, collab WebSocket, business logic. 2. Frontend React + TS — SPA, Milkdown editor, talks to the backend over REST + a WebSocket for live collab. 3. MCP server TypeScript — exposes tela to AI agents over the Model Context Protocol; a thin bearer-authed client over the REST API. 证据：`docs/architecture.md`
- **tela — Decisions ADR-lite**（documentation）：Each entry: context → decision → consequence. 证据：`docs/decisions.md`
- **CLAUDE.md**（documentation）：This file provides guidance to Claude Code claude.ai/code when working with code in this repository. 证据：`backend/vendor/github.com/jackc/pgx/v5/CLAUDE.md`
- **Contributing**（documentation）：If you would like to contribute code to go-jose you can do so through GitHub by forking the repository and sending a pull request. 证据：`backend/vendor/github.com/go-jose/go-jose/v4/CONTRIBUTING.md`
- **Contributing**（documentation）：Before you invest a significant amount of time on a change, please create a discussion or issue describing your proposal. This will help to ensure your proposed change has a reasonable chance of being merged. 证据：`backend/vendor/github.com/jackc/pgx/v5/CONTRIBUTING.md`
- **Contributing**（documentation）：Prometheus uses GitHub to manage reviews of pull requests. 证据：`backend/vendor/github.com/prometheus/procfs/CONTRIBUTING.md`
- **How to contribute**（documentation）：<!-- SPDX-FileCopyrightText: The go-mail Authors 证据：`backend/vendor/github.com/wneessen/go-mail/CONTRIBUTING.md`
- **Contributing to Go**（documentation）：It is the work of hundreds of contributors. We appreciate your help! 证据：`backend/vendor/golang.org/x/oauth2/CONTRIBUTING.md`
- **License**（source_file）：GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 证据：`LICENSE`
- **License**（source_file）：Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ 证据：`backend/vendor/github.com/MicahParks/jwkset/LICENSE`
- **License**（source_file）：Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ 证据：`backend/vendor/github.com/MicahParks/keyfunc/v3/LICENSE`
- **License**（source_file）：Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 证据：`backend/vendor/github.com/beorn7/perks/LICENSE`
- **License**（source_file）：Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ 证据：`backend/vendor/github.com/coreos/go-oidc/v3/LICENSE`
- **License**（source_file）：Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ 证据：`backend/vendor/github.com/go-jose/go-jose/v4/LICENSE`
- **License**（source_file）：Copyright c 2012 The Go Authors. All rights reserved. 证据：`backend/vendor/github.com/go-jose/go-jose/v4/json/LICENSE`
- **License**（source_file）：Copyright c 2012 Dave Grijalva Copyright c 2021 golang-jwt maintainers 证据：`backend/vendor/github.com/golang-jwt/jwt/v5/LICENSE`
- **License**（source_file）：Copyright c 2025 JSON Schema Go Project Authors 证据：`backend/vendor/github.com/google/jsonschema-go/LICENSE`
- **License**（source_file）：Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 证据：`backend/vendor/github.com/jackc/pgpassfile/LICENSE`
- **License**（source_file）：Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 证据：`backend/vendor/github.com/jackc/pgservicefile/LICENSE`
- **License**（source_file）：Copyright c 2013-2021 Jack Christensen 证据：`backend/vendor/github.com/jackc/pgx/v5/LICENSE`
- **License**（source_file）：Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 证据：`backend/vendor/github.com/jackc/puddle/v2/LICENSE`
- **License**（source_file）：Copyright c 2009 The Go Authors. All rights reserved. 证据：`backend/vendor/github.com/ledongthuc/pdf/LICENSE`
- 其余 20 条证据见 `AI_CONTEXT_PACK.json` 或 `EVIDENCE_INDEX.json`。

## 宿主 AI 必须遵守的规则

- **把本资产当作开工前上下文，而不是运行环境。**：AI Context Pack 只包含证据化项目理解，不包含目标项目的可执行状态。 证据：`docs/submission-assets/README.md`, `README.md`, `deck/README.md`
- **回答用户时区分可预览内容与必须安装后才能验证的内容。**：安装前体验的消费者价值来自降低误装和误判，而不是伪装成真实运行。 证据：`docs/submission-assets/README.md`, `README.md`, `deck/README.md`

## 用户开工前应该回答的问题

- 你准备在哪个宿主 AI 或本地环境中使用它？
- 你只是想先体验工作流，还是准备真实安装？
- 你最在意的是安装成本、输出质量、还是和现有规则的冲突？

## 验收标准

- 所有能力声明都能回指到 evidence_refs 中的文件路径。
- AI_CONTEXT_PACK.md 没有把预览包装成真实运行。
- 用户能在 3 分钟内看懂适合谁、能做什么、如何开始和风险边界。

---

## Doramagic Context Augmentation

下面内容用于强化 Repomix/AI Context Pack 主体。Human Manual 只提供阅读骨架；踩坑日志会被转成宿主 AI 必须遵守的工作约束。

## Human Manual 骨架

使用规则：这里只是项目阅读路线和显著性信号，不是事实权威。具体事实仍必须回到 repo evidence / Claim Graph。

宿主 AI 硬性规则：
- 不得把页标题、章节顺序、摘要或 importance 当作项目事实证据。
- 解释 Human Manual 骨架时，必须明确说它只是阅读路线/显著性信号。
- 能力、安装、兼容性、运行状态和风险判断必须引用 repo evidence、source path 或 Claim Graph。

- **概述与系统架构**：importance `high`
  - source_paths: README.md, docs/architecture.md, docs/decisions.md, backend/cmd/tela/main.go, backend/go.mod
- **核心功能、编辑器与协作**：importance `high`
  - source_paths: backend/internal/api/pages.go, backend/internal/api/spaces.go, backend/internal/api/dav.go, backend/internal/api/pages_ws.go, backend/internal/api/mcp_sheet_edit.go
- **AI 与 Agent 集成（Atlas / MCP / RAG）**：importance `high`
  - source_paths: backend/internal/atlas/engine/engine.go, backend/internal/atlas/engine/stage_outline.go, backend/internal/atlas/engine/stage_draft.go, backend/internal/atlas/engine/stage_publish.go, backend/internal/atlas/core/model.go
- **部署、运维与扩展**：importance `high`
  - source_paths: deploy/docker-compose.yml, deploy/docker-compose.split.yml, deploy/docker-compose.registry.yml, deploy/docker-compose.ai.yml, deploy/.env.example

## Repo Inspection Evidence / 源码检查证据

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `70a44d3ca09369e48012efc18bf062f70c49eb63`
- inspected_files: `README.md`, `docs/access-model.md`, `docs/agent-authoring.md`, `docs/ai-over-attachments.md`, `docs/api.md`, `docs/architecture.md`, `docs/atlas.md`, `docs/attachments.md`, `docs/billing.md`, `docs/custom-domains.md`, `docs/decisions.md`, `docs/deck.md`, `docs/deploy.md`, `docs/editions-and-pricing.md`, `docs/editions-deploy-runbook.md`, `docs/excalidraw-collab.md`, `docs/ideas.md`, `docs/knowledge-intelligence.md`, `docs/licensing.md`, `docs/mcp-directory-submission.md`

宿主 AI 硬性规则：
- 没有 repo_clone_verified=true 时，不得声称已经读过源码。
- 没有 repo_inspection_verified=true 时，不得把 README/docs/package 文件判断写成事实。
- 没有 quick_start_verified=true 时，不得声称 Quick Start 已跑通。

## Doramagic Pitfall Constraints / 踩坑约束

这些规则来自 Doramagic 发现、验证或编译过程中的项目专属坑点。宿主 AI 必须把它们当作工作约束，而不是普通说明文字。

### Constraint 1: 失败模式：security_permissions: Feature: Agent activity audit trail — who read/wrote what via MCP

- Trigger: Developers should check this security_permissions risk before relying on the project: Feature: Agent activity audit trail — who read/wrote what via MCP
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Feature: Agent activity audit trail — who read/wrote what via MCP. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Developers may expose sensitive permissions or credentials: Feature: Agent activity audit trail — who read/wrote what via MCP
- Evidence: failure_mode_cluster:github_issue | https://github.com/zcag/tela/issues/9 | Feature: Agent activity audit trail — who read/wrote what via MCP, failure_mode_cluster:github_issue | https://github.com/zcag/tela/issues/9 | Feature: Agent activity audit trail — who read/wrote what via MCP
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 2: 失败模式：installation: v0.8.0

- Trigger: Developers should check this installation risk before relying on the project: v0.8.0
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.8.0. Context: Observed during installation or first-run setup.
- Why it matters: Upgrade or migration may change expected behavior: v0.8.0
- Evidence: failure_mode_cluster:github_release | https://github.com/zcag/tela/releases/tag/v0.8.0 | v0.8.0
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 3: 来源证据：SEO completeness pass — landing meta/OG/schema + robots/sitemap/llms + app noindex

- Trigger: GitHub 社区证据显示该项目存在一个安装相关的待验证问题：SEO completeness pass — landing meta/OG/schema + robots/sitemap/llms + app noindex
- Why it matters: 可能增加新用户试用和生产接入成本。
- Evidence: community_evidence:github | https://github.com/zcag/tela/issues/2 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 4: 可能修改宿主 AI 配置

- Trigger: 项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。
- Host AI rule: 列出会写入的配置文件、目录和卸载/回滚步骤。
- Why it matters: 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。
- Evidence: capability.host_targets | https://github.com/zcag/tela | host_targets=mcp_host, claude, cursor
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 5: 失败模式：configuration: Reading mode — chrome-free, typographically elevated page reader

- Trigger: Developers should check this configuration risk before relying on the project: Reading mode — chrome-free, typographically elevated page reader
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Reading mode — chrome-free, typographically elevated page reader. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Developers may misconfigure credentials, environment, or host setup: Reading mode — chrome-free, typographically elevated page reader
- Evidence: failure_mode_cluster:github_issue | https://github.com/zcag/tela/issues/3 | Reading mode — chrome-free, typographically elevated page reader, failure_mode_cluster:github_issue | https://github.com/zcag/tela/issues/3 | Reading mode — chrome-free, typographically elevated page reader
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 6: 能力判断依赖假设

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: 将假设转成下游验证清单。
- Why it matters: 假设不成立时，用户拿不到承诺的能力。
- Evidence: capability.assumptions | https://github.com/zcag/tela | README/documentation is current enough for a first validation pass.
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 7: 维护活跃度未知

- Trigger: 未记录 last_activity_observed。
- Host AI rule: 补 GitHub 最近 commit、release、issue/PR 响应信号。
- Why it matters: 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- Evidence: evidence.maintainer_signals | https://github.com/zcag/tela | last_activity_observed missing
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

- Trigger: no_demo
- Evidence: downstream_validation.risk_items | https://github.com/zcag/tela | no_demo; severity=medium
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 9: 存在评分风险

- Trigger: no_demo
- Why it matters: 风险会影响是否适合普通用户安装。
- Evidence: risks.scoring_risks | https://github.com/zcag/tela | no_demo; severity=medium
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。

### Constraint 10: 来源证据：Feature: Agent activity audit trail — who read/wrote what via MCP

- Trigger: GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Feature: Agent activity audit trail — who read/wrote what via MCP
- Why it matters: 可能影响授权、密钥配置或安全边界。
- Evidence: community_evidence:github | https://github.com/zcag/tela/issues/9 | 来源类型 github_issue 暴露的待验证使用条件。
- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。