v1.1.0 - DevIntern Changelog

Init Command: New devintern init command for easy project setup
- Creates .devintern-code/ folder with project-specific configuration
- Generates .env file for JIRA credentials
- Creates .env.sample template with all configuration options
- Creates settings.json for per-project settings
- Automatic .gitignore Protection: Automatically adds .devintern-code/.env and .devintern-code/.env.local to .gitignore to prevent credential leaks
Per-Project Settings: New settings.json configuration file for project-specific behavior
- Configure different PR status transitions for different JIRA projects
- Example: {"projects": {"PROJ": {"prStatus": "In Review"}, "ABC": {"prStatus": "Code Review"}}}
- Automatically extracts project key from task key (e.g., “PROJ-123” → “PROJ”)
- Per-project configuration takes precedence over global environment variables
Enhanced Environment Configuration: Improved configuration loading with priority order
1. Custom path (via --env-file)
2. Project-specific (.devintern-code/.env) - NEW
3. Current working directory (.env)
4. Home directory (~/.env)
5. Tool installation directory
Comprehensive Test Suite: Added 29 unit tests for reliability
- Settings management tests (8 tests)
- CLI argument handling tests (21 tests)
- All tests organized in tests/ directory
- Full TypeScript type coverage including tests

JIRA PR Status Configuration: Moved from environment variable to settings.json
- JIRA_PR_STATUS environment variable deprecated in favor of per-project configuration
- Each JIRA project can now have its own status workflow
- Removed JIRA_PR_STATUS from .env.sample template
CLI Architecture: Improved command-line argument handling
- Fixed issue where init command conflicted with task key parsing
- Task keys like “DISCO-123” now work correctly alongside subcommands
- Early detection of init command to avoid Commander.js conflicts