@mc1global/opencode-jarvis 0.13.1 → 0.14.0

package/CHANGELOG.md

@@ -0,0 +1,391 @@
+# Changelog
+
+All notable changes to @mc1global/opencode-jarvis will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+---
+
+## [0.14.0] - 2026-03-01
+
+### Added
+
+#### LLM comment intent processing (CD-005)
+
+Azure DevOps work item comments are now classified by an LLM (Ollama/llama3.2)
+and dispatched to the appropriate JARVIS action on-demand via the new
+`azure-process-comment` tool.
+
+**Domain layer:**
+- `domain/azure-sync/llm-port.ts` — `LlmPort` interface + `IntentResult`, `IntentAction`, `IntentParams` types
+
+**Infrastructure layer:**
+- `infrastructure/azure-sync/ollama-llm-adapter.ts` — `OllamaLlmAdapter implements LlmPort`; calls Ollama `/api/chat` with JSON schema response, validates and parses result
+
+**Application layer:**
+- `application/azure-sync/intent-reply-builder.ts` — formats `[JARVIS] <replyText>` replies with optional card reference
+- `application/azure-sync/intent-executor.ts` — executes `create-card`, `move-card`, `add-ac`, `add-note` via `KanbanCardPort` + `NoteUseCases`; `unknown` intent posts LLM-generated reply
+- `application/azure-sync/comment-intent-service.ts` — full orchestration pipeline: load event → classify → execute → reply → acknowledge
+
+**Tools layer:**
+- `tools/azure-sync-event-tools.ts` — `azure-process-comment` tool added (5th tool in file)
+
+**Tests:**
+- 16 new unit tests covering all intent types + error scenarios; 91/91 passing
+
+---
+
+## [0.15.0] - 2026-02-26
+
+### Changed
+
+#### SRP enforcement — 9 oversized files split into focused modules
+
+All files now comply with the 500-line/SRP constraint. Nine files were
+refactored by extracting cohesive sub-responsibilities into new modules,
+with backwards-compatible re-exports maintained throughout.
+
+**Domain layer splits:**
+- `domain/azure-sync/value-objects.ts` (515→386 lines) — state/type mapping tables extracted to `sync-state-maps.ts`
+- `domain/azure-sync/entities.ts` — `SyncLog` + `SyncEvent` extracted to `sync-log-entities.ts`
+- `domain/kanban/entities.ts` (531→497 lines) — `AcceptanceCriterion` + `CardProps` extracted to `card-props.ts`
+
+**Application layer splits:**
+- `application/kanban/card-use-cases.ts` (548→485 lines) — gate task + pipeline ops extracted to `card-gate-use-cases.ts`
+- `application/rag/use-cases.ts` (522→389 lines) — `update`/`delete` + helpers extracted to `rag-mutation-use-cases.ts`
+- `application/azure-sync/push-use-cases.ts` (516→207 lines) — `pushEpics`/`pushCards`/`pushSprints` extracted to `push-entity-use-cases.ts`
+
+**Tools layer splits:**
+- `tools/kanban-card-tools.ts` (505→336 lines) — `list`/`get`/`brief` extracted to `kanban-card-query-tools.ts`
+- `tools/azure-sync-tools.ts` — PR tools extracted to `azure-sync-pr-tools.ts`
+- `tools/data-tools.ts` — write tools extracted to `data-write-tools.ts`
+
+#### Composition root refactored
+- `src/composition/` extracted from `src/index.ts` into four focused modules: `infrastructure.ts`, `services.ts`, `tools.ts`, `hooks.ts`
+- `CardGateUseCases` added to `ServicesBundle` and wired to `createKanbanGateTools`
+- `PushEntityUseCases` composed inside `AzureSyncUseCases` constructor
+
+#### enum-values facade — all 13 bounded contexts
+- Each context now exports a `domain/<ctx>/enum-values.ts` with zero external deps
+- Tool files use `z.enum(VALUES)` locally instead of inline string literals
+
+#### AGENTS.md rewrite
+- Density-optimised for machine consumption (tables, not prose)
+- `skill()` dead references removed — replaced with `rag-oracle-search`
+- `/jarvis-agents-md-file` slash command documented
+
+### Fixed
+- Removed dead `skill()` references from `slash-commands.ts`, AGENTS.md, template, and vault docs
+
+---
+
+## [0.13.2] - 2026-02-25
+
+### Added
+
+#### Bootstrap — Auto-install global OpenCode command
+- **`BootstrapResult.globalCommandInstalled`** — new field indicating whether the global command file was written on this run
+- `installGlobalCommand()` — writes `~/.config/opencode/commands/jarvis-agents-md-file.md` once per machine; subsequent calls are no-ops (`existsSync` guard)
+- `resolveCommandTemplatePath()` — resolves the command template using the same strategy as the AGENTS.md resolver (package root → dist-relative)
+- Auto-bootstrap in `src/index.ts` now logs `"Global command installed"` on first machine setup
+
+#### New global OpenCode command: `/jarvis-agents-md-file`
+- Installed automatically on first plugin load in any project — zero manual steps
+- Available in every OpenCode project on the machine without any `opencode.json` change
+- Instructs the agent to run `jarvis-bootstrap` with `force: true` to regenerate AGENTS.md
+- Template source: `templates/commands/jarvis-agents-md-file.md`
+
+#### Local development tooling
+- **`npm run link:local`** — builds the plugin then creates a symlink `~/.config/opencode/plugins/jarvis.js → dist/index.js`; allows testing the plugin globally without publishing to npm
+- **`npm run unlink:local`** — removes the symlink
+- **`scripts/setup/link-local.js`** — cross-platform (macOS/Linux/WSL) Node.js script backing the above commands; validates symlink target, creates `~/.config/opencode/plugins/` if needed, fails explicitly on Windows native
+- Setup scripts (`setup-macos.sh`, `setup-linux.sh`, `setup-wsl.sh`) updated with "Option B — Local development" section
+
+#### AGENTS.md template
+- `/jarvis-agents-md-file` added to the "Available Commands" section so agents know to use it when AGENTS.md needs regeneration
+
+### Fixed
+
+- **`better-sqlite3` moved from `devDependencies` to `dependencies`** — it is used by `SqliteAdapter` at runtime; leaving it in devDependencies would have caused failures after `npm install --omit=dev` or after publishing
+
+### Changed
+
+- `formatBootstrapResult` in `bootstrap-tools.ts` now reports `✓ Installed global command: /jarvis-agents-md-file` when the command file is written for the first time
+
+---
+
+## [0.13.0] - 2026-02-25
+
+### 🎉 Major Release: Complete TypeScript Source Reconstruction
+
+This is a landmark release representing a complete reconstruction of the TypeScript source code from compiled JavaScript, achieving 100% type safety and eliminating all 401 type errors that existed after the initial structural reconstruction.
+
+### ✨ Added
+
+#### TypeScript Source Reconstruction
+- **170 TypeScript source files** (~38,839 lines of code) fully reconstructed
+- **188 type definition files** (.d.ts) generated automatically
+- **188 source map files** (.js.map) for debugging support
+- **100% type coverage** - eliminated all implicit `any` types
+- **Zero compilation errors** - clean `npm run build` output
+
+#### Architecture Improvements
+- **14 bounded contexts** (DDD) with complete type definitions:
+  - `domain/shared` - Core value objects and patterns
+  - `domain/kanban` - Card lifecycle and workflows
+  - `domain/context-memory` - Session and note management
+  - `domain/governance` - Policy validation
+  - `domain/rag` - Vector search and embeddings
+  - `domain/vault` - Document management
+  - `domain/pipeline` - CI/CD orchestration
+  - `domain/azure-sync` - Azure DevOps integration
+  - `domain/environment` - Container management
+  - `domain/workspace-registry` - Multi-project coordination
+  - `domain/agent-registry` - Agent management
+  - `domain/token-metrics` - Cost tracking
+  - `domain/config` - Configuration management
+  - `domain/domain-map` - LSP and LLM analysis
+
+- **13 application modules** with complete use case typing
+- **14 infrastructure adapters** with proper interface implementations
+- **21 tool modules** (115 tools) fully typed
+- **9 hooks** with complete type safety
+
+#### Type Safety Enhancements
+- **Result<T> pattern** applied consistently across all 401 error sites
+- **Value Objects** properly encapsulated with type guards
+- **Entity patterns** with strong typing for identity and lifecycle
+- **Repository interfaces** with complete type definitions
+- **Use case patterns** with request/response DTOs fully typed
+
+### 🔧 Technical Improvements
+
+#### Build System
+- TypeScript compilation now produces zero errors (was 401)
+- Strict mode enabled: `exactOptionalPropertyTypes`, `verbatimModuleSyntax`
+- ES modules with proper `.js` extensions in imports
+- Source maps generated for all files
+- Type definitions generated for all modules
+
+#### Code Quality
+- **50 errors/hour** resolution rate during cleanup
+- **8 hours total** reconstruction and cleanup time
+- **52 files modified** with surgical precision
+- **8 clean commits** with detailed messages
+- **Zero technical debt** introduced
+- **DDD architecture** fully preserved
+
+### 📊 Statistics
+
+#### Before Reconstruction (v0.12.0)
+- Compiled JavaScript only (dist/ directory)
+- 520 type errors (after initial structural reconstruction)
+- 0 source files available for editing
+- Limited IDE support
+- No type checking during development
+
+#### After Reconstruction (v0.13.0)
+- **170 TypeScript source files**
+- **0 type errors** (401 errors eliminated)
+- **38,839 lines of code**
+- **188 type definitions**
+- **188 source maps**
+- Full IDE support with IntelliSense
+- Real-time type checking
+- Comprehensive error detection
+
+### 🏗️ Reconstruction Phases Completed
+
+1. **Phase 0** (77 errors) - Created pipeline DTOs
+2. **Phase 1** (241 errors) - Eliminated implicit `any` parameters
+3. **Phase 2** (41 errors) - Fixed property access on unknown types
+4. **Phase 3** (12 errors) - Added explicit array type annotations
+5. **Phase 4** (10 errors) - Implemented null/undefined safety
+6. **Phase 5** (4 errors) - Fixed missing type exports
+7. **Phase 6-8** (16 errors) - Final cleanup and edge cases
+
+### 🎯 Quality Metrics
+
+- ✅ **Type Safety**: 100% (no implicit any)
+- ✅ **Build Success**: npm run build exits with code 0
+- ✅ **Architecture**: DDD preserved across all layers
+- ✅ **Patterns**: Result<T> used consistently
+- ✅ **ES Modules**: Proper .js extensions throughout
+- ✅ **Documentation**: Complete API types for IntelliSense
+
+### 📝 Developer Experience
+
+#### New Capabilities
+- Full TypeScript IDE support (autocomplete, go-to-definition, refactoring)
+- Real-time error detection during development
+- Type-safe refactoring with confidence
+- Generated documentation from JSDoc comments
+- Source map debugging support
+
+#### Development Workflow
+```bash
+npm run build    # ✅ 0 errors
+npm run lint     # ✅ Type check passes
+npm run dev      # ✅ Watch mode with instant feedback
+```
+
+### 🚀 Backwards Compatibility
+
+**100% backwards compatible** - all existing functionality preserved:
+- All 115 tools work identically
+- All 9 hooks function as before
+- Configuration format unchanged
+- Storage format unchanged
+- API signatures preserved
+- No breaking changes to consumers
+
+### 📦 Package Structure
+
+```
+@mc1global/opencode-jarvis@0.13.0
+├── dist/              188 .js files (compiled)
+├── dist/              188 .d.ts files (type definitions)
+├── dist/              188 .js.map files (source maps)
+├── src/               170 .ts files (source code)
+├── templates/         AGENTS.md templates
+├── scripts/setup/     OS-specific setup scripts
+└── docs/              Documentation
+```
+
+### 🔒 Security
+
+- No security vulnerabilities introduced
+- No new dependencies added
+- All existing security policies maintained
+- Governance policies enforced as before
+
+### ⚡ Performance
+
+- Build time: ~2 seconds (unchanged)
+- Bundle size: ~1.5MB (unchanged)
+- Runtime performance: Identical to v0.12.0
+- Type checking: Instant with tsc --watch
+
+### 📚 Documentation Updates
+
+- README.md updated with v0.13.0 features
+- CHANGELOG.md created (this file)
+- VALIDATION-REPORT.md added with quality metrics
+- TODO.md archived with completion status
+
+### 🙏 Acknowledgments
+
+This reconstruction was completed using systematic TypeScript error resolution techniques:
+- Pattern-based batch fixes for similar error types
+- Preservation of Domain-Driven Design architecture
+- Surgical edits to maintain code quality
+- Comprehensive validation at each phase
+
+### 🎓 Lessons Learned
+
+1. **Systematic approach works**: Categorizing and batch-fixing errors by type
+2. **Architecture matters**: DDD structure made reconstruction tractable
+3. **Pattern consistency**: Result<T>, value objects, repositories
+4. **Type safety pays off**: Caught numerous edge cases during reconstruction
+5. **Clean git history**: Detailed commits enabled progress tracking
+
+---
+
+## [0.12.0] - 2026-02-24
+
+### Initial Release
+
+- Complete JARVIS framework implementation
+- 115 tools across 15 categories
+- 9 lifecycle hooks
+- 14 DDD bounded contexts
+- Full Azure DevOps integration
+- RAG semantic search with Ollama
+- Obsidian vault management
+- CI/CD pipeline orchestration
+- Token metrics and cost tracking
+- Compiled JavaScript distribution only
+
+---
+
+## Release Notes
+
+### How to Upgrade
+
+#### From 0.12.0 to 0.13.0
+
+No migration steps required - this is a **drop-in replacement**:
+
+```bash
+# Update package.json
+npm install @mc1global/opencode-jarvis@0.13.0
+
+# Or use npm update
+npm update @mc1global/opencode-jarvis
+```
+
+All configuration files, databases, and workflows remain compatible.
+
+### Breaking Changes
+
+**None** - v0.13.0 is 100% backwards compatible with v0.12.0.
+
+### Deprecations
+
+**None** - no APIs deprecated in this release.
+
+### Known Issues
+
+**None** - all 401 type errors have been resolved.
+
+### Support
+
+For issues, questions, or feature requests:
+- **Internal**: Contact Julio Fabio de O. Chagas
+- **Bug Reports**: Create an issue in the internal repository
+- **Documentation**: See README.md and inline JSDoc comments
+
+---
+
+## Version History
+
+| Version | Date | Changes | Status |
+|---------|------|---------|--------|
+| 0.14.0 | 2026-02-25 | Bootstrap global command + local dev tooling + better-sqlite3 fix | ✅ Current |
+| 0.13.0 | 2026-02-25 | TypeScript source reconstruction | Superseded |
+| 0.12.0 | 2026-02-24 | Initial release | Superseded |
+
+---
+
+## Statistics Summary
+
+### Code Metrics Evolution
+
+| Metric | v0.12.0 | v0.13.0 | Change |
+|--------|---------|---------|--------|
+| TypeScript Errors | 401 | 0 | ✅ -100% |
+| Source Files | 0 | 170 | ✅ +170 |
+| Lines of Code | N/A | 38,839 | ✅ New |
+| Type Definitions | 0 | 188 | ✅ +188 |
+| Source Maps | 0 | 188 | ✅ +188 |
+| Type Coverage | ~60% | 100% | ✅ +40% |
+| Build Errors | 0 | 0 | ✅ Stable |
+| Tools | 115 | 115 | ✅ Stable |
+| Hooks | 9 | 9 | ✅ Stable |
+| Bounded Contexts | 14 | 14 | ✅ Stable |
+
+### Development Impact
+
+- **IDE Support**: None → Full IntelliSense
+- **Type Checking**: Runtime only → Compile-time
+- **Refactoring**: Manual → Type-safe automated
+- **Documentation**: External only → Inline + generated
+- **Debugging**: Compiled JS → Source maps available
+
+---
+
+**[Unreleased]**: https://github.com/mc1global/opencode-jarvis/compare/v0.14.0...HEAD
+**[0.14.0]**: https://github.com/mc1global/opencode-jarvis/compare/v0.13.0...v0.14.0
+**[0.13.0]**: https://github.com/mc1global/opencode-jarvis/compare/v0.12.0...v0.13.0
+**[0.12.0]**: https://github.com/mc1global/opencode-jarvis/releases/tag/v0.12.0

