@eldrforge/kodrdriv 1.2.28 → 1.2.123

package/VERSION-AUDIT-FIX.md

@@ -1,333 +0,0 @@
-# Version Consistency Audit Fix
-
-## Summary
-
-Enhanced the `kodrdriv tree publish --audit-branches` command to detect version consistency issues, preventing publish failures caused by packages having release versions on development branches or vice versa.
-
-## Problems Fixed
-
-### 1. ✅ Audit Misses Version Issues
-
-**Before**: `--audit-branches` only checked:
-- Branch consistency
-- Uncommitted changes
-- Sync status
-- Merge conflicts
-
-**Did NOT check**:
-- Version patterns (dev vs release)
-- Whether versions match branch expectations
-- Monorepo version alignment
-
-**After**: Now checks all of the above PLUS:
-- ✅ Version patterns for each package
-- ✅ Validates versions match branch type
-- ✅ Shows clear fix instructions
-- ✅ Blocks publish if issues found
-
-### 2. ✅ Silent Version Inconsistencies
-
-**Before**: Developer could have:
-```
-✅ @fjell/common-config: 1.1.37-dev.0 (correct)
-❌ @fjell/logging: 4.4.64 (missing -dev.0 suffix)
-✅ @fjell/core: 4.4.72-dev.0 (correct)
-```
-
-And `--audit-branches` would say "All OK!" leading to:
-- Skipped packages during publish
-- Unclear failures
-- Wasted debugging time
-
-**After**: Audit now reports:
-```
-⚠️  Version Issues (1 package):
-   @fjell/logging
-   - Branch: working
-   - Version: 4.4.64
-   - Issue: Release version on development branch
-   - Fix: Run kodrdriv development to update to development version
-```
-
-## Implementation Details
-
-### New Utility Functions (`src/util/general.ts`)
-
-```typescript
-// Check if version has prerelease tag
-export const isDevelopmentVersion = (version: string): boolean
-
-// Check if version is release version (X.Y.Z)
-export const isReleaseVersion = (version: string): boolean
-
-// Get expected version pattern for branch
-export const getExpectedVersionPattern = (branchName: string): {
-    pattern: RegExp;
-    description: string;
-    isDevelopment: boolean;
-}
-
-// Validate version against branch expectations
-export const validateVersionForBranch = (version: string, branchName: string): {
-    valid: boolean;
-    issue?: string;
-    fix?: string;
-}
-```
-
-### Enhanced Branch Audit (`src/utils/branchState.ts`)
-
-Added new interfaces:
-```typescript
-interface VersionStatus {
-    version: string;
-    isValid: boolean;
-    issue?: string;
-    fix?: string;
-}
-
-interface PackageBranchAudit {
-    packageName: string;
-    path: string;
-    status: BranchStatus;
-    versionStatus?: VersionStatus;  // NEW
-    issues: string[];
-    fixes: string[];
-}
-
-interface BranchAuditResult {
-    totalPackages: number;
-    goodPackages: number;
-    issuesFound: number;
-    versionIssues: number;  // NEW
-    audits: PackageBranchAudit[];
-}
-```
-
-### Version Pattern Rules
-
-**Development Branches** (`working`, `development`, `dev`, `feature/*`, `wip/*`):
-- **Expected**: `X.Y.Z-<tag>` (e.g., `1.2.3-dev.0`)
-- **Invalid**: `X.Y.Z` (release versions)
-- **Fix**: `kodrdriv development`
-
-**Release Branches** (`main`, `master`, `production`, `release/*`):
-- **Expected**: `X.Y.Z` (e.g., `1.2.3`)
-- **Invalid**: `X.Y.Z-<tag>` (development versions)
-- **Fix**: Do not commit dev versions to release branches
-
-**Other Branches**:
-- **Expected**: Either format acceptable
-- **No strict validation**
-
-### Enhanced Audit Output
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  Branch State Audit (16 packages)                            ║
-║  All packages on: working                                    ║
-╠══════════════════════════════════════════════════════════════╣
-
-✅ Good State (15 packages):
-   @fjell/common-config (v1.1.37-dev.0)
-   @fjell/core (v4.4.72-dev.0)
-   @fjell/http-api (v4.4.62-dev.0)
-   ...
-
-⚠️  Version Issues (1 package):
-   @fjell/logging
-   - Branch: working
-   - Version: 4.4.64
-   - Issue: Release version on development branch
-   - Fix: Run kodrdriv development to update to development version
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📝 RECOMMENDED WORKFLOW:
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-1️⃣  FIX VERSION ISSUES (recommended before publish):
-   • @fjell/logging: cd logging && kodrdriv development
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🔄 After fixing issues, re-run audit to verify:
-   kodrdriv tree publish --audit-branches
-
-✅ Once all clear, proceed with publish:
-   kodrdriv tree publish --parallel --model "gpt-5-mini"
-
-╚══════════════════════════════════════════════════════════════╝
-
-⚠️  Found issues in 1 package(s). Review the fixes above.
-   1 package(s) have version consistency issues
-   Run 'kodrdriv development' in each package to fix version issues
-```
-
-### Integration with Tree Commands
-
-Enhanced tree.ts audit handling:
-```typescript
-const auditResult = await auditBranchState(packages, undefined, {
-    targetBranch,
-    checkPR: true,
-    checkConflicts: true,
-    checkVersions: true,  // NEW - enabled by default
-});
-
-if (auditResult.issuesFound > 0 || auditResult.versionIssues > 0) {
-    const totalIssues = auditResult.issuesFound + (auditResult.versionIssues || 0);
-    logger.warn(`Found issues in ${totalIssues} package(s)`);
-
-    if (auditResult.versionIssues > 0) {
-        logger.warn(`${auditResult.versionIssues} package(s) have version consistency issues`);
-    }
-}
-```
-
-## Real-World Usage
-
-### Before This Fix
-
-```bash
-$ kodrdriv tree publish --audit-branches
-✅ All 16 packages are in good state!
-
-$ kodrdriv tree publish --parallel
-# Publishes, but skips @fjell/logging
-# Developer confused: "Why was logging skipped? It had changes!"
-# 30 minutes debugging to find: version was 4.4.64 instead of 4.4.64-dev.0
-```
-
-### After This Fix
-
-```bash
-$ kodrdriv tree publish --audit-branches
-
-⚠️  Version Issues (1 package):
-   @fjell/logging
-   - Branch: working
-   - Version: 4.4.64
-   - Issue: Release version on development branch
-   - Fix: Run kodrdriv development to update to development version
-
-1️⃣  FIX VERSION ISSUES (recommended before publish):
-   • @fjell/logging: cd logging && kodrdriv development
-
-⚠️  Found issues in 1 package(s). Review the fixes above.
-
-$ cd logging && kodrdriv development
-✓ Updated to 4.4.65-dev.0
-
-$ kodrdriv tree publish --audit-branches
-✅ All 16 packages are in good state!
-
-$ kodrdriv tree publish --parallel
-# All packages publish successfully
-```
-
-## Files Modified
-
-```
-src/util/general.ts               - Added version validation utilities
-src/utils/branchState.ts           - Enhanced audit with version checking
-src/commands/tree.ts               - Enabled version checking in audit
-tests/utils/branchState.test.ts   - Updated tests for new fields
-VERSION-AUDIT-FIX.md              - This documentation
-```
-
-## Test Updates
-
-Updated existing tests to include new `versionIssues` field:
-```typescript
-const result: BranchAuditResult = {
-    totalPackages: 2,
-    goodPackages: 2,
-    issuesFound: 0,
-    versionIssues: 0,  // NEW
-    audits: [...]
-};
-```
-
-## Backward Compatibility
-
-✅ **Fully backward compatible**
-- Version checking enabled by default (can be disabled with `checkVersions: false`)
-- Existing audit functionality unchanged
-- New fields added to interfaces (optional in most contexts)
-
-## Impact
-
-### Before
-- ❌ Version issues discovered during publish (too late)
-- ❌ Unclear why packages skipped
-- ❌ 30+ minutes debugging per issue
-- ❌ No pre-flight validation
-
-### After
-- ✅ Version issues caught in audit (before publish)
-- ✅ Clear fix instructions shown
-- ✅ 2 minutes to identify and fix
-- ✅ Confidence before publishing
-
-## Remaining Work (Future Enhancements)
-
-### 1. Tree Development Command (Not Implemented)
-
-User requested but not yet implemented:
-```bash
-kodrdriv tree development
-```
-
-Would update ALL packages in monorepo to development versions in one command.
-
-**Current Workaround**: Run `kodrdriv development` in each package individually, or use the audit to identify which packages need updating.
-
-### 2. Smart Monorepo Detection (Not Implemented)
-
-User requested: When running `kodrdriv development` in one package, detect monorepo and ask:
-```
-📦 Detected monorepo: 16 packages found
-Update only this package, or all packages in monorepo? [single/all]
-```
-
-**Current Behavior**: Only updates current package.
-
-### 3. Automated Version Alignment (Not Implemented)
-
-User requested: Automatically update all packages when one is updated.
-
-**Current Behavior**: Manual per-package updates required.
-
-## Priority Assessment
-
-**COMPLETED (This PR)**:
-- ✅ Version consistency checking in audit
-- ✅ Clear error messages and fix instructions
-- ✅ Integration with existing workflows
-
-**FUTURE (Lower Priority)**:
-- Tree development command (nice-to-have)
-- Automatic monorepo-wide updates (quality-of-life)
-- Smart monorepo detection (convenience)
-
-The core issue (audit missing version problems) is **FIXED**. The remaining items are enhancements that improve convenience but don't block workflows.
-
-## Version
-
-Implemented in: **kodrdriv 1.2.29-dev.0**
-
----
-
-## Example Test Case
-
-Given monorepo with 3 packages:
-- package-a: 1.0.0-dev.0 on `working` branch ✓
-- package-b: 2.0.0 on `working` branch ✗ (missing -dev.0)
-- package-c: 3.0.0-dev.0 on `working` branch ✓
-
-Running `kodrdriv tree publish --audit-branches`:
-- ✅ Reports version issue in package-b
-- ✅ Provides fix command
-- ✅ Returns non-zero exit code
-- ✅ Prevents publish from proceeding until fixed
-

package/WORKFLOW-PRECHECK-IMPLEMENTATION.md

@@ -1,239 +0,0 @@
-# Workflow Precheck Implementation
-
-## Problem Statement
-
-The `kodrdriv publish` command was freezing when running in the getfjell/http-api repository during the `publish-tree` operation.
-
-### Root Cause
-
-The workflow file at `~/gitw/getfjell/http-api/.github/workflows/test.yml` is configured with:
-
-```yaml
-on:
-  push:
-    branches:
-      - main
-      - working
-      - 'feature/**'
-```
-
-**The problem:** This workflow triggers on `push` events but **NOT on `pull_request` events**.
-
-When `kodrdriv publish`:
-1. Creates a new branch and pushes commits ✅
-2. Creates a pull request ✅
-3. Waits for PR checks to complete using `waitForPullRequestChecks()` ❌
-
-The `waitForPullRequestChecks()` function queries the GitHub API for check runs associated with the PR. Because the workflow only triggers on `push` (not `pull_request`), GitHub doesn't associate those workflow runs with the PR, so the API returns no checks.
-
-The function was designed to detect this after 1 minute (6 consecutive checks with no results), but in your case it was likely stuck in a detection loop or the command was running with `skipUserConfirmation: true` which caused it to wait for the full 1-hour timeout.
-
-## Solution
-
-I've implemented **two complementary improvements** to prevent this issue:
-
-### 1. Workflow Validation Precheck (runs before PR creation)
-### 2. Smart Wait Skipping (skips waiting if no PR workflows detected)
-
-### Changes Made
-
-#### 1. Workflow Validation Precheck
-
-**New function** `checkWorkflowConfiguration()` in `@eldrforge/github-tools` that:
-- Lists all workflows in the repository
-- Analyzes each workflow file's YAML content
-- Determines if workflows will be triggered by PRs to the target branch
-- Returns detailed information about workflow configuration
-
-**Location:** `~/gitw/calenvarek/github-tools/src/github.ts`
-
-**Example output:**
-```typescript
-{
-  hasWorkflows: true,
-  workflowCount: 4,
-  hasPullRequestTriggers: false,  // ⚠️  This is the warning
-  triggeredWorkflowNames: [],
-  warning: "4 workflow(s) are configured, but none appear to trigger on pull requests to main"
-}
-```
-
-#### 2. Smart Wait Skipping
-
-**After** the PR is created, the publish command now checks the workflow configuration again and **skips waiting entirely** if no workflows will trigger on the PR.
-
-**Location:** `~/gitw/calenvarek/kodrdriv/src/commands/publish.ts` (lines 833-850)
-
-**Output when skipping:**
-```
-Waiting for PR #75 checks to complete...
-⏭️  Skipping check wait - no workflows configured to trigger on this PR
-```
-
-This prevents the command from freezing when workflows exist but don't trigger on PRs.
-
-#### 3. Improved Detection in `waitForPullRequestChecks`
-
-Made the wait function smarter and faster:
-- **Reduced wait time**: Now checks after 30 seconds instead of 1 minute
-- **Better detection**: Distinguishes between "no workflow runs" vs "workflow runs exist on branch but aren't PR checks"
-- **Explicit handling**: When workflows trigger on `push` but not `pull_request`, it detects this and proceeds without waiting
-
-**Location:** `~/gitw/calenvarek/github-tools/src/github.ts`
-
-**Key improvements:**
-```typescript
-// Changed from 6 checks (1 minute) to 3 checks (30 seconds)
-const maxConsecutiveNoChecks = 3;
-
-// New logic to detect workflows that trigger on push but not pull_request
-logger.info(`Found workflow runs on the branch, but none appear as PR checks.`);
-logger.info(`This usually means workflows trigger on 'push' but not 'pull_request'.`);
-// ... proceeds without waiting in non-interactive mode
-```
-
-#### 4. Precheck Warning
-
-Modified the `runPrechecks()` function to call `checkWorkflowConfiguration()` and warn users before creating the PR.
-
-**Location:** `~/gitw/calenvarek/kodrdriv/src/commands/publish.ts` (lines 244-267)
-
-**Output when workflows are missing:**
-```
-Checking GitHub Actions workflow configuration...
-⚠️  Found 4 workflow(s), but none are triggered by PRs to main.
-   The publish process will create a PR but will not wait for any checks to complete.
-   Consider updating workflow triggers to include: on.pull_request.branches: [main]
-```
-
-#### 5. Tests
-
-Created comprehensive test suite with 8 test cases covering:
-- No workflows configured
-- Workflows with `pull_request` triggers
-- Workflows without `pull_request` triggers
-- Branch-specific triggers
-- Wildcard patterns
-- Multiple workflows with mixed configurations
-- API error handling
-
-**Location:** `~/gitw/calenvarek/github-tools/tests/checkWorkflowConfiguration.test.ts`
-
-**Result:** All 8 tests passing ✅
-
-## How to Fix the http-api Workflow
-
-Update `~/gitw/getfjell/http-api/.github/workflows/test.yml`:
-
-```yaml
-name: Run Tests
-
-on:
-  push:
-    branches:
-      - main
-      - working
-      - 'feature/**'
-  pull_request:  # ← ADD THIS
-    branches:
-      - main
-
-permissions:
-  contents: read
-  statuses: write
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 22
-
-      - run: npm ci
-      - run: npm run lint
-      - run: npm run build
-      - run: npm test
-
-      - uses: codecov/codecov-action@v5
-        with:
-          slug: getfjell/http-api
-          token: ${{ secrets.CODECOV_TOKEN }}
-```
-
-**What this does:**
-- Triggers the workflow when PRs are opened/updated targeting `main` branch
-- GitHub will now associate the check runs with the PR
-- `kodrdriv publish` will detect the checks and wait for them to complete
-- The PR merge will only proceed after checks pass ✅
-
-## Testing the Fix
-
-After updating the workflow file and rebuilding:
-
-1. **Test the precheck:**
-   ```bash
-   cd ~/gitw/getfjell/http-api
-   kodrdriv publish --dry-run
-   ```
-
-   Before fix: Would warn about missing PR triggers
-   After fix: Should show workflow will run on PRs ✅
-
-2. **Test actual publish:**
-   ```bash
-   kodrdriv publish
-   ```
-
-   Should now:
-   - Create PR
-   - Detect workflow runs
-   - Wait for checks to complete
-   - Merge when checks pass
-
-## Related Files Modified
-
-### github-tools package:
-- `~/gitw/calenvarek/github-tools/src/github.ts` - Added `checkWorkflowConfiguration()` and `isTriggeredByPullRequest()`
-- `~/gitw/calenvarek/github-tools/src/index.ts` - Exported new function
-- `~/gitw/calenvarek/github-tools/tests/checkWorkflowConfiguration.test.ts` - New test file
-
-### kodrdriv package:
-- `~/gitw/calenvarek/kodrdriv/src/commands/publish.ts` - Added workflow validation to prechecks
-
-Both packages have been built and all tests pass.
-
-## Future Improvements
-
-Consider adding:
-1. Configuration option to skip workflow validation if desired
-2. Ability to specify minimum required workflows
-3. Integration with workflow file templates for new projects
-
-## Summary
-
-**What was frozen:** The `kodrdriv publish` command waiting for PR checks that never appeared
-
-**Why it happened:** The workflow triggers on `push` but not `pull_request`, so GitHub doesn't associate runs with the PR
-
-**How we fixed it:**
-1. ✅ **Precheck Warning**: Validates workflow configuration before creating the PR and warns about missing triggers
-2. ✅ **Smart Wait Skipping**: Automatically skips waiting if no workflows will trigger on the PR (no more freezing!)
-3. ✅ **Improved Detection**: Detects within 30 seconds when workflows exist on branch but aren't PR checks
-
-**How to fix your workflow:** Add `pull_request` trigger to your workflow files (see above)
-
-**Current state:**
-- ✅ Precheck implemented and warns users
-- ✅ Smart skip logic prevents freezing
-- ✅ Faster detection (30s instead of 1 minute)
-- ✅ Better error messages
-- ✅ All tests passing (8/8)
-- ✅ Both packages built
-- ⚠️  http-api workflow needs updating for best experience (see above)
-
-**Behavior now:**
-- **Before fix**: Command would freeze for up to 1 hour waiting for checks
-- **After fix**: Command detects the issue within 30 seconds and proceeds automatically in non-interactive mode, or prompts user in interactive mode
-

package/WORKFLOW-SKIP-SUMMARY.md

@@ -1,121 +0,0 @@
-# Smart Workflow Wait Skipping - Implementation Summary
-
-## The Problem You Asked About
-
-> "If there is no action fired from a pull request workflow, can we just not wait for it to complete?"
-
-**Answer: YES! ✅ Now implemented.**
-
-## What I've Added
-
-### 1. Pre-check Before Creating PR
-The publish command now checks workflow configuration **before** creating the PR and warns you:
-
-```
-Checking GitHub Actions workflow configuration...
-⚠️  Found 4 workflow(s), but none are triggered by PRs to main.
-   The publish process will create a PR but will not wait for any checks to complete.
-```
-
-### 2. **Smart Skip After Creating PR** ⭐ (This is what you asked for!)
-After the PR is created, the command checks workflow configuration again and **skips waiting entirely**:
-
-```
-Waiting for PR #75 checks to complete...
-⏭️  Skipping check wait - no workflows configured to trigger on this PR
-```
-
-**No more freezing!** The command proceeds immediately instead of waiting.
-
-### 3. Faster Detection When Checks Won't Appear
-If we can't determine workflow configuration in advance, the wait logic now:
-- Detects the issue in **30 seconds** instead of 1 minute
-- Distinguishes between "no workflows" vs "workflows exist but don't trigger on PRs"
-- Automatically proceeds in non-interactive mode (like in `publish-tree`)
-
-## How It Works
-
-```typescript
-// In publish.ts - after PR is created
-const workflowConfig = await GitHub.checkWorkflowConfiguration(targetBranch);
-if (!workflowConfig.hasWorkflows || !workflowConfig.hasPullRequestTriggers) {
-    logger.info('⏭️  Skipping check wait - no workflows configured to trigger on this PR');
-    shouldSkipWait = true;
-}
-```
-
-The command:
-1. Checks if workflows are configured
-2. Checks if any workflows will trigger on this PR
-3. If NO → skips waiting entirely
-4. If YES → waits for checks as normal
-
-## Timeline Comparison
-
-### Before These Changes:
-```
-Create PR ✓
-Wait for checks...
-  [10s] No checks found
-  [20s] No checks found
-  [30s] No checks found
-  [40s] No checks found
-  [50s] No checks found
-  [60s] No checks found - checking workflows...
-  [70s] Workflows exist, checking if triggered for PR...
-  [80s] Found runs on branch...
-  ... continues waiting or hangs ...
-```
-
-### After These Changes:
-```
-Precheck: Workflows exist but don't trigger on PRs ⚠️
-Create PR ✓
-Check workflow config again...
-⏭️  Skipping check wait - no workflows configured to trigger on this PR
-Merge PR ✓
-```
-
-**Time saved per publish:** Up to 60 minutes (if you were hitting the timeout!)
-
-## What Gets Detected
-
-The smart skip detects:
-- ❌ No workflows configured at all
-- ❌ Workflows configured but none trigger on `pull_request` events
-- ❌ Workflows trigger on PRs but not to your target branch (e.g., only to `develop`)
-- ✅ Workflows will run on this PR → waits normally
-
-## For Your http-api Repository
-
-The command will now:
-1. **Warn during precheck**: "4 workflow(s) configured, but none trigger on PRs to main"
-2. **Skip waiting**: Proceeds immediately after creating the PR
-3. **No freezing**: Command completes successfully
-
-To get actual CI checks on your PRs (recommended), add to `test.yml`:
-```yaml
-on:
-  push:
-    branches: [main, working, 'feature/**']
-  pull_request:  # ← Add this
-    branches: [main]
-```
-
-## Testing
-
-Run your `publish-tree` command again - it should now:
-- Complete much faster (no 1-hour wait!)
-- Show skip messages for repos without PR workflows
-- Wait normally for repos with PR workflows
-- Never freeze
-
-## Files Modified
-
-- `github-tools/src/github.ts` - Added `checkWorkflowConfiguration()`, improved `waitForPullRequestChecks()`
-- `github-tools/src/index.ts` - Exported new function
-- `kodrdriv/src/commands/publish.ts` - Added precheck + smart skip logic
-- `github-tools/tests/checkWorkflowConfiguration.test.ts` - 8 comprehensive tests (all passing)
-
-Both packages rebuilt and ready to use! ✅
-