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, 75 insertions, 0 deletions

diff --git a/tests/test-dev-fkeys--f4-compile-and-run-impl.el b/tests/test-dev-fkeys--f4-compile-and-run-impl.el
new file mode 100644
index 00000000..d59a6cd6
--- /dev/null
+++ b/tests/test-dev-fkeys--f4-compile-and-run-impl.el
@@ -0,0 +1,75 @@
+;;; test-dev-fkeys--f4-compile-and-run-impl.el --- Tests for cj/--f4-compile-and-run-impl -*- lexical-binding: t -*-
+
+;;; Commentary:
+;; Tests for the "Compile + Run" action handler. After kicking off the
+;; compile, attaches a one-shot `compilation-finish-functions' hook that
+;; runs the project on success.
+
+;;; Code:
+
+(require 'ert)
+(require 'cl-lib)
+(add-to-list 'load-path (expand-file-name "modules" user-emacs-directory))
+(require 'dev-fkeys)
+
+;;; Normal Cases
+
+(ert-deftest test-dev-fkeys-compile-and-run-impl-invokes-projectile-compile ()
+  "Normal: handler calls `projectile-compile-project'.
+
+Components integrated:
+- `cj/--f4-compile-and-run-impl' (unit under test)
+- `projectile-compile-project' (MOCKED via cl-letf)
+- `compilation-finish-functions' (real, scoped via let)"
+  (let ((compile-calls 0)
+        (compilation-finish-functions nil))
+    (cl-letf (((symbol-function 'projectile-compile-project)
+               (lambda (_arg) (cl-incf compile-calls))))
+      (cj/--f4-compile-and-run-impl)
+      (should (= compile-calls 1)))))
+
+(ert-deftest test-dev-fkeys-compile-and-run-impl-installs-finish-hook ()
+  "Normal: handler installs exactly one hook in `compilation-finish-functions'."
+  (let ((compilation-finish-functions nil))
+    (cl-letf (((symbol-function 'projectile-compile-project)
+               (lambda (_arg) nil)))
+      (cj/--f4-compile-and-run-impl)
+      (should (= (length compilation-finish-functions) 1)))))
+
+(ert-deftest test-dev-fkeys-compile-and-run-impl-hook-runs-projectile-run-on-success ()
+  "Normal: when the compile finishes successfully, the installed hook calls
+`projectile-run-project'.
+
+Components integrated:
+- `cj/--f4-compile-and-run-impl' (unit under test)
+- `projectile-compile-project' (MOCKED — no-op)
+- `projectile-run-project' (MOCKED — counts calls)
+- `compilation-finish-functions' (real)
+- `run-hook-with-args' (real — simulates compile.el firing the hook)"
+  (let ((run-calls 0)
+        (compilation-finish-functions nil))
+    (cl-letf (((symbol-function 'projectile-compile-project)
+               (lambda (_arg) nil))
+              ((symbol-function 'projectile-run-project)
+               (lambda (_arg) (cl-incf run-calls))))
+      (cj/--f4-compile-and-run-impl)
+      (run-hook-with-args 'compilation-finish-functions nil "finished\n")
+      (should (= run-calls 1)))))
+
+;;; Boundary Cases
+
+(ert-deftest test-dev-fkeys-compile-and-run-impl-hook-skips-projectile-run-on-failure ()
+  "Boundary: when the compile fails, projectile-run-project must not run.
+The hook still self-removes (covered in the make-once-hook tests)."
+  (let ((run-calls 0)
+        (compilation-finish-functions nil))
+    (cl-letf (((symbol-function 'projectile-compile-project)
+               (lambda (_arg) nil))
+              ((symbol-function 'projectile-run-project)
+               (lambda (_arg) (cl-incf run-calls))))
+      (cj/--f4-compile-and-run-impl)
+      (run-hook-with-args 'compilation-finish-functions nil "exited abnormally\n")
+      (should (= run-calls 0)))))
+
+(provide 'test-dev-fkeys--f4-compile-and-run-impl)
+;;; test-dev-fkeys--f4-compile-and-run-impl.el ends here