monoco-toolkit 0.3.11__py3-none-any.whl → 0.4.0__py3-none-any.whl

monoco/features/agent/apoptosis.py

@@ -1,44 +0,0 @@
-from .manager import SessionManager
-from .models import RoleTemplate
-
-class ApoptosisManager:
-    """
-    Manages the controlled shutdown (Apoptosis) and investigation (Autopsy) 
-    of failed agent sessions.
-    """
-    
-    def __init__(self, session_manager: SessionManager):
-        self.session_manager = session_manager
-        
-    def trigger_apoptosis(self, session_id: str, failure_reason: str = "Unknown") -> None:
-        """
-        Trigger the apoptosis process for a given session.
-        1. Mark session as crashed.
-        2. Spin up a Coroner agent to diagnose.
-        """
-        session = self.session_manager.get_session(session_id)
-        if not session:
-            return
-            
-        # 1. Mark as crashed
-        session.model.status = "crashed"
-        
-        # 2. Start Coroner
-        self._perform_autopsy(session, failure_reason)
-        
-    def _perform_autopsy(self, victim_session, failure_reason: str):
-        coroner_role = RoleTemplate(
-            name="Coroner",
-            description="Investigates cause of death for failed agents.",
-            trigger="system.crash",
-            goal=f"Determine why the previous agent failed. Reason: {failure_reason}",
-            system_prompt="You are the Coroner. Analyze the logs.",
-            engine="gemini"
-        )
-        
-        coroner_session = self.session_manager.create_session(
-            issue_id=victim_session.model.issue_id,
-            role=coroner_role
-        )
-        
-        coroner_session.start()

monoco/features/agent/manager.py

@@ -1,127 +0,0 @@
-from typing import Dict, List, Optional
-import uuid
-from pathlib import Path
-
-from .models import RoleTemplate
-from .worker import Worker
-from .session import Session, RuntimeSession
-from monoco.core.hooks import HookRegistry, get_registry
-from monoco.core.config import find_monoco_root, MonocoConfig
-
-
-class SessionManager:
-    """
-    Manages the lifecycle of sessions.
-    Responsible for creating, tracking, and retrieving sessions.
-    """
-
-    def __init__(
-        self,
-        project_root: Optional[Path] = None,
-        hook_registry: Optional[HookRegistry] = None,
-        config: Optional[MonocoConfig] = None,
-    ):
-        # In-memory storage for now. In prod, this might be a DB or file-backed.
-        self._sessions: Dict[str, RuntimeSession] = {}
-        self.project_root = project_root or find_monoco_root()
-        self.config = config
-
-        self.sessions_dir = self.project_root / ".monoco" / "sessions"
-        self.sessions_dir.mkdir(parents=True, exist_ok=True)
-
-        # Initialize hook registry
-        self.hook_registry = hook_registry or get_registry()
-
-        # Load hooks from config if available
-        self._load_hooks_from_config()
-
-        # Load persisted sessions
-        self._load_sessions()
-
-    def _load_sessions(self):
-        """Load sessions from disk."""
-        import json
-
-        for session_file in self.sessions_dir.glob("*.json"):
-            try:
-                data = json.loads(session_file.read_text())
-                session_model = Session(**data)
-                # Rehydrate as Observer
-                runtime = RuntimeSession(
-                    session_model,
-                    worker=None,  # No worker for loaded sessions initially (Observer mode)
-                    hook_registry=self.hook_registry,
-                    project_root=self.project_root,
-                    save_callback=self._save_session,
-                )
-                self._sessions[session_model.id] = runtime
-                # Check status immediately to see if it's still running
-                runtime.refresh_status()
-            except Exception as e:
-                print(f"Failed to load session {session_file}: {e}")
-
-    def _save_session(self, session: Session):
-        """Save session to disk."""
-        file_path = self.sessions_dir / f"{session.id}.json"
-        file_path.write_text(session.model_dump_json(indent=2))
-
-    def _load_hooks_from_config(self) -> None:
-        """Load and register hooks from configuration."""
-        if self.config is None:
-            try:
-                from monoco.core.config import get_config
-
-                self.config = get_config(str(self.project_root))
-            except Exception:
-                return
-
-        # Load hooks from config
-        if self.config and hasattr(self.config, "session_hooks"):
-            hooks_config = self.config.session_hooks
-            if hooks_config:
-                self.hook_registry.load_from_config(hooks_config, self.project_root)
-
-    def create_session(self, issue_id: str, role: RoleTemplate) -> RuntimeSession:
-        session_id = str(uuid.uuid4())
-        branch_name = (
-            f"agent/{issue_id}/{session_id[:8]}"  # Simple branch naming strategy
-        )
-
-        session_model = Session(
-            id=session_id,
-            issue_id=issue_id,
-            role_name=role.name,
-            branch_name=branch_name,
-        )
-
-        # Get timeout from config
-        timeout = 900
-        if self.config and hasattr(self.config, "agent"):
-            timeout = self.config.agent.timeout_seconds
-
-        worker = Worker(role, issue_id, timeout=timeout)
-        runtime = RuntimeSession(
-            session_model,
-            worker,
-            hook_registry=self.hook_registry,
-            project_root=self.project_root,
-            save_callback=self._save_session,
-        )
-        self._sessions[session_id] = runtime
-        self._save_session(session_model)
-        return runtime
-
-    def get_session(self, session_id: str) -> Optional[RuntimeSession]:
-        return self._sessions.get(session_id)
-
-    def list_sessions(self, issue_id: Optional[str] = None) -> List[RuntimeSession]:
-        if issue_id:
-            return [s for s in self._sessions.values() if s.model.issue_id == issue_id]
-        return list(self._sessions.values())
-
-    def terminate_session(self, session_id: str):
-        session = self.get_session(session_id)
-        if session:
-            session.terminate()
-            # We keep the record for history
-            # del self._sessions[session_id]

