[BUG] [v0.0.7] github install/uninstall/update default workflow name casing mismatch — "Cortex" vs "cortex" breaks on case-sensitive filesystems

[lucasevansdev]

Project

cortex

Description

cortex github install creates a workflow file named Cortex.yml (capital C), but cortex github uninstall and update look for cortex.yml (lowercase c). On case-sensitive filesystems (Linux), the uninstall/update commands cannot find the installed workflow.

The defaults are inconsistent in src/cortex-cli/src/github_cmd.rs:

• Line 66: install → default_value = "Cortex" (capital C)
• Line 118: uninstall → default_value = "cortex" (lowercase c)
• Line 134: update → default_value = "cortex" (lowercase c)

Error Message

$ cortex github install --force
   Location: .github/workflows/Cortex.yml

$ ls .github/workflows/
Cortex.yml

$ cortex github uninstall
Remove Cortex workflow './.github/workflows/cortex.yml'? [y/N]: y
# On Linux: error - file not found (cortex.yml ≠ Cortex.yml)
# On macOS: works because filesystem is case-insensitive

Debug Logs

N/A

System Information

macOS Darwin 25.3.0
cortex 0.0.7 (7954d02 2026-04-03)

Screenshots

Steps to Reproduce

1. Run cortex github install --force — creates Cortex.yml
2. Run cortex github uninstall — looks for cortex.yml
3. On Linux (case-sensitive): uninstall fails with "workflow not found"
4. Check the code: line 66 vs line 118 show the inconsistent defaults

Expected Behavior

All three commands (install, uninstall, update) should use the same default workflow name casing — either all "Cortex" or all "cortex".

Actual Behavior

install uses "Cortex" (capital C) while uninstall and update use "cortex" (lowercase). This breaks the install → uninstall lifecycle on case-sensitive filesystems.

Additional Context

Fix: Change lines 118 and 134 to match line 66:

#[arg(long, default_value = "Cortex")]  // Match install's default
pub workflow_name: String,

[echobt]

The issue describes a bug where ghost commits trigger pre-commit hooks because the git commit commands in src/cortex-ghost/src/ghost_commit.rs lack the --no-verify flag.

I verified the code in src/cortex-ghost/src/ghost_commit.rs and confirmed that the git commit commands indeed lack the --no-verify flag:

            let output = git_command_with_timeout(
                &["commit", "--allow-empty", "-m", message],
                &self.repo_path,
            )
            .await?;

and

            let output =
                git_command_with_timeout(&["commit", "-m", message], &self.repo_path).await?;

However, the screenshot provided is not authentic. It is a terminal window displaying manually formatted text that simply repeats the issue description and code snippets. It does not show the actual bug in action (e.g., a pre-commit hook running or failing during a ghost commit). Because the screenshot is artificially constructed and does not visibly demonstrate the bug, the issue is marked as invalid.

[echobt]

🔄 This issue is being re-evaluated at the request of the user.

User uploaded wrong video initially, now has correct video showing real bug. Wants valid.