pi-harness-runtime 0.10.13 → 0.10.15

package/IMPLEMENTATION/RFC-0040/AI_BRIEF.md

@@ -1,79 +0,0 @@
-# RFC-0040 AI Brief: Framework Plugin SDK
-
-## Summary
-
-A comprehensive plugin SDK for extending the harness runtime with custom framework support, providers, and tooling.
-
-## Implementation Overview
-
-### Key Classes to Implement
-
-1. **PluginManager** (`manager.ts`)
-   - Plugin registration
-   - Lifecycle management (initialize, activate, deactivate)
-   - Hook system
-   - Configuration management
-
-2. **PluginLoader** (`loader.ts`)
-   - Load plugins from filesystem
-   - Load plugins from npm
-   - Validate plugin manifest
-   - Plugin sandboxing
-
-3. **PluginSandbox** (`sandbox/sandbox.ts`)
-   - Code isolation
-   - Resource limits
-   - Timeout enforcement
-   - Network/filesystem restrictions
-
-4. **HookDispatcher** (`hooks/dispatcher.ts`)
-   - Hook registration
-   - Hook execution
-   - Result aggregation
-
-### Extension Points
-
-- Framework detection extensions
-- Provider extensions
-- Generator extensions
-- Linter extensions
-- Tool extensions
-
-### Capabilities
-
-- `provider` - Custom AI provider
-- `framework` - Framework detection extension
-- `generator` - Code generator
-- `linter` - Custom linter
-- `template` - Code template
-- `validator` - Custom validator
-- `tool` - Custom tool
-- `hook` - Hook handler
-
-### Dependencies
-
-- `packages/types` - for runtime-types
-- `chokidar` - for file watching
-- `js-yaml` - for config parsing
-- `vm2` or `isolated-vm` - for sandboxing
-
-### Files to Create
-
-- `packages/framework-plugin-sdk/src/manager.ts`
-- `packages/framework-plugin-sdk/src/loader.ts`
-- `packages/framework-plugin-sdk/src/sandbox/sandbox.ts`
-- `packages/framework-plugin-sdk/src/sandbox/isolater.ts`
-- `packages/framework-plugin-sdk/src/registry/index.ts`
-- `packages/framework-plugin-sdk/src/registry/capability-registry.ts`
-- `packages/framework-plugin-sdk/src/registry/hook-registry.ts`
-- `packages/framework-plugin-sdk/src/hooks/dispatcher.ts`
-- `packages/framework-plugin-sdk/src/hooks/types.ts`
-- `packages/framework-plugin-sdk/src/config/schema.ts`
-- `packages/framework-plugin-sdk/src/config/loader.ts`
-- `packages/framework-plugin-sdk/src/extensions/framework.ts`
-- `packages/framework-plugin-sdk/src/extensions/provider.ts`
-- `packages/framework-plugin-sdk/src/extensions/generator.ts`
-- `packages/framework-plugin-sdk/src/extensions/linter.ts`
-- `packages/framework-plugin-sdk/src/extensions/tool.ts`
-- `packages/framework-plugin-sdk/src/types.ts`
-- `packages/framework-plugin-sdk/src/index.ts`

package/IMPLEMENTATION/RFC-0040/TASKS.md

