@bolloon/bolloon-agent 0.2.8 → 0.2.10

package/dist/bollharness-integration/context-router.js

@@ -224,319 +224,319 @@ export class ContextRouter {
  * These can be stored in context-fragments/ directory
  */
 export const CONTEXT_FRAGMENTS = {
-    'general-dev-principles': `# General Development Principles
-
-## Core Values
-- **Code over Convention**: Write code that works correctly, not just conventionally
-- **Explicit over Implicit**: Make dependencies and side effects visible
-- **Composition over Inheritance**: Prefer composing behavior to inheriting it
-- **Fail Fast**: Detect errors early and fail loudly
-
-## Code Quality
-- Write self-documenting code with clear intent
-- Keep functions small and focused (single responsibility)
-- Avoid premature optimization
-- Test at boundaries
-
-## Collaboration
-- Commit early and often
-- Write meaningful commit messages
-- Review code for clarity, not just correctness
+    'general-dev-principles': `# General Development Principles
+
+## Core Values
+- **Code over Convention**: Write code that works correctly, not just conventionally
+- **Explicit over Implicit**: Make dependencies and side effects visible
+- **Composition over Inheritance**: Prefer composing behavior to inheriting it
+- **Fail Fast**: Detect errors early and fail loudly
+
+## Code Quality
+- Write self-documenting code with clear intent
+- Keep functions small and focused (single responsibility)
+- Avoid premature optimization
+- Test at boundaries
+
+## Collaboration
+- Commit early and often
+- Write meaningful commit messages
+- Review code for clarity, not just correctness
 - Leave code better than you found it`,
-    'code-quality': `# Code Quality Guidelines
-
-## Readability
-- Use meaningful variable and function names
-- Add comments that explain *why*, not *what*
-- Keep lines under 100 characters
-- Use consistent formatting
-
-## Maintainability
-- DRY (Don't Repeat Yourself)
-- SOLID principles
-- Keep modules loosely coupled
-- Make side effects explicit
-
-## Testing
-- Test behavior, not implementation
-- Cover edge cases
-- Write tests before debugging
+    'code-quality': `# Code Quality Guidelines
+
+## Readability
+- Use meaningful variable and function names
+- Add comments that explain *why*, not *what*
+- Keep lines under 100 characters
+- Use consistent formatting
+
+## Maintainability
+- DRY (Don't Repeat Yourself)
+- SOLID principles
+- Keep modules loosely coupled
+- Make side effects explicit
+
+## Testing
+- Test behavior, not implementation
+- Cover edge cases
+- Write tests before debugging
 - Aim for meaningful assertions`,
-    'agent-architecture': `# Agent Architecture Patterns
-
-## Multi-Agent Design
-- Define clear agent responsibilities
-- Use message passing for inter-agent communication
-- Maintain agent isolation
-- Implement graceful degradation
-
-## Skill System
-- Skills should be composable
-- Each skill has single responsibility
-- Skills communicate via structured interfaces
+    'agent-architecture': `# Agent Architecture Patterns
+
+## Multi-Agent Design
+- Define clear agent responsibilities
+- Use message passing for inter-agent communication
+- Maintain agent isolation
+- Implement graceful degradation
+
+## Skill System
+- Skills should be composable
+- Each skill has single responsibility
+- Skills communicate via structured interfaces
 - Version skills for compatibility`,
-    'multi-agent-patterns': `# Multi-Agent Collaboration Patterns
-
-## Task Delegation
-- Match tasks to agent capabilities
-- Track task state across agents
-- Handle partial failures gracefully
-- Aggregate results appropriately
-
-## Communication
-- Use structured message formats
-- Implement acknowledgment protocols
-- Handle timeouts and retries
+    'multi-agent-patterns': `# Multi-Agent Collaboration Patterns
+
+## Task Delegation
+- Match tasks to agent capabilities
+- Track task state across agents
+- Handle partial failures gracefully
+- Aggregate results appropriately
+
+## Communication
+- Use structured message formats
+- Implement acknowledgment protocols
+- Handle timeouts and retries
 - Log for debugging`,
-    'documentation-standards': `# Documentation Standards
-
-## When to Document
-- Document *why*, not *what*
-- Keep docs close to code
-- Update docs with code changes
-- Delete outdated documentation
-
-## Types of Documentation
-- README: Project overview and setup
-- API docs: Usage examples
-- Architecture docs: Design decisions
+    'documentation-standards': `# Documentation Standards
+
+## When to Document
+- Document *why*, not *what*
+- Keep docs close to code
+- Update docs with code changes
+- Delete outdated documentation
+
+## Types of Documentation
+- README: Project overview and setup
+- API docs: Usage examples
+- Architecture docs: Design decisions
 - Inline comments: Complex logic explanation`,
-    'decision-tracking': `# Decision Tracking with ADRs
-
-## ADR Format
-- Title and status
-- Context and problem statement
-- Decision and rationale
-- Consequences (positive and negative)
-
-## When to Create ADR
-- Architectural changes
-- Technology choices
-- Process changes
+    'decision-tracking': `# Decision Tracking with ADRs
+
+## ADR Format
+- Title and status
+- Context and problem statement
+- Decision and rationale
+- Consequences (positive and negative)
+
+## When to Create ADR
+- Architectural changes
+- Technology choices
+- Process changes
 - Cross-cutting concerns`,
-    'adr-patterns': `# Architecture Decision Records
-
-## Structure
-1. **Title**: Brief descriptive title
-2. **Status**: Proposed, Accepted, Deprecated
-3. **Context**: Background and constraints
-4. **Decision**: What we decided
-5. **Consequences**: What changed
-
-## Review Process
-- Propose with clear rationale
-- Solicit feedback from stakeholders
-- Document dissenting opinions
+    'adr-patterns': `# Architecture Decision Records
+
+## Structure
+1. **Title**: Brief descriptive title
+2. **Status**: Proposed, Accepted, Deprecated
+3. **Context**: Background and constraints
+4. **Decision**: What we decided
+5. **Consequences**: What changed
+
+## Review Process
+- Propose with clear rationale
+- Solicit feedback from stakeholders
+- Document dissenting opinions
 - Update status as decisions evolve`,
-    'project-governance': `# Project Governance
-
-## Truth Sources
-- Bolloon.md: Project overview and norms
-- docs/: Architecture and decisions
-- code/: Implementation
-- issues/: Tracking and discussions
-
-## Decision Making
-- Small changes: Direct implementation
-- Medium changes: Discuss first
+    'project-governance': `# Project Governance
+
+## Truth Sources
+- Bolloon.md: Project overview and norms
+- docs/: Architecture and decisions
+- code/: Implementation
+- issues/: Tracking and discussions
+
+## Decision Making
+- Small changes: Direct implementation
+- Medium changes: Discuss first
 - Large changes: ADR required`,
-    'truth-source-hierarchy': `# Truth Source Hierarchy
-
-## Priority Order
-1. **Code**: Ground truth for behavior
-2. **Tests**: Verification of behavior
-3. **Docs**: Explanation of behavior
-4. **Comments**: Intent and caveats
-5. **Commits**: History and rationale
-
-## Conflict Resolution
-- Code vs docs: Code wins
-- Comments vs code: Code wins
-- Multiple docs: Newest wins
+    'truth-source-hierarchy': `# Truth Source Hierarchy
+
+## Priority Order
+1. **Code**: Ground truth for behavior
+2. **Tests**: Verification of behavior
+3. **Docs**: Explanation of behavior
+4. **Comments**: Intent and caveats
+5. **Commits**: History and rationale
+
+## Conflict Resolution
+- Code vs docs: Code wins
+- Comments vs code: Code wins
+- Multiple docs: Newest wins
 - Stale info: Delete or update`,
-    'testing-patterns': `# Testing Patterns
-
-## Test Structure
-- Arrange: Set up test data
-- Act: Execute the behavior
-- Assert: Verify the outcomes
-
-## Test Types
-- Unit tests: Single function/class
-- Integration tests: Component interaction
-- E2E tests: Full system flow
-
-## Best Practices
-- Test one thing per test
-- Use descriptive test names
-- Keep tests independent
+    'testing-patterns': `# Testing Patterns
+
+## Test Structure
+- Arrange: Set up test data
+- Act: Execute the behavior
+- Assert: Verify the outcomes
+
+## Test Types
+- Unit tests: Single function/class
+- Integration tests: Component interaction
+- E2E tests: Full system flow
+
+## Best Practices
+- Test one thing per test
+- Use descriptive test names
+- Keep tests independent
 - Mock external dependencies`,
-    'quality-standards': `# Quality Standards
-
-## Code Review Checklist
-- [ ] Does it work correctly?
-- [ ] Is it readable?
-- [ ] Are there tests?
-- [ ] Is it documented?
-- [ ] Are there security concerns?
-- [ ] Performance implications?
-
-## Definition of Done
-- Code complete
-- Tests passing
-- Documentation updated
+    'quality-standards': `# Quality Standards
+
+## Code Review Checklist
+- [ ] Does it work correctly?
+- [ ] Is it readable?
+- [ ] Are there tests?
+- [ ] Is it documented?
+- [ ] Are there security concerns?
+- [ ] Performance implications?
+
+## Definition of Done
+- Code complete
+- Tests passing
+- Documentation updated
 - No known issues`,
-    'workflow-patterns': `# Workflow Patterns
-
-## Pipeline Design
-- Input validation
-- Transformation steps
-- Output generation
-- Error handling
-
-## State Management
-- Track workflow progress
-- Handle partial completion
-- Support retry logic
+    'workflow-patterns': `# Workflow Patterns
+
+## Pipeline Design
+- Input validation
+- Transformation steps
+- Output generation
+- Error handling
+
+## State Management
+- Track workflow progress
+- Handle partial completion
+- Support retry logic
 - Log state changes`,
-    'orchestration-patterns': `# Orchestration Patterns
-
-## Task Coordination
-- Define task dependencies
-- Execute in correct order
-- Handle parallel execution
-- Aggregate results
-
-## Error Recovery
-- Identify failure points
-- Implement retry strategies
-- Rollback when needed
+    'orchestration-patterns': `# Orchestration Patterns
+
+## Task Coordination
+- Define task dependencies
+- Execute in correct order
+- Handle parallel execution
+- Aggregate results
+
+## Error Recovery
+- Identify failure points
+- Implement retry strategies
+- Rollback when needed
 - Notify stakeholders`,
-    'document-processing': `# Document Processing
-
-## Supported Formats
-- Markdown: Primary format
-- PDF: Via external parser
-- DOCX: Via external parser
-- Plain text: Direct reading
-
-## Processing Pipeline
-- Load document
-- Extract text
-- Chunk content
-- Process chunks
+    'document-processing': `# Document Processing
+
+## Supported Formats
+- Markdown: Primary format
+- PDF: Via external parser
+- DOCX: Via external parser
+- Plain text: Direct reading
+
+## Processing Pipeline
+- Load document
+- Extract text
+- Chunk content
+- Process chunks
 - Aggregate results`,
-    'parser-patterns': `# Parser Patterns
-
-## Design Principles
-- Single responsibility per parser
-- Consistent error handling
-- Graceful degradation
-- Clear error messages
-
-## Content Extraction
-- Strip formatting
-- Preserve structure
-- Handle encoding
+    'parser-patterns': `# Parser Patterns
+
+## Design Principles
+- Single responsibility per parser
+- Consistent error handling
+- Graceful degradation
+- Clear error messages
+
+## Content Extraction
+- Strip formatting
+- Preserve structure
+- Handle encoding
 - Validate content`,
-    'p2p-protocols': `# P2P Protocols
-
-## Connection Management
-- Bootstrap connections
-- Maintain peer list
-- Handle disconnections
-- Reconnect gracefully
-
-## Message Routing
-- Direct messages
-- Broadcast messages
-- Topic subscriptions
+    'p2p-protocols': `# P2P Protocols
+
+## Connection Management
+- Bootstrap connections
+- Maintain peer list
+- Handle disconnections
+- Reconnect gracefully
+
+## Message Routing
+- Direct messages
+- Broadcast messages
+- Topic subscriptions
 - Message queuing`,
-    'connection-patterns': `# Connection Patterns
-
-## Lifecycle
-- Connect
-- Authenticate
-- Exchange
-- Disconnect
-
-## Reliability
-- Heartbeat monitoring
-- Timeout handling
-- Retry mechanisms
+    'connection-patterns': `# Connection Patterns
+
+## Lifecycle
+- Connect
+- Authenticate
+- Exchange
+- Disconnect
+
+## Reliability
+- Heartbeat monitoring
+- Timeout handling
+- Retry mechanisms
 - Graceful degradation`,
-    'constraint-design': `# Constraint Design
-
-## Principles
-- Constraints should be explicit
-- Fail with clear messages
-- Allow override when needed
-- Document rationale
-
-## Implementation
-- Pre-conditions
-- Post-conditions
-- Invariants
+    'constraint-design': `# Constraint Design
+
+## Principles
+- Constraints should be explicit
+- Fail with clear messages
+- Allow override when needed
+- Document rationale
+
+## Implementation
+- Pre-conditions
+- Post-conditions
+- Invariants
 - Error handling`,
-    'validation-patterns': `# Validation Patterns
-
-## Input Validation
-- Type checking
-- Range validation
-- Format validation
-- Business rule validation
-
-## Error Reporting
-- Clear error messages
-- Field-level errors
-- Actionable suggestions
+    'validation-patterns': `# Validation Patterns
+
+## Input Validation
+- Type checking
+- Range validation
+- Format validation
+- Business rule validation
+
+## Error Reporting
+- Clear error messages
+- Field-level errors
+- Actionable suggestions
 - Error codes`,
-    'social-protocols': `# Social Protocols
-
-## Agent Discovery
-- Broadcast presence
-- Maintain registry
-- Handle joins/leaves
-- Cache agent info
-
-## Collaboration
-- Task distribution
-- Result aggregation
-- Conflict resolution
+    'social-protocols': `# Social Protocols
+
+## Agent Discovery
+- Broadcast presence
+- Maintain registry
+- Handle joins/leaves
+- Cache agent info
+
+## Collaboration
+- Task distribution
+- Result aggregation
+- Conflict resolution
 - Consensus building`,
-    'agent-discovery': `# Agent Discovery
-
-## Registration
-- Announce capabilities
-- Update status
-- Heartbeat mechanism
-- Graceful cleanup
-
-## Lookup
-- Search by capability
-- Filter by status
-- Sort by relevance
+    'agent-discovery': `# Agent Discovery
+
+## Registration
+- Announce capabilities
+- Update status
+- Heartbeat mechanism
+- Graceful cleanup
+
+## Lookup
+- Search by capability
+- Filter by status
+- Sort by relevance
 - Cache results`,
-    'project-intro': `# Project Introduction
-
-## Overview
-Bolloon is a P2P AI document processing system with multi-agent collaboration.
-
-## Key Features
-- Document processing pipeline
-- P2P network communication
-- Multi-agent task coordination
+    'project-intro': `# Project Introduction
+
+## Overview
+Bolloon is a P2P AI document processing system with multi-agent collaboration.
+
+## Key Features
+- Document processing pipeline
+- P2P network communication
+- Multi-agent task coordination
 - Constraint-based guardrails`,
-    'getting-started': `# Getting Started
-
-## Setup
-1. Install dependencies
-2. Configure environment
-3. Initialize P2P identity
-4. Start processing
-
-## Basic Usage
-- Process documents
-- Coordinate with peers
+    'getting-started': `# Getting Started
+
+## Setup
+1. Install dependencies
+2. Configure environment
+3. Initialize P2P identity
+4. Start processing
+
+## Basic Usage
+- Process documents
+- Coordinate with peers
 - Monitor performance`,
 };

package/dist/bollharness-integration/gate-state-machine.js

@@ -106,19 +106,6 @@ export class GateStateMachine {
     getState() {
         return { ...this.state, artifacts: new Map(this.state.artifacts), conversationHistory: [...this.state.conversationHistory] };
     }
-    restore(state) {
-        this.state = {
-            currentGate: state.currentGate,
-            entrySatisfied: state.entrySatisfied,
-            blockers: [...state.blockers],
-            requiredArtifact: state.requiredArtifact,
-            requiredNextSkill: state.requiredNextSkill,
-            requiredReviewSubstrate: state.requiredReviewSubstrate,
-            valueInjection: state.valueInjection,
-            artifacts: new Map(state.artifacts),
-            conversationHistory: [...state.conversationHistory],
-        };
-    }
     getCurrentGate() {
         return this.state.currentGate;
     }
@@ -309,19 +296,19 @@ export class GateStateMachine {
      */
     async expandSituationWithUserInput(baseSituation, userInput) {
         const model = getModel();
-        const prompt = `基于以下 Gate 情境模板和用户当前输入，生成一个更具体的情境描述。
-
-Gate 情境模板：${baseSituation}
-
-用户当前输入/artifact 内容：
-${userInput.substring(0, 1000)}
-
-要求：
-1. 结合用户输入，把情境描述具体化
-2. 保留原始 Gate 情境的重点（用词可以调整）
-3. 提取用户输入中与该 Gate 决策相关的关键信息
-4. 输出一个 50-150 字的自然语言情境描述
-
+        const prompt = `基于以下 Gate 情境模板和用户当前输入，生成一个更具体的情境描述。
+
+Gate 情境模板：${baseSituation}
+
+用户当前输入/artifact 内容：
+${userInput.substring(0, 1000)}
+
+要求：
+1. 结合用户输入，把情境描述具体化
+2. 保留原始 Gate 情境的重点（用词可以调整）
+3. 提取用户输入中与该 Gate 决策相关的关键信息
+4. 输出一个 50-150 字的自然语言情境描述
+
 直接输出情境描述，不要解释。`;
         const result = await model.chat(prompt, '');
         return result.reply.trim();