eslint-plugin-sfmc 2.6.1 → 4.0.0

package/README.md

@@ -39,18 +39,19 @@ Add the following to your `.vscode/settings.json`:
 
 ```json
 {
-    "eslint.validate": [
-        "javascript",
-        "javascriptreact",
-        "typescript",
-        "typescriptreact",
-        "html",
-        "vue",
-        "markdown",
-        "ampscript",
-        "ssjs",
-        "sfmc"
-    ]
+  "eslint.validate": [
+    "javascript",
+    "javascriptreact",
+    "typescript",
+    "typescriptreact",
+    "html",
+    "vue",
+    "markdown",
+    "ampscript",
+    "ssjs",
+    "sfmc",
+    "handlebars"
+  ]
 }
 ```
 
@@ -72,15 +73,15 @@ Add the following to your `.vscode/settings.json`:
 
 ### Marketing Cloud Next
 
-Use the `-next` config variants when targeting **Marketing Cloud Next (MCN)**. MCN supports only a subset of AMPscript functions and does **not** support SSJS at all.
+Use the `-next` config variants when targeting **Marketing Cloud Next (MCN)**. MCN supports only a subset of AMPscript functions and does **not** support SSJS at all. Handlebars is MCN's templating language, so the `embedded-next` and `strict-next` configs also lint the `{{...}}` helpers and `{!$...}` bindings extracted from HTML (see [Handlebars Rules](#handlebars-rules-hbs-)).
 
-| Config                           | Files                        | What it does                                                                              |
-| -------------------------------- | ---------------------------- | ----------------------------------------------------------------------------------------- |
-| `sfmc.configs['ampscript-next']` | `**/*.ampscript`, `**/*.amp` | AMPscript rules + flags functions unsupported in MCN (single config object)               |
-| `sfmc.configs['ssjs-next']`      | `**/*.ssjs`                  | Flags all SSJS API calls as MCN-unsupported; all other SSJS quality rules disabled        |
-| `sfmc.configs['recommended-next']` | Both of the above          | AMPscript MCN-aware + SSJS flagged for standalone files                                   |
-| `sfmc.configs['embedded-next']`  | `**/*.html`                  | AMPscript MCN-aware + SSJS flagged for HTML-embedded code                                 |
-| `sfmc.configs['strict-next']`    | All of the above + HTML      | All AMPscript rules at `error` severity + MCN flag; SSJS fully flagged                   |
+| Config                             | Files                        | What it does                                                                                |
+| ---------------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------- |
+| `sfmc.configs['ampscript-next']`   | `**/*.ampscript`, `**/*.amp` | AMPscript rules + flags functions unsupported in MCN (single config object)                 |
+| `sfmc.configs['ssjs-next']`        | `**/*.ssjs`                  | Flags all SSJS API calls as MCN-unsupported; all other SSJS quality rules disabled          |
+| `sfmc.configs['recommended-next']` | Both of the above            | AMPscript MCN-aware + SSJS flagged for standalone files                                     |
+| `sfmc.configs['embedded-next']`    | `**/*.html`                  | AMPscript MCN-aware + SSJS flagged + Handlebars rules for HTML-embedded code                |
+| `sfmc.configs['strict-next']`      | All of the above + HTML      | All AMPscript rules at `error` severity + MCN flag; SSJS fully flagged; Handlebars rules on |
 
 `recommended-next`, `embedded-next`, and `strict-next` are arrays — spread them with `...`.
 
@@ -88,58 +89,69 @@ Use the `-next` config variants when targeting **Marketing Cloud Next (MCN)**. M
 // eslint.config.js — targeting Marketing Cloud Next
 import sfmc from 'eslint-plugin-sfmc';
 
