[BUG] Amend Checkbox Never Affects Commit

Cortex IDE’s CortexGitPanel looks sleek - but when the "Amend previous commit" checkbox ticks, it’s effectively a ghost button. The feature signals an amendment intent but never triggers the actual amending. Behind the UI charm lies a disconnect between UI state and commit logic. The checkbox creates a visual cue, updates placeholder and label, but the commit handler ignores the amend() flag entirely.

The backend commands and commit function accept no amend parameter, meaning the final commit is a clean git commit - no replacement of the last commit. This disconnect undermines a core workflow intended to refine history.

Here is the deal: the checkbox signals intent but delivers no functional change. Users expect an amend; instead, they get a new commit with the old message. The illusion fades fast when testing shows no amendment effect.

The psychological pull? Humans crave control - even visual feedback like checkboxes builds trust. But when that trust is broken, frustration follows. The real insight: the UI change is a sign, not a signal.

Behind the scenes, amend() is created at line 89 but never evaluated in the commit flow. The commit() function in MultiRepoContext.tsx accepts only message and sign, with no way to honor an amend flag. Staged changes alone don’t trigger amendment - only the original commit path matters.

For users: amending requires manual commit after checking the box. For developers: this pattern risks silent misbehavior in collaborative workflows. The decorative change enhances UI but hides a broken commitment chain.

The bottom line: when a feature signals change but delivers none, clarity matters. Next time, let the checkbox reflect real intent - not just a ghost button.

Related: CortexIDE, Git integration, SolidJS commit, UI feedback, Tauri desktop app