elemctl 0.32.2__tar.gz → 0.32.3__tar.gz

{elemctl-0.32.2 → elemctl-0.32.3}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: elemctl
-Version: 0.32.2
-Summary: CLI, MCP server and library for the Console API v2 of the 1C:Enterprise.Element platform (1cmycloud)
+Version: 0.32.3
+Summary: CLI, MCP server and library for the Console API v2 of the 1C:Enterprise.Element platform (1cmycloud): applications, builds from source, one-command deploy with verification, a compile probe
 Author: KeyFire
 License-Expression: MIT
 Project-URL: Homepage, https://github.com/keyfire/elemctl
@@ -38,9 +38,9 @@ Dynamic: license-file
 
 A command-line tool, MCP server and Python library for managing applications on the **1C:Enterprise.Element** cloud platform (1cmycloud.com) through Console API v2.
 
-elemctl covers an application's lifecycle on the platform without the web console: create an application, build a `.xasm`/`.xlib` build archive from project sources, upload the build, apply it to the application and make sure the apply actually happened (the platform can silently roll back), and manage development-environment branches, dumps and the technology version. The same engine is available in three ways: the `elemctl` command for the terminal and CI, an MCP server for AI agents (Claude Code and other MCP clients), and the `elemctl` Python module for your own scripts.
+elemctl covers an application's lifecycle on the platform without the web console: create an application, build a `.xasm`/`.xlib` build archive from project sources, upload the build, apply it to the application and make sure the apply actually happened (the platform can silently roll back), check compilation with a probe that never touches the working application, and manage development-environment branches, dumps and the technology version. The same engine is available in three ways: the `elemctl` command for the terminal and CI, an MCP server for AI agents (Claude Code and other MCP clients), and the `elemctl` Python module for your own scripts.
 