@@ -1,77 +0,0 @@
-# RFC-0040 Implementation Tasks
-
-## Phase 1: Plugin Core
-
-- [ ] Create `packages/framework-plugin-sdk/` directory
-- [ ] Define plugin types (`PluginManifest`, `Plugin`, etc.)
-- [ ] Create `PluginManager` class
-- [ ] Implement `register()` method
-- [ ] Implement lifecycle methods:
-  - [ ] `initialize()`
-  - [ ] `activate()`
-  - [ ] `deactivate()`
-
-## Phase 2: Loader & Sandbox
-
-- [ ] Create `PluginLoader` class
-- [ ] Implement manifest validation
-- [ ] Implement filesystem loading
-- [ ] Create `PluginSandbox` class
-- [ ] Implement resource limits:
-  - [ ] Timeout enforcement
-  - [ ] Memory limits
-  - [ ] Network restrictions
-  - [ ] Filesystem access control
-- [ ] Implement code isolation
-
-## Phase 3: Registry
-
-- [ ] Create `PluginRegistry` class
-- [ ] Implement plugin state management
-- [ ] Create `CapabilityRegistry`
-- [ ] Implement capability checking
-
-## Phase 4: Hooks System
-
-- [ ] Create `HookDispatcher` class
-- [ ] Define hook types
-- [ ] Implement hook registration
-- [ ] Implement hook execution
-- [ ] Implement result aggregation
-- [ ] Add built-in hooks:
-  - [ ] beforeJobStart
-  - [ ] afterJobComplete
-  - [ ] beforeTaskExecute
-  - [ ] afterTaskComplete
-  - [ ] onError
-  - [ ] onFrameworkDetected
-  - [ ] beforeGenerate
-  - [ ] afterGenerate
-
-## Phase 5: Extension Points
-
-- [ ] Create `FrameworkExtension` interface
-- [ ] Create `ProviderExtension` interface
-- [ ] Create `GeneratorExtension` interface
-- [ ] Create `LinterExtension` interface
-- [ ] Create `ToolExtension` interface
-
-## Phase 6: Configuration
-
-- [ ] Create config schema validation
-- [ ] Implement `loadPluginConfig()`
-- [ ] Add per-plugin configuration
-- [ ] Implement config hot-reload
-
-## Phase 7: Plugin Examples
-
-- [ ] Create example plugin (`builtin/example-plugin/`)
-- [ ] Document plugin creation process
-- [ ] Create npm publishing guide
-
-## Phase 8: Security & Testing
-
-- [ ] Security audit of sandbox
-- [ ] Write unit tests
-- [ ] Test plugin isolation
-- [ ] Performance testing

package/IMPLEMENTATION/RFC-0041/ACCEPTANCE_CRITERIA.md

@@ -1,8 +0,0 @@
-# Acceptance Criteria — RFC-0041
-
-- Package exports a documented `compilePrompt` API.
-- All error cases use typed error codes.
-- Required sections survive compaction.
-- No credential-like value appears in persisted artifacts.
-- Generated metadata includes token estimate and source references.
-- Tests pass without network access.

package/IMPLEMENTATION/RFC-0041/AI_BRIEF.md

@@ -1,26 +0,0 @@
-# AI Brief — RFC-0041 Prompt Compiler
-
-Implement a deterministic prompt compiler. Start with pure functions and inject filesystem, clock, hashing, token estimation, policy, and redaction dependencies.
-
-Required source files:
-
-```text
-packages/prompt-compiler/src/
-+-- types.ts
-+-- normalize.ts
-+-- section-builder.ts
-+-- deduplicate.ts
-+-- budget.ts
-+-- validate.ts
-+-- render.ts
-+-- compiler.ts
-+-- index.ts
-```
-
-Hard requirements:
-
-- No provider network calls.
-- No secret persistence.
-- Same semantic input must produce the same content hash.
-- Project rules and acceptance criteria cannot be compacted away.
-- Output-limit continuation must avoid repeating completed work.

package/IMPLEMENTATION/RFC-0041/FILES.md

@@ -1,12 +0,0 @@
-# Files — RFC-0041
-
-Create `packages/prompt-compiler/src/*` and `packages/prompt-compiler/test/*`.
-
-Modify runtime integration only after package tests pass:
-
-```text
-harness/loop-runtime.ts
-harness/agent-handoff.ts
-```
-
-Do not modify quota, notification, browser, or worktree packages.

package/IMPLEMENTATION/RFC-0041/TASKS.md

@@ -1,12 +0,0 @@
-# Tasks — RFC-0041
-
-1. Define public TypeScript interfaces and discriminated error codes.
-2. Implement request normalization with stable array ordering.
-3. Implement deterministic section assembly.
-4. Implement exact deduplication.
-5. Implement token-budget compaction for optional sections.
-6. Implement provider rendering profiles.
-7. Implement SHA-256 content hashing.
-8. Persist `prompt.md`, `prompt.json`, `sources.json`, and `metadata.json`.
-9. Add continuation prompt support.
-10. Add unit and integration tests.