monoco/features/agent/resources/atoms/atom-code-dev.yaml

@@ -1,61 +0,0 @@
----
-name: atom-code-dev
-type: atom
-domain: code
-description: 代码开发的原子操作 - 调研、实现、测试、文档
-version: 1.0.0
-author: Monoco Toolkit
-
-# 系统级合规规则
-compliance_rules:
-  - rule: "遵循项目代码规范"
-    severity: warning
-  
-  - rule: "优先编写测试"
-    severity: warning
-    mindset: "TDD"
-  
-  - rule: "保持代码简单直观"
-    severity: info
-    mindset: "KISS"
-
-# 原子操作定义
-operations:
-  - name: investigate
-    description: 理解需求与上下文，识别相关代码和依赖
-    reminder: "理解需求后再开始编码，识别相关文件和依赖 Issue"
-    checkpoints:
-      - "阅读并理解 Issue 描述"
-      - "识别相关代码文件"
-      - "检查依赖 Issue 状态"
-      - "评估技术可行性"
-    output: "技术方案草稿、风险清单"
-  
-  - name: implement
-    description: 实现代码变更
-    reminder: "遵循项目代码规范，小步提交，处理边界情况"
-    checkpoints:
-      - "遵循项目代码规范"
-      - "编写/更新必要的文档"
-      - "处理边界情况"
-      - "保持代码可审查性（单次提交 < 400 行）"
-  
-  - name: test
-    description: 运行测试确保代码质量
-    reminder: "所有测试必须通过，检查测试覆盖率"
-    checkpoints:
-      - "编写/更新单元测试"
-      - "运行测试套件 (pytest, cargo test, etc.)"
-      - "修复失败的测试"
-      - "检查测试覆盖率"
-    compliance_rules:
-      - rule: "所有单元测试必须通过后才能提交"
-        severity: error
-  
-  - name: document
-    description: 更新文档
-    reminder: "代码变更必须同步更新文档"
-    checkpoints:
-      - "更新代码注释"
-      - "更新相关文档"
-      - "更新 CHANGELOG（如适用）"

monoco/features/agent/resources/atoms/atom-issue-lifecycle.yaml

