RMT App Platform Tooling
Build, lint and editor support for RMT app platform projects.
What it covers
App Platform tooling connects RMT source to lint, compile, and scaffold reports. It checks more than syntax: missing references, forbidden DOM sinks, and incomplete app records are rejected before a host loads output.
Public building blocks
tools/rmt-language/app-platform-tooling.jscreates the public tooling report.tests/fixtures/rmt-app-platform-tooling.rmtis the executable input.tests/fixtures/rmt-app-platform-tooling.core.jsonrecords expected normalized output.
Recommended workflow
Run lint and compile against the same source. Fix diagnostics in that source, update the core snapshot only for an intentional semantic change, and then exercise the host fixture.
Next steps
Tooling For Orchestration
The app-platform tooling layer treats validation, animation and transition as first-class records. Completion, hover, document symbols and snippets explain field rules, animation presets, transition effects, durationMs, target action, use animation, from surfaces, to surfaces, interrupt, reducedMotion and lane transition. That gives the editor the same contracts that the compiler and Maraca consume.
For precise keyword contexts, this page points to the RMT Reference.
New snippets:
rmt-vnext-validationrmt-vnext-animationrmt-vnext-transitionrmt-vnext-maraca-orchestration-app
Local gates for changes in this layer:
node scripts/run_xtend_tests.js rmt-completions rmt-navigation rmt-vnext-tooling rmt-editor-packaging --json
node scripts/run_xtend_tests.js maraca-docs rmt-tooling-docs rmt-reference-docs --jsonNew in 0.8.0
Editor and reference catalogs include execution fastpass, effect navigation, effect close surface and effect focus surface. Compiler and runtime validate the same restricted shell contract; see Actions and Events.
Hydrangea JIT adds the opt-in jit-compile Tooling Bridge operation. It combines compile, safe preview and optional Maraca preparation without changing the Core schema or compiler rules. Its framework-artifact cache stays separate from user source; the existing backend remains the default.
No-Manual-HTML source gate
The tooling contract is xtend.epic18.rmt-app-platform-tooling.v1. The optional syntax audit rejects application innerHTML writes and reports source positions; structured RMT views and the explicit Trusted-DOM boundary remain the output paths.
node scripts/run_xtend_tests.js rmt-app-platform-tooling --jsonSee Trusted DOM and Sanitizing for Maraca build integration and the syntax-audit limits.