-export default [
-  ...sfmc.configs['recommended-next'],
-  ...sfmc.configs['embedded-next'],
-];
+export default [...sfmc.configs['recommended-next'], ...sfmc.configs['embedded-next']];
 ```
 
 ## AMPscript Rules (`amp-*`)
 
-| Rule                                                                                        | Default | Description                                                  |
-| ------------------------------------------------------------------------------------------- | ------- | ------------------------------------------------------------ |
-| [`sfmc/amp-no-unknown-function`](docs/rules/amp/no-unknown-function.md)                     | `error` | Disallow calls to unknown AMPscript functions                |
-| [`sfmc/amp-function-arity`](docs/rules/amp/function-arity.md)                               | `error` | Enforce correct argument counts                              |
-| [`sfmc/amp-arg-types`](docs/rules/amp/arg-types.md)                                         | `error` | Check that literal arguments match expected parameter types and allowed values |
-| [`sfmc/amp-set-requires-target`](docs/rules/amp/set-requires-target.md)                     | `error` | Require `set` to have a target variable                      |
-| [`sfmc/amp-no-smart-quotes`](docs/rules/amp/no-smart-quotes.md)                             | `error` | Disallow smart/curly quotes in strings                       |
-| [`sfmc/amp-no-var-redeclaration`](docs/rules/amp/no-var-redeclaration.md)                   | `warn`  | Disallow re-declaring a variable with `var`                  |
-| [`sfmc/amp-no-empty-block`](docs/rules/amp/no-empty-block.md)                               | `warn`  | Disallow empty `%%[ ]%%` blocks                              |
-| [`sfmc/amp-no-loop-counter-assign`](docs/rules/amp/no-loop-counter-assign.md)               | `warn`  | Disallow assigning to the `for` loop counter                 |
-| [`sfmc/amp-no-inline-statement`](docs/rules/amp/no-inline-statement.md)                     | `warn`  | Disallow statements inside inline expressions                |
-| [`sfmc/amp-no-deprecated-function`](docs/rules/amp/no-deprecated-function.md)               | `warn`  | Flag deprecated functions and suggest replacements           |
-| [`sfmc/amp-naming-convention`](docs/rules/amp/naming-convention.md)                         | `warn`  | Enforce variable naming convention                           |
-| [`sfmc/amp-no-empty-then`](docs/rules/amp/no-empty-then.md)                                 | `warn`  | Disallow IF with empty THEN branch                           |
-| [`sfmc/amp-require-rowcount-check`](docs/rules/amp/require-rowcount-check.md)               | `warn`  | Require RowCount check before FOR on LookupRows              |
-| [`sfmc/amp-no-html-comment`](docs/rules/amp/no-html-comment.md)                             | `warn`  | Disallow HTML comments inside AMPscript blocks               |
-| [`sfmc/amp-no-js-line-comment`](docs/rules/amp/no-js-line-comment.md)                       | `warn`  | Disallow JS-style `//` line comments in AMPscript            |
-| [`sfmc/amp-no-nested-script-tag`](docs/rules/amp/no-nested-script-tag.md)                   | `error` | Disallow `<script>` tags nested inside AMPscript script tags |
-| [`sfmc/amp-no-nested-ampscript-delimiter`](docs/rules/amp/no-nested-ampscript-delimiter.md) | `error` | Disallow AMPscript delimiters nested inside AMPscript blocks |
-| [`sfmc/amp-prefer-attribute-value`](docs/rules/amp/prefer-attribute-value.md)               | off     | Prefer `AttributeValue()` over bare personalization          |
-| [`sfmc/amp-require-variable-declaration`](docs/rules/amp/require-variable-declaration.md)   | off     | Require `var` before `set`                                   |
-| [`sfmc/amp-no-email-excluded-function`](docs/rules/amp/no-email-excluded-function.md)       | off     | Flag functions unavailable in email context                  |
+| Rule                                                                                        | Default                  | Description                                                                         |
+| ------------------------------------------------------------------------------------------- | ------------------------ | ----------------------------------------------------------------------------------- |
+| [`sfmc/amp-no-unknown-function`](docs/rules/amp/no-unknown-function.md)                     | `error`                  | Disallow calls to unknown AMPscript functions                                       |
+| [`sfmc/amp-no-mcn-unsupported`](docs/rules/amp/no-mcn-unsupported.md)                       | off (`error` in `-next`) | Flag AMPscript functions unavailable in the targeted MCN API version (`apiVersion`) |
+| [`sfmc/amp-function-arity`](docs/rules/amp/function-arity.md)                               | `error`                  | Enforce correct argument counts                                                     |
+| [`sfmc/amp-arg-types`](docs/rules/amp/arg-types.md)                                         | `error`                  | Check that literal arguments match expected parameter types and allowed values      |
+| [`sfmc/amp-set-requires-target`](docs/rules/amp/set-requires-target.md)                     | `error`                  | Require `set` to have a target variable                                             |
+| [`sfmc/amp-no-smart-quotes`](docs/rules/amp/no-smart-quotes.md)                             | `error`                  | Disallow smart/curly quotes in strings                                              |
+| [`sfmc/amp-no-var-redeclaration`](docs/rules/amp/no-var-redeclaration.md)                   | `warn`                   | Disallow re-declaring a variable with `var`                                         |
+| [`sfmc/amp-no-empty-block`](docs/rules/amp/no-empty-block.md)                               | `warn`                   | Disallow empty `%%[ ]%%` blocks                                                     |
+| [`sfmc/amp-no-loop-counter-assign`](docs/rules/amp/no-loop-counter-assign.md)               | `warn`                   | Disallow assigning to the `for` loop counter                                        |
+| [`sfmc/amp-no-inline-statement`](docs/rules/amp/no-inline-statement.md)                     | `warn`                   | Disallow statements inside inline expressions                                       |
+| [`sfmc/amp-no-deprecated-function`](docs/rules/amp/no-deprecated-function.md)               | `warn`                   | Flag deprecated functions and suggest replacements                                  |
+| [`sfmc/amp-naming-convention`](docs/rules/amp/naming-convention.md)                         | `warn`                   | Enforce variable naming convention                                                  |
+| [`sfmc/amp-no-empty-then`](docs/rules/amp/no-empty-then.md)                                 | `warn`                   | Disallow IF with empty THEN branch                                                  |
+| [`sfmc/amp-require-rowcount-check`](docs/rules/amp/require-rowcount-check.md)               | `warn`                   | Require RowCount check before FOR on LookupRows                                     |
+| [`sfmc/amp-no-html-comment`](docs/rules/amp/no-html-comment.md)                             | `warn`                   | Disallow HTML comments inside AMPscript blocks                                      |
+| [`sfmc/amp-no-js-line-comment`](docs/rules/amp/no-js-line-comment.md)                       | `warn`                   | Disallow JS-style `//` line comments in AMPscript                                   |
+| [`sfmc/amp-no-nested-script-tag`](docs/rules/amp/no-nested-script-tag.md)                   | `error`                  | Disallow `<script>` tags nested inside AMPscript script tags                        |
+| [`sfmc/amp-no-nested-ampscript-delimiter`](docs/rules/amp/no-nested-ampscript-delimiter.md) | `error`                  | Disallow AMPscript delimiters nested inside AMPscript blocks                        |
+| [`sfmc/amp-prefer-attribute-value`](docs/rules/amp/prefer-attribute-value.md)               | off                      | Prefer `AttributeValue()` over bare personalization                                 |
+| [`sfmc/amp-require-variable-declaration`](docs/rules/amp/require-variable-declaration.md)   | off                      | Require `var` before `set`                                                          |
+| [`sfmc/amp-no-email-excluded-function`](docs/rules/amp/no-email-excluded-function.md)       | off                      | Flag functions unavailable in email context                                         |
 
 ## SSJS Rules (`ssjs-*`)
 
