Scramjet 0.90.0 moves structural-mapping ownership to the Mach 12 development methodology while preserving cross-command-set planning use.
Highlights
- Mach 12 ownership: Rename the canonical mapper from
scramjet:structural-mappertomach12:structural-mapperand package it with Mach 12’s planning specialists. - Cross-set availability: Keep registered agents callable across command-set boundaries, including ordinary file-level planning outside an active Mach 12 command.
- Coherent optional activation: Dispatch the mapper from ordinary planning only when Mach 12 has registered it, without adding a substitute procedure or runtime discovery machinery.
- Preserved evidence contract: Retain the mapper’s read-only tools, bounded Current-State Structural Evidence Packet, and mapper-first Mach 12 planning handoff.
- Aligned distribution and guidance: Update command wiring, command-set metadata, documentation, installer coverage, and structural contract tests for the new ownership boundary.
Breaking change
- External prompts or custom commands that call
scramjet:structural-mapperby name must migrate tomach12:structural-mapper; no compatibility alias is retained.
Known limitations
- Structural mapping outside Mach 12 depends on the Mach 12 command set being installed and its mapper being registered.
- Deterministic tests establish naming, discovery, wiring, and installation behavior; they do not by themselves prove planning usefulness.
Closes #518 by aligning the mapper’s ownership with its planning scope while preserving intentional cross-set use.
Reviewed by GPT-5.6 Sol