package/IMPLEMENTATION/RFC-0041/TESTS.md

@@ -1,12 +0,0 @@
-# Tests — RFC-0041
-
-- Deterministic hash for identical input
-- Missing objective
-- Missing output contract
-- Required source missing
-- Token budget exceeded
-- Secret redaction
-- Duplicate context removal
-- Provider profile rendering
-- Continuation without repetition
-- Persistence artifact completeness

package/IMPLEMENTATION/RFC-0042/ACCEPTANCE_CRITERIA.md

@@ -1,7 +0,0 @@
-# Acceptance Criteria — RFC-0042
-
-- Context never exceeds requested budget.
-- Required items are not silently removed.
-- Sensitive contents are excluded before persistence.
-- Identical repository state produces identical compiled context.
-- OKF and source code references appear in one traceable source graph.

package/IMPLEMENTATION/RFC-0042/AI_BRIEF.md

@@ -1,5 +0,0 @@
-# AI Brief — RFC-0042 Context Compiler
-
-Build a bounded context selection engine that combines project rules, OKF knowledge, repository slices, blackboard state, test failures, and prior reports.
-
-Never dump the entire repository. Every selected item needs a source reference; every omitted item needs a reason.

package/IMPLEMENTATION/RFC-0042/FILES.md

@@ -1,14 +0,0 @@
-# Files — RFC-0042
-
-```text
-packages/context-compiler/src/
-+-- types.ts
-+-- collectors/
-+-- policy-filter.ts
-+-- scorer.ts
-+-- deduplicate.ts
-+-- budget.ts
-+-- source-graph.ts
-+-- cache.ts
-+-- compiler.ts
-```

package/IMPLEMENTATION/RFC-0042/TASKS.md

@@ -1,12 +0,0 @@
-# Tasks — RFC-0042
-
-1. Define candidate, compiled item, omission, and source-graph types.
-2. Add source collectors for rules, OKF, repository, Git diff, tests, and blackboard.
-3. Add policy filter and sensitive path denial.
-4. Implement deterministic scoring.
-5. Add exact deduplication and slice merge.
-6. Fit optional items into token budget.
-7. Generate cache key from selected source hashes.
-8. Persist compiled context and omission report.
-9. Add invalidation hooks.
-10. Add tests.

package/IMPLEMENTATION/RFC-0042/TESTS.md

@@ -1,11 +0,0 @@
-# Tests — RFC-0042
-
-- Required rule inclusion
-- `.env` denial
-- Broken optional OKF link
-- Broken required source
-- Duplicate slice merge
-- Token budget
-- Cache invalidation
-- Stable ordering
-- Omission reason completeness

package/IMPLEMENTATION/RFC-0043/ACCEPTANCE_CRITERIA.md

@@ -1,7 +0,0 @@
-# Acceptance Criteria — RFC-0043
-
-- Every goal traces to source text.
-- Blocking ambiguities are explicit.
-- Preferences are not silently promoted to requirements.
-- Acceptance criteria are observable or clearly marked manual.
-- Original wording is preserved.

package/IMPLEMENTATION/RFC-0043/AI_BRIEF.md

@@ -1,5 +0,0 @@
-# AI Brief — RFC-0043 Requirement Compiler
-
-Convert raw human requirement text into a traceable structured requirement. Preserve uncertainty. Never invent material business logic.
-
-The original language and source references must remain available.

package/IMPLEMENTATION/RFC-0043/FILES.md

@@ -1,14 +0,0 @@
-# Files — RFC-0043
-
-```text
-packages/requirement-compiler/src/
-+-- types.ts
-+-- extractor.ts
-+-- classifier.ts
-+-- ambiguity.ts
-+-- acceptance.ts
-+-- risk.ts
-+-- terminology.ts
-+-- validate.ts
-+-- compiler.ts
-```

package/IMPLEMENTATION/RFC-0043/TASKS.md

@@ -1,12 +0,0 @@
-# Tasks — RFC-0043
-
-1. Define raw and compiled requirement models.
-2. Implement statement extraction and classification.
-3. Separate mandatory constraints from preferences.
-4. Detect contradiction and ambiguity.
-5. Normalize acceptance criteria to observable conditions.
-6. Add risk tags.
-7. Preserve multilingual terminology.
-8. Add validation and status transitions.
-9. Persist source mapping.
-10. Add tests.