-| Rule                                                                                                    | Default | Description                                                          |
-| ------------------------------------------------------------------------------------------------------- | ------- | -------------------------------------------------------------------- |
-| [`sfmc/ssjs-require-platform-load`](docs/rules/ssjs/require-platform-load.md)                           | `error` | Require `Platform.Load("core")` before Core or requiresCoreLoad globals |
-| [`sfmc/ssjs-no-unsupported-syntax`](docs/rules/ssjs/no-unsupported-syntax.md)                           | `error` | Flag ES6+ syntax not supported by SFMC                               |
-| [`sfmc/ssjs-no-unknown-function`](docs/rules/ssjs/no-unknown-function.md)                               | `error` | Disallow unknown methods on Platform.*, HTTP, Core Library, and WSProxy |
-| [`sfmc/ssjs-no-deprecated-function`](docs/rules/ssjs/no-deprecated-function.md)                         | `error` | Flag use of deprecated SFMC SSJS APIs (e.g. ContentArea, ContentAreaObj) |
-| [`sfmc/ssjs-no-property-call`](docs/rules/ssjs/no-property-call.md)                                     | `error` | Disallow calling Platform.Request/Response properties as functions   |
-| [`sfmc/ssjs-platform-function-arity`](docs/rules/ssjs/platform-function-arity.md)                       | `error` | Enforce correct arity for `Platform.Function.*`                      |
-| [`sfmc/ssjs-require-platform-load-order`](docs/rules/ssjs/require-platform-load-order.md)               | `error` | Require `Platform.Load()` before Core usage in order                 |
-| [`sfmc/ssjs-no-hardcoded-credentials`](docs/rules/ssjs/no-hardcoded-credentials.md)                     | `error` | Flag hardcoded keys in encryption calls                              |
-| [`sfmc/ssjs-cache-loop-length`](docs/rules/ssjs/cache-loop-length.md)                                   | `warn`  | Require caching `.length` in for-loops                               |
-| [`sfmc/ssjs-require-hasownproperty`](docs/rules/ssjs/require-hasownproperty.md)                         | `warn`  | Require `hasOwnProperty` guard in for-in loops                       |
-| [`sfmc/ssjs-prefer-platform-load-version`](docs/rules/ssjs/prefer-platform-load-version.md)             | `warn`  | Enforce a minimum `Platform.Load` version string                     |
-| [`sfmc/ssjs-no-unavailable-method`](docs/rules/ssjs/no-unavailable-method.md)                           | `warn`  | Flag Array/String methods unavailable or broken in SFMC's ES3 engine |
-| [`sfmc/ssjs-prefer-parsejson-safe-arg`](docs/rules/ssjs/prefer-parsejson-safe-arg.md)                   | `warn`  | Require string coercion on `ParseJSON` argument                      |
-| [`sfmc/ssjs-no-switch-default`](docs/rules/ssjs/no-switch-default.md)                                   | `warn`  | Disallow `default` clause in `switch` statements                     |
-| [`sfmc/ssjs-no-treatascontent-injection`](docs/rules/ssjs/no-treatascontent-injection.md)               | `warn`  | Flag dynamic string concatenation in `TreatAsContent` calls          |
-| [`sfmc/ssjs-core-method-arity`](docs/rules/ssjs/core-method-arity.md)                                   | `warn`  | Enforce correct argument counts for Core Library object methods      |
-| [`sfmc/ssjs-arg-types`](docs/rules/ssjs/arg-types.md)                                                   | `warn`  | Check that literal arguments match expected parameter types          |
+| Rule                                                                                        | Default                  | Description                                                              |
+| ------------------------------------------------------------------------------------------- | ------------------------ | ------------------------------------------------------------------------ |
+| [`sfmc/ssjs-require-platform-load`](docs/rules/ssjs/require-platform-load.md)               | `error`                  | Require `Platform.Load("core")` before Core or requiresCoreLoad globals  |
+| [`sfmc/ssjs-no-unsupported-syntax`](docs/rules/ssjs/no-unsupported-syntax.md)               | `error`                  | Flag ES6+ syntax not supported by SFMC                                   |
+| [`sfmc/ssjs-no-unknown-function`](docs/rules/ssjs/no-unknown-function.md)                   | `error`                  | Disallow unknown methods on Platform.\*, HTTP, Core Library, and WSProxy |
+| [`sfmc/ssjs-no-mcn-unsupported`](docs/rules/ssjs/no-mcn-unsupported.md)                     | off (`error` in `-next`) | Flag all SSJS API usage as unsupported in Marketing Cloud Next           |
+| [`sfmc/ssjs-no-deprecated-function`](docs/rules/ssjs/no-deprecated-function.md)             | `error`                  | Flag use of deprecated SFMC SSJS APIs (e.g. ContentArea, ContentAreaObj) |
+| [`sfmc/ssjs-no-property-call`](docs/rules/ssjs/no-property-call.md)                         | `error`                  | Disallow calling Platform.Request/Response properties as functions       |
+| [`sfmc/ssjs-platform-function-arity`](docs/rules/ssjs/platform-function-arity.md)           | `error`                  | Enforce correct arity for `Platform.Function.*`                          |
+| [`sfmc/ssjs-require-platform-load-order`](docs/rules/ssjs/require-platform-load-order.md)   | `error`                  | Require `Platform.Load()` before Core usage in order                     |
+| [`sfmc/ssjs-no-hardcoded-credentials`](docs/rules/ssjs/no-hardcoded-credentials.md)         | `error`                  | Flag hardcoded keys in encryption calls                                  |
+| [`sfmc/ssjs-cache-loop-length`](docs/rules/ssjs/cache-loop-length.md)                       | `warn`                   | Require caching `.length` in for-loops                                   |
+| [`sfmc/ssjs-require-hasownproperty`](docs/rules/ssjs/require-hasownproperty.md)             | `warn`                   | Require `hasOwnProperty` guard in for-in loops                           |
+| [`sfmc/ssjs-prefer-platform-load-version`](docs/rules/ssjs/prefer-platform-load-version.md) | `warn`                   | Enforce a minimum `Platform.Load` version string                         |
+| [`sfmc/ssjs-no-unavailable-method`](docs/rules/ssjs/no-unavailable-method.md)               | `warn`                   | Flag Array/String methods unavailable or broken in SFMC's ES3 engine     |
+| [`sfmc/ssjs-prefer-parsejson-safe-arg`](docs/rules/ssjs/prefer-parsejson-safe-arg.md)       | `warn`                   | Require string coercion on `ParseJSON` argument                          |
+| [`sfmc/ssjs-no-switch-default`](docs/rules/ssjs/no-switch-default.md)                       | `warn`                   | Disallow `default` clause in `switch` statements                         |
+| [`sfmc/ssjs-no-treatascontent-injection`](docs/rules/ssjs/no-treatascontent-injection.md)   | `warn`                   | Flag dynamic string concatenation in `TreatAsContent` calls              |
+| [`sfmc/ssjs-core-method-arity`](docs/rules/ssjs/core-method-arity.md)                       | `warn`                   | Enforce correct argument counts for Core Library object methods          |
+| [`sfmc/ssjs-arg-types`](docs/rules/ssjs/arg-types.md)                                       | `warn`                   | Check that literal arguments match expected parameter types              |
+
+## Handlebars Rules (`hbs-*`)
+
+Handlebars is the templating language for **Marketing Cloud Next (MCN)** only. These rules are enabled at `error` severity in the `-next` configs and are `off` in the classic (Engagement) configs — in classic SFMC, `{{...}}` is plain content and must not be flagged.
+
+| Rule                                                                              | Default (`-next`) | Description                                                                          |
+| --------------------------------------------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------ |
+| [`sfmc/hbs-no-unknown-helper`](docs/rules/hbs/no-unknown-helper.md)               | `error`           | Disallow helper invocations that are not part of the MCN catalog                     |
+| [`sfmc/hbs-no-unknown-binding`](docs/rules/hbs/no-unknown-binding.md)             | `error`           | Disallow unknown `{!$...}` built-in data bindings                                    |
+| [`sfmc/hbs-helper-arity`](docs/rules/hbs/helper-arity.md)                         | `error`           | Enforce correct positional-argument counts for known helpers                         |
+| [`sfmc/hbs-no-unsupported-construct`](docs/rules/hbs/no-unsupported-construct.md) | `error`           | Disallow constructs unsupported by the MCN engine (partials, decorators, `log`)      |
+| [`sfmc/hbs-no-mcn-unsupported`](docs/rules/hbs/no-mcn-unsupported.md)             | `error`           | Flag helpers and bindings unavailable in the targeted MCN API version (`apiVersion`) |
 
 ## Processors
 

