monoco-toolkit 0.1.0__tar.gz

monoco_toolkit-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,49 @@
+name: CI
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+jobs:
+  build-and-test:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - uses: actions/checkout@v4
+
+    # ----------------------------------------------------
+    # Python / Daemon Setup
+    # ----------------------------------------------------
+    - name: Install uv
+      uses: astral-sh/setup-uv@v5
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version-file: "pyproject.toml"
+
+    - name: Install Python Dependencies
+      run: uv sync --all-extras --dev
+
+    - name: Run Python Tests
+      run: uv run pytest
+
+    # ----------------------------------------------------
+    # Node.js / Kanban Setup
+    # ----------------------------------------------------
+    - name: Use Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '20.x'
+        cache: 'npm'
+        cache-dependency-path: Kanban/package-lock.json
+
+    - name: Install Node Dependencies
+      working-directory: ./Kanban
+      run: npm ci
+
+    - name: Build Kanban
+      working-directory: ./Kanban
+      run: npm run build

monoco_toolkit-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,40 @@
+name: Deploy Docs
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'docs/**'
+      - 'mkdocs.yml'
+
+permissions:
+  contents: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Configure Git Credentials
+        run: |
+          git config user.name github-actions[bot]
+          git config user.email 41898282+github-actions[bot]@users.noreply.github.com
+          
+      - uses: actions/setup-python@v5
+        with:
+          python-version: 3.x
+          
+      - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV 
+      
+      - uses: actions/cache@v4
+        with:
+          key: mkdocs-material-${{ env.cache_id }}
+          path: .cache
+          restore-keys: |
+            mkdocs-material-
+            
+      - run: pip install mkdocs-material 
+      
+      - run: mkdocs gh-deploy --force

monoco_toolkit-0.1.0/.github/workflows/publish-pypi.yml

@@ -0,0 +1,45 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build-n-publish:
+    name: Build and publish Monoco Toolkit to PyPI
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write # Mandatory for trusted publishing
+      contents: read
+    environment: pypi
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version-file: "pyproject.toml"
+
+      - name: Install Dependencies
+        run: uv sync --all-extras --dev
+
+      - name: Run Tests
+        run: uv run pytest
+
+      - name: Lint Issues
+        run: uv run monoco issue lint --recursive
+
+      - name: Build distribution
+        run: uv build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          skip-existing: true

monoco_toolkit-0.1.0/.gitignore

@@ -0,0 +1,59 @@
+# System Files
+.DS_Store
+Thumbs.db
+
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# Python Virtual Environment
+.venv/
+venv/
+ENV/
+
+# Pytest
+.pytest_cache/
+.coverage
+htmlcov/
+
+# Node.js
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.next/
+out/
+build/
+
+# Project Specific
+MemoryDaemon/
+.reference/
+.references/
+test.pdf
+.env
+.monoco/local_config.yaml
+
+# IDEs
+.vscode/
+.idea/
+*.swp
+*.swo

monoco_toolkit-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,67 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement.
+All complaints will be reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