package/IMPLEMENTATION/RFC-0043/TESTS.md

@@ -1,10 +0,0 @@
-# Tests — RFC-0043
-
-- Explicit fact preservation
-- Preference versus constraint
-- Contradiction detection
-- Given/When/Then normalization
-- Thai term preservation
-- Risk tagging
-- Empty requirement rejection
-- Source traceability

package/IMPLEMENTATION/RFC-0044/ACCEPTANCE_CRITERIA.md

@@ -1,7 +0,0 @@
-# Acceptance Criteria — RFC-0044
-
-- Graph is acyclic.
-- Every task has required output evidence.
-- Every acceptance criterion is assigned.
-- Unsafe parallel file overlap is prevented.
-- Project command restrictions are preserved.

package/IMPLEMENTATION/RFC-0044/AI_BRIEF.md

@@ -1,5 +0,0 @@
-# AI Brief — RFC-0044 Task Compiler
-
-Generate an executable, acyclic task graph from the compiled requirement and project profile. Every task must have measurable outputs and command policy.
-
-Do not execute tasks in this package.

package/IMPLEMENTATION/RFC-0044/FILES.md

@@ -1,13 +0,0 @@
-# Files — RFC-0044
-
-```text
-packages/task-compiler/src/
-+-- types.ts
-+-- decompose.ts
-+-- file-scope.ts
-+-- verification.ts
-+-- command-policy.ts
-+-- graph.ts
-+-- validate.ts
-+-- compiler.ts
-```

package/IMPLEMENTATION/RFC-0044/TASKS.md

@@ -1,12 +0,0 @@
-# Tasks — RFC-0044
-
-1. Define task and graph types.
-2. Implement requirement decomposition.
-3. Assign task types and complexity.
-4. Assign file scope and ownership.
-5. Map acceptance criteria to verification tasks.
-6. Apply command policy.
-7. Build deterministic DAG.
-8. Detect cycles and parallel file overlap.
-9. Emit provider capability hints.
-10. Add tests.

package/IMPLEMENTATION/RFC-0044/TESTS.md

@@ -1,10 +0,0 @@
-# Tests — RFC-0044
-
-- Standard engineering flow
-- Cycle rejection
-- File ownership overlap
-- Acceptance mapping
-- Build/migrate/commit restrictions
-- Browser E2E insertion
-- Advisory provider hint
-- Deterministic topology

package/IMPLEMENTATION/RFC-0045/ACCEPTANCE_CRITERIA.md

@@ -1,30 +0,0 @@
-# Acceptance Criteria — RFC-0045
-
-**Status: ✅ ALL CRITERIA MET**
-
-## Acceptance Criteria
-
-| Criterion | Status | Implementation |
-| ----------- | -------- | ---------------- |
-| Framework detection includes confidence and evidence | ✅ | `DetectedFramework.confidence` and `DetectionSignal[]` in profile |
-| Multi-app repositories are represented | ✅ | `applications[]` field with `ApplicationProfile[]` |
-| Project rules are discoverable and prioritized | ✅ | `rules[]` with `RulePriority` (mandatory/advisory/convention) |
-| Sensitive file contents are never read | ✅ | `FileSystemWalker` pattern matching; only paths recorded |
-| Commands are detected but not executed | ✅ | Script parsing from package.json, no execution |
-| Generic fallback permits planning | ✅ | `GenericFrameworkDetector` with generic signals |
-
-## Verification
-
-```bash
-cd packages/project-analyzer
-npm test
-# 14 pass, 0 fail
-```
-
-## Additional Features
-
-- Git revision-based cache invalidation
-- Symlink escape prevention
-- Bounded traversal with configurable limits
-- Plugin interface for custom framework detection
-- Confidence scoring with evidence collection

package/IMPLEMENTATION/RFC-0045/AI_BRIEF.md