package/docs/rules/amp/no-mcn-unsupported.md

@@ -0,0 +1,76 @@
+# `sfmc/amp-no-mcn-unsupported`
+
+> Disallow AMPscript functions that are not available in the targeted Marketing Cloud Next API version.
+
+| | |
+|---|---|
+| **Type** | `problem` |
+| **Default severity** | `error` in all `-next` configs; `off` otherwise |
+| **Fixable** | — |
+
+## Why This Rule Exists
+
+Only a subset of AMPscript functions are available in Marketing Cloud Next (MCN), and support has been added gradually across MCN releases. This rule flags AMPscript functions that will not work in the MCN release you target:
+
+- Functions that **Marketing Cloud Next never supported** — they only work in classic Marketing Cloud Engagement.
+- Functions that were **added in a later MCN release** than the one you target (see the `apiVersion` option below).
+- Functions that work in MCN AMPscript but have **no Handlebars equivalent**, so they cannot be carried over if you later migrate the content to Handlebars.
+
+Unknown function names are handled separately by [`sfmc/amp-no-unknown-function`](no-unknown-function.md); this rule only checks functions that actually exist in AMPscript.
+
+## Settings
+
+| Setting | Values | Default |
+|---------|--------|---------|
+| severity | `"error"` \| `"warn"` \| `"off"` | `"error"` in `-next` configs |
+
+### Options
+
+| Option | Type | Default | Description |
+|--------|------|---------|-------------|
+| `apiVersion` | `number` | — | The targeted Marketing Cloud Next API version (e.g. `65` = Winter '26, `67` = Summer '26). |
+
+**What `apiVersion` does** (shared with the SSJS and Handlebars MCN rules):
+
+- **Leave it unset** to check against _any_ MCN release: a function is flagged only if it is never supported in Marketing Cloud Next. Anything that works in some MCN release is allowed.
+- **Set it to your target release** (for example `65`) to also flag functions that were added in a _later_ MCN release than the one you run. A function is allowed only when it is available in your target release or an earlier one.
+
+## Examples
+
+```js
+// eslint.config.js
+rules: {
+  'sfmc/amp-no-mcn-unsupported': ['error', { apiVersion: 65 }]
+}
+```
+
+Or use the built-in `recommended-next` / `strict-next` / `embedded-next` configs, which apply this rule automatically (without an `apiVersion`, flagging only never-supported functions).
+
+**Not allowed (with `apiVersion: 65`):**
+
+```ampscript
+%%[
+  /* InsertDE is never available in Marketing Cloud Next */
+  InsertDE("MyDE", "Col", "Value")
+  /* Concat was added in a later MCN release than the one targeted (65) */
+  set @x = Concat("a", "b")
+]%%
+```
+
+**Allowed (with `apiVersion: 67`):**
+
+```ampscript
+%%[
+  /* Concat is available in this MCN release */
+  set @x = Concat("a", "b")
+]%%
+```
+
+## When to Disable
+
+Disable this rule when you are not targeting Marketing Cloud Next (the default `engagement` configs already leave it `off`).
+
+```js
+// eslint.config.js
+rules: { 'sfmc/amp-no-mcn-unsupported': 'off' }
+```

