docs: extend attributeCollection invariant to Adobe CF 2023 and 2025

Reviewer A round 1 on #2755 caught a real correctness gap: develop's
`Global.cfc::$header()` comment explicitly says "Adobe CF 2023+ rejects
the raw arguments scope" — the `+` is load-bearing — and #2750 patched
all 13 wrappers precisely because the restriction extends past 2023.
The docs as previously written named only "Adobe CF 2023", giving a
developer reading invariant #10 no signal to guard their code on
Adobe CF 2025.

Updates:
- CLAUDE.md invariant #10: "Adobe CF 2023" → "Adobe CF 2023 and 2025"
  throughout (opener, throw clause, "require the plain struct" clause).
- .ai/wheels/cross-engine-compatibility.md: section heading is
  "(Adobe CF 2023/2025)"; intro and Why paragraph name both engines;
  WRONG block comment says "crashes Adobe CF 2023 and 2025".
- RIGHT example in the .ai/ doc now mirrors the WRONG block by showing
  both invocation forms working once `local.args` is a plain struct
  (cfheader interpolated form + cfimage direct form), with a brief
  comment explaining why both are safe at that point — addresses
  Reviewer A's non-blocking nit that the original RIGHT example showed
  only the string-interpolated form while $image() uses the direct form.

Engine matrix is unchanged otherwise: Lucee 6/7 + BoxLang +
Adobe 2018/2021 still accept; Adobe 2023/2025 reject.

Signed-off-by: Peter Amiri <peter@alurium.com>

Author: bpamiri

.ai/wheels/cross-engine-compatibility.md

@@ -233,24 +233,27 @@ private string function myHelper() { ... }
 public string function $myHelper() { ... }
 ```
 
-### `attributeCollection` with the `arguments` Scope (Adobe CF 2023)
+### `attributeCollection` with the `arguments` Scope (Adobe CF 2023/2025)
 
-Adobe CF 2023 rejects the raw `arguments` scope when passed as `attributeCollection` to *any* built-in CFML tag, throwing engine-specific errors (`cfheader` reports `"Failed to add HTML header"`) and aborting the request. Lucee 6/7, BoxLang, and Adobe CF 2018/2021 all accept the `arguments` scope without complaint. Both the string-interpolated form (`attributeCollection = "#arguments#"`) and the CFScript direct-struct form (`attributeCollection = arguments`) are affected.
+Adobe CF 2023 and 2025 reject the raw `arguments` scope when passed as `attributeCollection` to *any* built-in CFML tag, throwing engine-specific errors (`cfheader` reports `"Failed to add HTML header"`) and aborting the request. Lucee 6/7, BoxLang, and Adobe CF 2018/2021 all accept the `arguments` scope without complaint. Both the string-interpolated form (`attributeCollection = "#arguments#"`) and the CFScript direct-struct form (`attributeCollection = arguments`) are affected.
 
 ```cfm
-// WRONG — crashes Adobe CF 2023
+// WRONG — crashes Adobe CF 2023 and 2025
 cfheader(attributeCollection = "#arguments#");
 cfimage(attributeCollection = arguments);
 
-// RIGHT — copy to a plain struct first
+// RIGHT — copy to a plain struct first; either invocation form works once
+// `local.args` is a plain struct (the engine's stricter check only objects
+// to the special `arguments` scope object, not to the form of the call).
 local.args = {};
 for (local.key in arguments) {
     local.args[local.key] = arguments[local.key];
 }
 cfheader(attributeCollection = "#local.args#");