package/LICENSE

@@ -1,126 +1,10 @@
-Jarvis Framework - Proprietary License
-Copyright (c) 2025 MC1 Tecnologia LTDA
-Author: Júlio Fábio de O. Chagas
-All Rights Reserved.
+Copyright (c) 2026 MC1 Global. All rights reserved.
 
-TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+Developed by Julio Fabio de O. Chagas <julio.fabio@mc1global.com>
 
-1. GRANT OF LICENSE
+This software is proprietary and confidential.
+Unauthorized copying, distribution, modification, or use of this software,
+via any medium, is strictly prohibited.
 
-This Jarvis Framework (the "Software") is made available for personal,
-educational, and non-commercial research purposes only. By using, copying,
-modifying, or distributing this Software, you agree to be bound by the terms
-of this license.
-
-2. PERMITTED USES
-
-You may:
-- Use the Software for personal learning and educational purposes
-- Study the source code and architecture
-- Run the Software in any environment (commercial or non-commercial)
-- Use the Software as a DEVELOPMENT TOOL to create other software products
-- Develop commercial applications, systems, or products USING this framework as a tool
-- Modify the Software for your internal development processes
-- Share knowledge and insights gained from studying the Software
-
-Examples of PERMITTED commercial use:
-✅ Using Jarvis Framework to develop a commercial e-commerce platform
-✅ Using Jarvis Framework to build a SaaS product
-✅ Using Jarvis Framework as internal development tool in your company
-✅ Using Jarvis Framework to create commercial mobile/web applications
-
-3. RESTRICTIONS
-
-You may NOT, without prior written authorization from the copyright holder:
-- Sell, rent, lease, or license THE FRAMEWORK ITSELF to third parties
-- Create and commercialize DERIVATIVE FRAMEWORKS based on this Software
-- Redistribute the framework as a commercial product
-- Create competing framework products using this codebase
-- Remove or modify copyright notices or this license
-- Claim ownership or authorship of the framework
-
-Examples of PROHIBITED use:
-❌ Creating "Super Jarvis Pro" framework to sell
-❌ Offering "Jarvis-as-a-Service" commercially
-❌ Building and selling a competing multi-agent framework based on this code
-❌ Packaging and selling the framework under a different name
-
-4. COMMERCIAL USE AUTHORIZATION
-
-Authorization is required ONLY for:
-- Commercializing THE FRAMEWORK ITSELF
-- Creating and selling derivative frameworks
-- Offering the framework as a commercial product or service
-
-Authorization is NOT required for:
-- Using the framework as a tool to develop your commercial products
-- Internal use within commercial organizations
-- Building commercial applications with the framework
-
-For framework commercialization inquiries, contact: [Contact via GitHub]
-
-5. DERIVATIVE WORKS
-
-You may create derivative works for:
-- Personal use and learning
-- Commercial applications BUILT WITH the framework (as a tool)
-- Internal development processes
-- Non-commercial open-source projects
-
-You may NOT create derivative works that:
-- Compete with or replace this framework
-- Are distributed as alternative frameworks
-- Are sold as framework products or services
-
-6. ATTRIBUTION
-
-All uses must include:
-- Copyright notice
-- Link to original repository: https://github.com/samuraisatoshi/claude_agent_boilerplate
-- Acknowledgment of original author
-
-7. NO WARRANTY
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-8. TERMINATION
-
-This license automatically terminates if you fail to comply with any term
-herein. Upon termination, you must destroy all copies of the Software in
-your possession.
-
-9. GOVERNING LAW
-
-This license shall be governed by and construed in accordance with the laws
-applicable in the jurisdiction of the copyright holder.
-
-10. CONTACT FOR COMMERCIAL LICENSING
-
-Author: Júlio Fábio de O. Chagas
-Company: MC1 Tecnologia LTDA
-
-For commercial use authorization, please contact directly with details
-of your intended use.
-
----
-
-SUMMARY:
-✅ Personal/Educational Use: FREE
-✅ Using framework to BUILD commercial products: FREE
-✅ Internal use in commercial organizations: FREE
-✅ Open-Source Non-Commercial: FREE (with attribution)
-❌ Commercializing THE FRAMEWORK ITSELF: REQUIRES AUTHORIZATION
-❌ Creating competing frameworks: REQUIRES AUTHORIZATION
-❌ Selling framework derivatives: REQUIRES AUTHORIZATION
-
-EXAMPLES:
-✅ OK: Use Jarvis to develop your SaaS product
-❌ NOT OK: Sell "Jarvis Pro Framework" as a product
-
-Last Updated: November 2025
+This package is licensed exclusively for use by MC1 Global
+and its authorized teams.