package/docs/rules/amp/no-unknown-function.md

@@ -12,7 +12,7 @@
 
 AMPscript does not support user-defined functions. Every function call must match a name in Salesforce's published catalog. Calling an unknown name causes a runtime error (or is silently ignored depending on the execution context), making the code unreliable. This rule catches typos and invented names before deployment.
 
-When targeting **Marketing Cloud Next**, only a subset of AMPscript functions are supported. Use the `target: 'next'` option to flag functions that cannot run in MCN.
+This rule only reports **unknown** function names. Functions that exist in the catalog but are unavailable when targeting Marketing Cloud Next are handled by [`sfmc/amp-no-mcn-unsupported`](no-mcn-unsupported.md).
 
 ## Settings
 
@@ -20,16 +20,10 @@ When targeting **Marketing Cloud Next**, only a subset of AMPscript functions ar
 |---------|--------|---------|
 | severity | `"error"` \| `"warn"` \| `"off"` | `"error"` |
 
-### Options
-
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `target` | `'engagement'` \| `'next'` | — | Target platform. Set to `'next'` to additionally flag AMPscript functions not available in Marketing Cloud Next (API v67.0+). |
+This rule takes no options.
 
 ## Examples
 
-### Standard usage (Marketing Cloud Engagement)
-
 **Not allowed:**
 
 ```ampscript
@@ -48,37 +42,6 @@ When targeting **Marketing Cloud Next**, only a subset of AMPscript functions ar
 ]%%
 ```
 