monoco_toolkit-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,106 @@
+# Contributing to Monoco
+
+Thank you for your interest in contributing to Monoco! We welcome contributions from everyone.
+
+## Getting Started
+
+1. **Fork** the repository on GitHub.
+2. **Clone** your fork locally.
+3. **Install** dependencies: `pip install -e .`
+
+## Development Workflow
+
+Monoco follows an **Issue-Driven Development** process.
+
+1.  **Find or Create an Issue**:
+    - Use the CLI: `monoco issue create feature -t "My Feature"`
+    - Or browse existing issues in `Issues/`.
+2.  **Create a Branch**:
+    - `git checkout -b feat/my-feature`
+3.  **Implement**:
+    - Follow the "Task as Code" philosophy.
+    - Keep changes atomic.
+4.  **Verify**:
+    - Run tests: `pytest`
+    - Lint issues: `monoco issue lint`
+5.  **Submit a Pull Request**:
+    - Reference the Issue ID (e.g., `Fixes FEAT-0123`) in your PR description.
+
+## Code Style
+
+- **Python**: Follow PEP 8. Use `ruff` or `black` if available.
+- **Commit Messages**: Clear and concise. Prefer "Why" over "What".
+
+## Community
+
+- Join our discussions on GitHub.
+- Be respectful and follow our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Release Process
+
+### For Maintainers
+
+Monoco Toolkit uses **automated publishing** to PyPI via GitHub Actions.
+
+#### 1. Update Version
+
+Edit `pyproject.toml`:
+
+```toml
+[project]
+version = "0.2.0"  # Bump version
+```
+
+#### 2. Commit and Tag
+
+```bash
+git add pyproject.toml
+git commit -m "chore: bump version to 0.2.0"
+git push
+
+# Create and push tag
+git tag v0.2.0
+git push origin v0.2.0
+```
+
+#### 3. Automated Workflow
+
+GitHub Actions will automatically:
+
+- ✅ Run tests (`pytest`)
+- ✅ Lint issues (`monoco issue lint --recursive`)
+- ✅ Build distribution (`uv build`)
+- ✅ Publish to PyPI (via Trusted Publishing)
+
+#### 4. Verify Release
+
+```bash
+pip install --upgrade monoco-toolkit
+monoco --version
+```
+
+### Versioning
+
+We follow [Semantic Versioning](https://semver.org/):
+
+- **MAJOR**: Breaking changes
+- **MINOR**: New features (backward compatible)
+- **PATCH**: Bug fixes
+
+### Pre-releases
+
+For alpha/beta releases:
+
+```bash
+# Update version to "0.2.0-alpha.1"
+git tag v0.2.0-alpha.1
+git push origin v0.2.0-alpha.1
+```
+
+### Troubleshooting
+
+If the release fails, check:
+
+1. PyPI Trusted Publisher is configured correctly (see `docs/pypi-trusted-publishing.md`)
+2. All tests pass locally
+3. GitHub Actions has `id-token: write` permission

monoco_toolkit-0.1.0/Issues/Chores/closed/CHORE-0001-/346/233/264/346/226/260Issue/346/226/207/346/241/243/345/222/214I18n.md

@@ -0,0 +1,32 @@
+---
+id: CHORE-0001
+type: chore
+status: closed
+stage: done
+title: 更新 Issue 管理文档并扫描 i18n (Update Issue Docs)
+created_at: "2026-01-10T20:55:18.498670"
+opened_at: "2026-01-10T20:55:18.498656"
+updated_at: "2026-01-10T20:56:33.172498"
+closed_at: "2026-01-10T20:56:33.172533"
+solution: implemented
+dependencies: []
+related: []
+tags: []
+parent: EPIC-0001
+---
+
+## CHORE-0001: 更新 Issue 管理文档并扫描 i18n
+
+## 目标 (Objective)
+
+保持文档与最新的 Issue 管理功能（如 API、CLI 变更）同步，并确保所有新内容都已扫描并准备好进行国际化。
+
+## 验收标准 (Acceptance Criteria)
+
+1.  **文档同步 (Documentation Synced)**: `Toolkit/skills/issue-management` 与当前代码匹配。
+2.  **I18n 扫描 (I18n Scanned)**: 运行了 `monoco i18n scan` 并解决了缺失的键。
+
+## 技术任务 (Technical Tasks)
+
+- [x] 运行 `monoco i18n scan`。
+- [x] 更新 `docs/` 中的 `.md` 文件。

monoco_toolkit-0.1.0/Issues/Chores/closed/CHORE-0002-/345/256/214/346/210/220I18n/346/226/207/346/241/243.md

@@ -0,0 +1,33 @@
+---
+id: CHORE-0002
+type: chore
+status: closed
+title: 完善 monoco i18n 命令文档 (Complete i18n Docs)
+created_at: "2026-01-09"
+solution: "completed"
+tags: ["documentation", "i18n", "cli"]
+parent: EPIC-0001
+---
+
+## CHORE-0002: 完善 monoco i18n 命令文档
+
+## 目标 (Objective)
+
+完善 `monoco i18n` 命令的文档体系，包括 CLI 内建帮助信息和用户手册。确保用户能够清晰理解和使用 i18n 扫描能力，维护项目文档的多语言质量。
+
+## 验收标准 (Acceptance Criteria)
+
+1.  **CLI Help 增强**:
+    - `monoco i18n --help` 提供清晰的命令描述。
+    - `monoco i18n scan --help` 详细说明参数（如 `--root`）和输出含义。
+2.  **用户手册**:
+    - 创建 `Toolkit/docs/zh/i18n/manual.md`，详细介绍 i18n 系统规范、命令使用方法及常见问题。
+    - 手册内容需包含 `Suffix 模式` 和 `Subdir 模式` 的示例说明。
+3.  **文档索引**:
+    - 在 `Toolkit/README.md` 或相关索引页添加 i18n 手册的链接。
+
+## 技术任务 (Technical Tasks)
+
+- [x] **增强 CLI 文档字符串**: 优化 `Toolkit/monoco/features/i18n/commands.py` 中的 help 文本。
+- [x] **创建用户手册**: 撰写 `Toolkit/docs/zh/i18n/manual.md`。
+- [x] **更新索引**: 更新项目文档索引，纳入 i18n 手册。

monoco_toolkit-0.1.0/Issues/Epics/closed/EPIC-0008-github-/345/217/221/345/270/203/345/207/206/345/244/207.md

@@ -0,0 +1,40 @@
+---
+id: EPIC-0008
+uid: 6d3cd8
+type: epic
+status: closed
+stage: done
+title: GitHub 发布准备
+created_at: "2026-01-13T13:21:46"
+opened_at: "2026-01-13T13:21:46"
+updated_at: "2026-01-13T13:32:38"
+closed_at: "2026-01-13T13:32:38"
+solution: implemented
+dependencies: []
+related: []
+tags: []
+progress: 4/4
+files_count: 0
+---
+
+## EPIC-0008: GitHub 发布准备
+
+## Objective
+
+准备 Monoco 项目正式开源发布所需的门面资产与合规文档，并确保外部开发者能够顺利上手。
+
+## Acceptance Criteria
+
+- [x] 根目录包含全英文的 `README.md`，清晰描述 Monoco 的价值主张。
+- [x] 包含合规的 `LICENSE` (MIT) 文件。
+- [x] 包含 `CONTRIBUTING.md` 和 `CODE_OF_CONDUCT.md`。
+- [x] 项目官网 (GitHub Pages) 有清晰的文档入口。
+- [x] 一键安装脚本经过测试并可供外部使用。
+
+## Technical Tasks
+
+- [x] 编写全英文 `README.md`，替换/完善现有的顶层描述。
+- [x] 创建 `LICENSE`, `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`。
+- [x] 实现并文档化一键安装脚本 (Installer)。
+- [x] 审核并清理仓库中的敏感信息或无效的测试数据。
+- [x] 为核心模块 (Toolkit, Typedown) 编写入门教程。

monoco_toolkit-0.1.0/Issues/Epics/open/EPIC-0001-Monoco/345/267/245/345/205/267/347/256/261.md

@@ -0,0 +1,36 @@
+---
+id: EPIC-0001
+type: epic
+status: open
+title: 'EPIC-0001: Monoco 生态内核构建 (Kernel Construction)'
+created_at: 2026-01-08
+tags:
+- toolkit
+- infrastructure
+- core
+progress: 5/6
+files_count: 0
+stage: doing
+---
+
+## EPIC-0001: Monoco 生态内核构建 (Kernel Construction)
+
+## 目标 (Objective)
+
+构建 Monoco Toolkit 的核心基础设施 (CLI & Configuration)，为所有上层业务模块提供统一的**命令行**运行时底座。
+
+## 关键交付 (Key Deliverables)
+
+1. **CLI 框架 (CLI Framework)**: 基于 Typer 封装的标准 CLI 入口，支持多层级命令路由。
+2. **配置系统 (Config System)**: 统一的 `monoco.yaml` 加载与验证机制。
+3. **模块加载器 (Module Loader)**: 用于动态加载 `monoco/features/` 下各个业务模块的插件机制。
+4. **IoC 容器 (Dependency Injection)**: 基础的依赖注入支持。
+
+> **注意**: 具体的业务功能（如 Issue 管理、Spike 管理）已拆分为独立的 Epic，本 Epic 仅关注“容器”本身。
+> 架构规范请参考: `Toolkit/docs/zh/architecture.md`
+
+## 子故事 (Child Features)
+
+- [x] [[FEAT-0002]]: Toolkit 核心基础设施 (CLI, IoC, Config) (Done)
+- [x] [[FEAT-0018]]: 运行时远程交互 (Daemon, RPC) (Done)
+- [ ] [[FEAT-0029]]: 统一模块加载器与生命周期管理 (Module Loader)

monoco_toolkit-0.1.0/Issues/Epics/open/EPIC-0002-/346/231/272/350/203/275/344/273/273/345/212/241/345/206/205/346/240/270/344/270/216/347/212/266/346/200/201/346/234/272.md

@@ -0,0 +1,43 @@
+---
+id: EPIC-0002
+type: epic
+status: open
+stage: doing
+title: 智能任务内核与状态机 (Intelligent Task Kernel & State Machine)
+created_at: '2026-01-10T21:17:57.213576'
+opened_at: '2026-01-10T21:17:57.213562'
+updated_at: '2026-01-10T21:17:57.213578'
+dependencies: []
+related:
+- EPIC-0001
+tags:
+- core
+- issue-system
+- backend
+progress: 8/12
+files_count: 0
+---
+
+## EPIC-0002: 智能任务内核与状态机 (Intelligent Task Kernel)
+
+## 目标 (Objective)
+
+重构 Monoco 的任务管理**内核 (Core)**，使其成为一个严谨的代理原生系统。
+本 Epic 关注 **后端逻辑、API 和 CLI/TUI 实现**，它作为“发动机”，为上层 UI（如 EPIC-0002 中的 Web 看板）提供数据和逻辑支持。
+
+我们的目标是从单纯的“文件管理工具”迈向代理 (Agent) 与人类可协作使用的“项目管理平台”。
+
+## 验收标准 (Acceptance Criteria)
+
+1.  **新本体论对齐 (New Ontology Alignment)**: 系统必须强制执行 战略 (Epic) -> 价值 (Feature) -> 执行 (Chore/Fix) 的层级结构。
+2.  **API 层 (API Layer)**: 构建健壮的 Python API (`monoco.features.issue.core`)，能够支持外部前端（Web/TUI）。
+3.  **状态管理 (State Management)**: 实现处理状态流转 (Todo -> Doing -> Review -> Done) 的正式状态机，并具备严格的生命周期校验。
+4.  **UI 实现 (UI Implementation)**: 实现一个功能性的 TUI (终端用户界面)，用于在终端中可视化看板。
+
+## 技术任务 (Technical Tasks)
+
+- [ ] **架构 (Architecture)**: 定义用于 Issue 流转的严格状态机和事件钩子。
+- [ ] **API 重构 (API Refactoring)**: 暴露 CRUD 和看板视图 API 供 UI 消费。
+- [ ] **TUI 开发 (TUI Development)**: 实现基于 `textual` 或 `rich` 的看板视图。
+- [ ] **CLI 更新 (CLI Updates)**: 使 CLI 命令 (`start`, `submit`) 与新状态机对齐。
+- [ ] **数据迁移 (Migration)**: 确保现有 Issue 兼容新 Schema。

monoco_toolkit-0.1.0/Issues/Epics/open/EPIC-0003-/345/217/257/346/216/247/345/244/226/351/203/250/347/237/245/350/257/206/346/221/204/345/205/245.md

@@ -0,0 +1,42 @@
+---
+id: EPIC-0003
+type: epic
+status: open
+stage: doing
+title: 可控外部知识摄入 (Controlled Knowledge Ingestion)
+created_at: 2026-01-12
+tags:
+  - knowledge
+  - spike
+  - agent-native
+progress: 0/3
+files_count: 0
+---
+
+## EPIC-0003: 可控外部知识摄入 (Controlled Knowledge Ingestion)
+
+## 目标 (Objective)
+
+为 Agent 提供一种安全、确定性且可引用的方式来摄入外部知识 (URLs, Papers, Docs)。解决 Agent 随意访问互联网导致的上下文不可控和幻觉问题。
+
+## 概念: Spike (探针)
+
+Spike 原意为敏捷开发中的“探针任务”。在 Monoco 中，我们将 Spike 定义为**“对外部知识的切片引用”**。
+
+1. **确定性**: 每个 Spike 都是本地 `.references/` 目录下的一个文件，Agent 读取的是固化的本地副本，而非易变的互联网内容。
+2. **可引用**: 通过 `[[SPIKE-001]]` 引用知识，就像引用代码一样。
+
+## 关键交付 (Key Deliverables)
+
+1. **Spike CLI (`monoco spike`)**:
+   - `add <url>`: 下载 URL 内容，转换为 Markdown，存入 `.references/`。
+   - `list`: 列出已有知识。
+   - `read <id>`: 读取知识内容。
+2. **知识清洗 (Content Cleaning)**: 使用 `trafilatura` 或类似工具提取核心文本，去除广告和噪音。
+3. **引用完整性 (Referential Integrity)**: 确保 Issue 中引用的 Spike ID 在本地存在。
+
+## 子故事 (Child Features)
+
+- [x] [[FEAT-0004]]: Spike 基础管理 (Add/List/Read) (Done - 已在初期实现)
+- [ ] [[FEAT-0033]]: Spike 内容清洗与元数据增强 (Content Cleaning)
+- [ ] [[FEAT-0034]]: 知识库向量化索引 (Vector Indexing) (Optional)

monoco_toolkit-0.1.0/Issues/Epics/open/EPIC-0004-/345/212/250/346/200/201/346/226/207/346/241/243/345/233/275/351/231/205/345/214/226/344/275/223/347/263/273.md

@@ -0,0 +1,40 @@
+---
+id: EPIC-0004
+type: epic
+status: open
+stage: doing
+title: 动态文档国际化体系 (Dynamic Documentation I18n)
+created_at: 2026-01-12
+tags:
+- i18n
+- documentation
+- agent-native
+progress: 6/6
+files_count: 5
+---
+
+## EPIC-0004: 动态文档国际化体系 (Dynamic Documentation I18n)
+
+## 目标 (Objective)
+
+确保 Monoco 的文档在快速迭代中保持**中英双语同步**。通过 Agent 自动化流程，降低维护多语言文档的成本，防止文档腐烂。
+
+## 核心理念 (Core Concepts)
+
+1. **同构映射 (Isomorphic Mapping)**: 中文文档与英文文档必须保持 1:1 的文件结构映射。
+   - `docs/en/guide.md` <-> `docs/zh/guide.md`
+2. **自动化流水线 (Automation Pipeline)**: 任何对源语言（通常是中文）的修改，都应触发翻译任务。
+3. **校验 (Validation)**: 构建工具检查是否存在“孤儿文档”（缺少对应的翻译版本）。
+
+## 关键交付 (Key Deliverables)
+
+1. **I18n CLI (`monoco i18n`)**:
+   - `scan`: 扫描文档目录，报告缺失的翻译。
+   - `sync`: 自动补全缺失的文件（占位符或调用 LLM 翻译）。
+2. **锚点对齐 (Anchor Alignment)**: 尝试保持段落级别的对应关系，便于 Agent 进行双语对照学习。
+
+## 子故事 (Child Features)
+
+- [ ] [[FEAT-0035]]: I18n 扫描器与状态报告 (Scanner)
+- [ ] [[FEAT-0036]]: 基于 LLM 的自动翻译流水线 (Auto-Translate)
+- [ ] [[FEAT-0037]]: pre-commit 文档一致性检查 (Consistency Check)

monoco_toolkit-0.1.0/Issues/Epics/open/EPIC-0005-Monoco/346/234/215/345/212/241/350/277/220/350/241/214/346/227/266.md

@@ -0,0 +1,40 @@
+---
+id: EPIC-0005
+type: epic
+status: open
+stage: doing
+title: Monoco 服务运行时 (Monoco Server Runtime)
+created_at: 2026-01-12
+tags:
+  - server
+  - daemon
+  - sse
+  - infrastructure
+progress: 1/3
+files_count: 0
+---
+
+## EPIC-0005: Monoco 服务运行时 (Monoco Server Runtime)
+
+## 目标 (Objective)
+
+构建常驻的 **Monoco Daemon (`monoco serve`)**，不仅作为 API Server，更是文件系统的高性能**实时视图 (Real-time View)**。它是连接底层文件系统 (FS) 与上层交互界面 (Web/TUI) 的桥梁。
+
+## 核心职责 (Core Responsibilities)
+
+1. **高性能缓存 (Watcher & Cache)**: 实时监听文件系统变更 (`watchdog`)，维护内存中的领域模型缓存，避免每次 API 调用都重读磁盘 IO。
+2. **实时推送 (Real-time Push)**: 通过 Server-Sent Events (SSE) 或 WebSocket 向前端推送变更事件 (e.g., `issue_updated`, `spike_added`)。
+3. **API 网关 (API Gateway)**: 聚合各个 Feature (Issue, Spike) 的 API 路由，提供统一的 RESTful/RPC 接口。
+
+## 关键交付 (Key Deliverables)
+
+1. **Daemon 宿主**: 基于 FastAPI 的服务脚手架。
+2. **文件监听器 (File Watcher)**: 统一的 Watcher 服务，支持多 Feature 订阅。
+3. **SSE 通道**: 稳定的事件推送机制。
+4. **CORS & Security**: 前后端分离的基础安全配置。
+
+## 子故事 (Child Features)
+
+- [x] [[FEAT-0018]]: 运行时基础 (Daemon/RPC) (Done)
+- [ ] [[FEAT-0006]]: SSE 事件推送实现 (In Progress)
+- [ ] [[FEAT-0038]]: 统一文件监听与事件分发服务 (Watcher Service)