@@ -1,73 +0,0 @@
----
-name: atom-issue-lifecycle
-type: atom
-domain: issue
-description: Issue 生命周期管理的原子操作 - 创建、启动、提交、关闭工作单元
-version: 1.0.0
-author: Monoco Toolkit
-
-# 系统级合规规则（定义一次，全局生效）
-compliance_rules:
-  - rule: "禁止在 main/master 分支直接修改代码"
-    severity: error
-    check: "git branch --show-current"
-    fail_if: "main|master"
-  
-  - rule: "必须使用 feature 分支进行开发"
-    severity: error
-    command: "monoco issue start <ID> --branch"
-  
-  - rule: "提交前必须通过 lint 检查"
-    severity: error
-    command: "monoco issue lint"
-  
-  - rule: "每个 Issue 必须至少包含 2 个 Checkbox"
-    severity: error
-    check: "checkbox_count >= 2"
-  
-  - rule: "Review/Done 阶段必须包含 Review Comments"
-    severity: warning
-    check: "review_comments_section exists"
-
-# 原子操作定义
-operations:
-  - name: create
-    description: 创建新的 Issue 工作单元
-    command: "monoco issue create <type> -t <title>"
-    reminder: "选择合适的类型 (epic/feature/chore/fix)，编写清晰的描述"
-    checkpoints:
-      - "必须包含至少 2 个 Checkbox"
-      - "标题必须与 Front Matter 一致"
-  
-  - name: start
-    description: 启动开发，创建功能分支
-    command: "monoco issue start <ID> --branch"
-    reminder: "确保使用 --branch 创建功能分支，禁止在 main/master 上开发"
-    checkpoints:
-      - "禁止在 main/master 分支直接修改代码"
-      - "必须创建 feature 分支"
-  
-  - name: sync
-    description: 同步文件追踪，记录修改的文件
-    command: "monoco issue sync-files"
-    reminder: "定期同步文件追踪，保持 Issue 与代码变更同步"
-  
-  - name: lint
-    description: 检查 Issue 合规性
-    command: "monoco issue lint"
-    reminder: "提交前必须运行 lint 检查"
-    checkpoints:
-      - "必须通过所有合规检查"
-  
-  - name: submit
-    description: 提交代码进行评审
-    command: "monoco issue submit <ID>"
-    reminder: "确保所有测试通过，lint 无错误后再提交"
-    checkpoints:
-      - "所有单元测试必须通过"
-      - "必须通过 lint 检查"
-  
-  - name: close
-    description: 关闭 Issue，清理环境
-    command: "monoco issue close <ID> --solution completed --prune"
-    reminder: "代码合并后及时关闭 Issue，清理 feature 分支"

monoco/features/agent/resources/atoms/atom-knowledge.yaml

@@ -1,55 +0,0 @@
----
-name: atom-knowledge
-type: atom
-domain: knowledge
-description: 知识管理的原子操作 - 捕获、处理、转化、归档
-version: 1.0.0
-author: Monoco Toolkit
-
-# 系统级合规规则
-compliance_rules:
-  - rule: "Memo 是临时的，不应无限堆积"
-    severity: warning
-  
-  - rule: "可执行的想法必须转为 Issue 追踪"
-    severity: error
-
-# 原子操作定义
-operations:
-  - name: capture
-    description: 快速捕获 fleeting ideas
-    command: "monoco memo add <content>"
-    reminder: "保持简洁，不中断当前工作流，添加上下文"
-    checkpoints:
-      - "使用简洁的描述"
-      - "添加上下文（-c file:line 如适用）"
-      - "不中断当前任务流"
-  
-  - name: process
-    description: 定期处理 Memo，评估价值
-    command: "monoco memo list"
-    reminder: "定期回顾和分类 Memo（建议每周）"
-    checkpoints:
-      - "运行 monoco memo list 查看所有 Memo"
-      - "评估每个 Memo 的价值"
-      - "分类：可执行 / 纯参考 / 无价值"
-  
-  - name: convert
-    description: 将可执行的 Memo 转化为 Issue
-    command: "monoco issue create <type> -t <title>"
-    reminder: "有价值的想法尽快转为 Issue"
-    checkpoints:
-      - "判断 Issue 类型 (feature/chore/fix)"
-      - "编写清晰的描述和验收标准"
-      - "关联原始 Memo"
-    compliance_rules:
-      - rule: "可执行的想法必须转为 Issue 追踪"
-        severity: error
-  
-  - name: archive
-    description: 归档纯参考资料
-    reminder: "纯参考资料归档保存，无价值的直接删除"
-    checkpoints:
-      - "确认 Memo 内容为纯参考资料"
-      - "移动到知识库或文档"
-      - "从 Memo 列表中移除"

monoco/features/agent/resources/atoms/atom-review.yaml

