Concept Vocabulary Unification

To fix naming drift, standardize scenario vocabulary by extracting canonical terms from requirements and a glossary, then map concepts to single domain-consistent names across models, APIs, and labels while preserving workflow behavior.

A glossary file like docs/concepts/GLOSSARY.md captures unified terminology and historical mappings, ensuring domain language consistency remains clear for engineers and stakeholders as new definitions are introduced.

Unify vocabulary by analyzing models and interfaces to update references with domain-consistent names, ensuring the renaming process strictly preserves existing business behavior and workflow logic.

You need to standardize scenario terminology before merging when prompt-manager skill packs describing workflows and domain models show inconsistent naming across documentation, tests, and operational requirements.

The best way to align scenario names in prompt-manager skill packs is to read the glossary, extract canonical terms from technical targets, and update documentation references to remove terminology drift.

Updating concept mappings in tests does not alter existing workflow behavior, as the standardization process updates names and references while explicitly preserving the underlying business logic and operational targets.