rein-scene-forge-dsh-plugin

Hand-writing tour_robot YAML scene configurations is rarely the hard part; the hard part is realizing a field name is off, the schema does not line up, or is_valid passed while is_publishable still says no. rein-scene-forge-dsh-plugin turns that entire chain into a repeatable, auditable pipeline: it starts from an authoritative points.json and narration material, validates every target object against the JSON Schemas under schemas/tour-robot, and rejects unknown fields outright so the output is semantically clean before anything else.

The plugin ships a versioned, machine-readable rule set under rules/ and exposes four deterministic tools—get_authoring_rules, analyze_point_input, validate_authoring_model, and validate_tour_robot_scene—so callers can step through rule versions, analyse point inputs, validate individual authoring fields, and finally validate the full scene. Each step has deterministic input and output, making it easy to wire into CI or batch scripts. New scenes enable dynamic PAD reception by default, and missing user instructions must never silently disable it, preventing broken reception chains from reaching production.

It is best suited for developers and operations teams who need to bulk-generate, validate, and publish tour_robot scene configurations: prepare the points.json and narration material, and the plugin handles field selection, schema validation, SOP walkthrough, and writing out the four configuration files (map_config, scene_config, explain_config, reception_pack).