-*elemctl is a CLI tool, MCP server and Python library for the 1C:Enterprise.Element (1cmycloud) Console API: manage applications, upload builds and deploy with honest apply verification. The CLI output is plain JSON.*
+*elemctl is a CLI tool, MCP server and Python library for the 1C:Enterprise.Element (1cmycloud) Console API: manage applications, upload builds, deploy with honest apply verification and check compilation with a probe. The CLI output is plain JSON.*
 
 Development notes and updates (in Russian): the [1C × AI: engineering workshop](https://t.me/ceh_1c_ai) Telegram channel.
 

{elemctl-0.32.2 → elemctl-0.32.3}/README.md

@@ -6,9 +6,9 @@
 
 A command-line tool, MCP server and Python library for managing applications on the **1C:Enterprise.Element** cloud platform (1cmycloud.com) through Console API v2.
 
-elemctl covers an application's lifecycle on the platform without the web console: create an application, build a `.xasm`/`.xlib` build archive from project sources, upload the build, apply it to the application and make sure the apply actually happened (the platform can silently roll back), and manage development-environment branches, dumps and the technology version. The same engine is available in three ways: the `elemctl` command for the terminal and CI, an MCP server for AI agents (Claude Code and other MCP clients), and the `elemctl` Python module for your own scripts.
+elemctl covers an application's lifecycle on the platform without the web console: create an application, build a `.xasm`/`.xlib` build archive from project sources, upload the build, apply it to the application and make sure the apply actually happened (the platform can silently roll back), check compilation with a probe that never touches the working application, and manage development-environment branches, dumps and the technology version. The same engine is available in three ways: the `elemctl` command for the terminal and CI, an MCP server for AI agents (Claude Code and other MCP clients), and the `elemctl` Python module for your own scripts.
 
-*elemctl is a CLI tool, MCP server and Python library for the 1C:Enterprise.Element (1cmycloud) Console API: manage applications, upload builds and deploy with honest apply verification. The CLI output is plain JSON.*
+*elemctl is a CLI tool, MCP server and Python library for the 1C:Enterprise.Element (1cmycloud) Console API: manage applications, upload builds, deploy with honest apply verification and check compilation with a probe. The CLI output is plain JSON.*
 
 Development notes and updates (in Russian): the [1C × AI: engineering workshop](https://t.me/ceh_1c_ai) Telegram channel.
 

{elemctl-0.32.2 → elemctl-0.32.3}/docs/SPEC.md

@@ -12,7 +12,7 @@ The `elemctl` Python package consists of three layers on top of a shared core:
 2. **CLI** – the `elemctl` console command (entry point `elemctl` in `[project.scripts]`).
 3. **MCP server** – the same operations exposed as tools for AI agents; stdio transport; the `mcp>=1.2,<3` dependency is included as the optional extra `elemctl[mcp]` (uses the ergonomic server class of the `mcp` package: `FastMCP` in mcp 1.x, `MCPServer` in mcp 2.x).
 
-Package requirements: name `elemctl`, version 0.1.0, Python >= 3.10, MIT license, author KeyFire, `src/elemctl/` layout, `dev` extra with pytest. The LICENSE, README.md, .env.example, and .gitignore files are provided by the customer and are not modified.
+Package requirements: name `elemctl`, version 0.1.0, Python >= 3.10, MIT license, author KeyFire, `src/elemctl/` layout, `dev` extra with pytest. The LICENSE, README.md, .env.example, and .gitignore files are given and are not modified.
 
 ## 2. Connection configuration
 

{elemctl-0.32.2 → elemctl-0.32.3}/docs/SPEC.ru.md

@@ -22,7 +22,7 @@ Python-пакет `elemctl` из трёх слоёв поверх общего
 
 Требования пакета: имя `elemctl`, версия 0.1.0, Python >= 3.10, лицензия MIT,
 автор KeyFire, layout `src/elemctl/`, extra `dev` с pytest. Файлы LICENSE,
-README.md, .env.example и .gitignore предоставлены заказчиком и не меняются.
+README.md, .env.example и .gitignore заданы и не меняются.
 
 ## 2. Конфигурация подключения
 

{elemctl-0.32.2 → elemctl-0.32.3}/docs/changelog.md

@@ -13,6 +13,14 @@ day are named in the heading. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## 2026-08-30 – 0.32.3
+
+### Changed
+
+- **The package description names the probe.** The PyPI summary and the site descriptions
+  listed applications, builds and deploys and said nothing about the compilation check the
+  server runs without risking the working application – a reason of its own to pick elemctl.
+
 ## 2026-08-27 – 0.32.2
 
 ### Added

{elemctl-0.32.2 → elemctl-0.32.3}/docs/changelog.ru.md

@@ -13,6 +13,14 @@ sidebar:
 [Keep a Changelog](https://keepachangelog.com/ru/1.1.0/), проект следует
 [семантическому версионированию](https://semver.org/lang/ru/).
 
+## 30.08.2026 – 0.32.3
+
+### Изменено
+
+- **Описание пакета называет пробник.** Сводка на карточке PyPI и описания сайта
+  перечисляли приложения, сборки и деплой, но молчали про проверку компиляции на сервере
+  без риска для рабочего приложения – а это отдельная причина ставить elemctl.
+
 ## 27.08.2026 – 0.32.2
 
 ### Добавлено

{elemctl-0.32.2 → elemctl-0.32.3}/docs/index.md

@@ -1,6 +1,6 @@
 ---
 title: "Elemctl"
-description: "A CLI, MCP server and library for the 1C:Element Console API: applications, builds from source and one-command deploys with an honest check that the change actually landed."
+description: "A CLI, MCP server and library for the 1C:Element Console API: applications, builds from source, one-command deploys with an honest check that the change actually landed, and a probe that compiles sources on the server without touching the working application."
 sidebar:
   label: Home
   order: 1
@@ -8,7 +8,7 @@ sidebar:
 
 A command-line tool, MCP server and Python library for managing applications on the **1C:Enterprise.Element** cloud platform (1cmycloud.com) through Console API v2.
 
-elemctl covers an application's lifecycle on the platform without the web console: create an application, build a `.xasm`/`.xlib` build archive from project sources, upload the build, apply it to the application and make sure the apply actually happened (the platform can silently roll back), and manage development-environment branches, dumps and the technology version. The same engine is available in three ways: the `elemctl` command for the terminal and CI, an MCP server for AI agents (Claude Code and other MCP clients), and the `elemctl` Python module for your own scripts.
+elemctl covers an application's lifecycle on the platform without the web console: create an application, build a `.xasm`/`.xlib` build archive from project sources, upload the build, apply it to the application and make sure the apply actually happened (the platform can silently roll back), check compilation with a probe that never touches the working application, and manage development-environment branches, dumps and the technology version. The same engine is available in three ways: the `elemctl` command for the terminal and CI, an MCP server for AI agents (Claude Code and other MCP clients), and the `elemctl` Python module for your own scripts.
 
 Development notes and updates (in Russian): the [1C × AI: engineering workshop](https://t.me/ceh_1c_ai) Telegram channel.
 

{elemctl-0.32.2 → elemctl-0.32.3}/docs/index.ru.md

@@ -1,6 +1,6 @@
 ---
 title: "Elemctl"
-description: "CLI, MCP-сервер и библиотека для Console API 1С:Элемента: приложения, сборки из исходников и деплой одной командой с честной проверкой, что изменение применилось."
+description: "CLI, MCP-сервер и библиотека для Console API 1С:Элемента: приложения, сборки из исходников, деплой одной командой с честной проверкой, что изменение применилось, и пробник, который компилирует исходники на сервере, не трогая рабочее приложение."
 sidebar:
   label: Главная
   order: 1
@@ -14,6 +14,7 @@ elemctl закрывает жизненный цикл приложения на
 создать приложение, собрать архив сборки `.xasm`/`.xlib` из исходников
 проекта, загрузить сборку, применить её к приложению и убедиться, что
 применение действительно произошло (платформа умеет молча откатывать),
+проверить компиляцию пробником, который не трогает рабочее приложение,
 управлять ветками среды разработки, дампами и версией технологии. Один и
 тот же движок доступен тремя способами: команда `elemctl` для терминала и
 CI, MCP-сервер для AI-агентов (Claude Code и другие MCP-клиенты) и
@@ -162,7 +163,7 @@ elemctl branches merge <branch-id>
   `deploy` и `verify` - ходить за причиной в журнал сервера не нужно.
 - Скомпилировать исходники, ничего не создавая на платформе, нельзя: компиляция
   серверная и происходит на применении сборки. Ровно для этого есть `probe` – он
-  принимает удар на одноразовое приложение вместо рабочего. Прогон стоит
+  подставляет под удар одноразовое приложение вместо рабочего. Прогон стоит
   столько же, сколько создание приложения (минуты), поэтому его место перед
   деплоем или в CI, а не в цикле "на каждое нажатие".
 - Проект платформы опознаётся парой `Vendor` + `Name` манифеста, а не `Ид` из

{elemctl-0.32.2 → elemctl-0.32.3}/docs/mcp.ru.md

@@ -49,7 +49,7 @@ claude mcp add elemctl -- elemctl mcp
 
 Рядом с ними встают инструменты, которые приносят плагины (см. ниже).
 
-Одно окружение не приковывает: у каждого инструмента, обращающегося к платформе,
+Одним окружением дело не ограничено: у каждого инструмента, обращающегося к платформе,
 есть необязательный `env_file` - путь к `.env` другого стенда. Так один сервер
 работает и с облаком, и с локальной установкой, без перезапуска с другими
 реквизитами. `list_apps` по умолчанию отдаёт краткие карточки (id, имя, статус,

{elemctl-0.32.2 → elemctl-0.32.3}/pyproject.toml

@@ -7,7 +7,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "elemctl"
 dynamic = ["version"]
-description = "CLI, MCP server and library for the Console API v2 of the 1C:Enterprise.Element platform (1cmycloud)"
+description = "CLI, MCP server and library for the Console API v2 of the 1C:Enterprise.Element platform (1cmycloud): applications, builds from source, one-command deploy with verification, a compile probe"
 readme = "README.md"
 requires-python = ">=3.10"
 license = "MIT"

{elemctl-0.32.2 → elemctl-0.32.3}/src/elemctl/__init__.py

@@ -18,7 +18,7 @@ from .errors import (
     TransportError,
 )
 
-__version__ = "0.32.2"
+__version__ = "0.32.3"
 
 __all__ = [
     "ApiError",

{elemctl-0.32.2 → elemctl-0.32.3}/src/elemctl/build.py

@@ -538,7 +538,7 @@ def read_assembly_project(path):
     The manifest carries the technical pair the platform recognizes a project by
     (vendor plus name), and the project descriptor inside the archive carries the
     presentation - the name a console shows. The two are different things: a
-    project named `site` is shown as "1C:Fresh Site", and comparing one against
+    project named `crm` is shown as "Acme CRM", and comparing one against
     the other calls every correct upload a mismatch.
 
     Light, like read_assembly_manifest: two entries are read, nothing is walked.

{elemctl-0.32.2 → elemctl-0.32.3}/src/elemctl/cli.py

@@ -404,7 +404,7 @@ def cmd_projects_delete(args):
 def cmd_builds_list(args):
     """The project's assemblies, newest first and limited by default.
 
-    The site project alone holds over a thousand assemblies: printing them all
+    A long-lived project alone holds over a thousand assemblies: printing them all
     made the answer to "which commit is the applied build from" a matter of
     piping through head and hoping the right card made the cut. The default
     shows the latest ten; --limit 0 brings the whole list back, and the cut is
@@ -467,8 +467,8 @@ def _upload_name_mismatch(client, project_id, file_path):
 
     Compared is what the console actually shows against what this archive would put
     there - the PRESENTATION of its project descriptor. The technical name of the
-    manifest is a different thing: a project named `site` is shown as "1C:Fresh
-    Site", and comparing those two called every correct upload a rename and refused
+    manifest is a different thing: a project named `crm` is shown as "Acme CRM",
+    and comparing those two called every correct upload a rename and refused
     it. The manifest name answers only when the archive carries no descriptor.
     """
     try:

{elemctl-0.32.2 → elemctl-0.32.3}/src/elemctl/mcp_server.py

@@ -61,7 +61,7 @@ INSTRUCTIONS = (
     "ensure_app, delete_app и merge_branch выполняются минутами и синхронно блокируют вызов "
     "до конца – в чате это выглядит зависанием без вывода. Такие операции "
     "запускать CLI-командой elemctl фоновым процессом (у агента – механизм "
-    "фонового запуска вроде run_in_background, результат придёт нотификацией), а "
+    "фонового запуска вроде run_in_background, результат придёт уведомлением), а "
     "не синхронным вызовом MCP-инструмента; сами MCP-инструменты предпочтительны "
     "для быстрых операций чтения (list/get/find/list-builds/verify-deploy). "
     "Окружение: по умолчанию используется то, с которым запущен сервер; чтобы "

{elemctl-0.32.2 → elemctl-0.32.3}/src/elemctl.egg-info/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: elemctl
-Version: 0.32.2
-Summary: CLI, MCP server and library for the Console API v2 of the 1C:Enterprise.Element platform (1cmycloud)
+Version: 0.32.3
+Summary: CLI, MCP server and library for the Console API v2 of the 1C:Enterprise.Element platform (1cmycloud): applications, builds from source, one-command deploy with verification, a compile probe
 Author: KeyFire
 License-Expression: MIT
 Project-URL: Homepage, https://github.com/keyfire/elemctl
@@ -38,9 +38,9 @@ Dynamic: license-file
 
 A command-line tool, MCP server and Python library for managing applications on the **1C:Enterprise.Element** cloud platform (1cmycloud.com) through Console API v2.
 
-elemctl covers an application's lifecycle on the platform without the web console: create an application, build a `.xasm`/`.xlib` build archive from project sources, upload the build, apply it to the application and make sure the apply actually happened (the platform can silently roll back), and manage development-environment branches, dumps and the technology version. The same engine is available in three ways: the `elemctl` command for the terminal and CI, an MCP server for AI agents (Claude Code and other MCP clients), and the `elemctl` Python module for your own scripts.
+elemctl covers an application's lifecycle on the platform without the web console: create an application, build a `.xasm`/`.xlib` build archive from project sources, upload the build, apply it to the application and make sure the apply actually happened (the platform can silently roll back), check compilation with a probe that never touches the working application, and manage development-environment branches, dumps and the technology version. The same engine is available in three ways: the `elemctl` command for the terminal and CI, an MCP server for AI agents (Claude Code and other MCP clients), and the `elemctl` Python module for your own scripts.
 
-*elemctl is a CLI tool, MCP server and Python library for the 1C:Enterprise.Element (1cmycloud) Console API: manage applications, upload builds and deploy with honest apply verification. The CLI output is plain JSON.*
+*elemctl is a CLI tool, MCP server and Python library for the 1C:Enterprise.Element (1cmycloud) Console API: manage applications, upload builds, deploy with honest apply verification and check compilation with a probe. The CLI output is plain JSON.*
 
 Development notes and updates (in Russian): the [1C × AI: engineering workshop](https://t.me/ceh_1c_ai) Telegram channel.
 

{elemctl-0.32.2 → elemctl-0.32.3}/tests/test_docs_coverage.py

@@ -133,3 +133,39 @@ def test_guard_notices_a_broken_raw_link_in_the_readme(guard, monkeypatch):
         lambda name: original(name) + f"\n![gone]({guard._RAW_PREFIX}docs/renamed.png)\n",
     )
     assert any("renamed.png" in problem for problem in guard.check())
+
+
+def test_guard_notices_a_feature_missing_from_one_annotation(guard, monkeypatch):
+    # the failure this check exists for: the block on the page names a capability and the
+    # one-liners around it - which is what a search engine and an AI answer quote - do not
+    surfaces = guard.pitch_surfaces()
+    surfaces["ru"]["docs/index.ru.md"] = surfaces["ru"]["docs/index.ru.md"].replace("пробник", "")
+    monkeypatch.setattr(guard, "pitch_surfaces", lambda: surfaces)
+    problems = guard.pitch_problems()
+    assert len(problems) == 1
+    assert "docs/index.ru.md" in problems[0]
+
+
+def test_guard_notices_a_headline_no_row_names(guard, monkeypatch):
+    original = guard.box_headlines
+    monkeypatch.setattr(
+        guard, "box_headlines",
+        lambda name, heading: original(name, heading) + ["Invented feature"],
+    )
+    assert any("Invented feature" in problem for problem in guard.pitch_problems())
+
+
+def test_guard_notices_a_row_the_page_dropped(guard, monkeypatch):
+    original = guard.box_headlines
+    monkeypatch.setattr(
+        guard, "box_headlines",
+        lambda name, heading: [h for h in original(name, heading) if h not in ("Dumps", "Дампы")],
+    )
+    assert any("Dumps" in problem for problem in guard.pitch_problems())
+
+
+def test_the_annotations_are_read_as_annotations(guard):
+    # an extractor quietly returning a whole file would make every word check above vacuous
+    for locale, group in guard.pitch_surfaces().items():
+        for where, text in group.items():
+            assert 80 < len(text) < 600, f"{locale} {where}: {len(text)} characters"