prolog-engine-onboardinglisted

# Prolog Engine Onboarding Workflow Use this skill whenever adding a new Prolog engine or dialect target to the toolkit. The onboarding process is **interactive and iterative**: at each phase, ask clarifying questions to gather exact requirements, create or modify files incrementally, run tests/validations, and seek user feedback before proceeding to the next step until the human programmer explicitly confirms that onboarding is complete. --- ## Phase 1: Information Gathering & Dialect Assessment Ask the human programmer (or inspect engine documentation/CLI): 1. **Engine Identification**: Full name (e.g., `GNU Prolog`, `Ciao Prolog`), CLI binary name (e.g. `gprolog`, `ciao`), and short slug (e.g. `gprolog`, `ciao`). 2. **Engine Features & String Representation**: Supported standard features and double quote representation (`chars`, `codes`, `atom`, or custom `string`)? 3. **Standard Libraries & Import Directives**: What is the import syntax (`:- use_module(library(...)).` vs `:- use_module(...)` vs auto-loaded)? List key libraries: DCG, CLP, reification, safe type tests, formatting, list utilities. 4. **Package & Build System**: Package manager (`bakage`, `pack`, `npm`, none)? 5. **Testing Framework**: Native test framework (`testing.pl`, `plunit`, `bsl`, custom)? 6. **Safety & Timeout Execution Flags**: Default CLI execution flags (e.g. `--quiet`, `-g`, `--goal`) for batch/script execution under safety runners. --- ## Phase 2: Dialect Standards & Standard Library Chea