-### MCN target
-
-Configure the rule with `target: 'next'` to flag functions unsupported in Marketing Cloud Next:
-
-```js
-// eslint.config.js
-rules: {
-  'sfmc/amp-no-unknown-function': ['error', { target: 'next' }]
-}
-```
-
-Or use the built-in `recommended-next` / `strict-next` / `embedded-next` configs which apply this automatically.
-
-**Not allowed (with `target: 'next'`):**
-
-```ampscript
-%%[
-  /* InsertDE is not supported in Marketing Cloud Next */
-  InsertDE("MyDE", "Col", "Value")
-]%%
-```
-
-**Allowed (with `target: 'next'`):**
-
-```ampscript
-%%[
-  /* UpsertDE is supported in Marketing Cloud Next */
-  UpsertDE("MyDE", 1, "Key", @key, "Col", "Value")
-]%%
-```
-
 ## When to Disable
 
 Only disable this rule if you are intentionally using a proprietary or undocumented SFMC extension that is not in the public catalog.

package/docs/rules/hbs/helper-arity.md

@@ -0,0 +1,55 @@
+# `sfmc/hbs-helper-arity`
+
+> Enforce correct positional-argument counts for known Marketing Cloud Next Handlebars helpers.
+
+| | |
+|---|---|
+| **Type** | `problem` |
+| **Default severity** | `error` in the `-next` configs; `off` in classic configs |
+| **Fixable** | — |
+
+## Why This Rule Exists
+
+Each Marketing Cloud Next helper has a fixed set of positional parameters defined in the catalog. Calling a helper with too few required arguments, or with more arguments than it accepts, fails at render time. This rule validates every helper invocation against the helper's `params` definition.
+
+Only **positional** arguments are checked. Helpers with a variadic trailing parameter (for example `concat`, `and`, `set`) have no upper bound. Hash (named) arguments are not counted as positional arguments. A bare `{{foo}}` mustache with no arguments is a data binding, not an invocation, and is skipped.
+
+Handlebars only exists when targeting MCN, so this rule is enabled only in the `-next` configs.
+
+## Settings
+
+| Setting | Values | Default |
+|---------|--------|---------|
+| severity | `"error"` \| `"warn"` \| `"off"` | `"error"` (in `-next` configs) |
+
+This rule has no configuration options.
+
+## Examples
+
+**Not allowed:**
+
+```handlebars
+{{! formatDate requires a value and a format string }}
+{{formatDate order.createdAt}}
+
+{{! uppercase takes exactly one argument }}
+{{uppercase firstName lastName}}
+```
+
+**Allowed:**
+
+```handlebars
+{{formatDate order.createdAt "yyyy-MM-dd"}}
+
+{{uppercase firstName}}
+
+{{! concat is variadic — any number of arguments is fine }}
+{{concat firstName " " lastName}}
+```
+
+## When to Disable
+
+```js
+// eslint.config.js
+rules: { 'sfmc/hbs-helper-arity': 'off' }
+```

package/docs/rules/hbs/no-mcn-unsupported.md