package/QUICK-GUIDE.md

@@ -0,0 +1,67 @@
+# JARVIS Plugin — Quick Reference Card
+
+> Full documentation: see [README.md](README.md) or https://www.npmjs.com/package/@mc1global/opencode-jarvis
+
+## Setup in 60 Seconds
+
+```bash
+# 1. Prerequisites (choose your OS)
+#    macOS:    curl -fsSL <repo-url>/scripts/setup/setup-macos.sh | bash
+#    Linux:    curl -fsSL <repo-url>/scripts/setup/setup-linux.sh | bash
+#    WSL:      curl -fsSL <repo-url>/scripts/setup/setup-wsl.sh | bash
+
+# 2. Add plugin to your project (in YOUR PROJECT ROOT directory)
+echo '{ "plugin": ["@mc1global/opencode-jarvis"] }' > opencode.json
+
+# 3. Launch OpenCode — JARVIS auto-bootstraps everything
+cd /path/to/your/project
+opencode
+```
+
+## Where Does `opencode.json` Go?
+
+```
+your-project/opencode.json              <-- Per-project (recommended)
+~/.config/opencode/opencode.json         <-- Global (all projects)
+```
+
+Project-level overrides global. Both are merged for non-conflicting keys.
+
+## First Session Checklist
+
+- Run diagnostics: `/healthcheck`
+- Index codebase: `rag-index` tool
+- Index docs: `rag-oracle-index` tool with `directory="obsidian-vault"`
+- View board: `kanban-board-view` tool
+
+## Key Commands
+
+- `/healthcheck` — Diagnose environment + show fix commands
+- `/sync-azure` — Sync kanban with Azure DevOps
+- `/start-card CD-XXX` — Start working on a card (full lifecycle)
+- `/config` — Agent-guided configuration wizard
+
+## Key Skills (load via `skill()` tool)
+
+- `jarvis-kanban` — Card lifecycle, grooming, sprints
+- `jarvis-azure-sync` — Azure DevOps sync workflow
+- `jarvis-onboarding` — Setup, tools, orientation
+
+## Files Created by JARVIS
+
+```
+config/jarvis.yaml          In git — Configuration
+AGENTS.md                   In git — Agent instructions
+obsidian-vault/             In git — Documentation
+.jarvis/jarvis.db           Local  — SQLite database (gitignored)
+.jarvis/rag/                Local  — RAG embeddings (gitignored)
+~/.jarvis/registry.db       Global — Workspace registry
+```
+
+## Windows (WSL) Notes
+
+- JARVIS must run inside WSL, not native Windows
+- Use `setup-wsl.sh` for automated installation
+- Best performance: keep project files in WSL filesystem (`~/code/`)
+- Access Windows files via `/mnt/c/Users/YourName/...`
+- See: https://opencode.ai/docs/windows-wsl