@@ -1,60 +0,0 @@
----
-name: atom-review
-type: atom
-domain: review
-description: 代码评审的原子操作 - 检出、验证、对抗、反馈
-version: 1.0.0
-author: Monoco Toolkit
-
-# 系统级合规规则
-compliance_rules:
-  - rule: "必须先通过 Engineer 的测试 (Verify)，再进行对抗测试 (Challenge)"
-    severity: error
-  
-  - rule: "必须尝试编写至少一个边界测试用例"
-    severity: warning
-  
-  - rule: "禁止未经测试直接 Approve"
-    severity: error
-
-# 原子操作定义
-operations:
-  - name: checkout
-    description: 检出待评审的代码
-    reminder: "获取待评审的 PR/Branch，确认与 Base 分支的差异"
-    checkpoints:
-      - "检出 PR/Branch"
-      - "确认与 Base 分支的差异"
-      - "检查环境配置"
-  
-  - name: verify
-    description: 验证 Engineer 提交的测试 (White-box)
-    reminder: "先运行 Engineer 编写的测试，验证功能正确性"
-    checkpoints:
-      - "运行 Engineer 编写的单元测试"
-      - "运行集成测试（如适用）"
-      - "检查测试覆盖率报告"
-    compliance_rules:
-      - rule: "如果现有测试失败，直接进入 Reject 流程"
-        severity: error
-  
-  - name: challenge
-    description: 对抗测试，尝试破坏代码 (Black-box / Edge Cases)
-    reminder: "Try to break it - 寻找边界情况和安全漏洞"
-    checkpoints:
-      - "分析代码逻辑，寻找盲区（并发、大/小数值、注入攻击等）"
-      - "编写新的 Challenge Test Cases"
-      - "运行这些新测试"
-    compliance_rules:
-      - rule: "必须尝试编写至少一个边界测试用例"
-        severity: warning
-  
-  - name: feedback
-    description: 提供评审反馈
-    reminder: "明确批准、拒绝或请求修改，提供具体反馈"
-    checkpoints:
-      - "功能是否正确实现"
-      - "代码是否符合设计规范"
-      - "测试是否充分"
-      - "文档是否同步更新"
-      - "是否遵循项目规范"

monoco/features/agent/resources/en/skills/monoco_atom_core/SKILL.md

@@ -1,99 +0,0 @@
----
-name: monoco_atom_core
-description: Core skill for Monoco Toolkit. Provides essential commands for project initialization, configuration, and workspace management.
-type: atom
-version: 1.0.0
----
-
-# Monoco Core
-
-Core functionality and commands for the Monoco Toolkit.
-
-## Overview
-
-Monoco is a developer productivity toolkit that provides:
-
-- **Project initialization** with standardized structure
-- **Configuration management** at global and project levels
-- **Workspace management** for multi-project setups
-
-## Key Commands
-
-### Project Setup
-
-- **`monoco init`**: Initialize a new Monoco project
-  - Creates `.monoco/` directory with default configuration
-  - Sets up project structure (Issues/, .references/, etc.)
-  - Generates initial documentation
-
-### Configuration
-
-- **`monoco config`**: Manage configuration
-  - `monoco config get <key>`: View configuration value
-  - `monoco config set <key> <value>`: Update configuration
-  - Supports both global (`~/.monoco/config.yaml`) and project (`.monoco/config.yaml`) scopes
-
-### Agent Integration
-
-- **`monoco sync`**: Synchronize with agent environments
-  - Injects system prompts into agent configuration files (GEMINI.md, CLAUDE.md, etc.)
-  - Distributes skills to agent framework directories
-  - Respects language configuration from `i18n.source_lang`
-
-- **`monoco uninstall`**: Clean up agent integrations
-  - Removes managed blocks from agent configuration files
-  - Cleans up distributed skills
-
-### Git Workflow Integration
-
-Monoco enforces a **Feature Branch Workflow** to ensure code isolation and quality:
-
-- **`monoco init`**: Automatically installs Git Hooks
-  - **pre-commit**: Runs Issue Linter and code formatting checks
-  - **pre-push**: Executes test suite and integrity validation
-  - All hooks configurable via `.monoco/config.yaml`
-
-- **Branch Isolation Strategy**:
-  - ⚠️ **Required**: Use `monoco issue start <ID> --branch` to create isolated environment
-  - Auto-generates normalized branch names: `feat/<id>-<slug>`
-  - **Main Protection**: Linter blocks direct code modifications on `main`/`master` branches
-
-- **File Tracking**: `monoco issue sync-files` auto-syncs Git changes to Issue metadata
-
-> 📖 **Detailed Workflow**: See `monoco-issue` skill for complete Issue lifecycle management guide.
-
-## Configuration Structure
-
-Configuration is stored in YAML format at:
-
-- **Global**: `~/.monoco/config.yaml`
-- **Project**: `.monoco/config.yaml`
-
-Key configuration sections:
-
-- `core`: Log level, author
-- `paths`: Directory paths (issues, spikes, specs)
-- `project`: Project metadata, spike repos, workspace members
-- `i18n`: Internationalization settings
-- `agent`: Agent framework integration settings
-
-## Best Practices
-
-### Basic Operations
-
-1. **Use CLI commands** instead of manual file editing when possible
-2. **Run `monoco sync`** after configuration changes to update agent environments
-3. **Commit `.monoco/config.yaml`** to version control for team consistency
-4. **Keep global config minimal** - most settings should be project-specific
-
-### Git Workflow (⚠️ CRITICAL for Agents)
-
-5. **Strictly follow branch isolation**:
-   - ✅ Always use: `monoco issue start <ID> --branch`
-   - ❌ Never modify code directly on `main`/`master` branches
-   - 📝 Before commit: Run `monoco issue sync-files` to update file tracking
-
-6. **Quality Gates**:
-   - Git Hooks will auto-run checks, don't bypass (`--no-verify`)
-   - Ensure `monoco issue lint` passes before committing
-   - Use `monoco issue submit` to generate delivery reports