+cfimage(attributeCollection = local.args);
 ```
 
-**Why**: Adobe CF 2023 imposes a stricter type check on `attributeCollection` and requires a plain CFML struct, not the special `arguments` scope object. The struct-copy pattern is safe and idiomatic across all engines. `$header()` is the dispatch-path blocker (runs on every request) — the others surface as soon as the corresponding helper is called.
+**Why**: Adobe CF 2023 and 2025 impose a stricter type check on `attributeCollection` and require a plain CFML struct, not the special `arguments` scope object. The struct-copy pattern is safe and idiomatic across all engines. `$header()` is the dispatch-path blocker (runs on every request) — the others surface as soon as the corresponding helper is called.
 
 **Reference fix**: [#2750](https://github.com/wheels-dev/wheels/pull/2750) (closes #2741) — patches all 13 affected wrappers in `vendor/wheels/Global.cfc` uniformly: `$header`, `$cache`, `$content`, `$mail`, `$directory`, `$file`, `$location`, `$htmlhead`, `$image`, `$dbinfo`, `$invoke`, `$wddx`, `$zip`. `$dbinfo()` rebuilds the local copy before each of its four `cfdbinfo` calls because the catch path mutates `arguments` between calls — a useful pattern when a helper writes through `arguments` between tag invocations.
 

CLAUDE.md

@@ -46,7 +46,7 @@ The framework must run on Lucee 5/6/7, Adobe CF 2018/2021/2023/2025, and BoxLang
 7. **`private` mixin functions are not integrated.** `$integrateComponents()` only copies `public` methods into model/controller objects. ALL helpers in `vendor/wheels/model/*.cfc`, view helpers, etc. MUST use `public` access with `$` prefix for internal scope. BoxLang passes; Lucee/Adobe fail.
 8. **`Left(str, 0)` crashes Lucee 7.** Guard: `len > 0 ? Left(str, len) : ""`.
 9. **`toBeInstanceOf("component")` fails on BoxLang** — returns the FQN, not the literal `"component"`. Use `toBeWheelsModel()` for finder results.
-10. **Adobe CF 2023 rejects the `arguments` scope as `attributeCollection` on *any* built-in CFML tag.** Affects every `cfheader` / `cfcache` / `cfcontent` / `cfmail` / `cfdirectory` / `cffile` / `cflocation` / `cfhtmlhead` / `cfimage` / `cfdbinfo` / `cfinvoke` / `cfwddx` / `cfzip` wrapper. Covers both the string-interpolated (`attributeCollection = "#arguments#"`) and direct-struct (`attributeCollection = arguments`) forms. Adobe 2023 throws — `cfheader`'s message is `"Failed to add HTML header"`; other tags surface their own — and `$header()` is catastrophic because it runs on every request. Copy to a plain struct first: `local.args = {}; for (local.key in arguments) { local.args[local.key] = arguments[local.key]; }`. Lucee 6/7, BoxLang, and Adobe 2018/2021 accept both forms; Adobe 2023 requires the plain struct. The 13 sites in `vendor/wheels/Global.cfc` were patched uniformly in [#2750](https://github.com/wheels-dev/wheels/pull/2750).
+10. **Adobe CF 2023 and 2025 reject the `arguments` scope as `attributeCollection` on *any* built-in CFML tag.** Affects every `cfheader` / `cfcache` / `cfcontent` / `cfmail` / `cfdirectory` / `cffile` / `cflocation` / `cfhtmlhead` / `cfimage` / `cfdbinfo` / `cfinvoke` / `cfwddx` / `cfzip` wrapper. Covers both the string-interpolated (`attributeCollection = "#arguments#"`) and direct-struct (`attributeCollection = arguments`) forms. Adobe 2023/2025 throw — `cfheader`'s message is `"Failed to add HTML header"`; other tags surface their own — and `$header()` is catastrophic because it runs on every request. Copy to a plain struct first: `local.args = {}; for (local.key in arguments) { local.args[local.key] = arguments[local.key]; }`. Lucee 6/7, BoxLang, and Adobe 2018/2021 accept both forms; Adobe 2023/2025 require the plain struct. The 13 sites in `vendor/wheels/Global.cfc` were patched uniformly in [#2750](https://github.com/wheels-dev/wheels/pull/2750).
 
 Verify Adobe CF fixes locally before pushing — don't iterate via CI:
 ```bash