feat(dev-fkeys): add project-aware F4 compile/run dispatcher

I added a new module `modules/dev-fkeys.el` that owns the dev F-key block. F4 prompts via `completing-read` with a candidate set filtered by project type (compiled / interpreted / unknown). C-F4 is the compile-only fast path. M-F4 is clean + rebuild. It runs a heuristic clean command derived from the project markers (go.mod, Cargo.toml, Eask, Makefile, CMakeLists.txt) and chains `projectile-compile-project` on success. S-F4 stays on `recompile` and now lives globally instead of duplicated across prog-general.el and prog-c.el. F6 is bound globally to `projectile-test-project` as a Phase 1 stopgap. Phase 2 replaces it with the polyglot test runner spec'd in todo.org.

Project-type detection runs against the projectile root and falls back to `unknown` when no marker matches. Interpreted markers are checked first so a Python or Node project with a Makefile for tasks classifies as interpreted instead of compiled. Compile + Run sequencing uses a one-shot `compilation-finish-functions` hook that self-removes on first invocation and only fires the follow-up when the status string starts with `finished`.

Cleanup in the same commit:
- Dropped F4/F5/F6 from `prog-general.el`'s prog-mode-hook. They are now global.
- Dropped F6→format bindings from prog-c.el / prog-python.el / prog-shell.el. C-; f was already bound in each, so this is pure removal.
- Dropped the duplicate S-F4 from prog-c.el. The global binding covers it.
- Updated the keybinding header in prog-general.el and the workflow comments in prog-c.el / prog-shell.el.
- Wired `(require 'dev-fkeys)` in init.el alongside coverage-core.

TDD: 73 tests across 11 files, one per helper. Production code is split into small testable internals (`cj/--detect-project-type`, `cj/--f4-candidates`, `cj/--f4-derive-clean-cmd`, `cj/--f4-make-once-hook`, `cj/--f4-dispatch`, `cj/--f4-compile-and-run-impl`, `cj/--f4-clean-rebuild-impl`, `cj/--f4-project-root`) plus three thin interactive wrappers. Smoke tests confirm bindings register on load.

Known limitation: if another `compilation-finish-functions` hook fires between my add-hook and the compile finishing, the chain can fire on the wrong compile. The hook self-removes on first invocation regardless of which compile it sees. Documented in the impl docstring. Acceptable for v1.

Phase 2 will replace F6 with the polyglot test runner (tree-sitter queries for Python/Go/TS, sexp scan for Elisp, buffer-local last-test memory).

1 files changed, 66 insertions, 0 deletions

diff --git a/tests/test-dev-fkeys--f4-candidates.el b/tests/test-dev-fkeys--f4-candidates.el
new file mode 100644
index 00000000..a2d1afa4
--- /dev/null
+++ b/tests/test-dev-fkeys--f4-candidates.el
@@ -0,0 +1,66 @@
+;;; test-dev-fkeys--f4-candidates.el --- Tests for cj/--f4-candidates -*- lexical-binding: t -*-
+
+;;; Commentary:
+;; Tests for the candidate-menu builder. Returns an alist of
+;; (LABEL . ACTION) for the F4 completing-read prompt. The first entry
+;; is the default (selected on RET).
+
+;;; Code:
+
+(require 'ert)
+(add-to-list 'load-path (expand-file-name "modules" user-emacs-directory))
+(require 'dev-fkeys)
+
+;;; Normal Cases
+
+(ert-deftest test-dev-fkeys-f4-candidates-compiled-has-four-entries ()
+  "Normal: compiled project gets all four candidates."
+  (let ((cands (cj/--f4-candidates 'compiled)))
+    (should (= (length cands) 4))))
+
+(ert-deftest test-dev-fkeys-f4-candidates-compiled-default-is-compile-and-run ()
+  "Normal: first candidate for compiled is Compile + Run (the default)."
+  (let ((cands (cj/--f4-candidates 'compiled)))
+    (should (equal (caar cands) "Compile + Run"))
+    (should (eq (cdar cands) 'compile-and-run))))
+
+(ert-deftest test-dev-fkeys-f4-candidates-compiled-includes-all-actions ()
+  "Normal: compiled menu maps each label to its action symbol."
+  (let ((cands (cj/--f4-candidates 'compiled)))
+    (should (eq (cdr (assoc "Compile + Run" cands))   'compile-and-run))
+    (should (eq (cdr (assoc "Compile" cands))         'compile-only))
+    (should (eq (cdr (assoc "Run" cands))             'run-only))
+    (should (eq (cdr (assoc "Clean + Rebuild" cands)) 'clean-rebuild))))
+
+(ert-deftest test-dev-fkeys-f4-candidates-interpreted-is-run-only ()
+  "Normal: interpreted project gets a single Run candidate."
+  (let ((cands (cj/--f4-candidates 'interpreted)))
+    (should (= (length cands) 1))
+    (should (equal (caar cands) "Run"))
+    (should (eq (cdar cands) 'run-only))))
+
+(ert-deftest test-dev-fkeys-f4-candidates-unknown-is-compile-plain ()
+  "Normal: unknown project gets a single Compile candidate that calls plain compile."
+  (let ((cands (cj/--f4-candidates 'unknown)))
+    (should (= (length cands) 1))
+    (should (equal (caar cands) "Compile"))
+    (should (eq (cdar cands) 'compile-plain))))
+
+;;; Boundary Cases
+
+(ert-deftest test-dev-fkeys-f4-candidates-bogus-symbol-falls-back-to-unknown ()
+  "Boundary: an unrecognized project-type symbol falls through to the unknown branch."
+  (let ((cands (cj/--f4-candidates 'fictional-type)))
+    (should (= (length cands) 1))
+    (should (eq (cdar cands) 'compile-plain))))
+
+;;; Error Cases
+
+(ert-deftest test-dev-fkeys-f4-candidates-nil-falls-back-to-unknown ()
+  "Error: nil project-type falls through to the unknown branch."
+  (let ((cands (cj/--f4-candidates nil)))
+    (should (= (length cands) 1))
+    (should (eq (cdar cands) 'compile-plain))))
+
+(provide 'test-dev-fkeys--f4-candidates)
+;;; test-dev-fkeys--f4-candidates.el ends here