monoco/features/agent/resources/en/skills/monoco_workflow_agent_engineer/SKILL.md

@@ -1,94 +0,0 @@
----
-name: monoco_workflow_agent_engineer
-description: Standardized workflow for the Engineer role (Flow Skill). Defines the standard operating procedure from requirement investigation to code submission, ensuring test coverage and code quality.
-type: workflow
-role: engineer
-version: 1.0.0
----
-
-# Engineer Flow
-
-Standardized workflow for the Engineer role, ensuring code development follows the "Investigate → Code → Test → Report → Submit" process.
-
-## Workflow State Machine
-
-```mermaid
-stateDiagram-v2
-    [*] --> Investigate: Receive Task
-    
-    Investigate --> Code: Requirements Clear
-    Investigate --> Investigate: Requirements Fuzzy<br/>(Request Clarification)
-    
-    Code --> Test: Coding Complete
-    
-    Test --> Test: Test Failed<br/>(Fix Code)
-    Test --> Report: Test Passed
-    
-    Report --> Submit: Report Complete
-    
-    Submit --> [*]: Submission Successful
-```
-
-## Execution Steps
-
-### 1. Investigate
-
-- **Goal**: Fully understand requirements, identify technical risks and dependencies
-- **Input**: Issue description, relevant code, dependent Issues
-- **Output**: Technical solution draft, risk checklist
-- **Checkpoints**:
-  - [ ] Read and understand Issue description
-  - [ ] Identify relevant code files
-  - [ ] Check dependent Issue status
-  - [ ] Assess technical feasibility
-
-### 2. Code
-
-- **Goal**: Implement feature or fix defect
-- **Prerequisites**: Requirements are clear, branch is created (`monoco issue start <ID> --branch`)
-- **Checkpoints**:
-  - [ ] Follow project coding standards
-  - [ ] Write/update necessary documentation
-  - [ ] Handle edge cases
-
-### 3. Test
-
-- **Goal**: Ensure code quality and functional correctness
-- **Strategy**: Loop testing until passed
-- **Checkpoints**:
-  - [ ] Write/update unit tests
-  - [ ] Run test suite (`pytest`, `cargo test`, etc.)
-  - [ ] Fix failed tests
-  - [ ] Check test coverage
-
-### 4. Report
-
-- **Goal**: Document changes, update Issue status
-- **Checkpoints**:
-  - [ ] Update Issue file tracking (`monoco issue sync-files`)
-  - [ ] Write change summary
-  - [ ] Update task checklist (Checkboxes)
-
-### 5. Submit
-
-- **Goal**: Complete code submission, enter review process
-- **Checkpoints**:
-  - [ ] Run `monoco issue lint` for compliance check
-  - [ ] Run `monoco issue submit <ID>`
-  - [ ] Wait for review results
-
-## Decision Branches
-
-| Condition | Action |
-|-----------|--------|
-| Requirements unclear | Return to Investigate, request clarification |
-| Test failed | Return to Code, fix issues |
-| Lint failed | Fix compliance issues, resubmit |
-| Review rejected | Return to Code, modify according to feedback |
-
-## Compliance Requirements
-
-- **Prohibited**: Skip tests and submit directly
-- **Prohibited**: Modify code directly on main/master branch
-- **Required**: Use `monoco issue start --branch` to create feature branch
-- **Required**: All unit tests must pass before Submit