New Feature: /Application function / test-spec gap analysis

.gitignore

@@ -8,6 +8,8 @@ grapher/**
 
 # Test Results
 tests/results/**
+bx/tests/results/**
+cfml/tests/results/**
 
 # Dependencies
 system/modules/**

CONTRIBUTING.md

@@ -61,7 +61,19 @@ If you discover a security vulnerability, please send an email to the developmen
 2. Make sure you have CommandBox installed: https://www.ortussolutions.com/products/commandbox#download
 3. Start a CommandBox shell in the root of the project: `box`
 4. Install the development dependencies: `install`
-5. Hack away! Create tests under `/tests/specs` and run the tests!
+5. Hack away! Create tests under `/tests/specs` (and optional fixtures under `/tests/resources`) and run the tests!
+
+With a CommandBox server started for this project (`box run-script start:lucee` or your usual `server start`), run the **full** suite from the repo root:
+
+```bash
+box testbox run reporter=json
+```
+
+That uses `box.json` → `testbox.runner` (default `http://localhost:49616/tests/runner.cfm`) and discovers all bundles under `tests/specs`. Fix any failures before opening a PR.
+
+### Features consumed from any application
+
+Gap analysis and Smoke Test are implemented in **`system/runners/HTMLRunner.cfm`** and TestBox services, not in consuming applications. **Do not** add vendor-specific or app-specific CFC glue to TestBox for those features. Prefer **documented URL parameters** (and optional **`request`** overrides). A consumer typically only needs a **`/testbox` mapping**, a thin **`runner.cfm`** that includes **`HTMLRunner.cfm`**, and test specs—optionally with **`cfparam`** defaults for URLs such as **`directory`** and **`coveragePathToCapture`**.
 
 ## Language Compatiblity
 
@@ -83,6 +95,8 @@ box run-script format
 box run-script format:watch
 ```
 
+If CommandBox reports that `cfformat` cannot be resolved, install the formatter: `box install commandbox-cfformat`.
+
 We recommend that anytime you hack on the core you start the formatter watcher (`box run-script format:watch`). This will monitor your changes and auto-format your code for you.
 
 You can also see the Ortus Coding Standards you must follow here: https://github.com/Ortus-Solutions/coding-standards.

box.json

@@ -51,9 +51,9 @@
     },
     "scripts":{
         "release":"recipe build/release.boxr",
-        "format":"cfformat run system/**/*.cfc,test-harness/**/*.cfc,tests/specs/**/*.cfc --overwrite",
-        "format:check":"cfformat check system/**/*.cfc,test-harness/**/*.cfc,tests/specs/**/*.cfc ./.cfformat.json",
-        "format:watch":"cfformat watch system/**/*.cfc,test-harness/**/*.cfc,tests/specs/**/*.cfc ./.cfformat.json",
+        "format":"cfformat run system/**/*.cfc,test-harness/**/*.cfc,tests/specs/**/*.cfc,tests/resources/**/*.cfc --overwrite",
+        "format:check":"cfformat check system/**/*.cfc,test-harness/**/*.cfc,tests/specs/**/*.cfc,tests/resources/**/*.cfc ./.cfformat.json",
+        "format:watch":"cfformat watch system/**/*.cfc,test-harness/**/*.cfc,tests/specs/**/*.cfc,tests/resources/**/*.cfc ./.cfformat.json",
         "start:lucee":"server start serverConfigFile=server-lucee@5.json",
         "start:adobe":"server start serverConfigFile=server-adobe@2025.json",
         "start:boxlang":"server start serverConfigFile=server-boxlang@1.json",