@@ -0,0 +1,69 @@
+# `sfmc/hbs-no-mcn-unsupported`
+
+> Disallow Handlebars helpers and bindings not available in the targeted Marketing Cloud Next API version.
+
+| | |
+|---|---|
+| **Type** | `problem` |
+| **Default severity** | `error` in all `-next` configs; `off` otherwise |
+| **Fixable** | — |
+
+## Why This Rule Exists
+
+Marketing Cloud Next (MCN) adds new Handlebars helpers and `{!$...}` data bindings across its releases. This rule flags helpers and bindings that will not work in the MCN release you target:
+
+- Helpers/bindings that **Marketing Cloud Next never supported**.
+- Helpers/bindings that were **added in a later MCN release** than the one you target (see the `apiVersion` option below).
+
+Unknown helpers and bindings — ones that are not part of Marketing Cloud Next at all — are handled separately by [`sfmc/hbs-no-unknown-helper`](no-unknown-helper.md) and [`sfmc/hbs-no-unknown-binding`](no-unknown-binding.md); this rule only checks the release availability of helpers and bindings that MCN does provide. Handlebars constructs that MCN never supports (partials, decorators, `{{log}}`, etc.) are handled by [`sfmc/hbs-no-unsupported-construct`](no-unsupported-construct.md).
+
+## Settings
+
+| Setting | Values | Default |
+|---------|--------|---------|
+| severity | `"error"` \| `"warn"` \| `"off"` | `"error"` in `-next` configs |
+
+### Options
+
+| Option | Type | Default | Description |
+|--------|------|---------|-------------|
+| `apiVersion` | `number` | — | The targeted Marketing Cloud Next API version (e.g. `65` = Winter '26, `67` = Summer '26). |
+
+**What `apiVersion` does** (shared with the AMPscript and SSJS MCN rules):
+
+- **Leave it unset** to check against _any_ MCN release: a helper or binding is flagged only if it is never supported in Marketing Cloud Next. Anything that works in some MCN release is allowed.
+- **Set it to your target release** (for example `65`) to also flag helpers and bindings that were added in a _later_ MCN release than the one you run. An item is allowed only when it is available in your target release or an earlier one.
+
+Every Handlebars helper and binding is available in some MCN release, so with no `apiVersion` set nothing is flagged. Setting `apiVersion` to an earlier release flags the helpers and bindings added after it — for example, `apiVersion: 65` flags the helpers introduced in release 67.
+
+## Examples
+
+```js
+// eslint.config.js
+rules: {
+  'sfmc/hbs-no-mcn-unsupported': ['error', { apiVersion: 65 }]
+}
+```
+
+**Not allowed (with `apiVersion: 65`):**
+
+```handlebars
+{{! dateAdd was added in a later MCN release than the one targeted (65) }}
+{{dateAdd order.createdAt 7 "days"}}
+```
+
+**Allowed (with `apiVersion: 65`):**
+
+```handlebars
+{{! add is available in this MCN release }}
+{{add price tax}}
+```
+
+## When to Disable
+
+Disable this rule when you are not targeting Marketing Cloud Next (the default `engagement` configs already leave it `off`).
+
+```js
+// eslint.config.js
+rules: { 'sfmc/hbs-no-mcn-unsupported': 'off' }
+```

package/docs/rules/hbs/no-unknown-binding.md

@@ -0,0 +1,49 @@
+# `sfmc/hbs-no-unknown-binding`
+
+> Disallow unknown `{!$...}` built-in data bindings in Marketing Cloud Next Handlebars.
+
+| | |
+|---|---|
+| **Type** | `problem` |
+| **Default severity** | `error` in the `-next` configs; `off` in classic configs |
+| **Fixable** | — |
+
+## Why This Rule Exists
+
+Marketing Cloud Next exposes a fixed set of built-in data bindings written as `{!$namespace.Field}` tokens (for example `{!$Context.MessageContext}`). These `{!$...}` tokens are **not** Handlebars helper syntax — the Handlebars parser treats them as literal content — so this rule scans the raw source text with a regex pass rather than walking the AST, mirroring the `handlebars/unknown-binding` diagnostic emitted by the language server.
+
+An unrecognized binding name is a typo or a reference to a namespace/field that MCN does not provide, and resolves to empty output at render time. The rule offers a "did you mean" suggestion when a close match exists.
+
+Handlebars only exists when targeting MCN, so this rule is enabled only in the `-next` configs.
+
+## Settings
+
+| Setting | Values | Default |
+|---------|--------|---------|
+| severity | `"error"` \| `"warn"` \| `"off"` | `"error"` (in `-next` configs) |
+
+This rule has no configuration options.
+
+## Examples
+
+**Not allowed:**
+
+```handlebars
+{{! 'Contect' is not a known binding namespace }}
+{!$Contect.MessageContext}
+```
+
+**Allowed:**
+
+```handlebars
+{!$Context.MessageContext}
+```
+
+## When to Disable
+
+Disable only if you use a binding that is available in your MCN account but missing from the bundled catalog (please report it so the catalog can be updated).
+
+```js
+// eslint.config.js
+rules: { 'sfmc/hbs-no-unknown-binding': 'off' }
+```