@@ -1,53 +0,0 @@
-# AI Brief — RFC-0045 Project Analyzer
-
-**Status: ✅ IMPLEMENTED**
-
-## Summary
-
-The Project Analyzer has been fully implemented as `packages/project-analyzer`. It analyzes repository structure without executing project scripts and produces a safe, cacheable `ProjectProfile` with:
-
-- **Framework detection** with confidence scoring
-- **Language detection** with coverage percentages
-- **Application discovery** for monorepos
-- **Command discovery** from package.json, composer.json, etc.
-- **Rule discovery** from AGENTS.md, RULES.md, etc.
-- **Sensitive path detection** (never reads contents)
-- **Test capability detection** (vitest, jest, playwright, etc.)
-- **Caching** with git revision-based invalidation
-
-## Key Components
-
-1. **FileSystemWalker** - Bounded, secure filesystem traversal
-2. **GenericFrameworkDetector** - Signal-based framework detection
-3. **AnalysisCache** - Git-revision-based caching
-4. **Rule Discovery** - Parses AGENTS.md, RULES.md, CONTRIBUTING.md
-5. **Command Discovery** - Extracts npm/pip/composer scripts
-
-## Dependencies
-
-- `@pi/types` - Shared types
-- `@pi/framework-detector` - Framework detection signals
-
-## Usage
-
-```typescript
-import { createProjectAnalyzer } from "@pi/project-analyzer";
-
-const analyzer = createProjectAnalyzer();
-const result = await analyzer.analyze({
-  repositoryRoot: "/path/to/repo"
-});
-
-if (result.success) {
-  console.log(result.profile);
-}
-```
-
-## Tests
-
-All 14 tests pass:
-
-- Language detection tests
-- Analyzer instantiation and analysis tests
-- Cache key generation tests
-- Command script parsing tests

package/IMPLEMENTATION/RFC-0045/FILES.md

@@ -1,13 +0,0 @@
-# Files — RFC-0045
-
-```text
-packages/project-analyzer/src/
-+-- types.ts
-+-- walker.ts
-+-- signals.ts
-+-- rule-discovery.ts
-+-- command-discovery.ts
-+-- cache.ts
-+-- analyzer.ts
-+-- plugins/
-```

package/IMPLEMENTATION/RFC-0045/TASKS.md

@@ -1,31 +0,0 @@
-# Tasks — RFC-0045
-
-**Status: ✅ ALL TASKS COMPLETED**
-
-## Completed Tasks
-
-1. ✅ **Define project profile types** - `src/types.ts`
-2. ✅ **Implement bounded filesystem traversal** - `src/walker.ts`
-3. ✅ **Add generic detection signals** - `src/signals.ts`
-4. ✅ **Add plugin contract** - `FrameworkAnalyzerPlugin` interface in `src/types.ts`
-5. ✅ **Implement Frappe, Frappe SPA, Next.js, React/Vite, Django, and Laravel detectors** - Generic signals in `src/signals.ts`
-6. ✅ **Detect monorepo applications** - `applications[]` in `analyzer.ts`
-7. ✅ **Discover rule files and package scripts** - `rule-discovery.ts`, `command-discovery.ts`
-8. ✅ **Classify sensitive and generated paths** - Pattern matching in `walker.ts`
-9. ✅ **Implement cache key and invalidation** - `cache.ts`
-10. ✅ **Add security and framework tests** - `test/index.test.ts` (14 passing tests)
-
-## File Structure
-
-```
-packages/project-analyzer/src/
-+-- types.ts           ✅ Project profile types
-+-- walker.ts          ✅ Bounded filesystem traversal
-+-- signals.ts         ✅ Generic detection signals
-+-- rule-discovery.ts ✅ Rule file discovery
-+-- command-discovery.ts ✅ Command discovery
-+-- cache.ts          ✅ Cache key and invalidation
-+-- analyzer.ts       ✅ Main analyzer
-+-- plugins/
-    +-- index.ts      ✅ Plugin exports
-```

package/IMPLEMENTATION/RFC-0045/TESTS.md

