ai-edtlisted

# AI-EDT AI-EDT exposes a running 1C:EDT instance over MCP. Search, navigation and analysis run against EDT's semantic model, not against file text, so references, definitions and call hierarchies are resolved the way the IDE resolves them. Plain text and regular-expression search over the module catalogue is available too, as one operation among others. The tool catalogue lives in `references/`. Read the file you need for the task at hand rather than all of them. ## When to use it - Reading and editing BSL: modules, methods, references, call graphs, refactoring. - Metadata: inspect, create, change, delete, rename with cascade. - Managed forms: structure, a screenshot of the WYSIWYG editor, editing without hand-written XML. - 1C queries: syntax and semantic validation before anything runs. - Project problems, infobase updates, YAxUnit tests, debugging and profiling. - **A configuration or extension delivered as one binary file.** A `.cf` becomes a project in a single call (`config_io operation=import_configuration_from_binary`), with no project needed beforehand. A `.cfe` the same way, but an extension that borrows from its base configuration needs `baseConfigurationPath` pointing at the matching `.cf` - without it the extension is staged against an empty infobase, which only carries an extension that adopts nothing. An `.epf` or `.erf` is different: `unpack_external_binary` needs an existing project to name, because it takes the platform runtime and the host