package/docs/rules/hbs/no-unknown-helper.md

@@ -0,0 +1,60 @@
+# `sfmc/hbs-no-unknown-helper`
+
+> Disallow Handlebars helper invocations that are not part of the Marketing Cloud Next catalog.
+
+| | |
+|---|---|
+| **Type** | `problem` |
+| **Default severity** | `error` in the `-next` configs; `off` in classic configs |
+| **Fixable** | — |
+
+## Why This Rule Exists
+
+Marketing Cloud Next (MCN) runs a locked-down Handlebars engine that cannot register custom helpers. Every helper name must exist in the published MCN catalog. An unknown helper name is a typo or an unsupported construct that fails at render time. This rule flags any helper invocation whose name is not in the catalog and offers a "did you mean" suggestion when a close match exists.
+
+A bare `{{foo}}` mustache with no arguments is treated as a **data binding**, not a helper invocation, and is not flagged by this rule. Helper detection applies to inline mustaches with arguments, subexpressions, and block helpers.
+
+Handlebars only exists when targeting MCN, so this rule is enabled only in the `-next` configs. In classic (Marketing Cloud Engagement) configs it is disabled because `{{...}}` is plain content there.
+
+## Settings
+
+| Setting | Values | Default |
+|---------|--------|---------|
+| severity | `"error"` \| `"warn"` \| `"off"` | `"error"` (in `-next` configs) |
+
+This rule has no configuration options.
+
+## Examples
+
+**Not allowed:**
+
+```handlebars
+{{! 'formatDates' is not a catalog helper — did you mean 'formatDate'? }}
+{{formatDates order.createdAt "yyyy-MM-dd"}}
+
+{{#eachItem items}}
+  {{this.name}}
+{{/eachItem}}
+```
+
+**Allowed:**
+
+```handlebars
+{{formatDate order.createdAt "yyyy-MM-dd"}}
+
+{{#each items}}
+  {{this.name}}
+{{/each}}
+
+{{! bare binding, not a helper — never flagged }}
+{{firstName}}
+```
+
+## When to Disable
+
+Disable only if you rely on a helper that is genuinely available in your MCN account but missing from the bundled catalog (please report it so the catalog can be updated).
+
+```js
+// eslint.config.js
+rules: { 'sfmc/hbs-no-unknown-helper': 'off' }
+```

package/docs/rules/hbs/no-unsupported-construct.md

@@ -0,0 +1,65 @@
+# `sfmc/hbs-no-unsupported-construct`
+
+> Disallow Handlebars constructs unsupported by the Marketing Cloud Next engine (partials, decorators, log).
+
+| | |
+|---|---|
+| **Type** | `problem` |
+| **Default severity** | `error` in the `-next` configs; `off` in classic configs |
+| **Fixable** | — |
+
+## Why This Rule Exists
+
+The Marketing Cloud Next Handlebars engine is a locked-down subset of handlebars.js. Several standard handlebars.js constructs are not available and fail at render time:
+
+- Partials — `{{> partialName}}`
+- Partial blocks — `{{#> partialName}}...{{/partialName}}`
+- Inline partials — `{{#*inline "name"}}...{{/inline}}`
+- Decorators — `{{* decorator}}` and `{{#* decorator}}...{{/*decorator}}`
+- The debugging helper `{{log}}`
+
+This rule flags each of these, mirroring the `handlebars/unsupported-construct` diagnostic emitted by the language server. The full explanation for the specific construct is included in the reported message.
+
+Handlebars only exists when targeting MCN, so this rule is enabled only in the `-next` configs.
+
+## Settings
+
+| Setting | Values | Default |
+|---------|--------|---------|
+| severity | `"error"` \| `"warn"` \| `"off"` | `"error"` (in `-next` configs) |
+
+This rule has no configuration options.
+
+## Examples
+
+**Not allowed:**
+
+```handlebars
+{{> header}}
+
+{{#> layout}}
+  body
+{{/layout}}
+
+{{log "debugging"}}
+```
+
+**Allowed:**
+
+```handlebars
+{{! inline the shared markup instead of using a partial }}
+<h1>{{title}}</h1>
+
+{{#each items}}
+  {{this.name}}
+{{/each}}
+```
+
+## When to Disable
+
+These constructs do not run in MCN, so disabling the rule only hides a guaranteed render-time failure. Leave it enabled.
+
+```js
+// eslint.config.js
+rules: { 'sfmc/hbs-no-unsupported-construct': 'off' }
+```