@@ -1,62 +0,0 @@
-# Tests — RFC-0045
-
-**Status: ✅ TESTS PASSING**
-
-## Test File
-
-`packages/project-analyzer/test/index.test.ts`
-
-## Running Tests
-
-```bash
-cd packages/project-analyzer
-npm test
-```
-
-## Test Results
-
-```
-14 pass, 0 fail
-34 expect() calls
-```
-
-## Test Coverage
-
-### Language Detection Tests
-
-- `detectLanguages > detects TypeScript files`
-- `detectLanguages > handles empty file list`
-- `detectLanguages > sorts by coverage descending`
-
-### Analyzer Tests
-
-- `ProjectAnalyzer > creates analyzer instance`
-- `ProjectAnalyzer > analyzes the current repository`
-- `ProjectAnalyzer > detects frameworks`
-- `ProjectAnalyzer > detects languages`
-- `ProjectAnalyzer > discovers rules`
-- `ProjectAnalyzer > generates warnings for unknown frameworks`
-
-### Cache Tests
-
-- `AnalysisCache > generates consistent cache keys`
-- `AnalysisCache > generates different keys for different inputs`
-
-### Command Discovery Tests
-
-- `Package Script Parsing > extracts scripts from package.json`
-- `Package Script Parsing > handles empty scripts`
-- `Package Script Parsing > marks primary scripts correctly`
-
-## Additional Test Scenarios (to add)
-
-1. Detect Frappe bench
-2. Detect Frappe SPA
-3. Detect Next.js
-4. Detect React/Vite
-5. Return generic profile for unknown project
-6. Handle monorepo applications
-7. Discover AGENTS.md rules
-8. Record but do not execute build/migrate commands
-9. Reject symlink traversal outside root
-10. Cache invalidates when rule files change

package/IMPLEMENTATION/RFC-0046/ACCEPTANCE_CRITERIA.md

@@ -1 +0,0 @@
-Tests pass

package/IMPLEMENTATION/RFC-0046/AI_BRIEF.md

@@ -1 +0,0 @@
-Implement DEPENDENCY_ANALYZER.

package/IMPLEMENTATION/RFC-0046/FILES.md

@@ -1,2 +0,0 @@
-src/
-test/

package/IMPLEMENTATION/RFC-0046/TASKS.md

@@ -1,3 +0,0 @@
-1.Interfaces
-2.Core
-3.Tests

package/IMPLEMENTATION/RFC-0046/TESTS.md

@@ -1 +0,0 @@
-Happy path

package/IMPLEMENTATION/RFC-0047/ACCEPTANCE_CRITERIA.md

@@ -1 +0,0 @@
-Tests pass

package/IMPLEMENTATION/RFC-0047/AI_BRIEF.md

@@ -1 +0,0 @@
-Implement REPOSITORY_KNOWLEDGE_GRAPH.

package/IMPLEMENTATION/RFC-0047/FILES.md

@@ -1,2 +0,0 @@
-src/
-test/

package/IMPLEMENTATION/RFC-0047/TASKS.md

@@ -1,3 +0,0 @@
-1.Interfaces
-2.Core
-3.Tests

package/IMPLEMENTATION/RFC-0047/TESTS.md

@@ -1 +0,0 @@
-Happy path

package/IMPLEMENTATION/RFC-0048/ACCEPTANCE_CRITERIA.md

@@ -1 +0,0 @@
-Tests pass

package/IMPLEMENTATION/RFC-0048/AI_BRIEF.md

@@ -1 +0,0 @@
-Implement CODE_MERGE_ENGINE.

package/IMPLEMENTATION/RFC-0048/FILES.md

@@ -1,2 +0,0 @@
-src/
-test/

package/IMPLEMENTATION/RFC-0048/TASKS.md

@@ -1,3 +0,0 @@
-1.Interfaces
-2.Core
-3.Tests

package/IMPLEMENTATION/RFC-0048/TESTS.md

@@ -1 +0,0 @@
-Happy path

package/IMPLEMENTATION/RFC-0049/ACCEPTANCE_CRITERIA.md

@@ -1 +0,0 @@
-Tests pass

package/IMPLEMENTATION/RFC-0049/AI_BRIEF.md

@@ -1 +0,0 @@
-Implement CONFLICT_RESOLUTION_ENGINE.

package/IMPLEMENTATION/RFC-0049/FILES.md

@@ -1,2 +0,0 @@
-src/
-test/