Publish a Unica version to the public marketplace, or resume a release that stalled part-way. Use when asked to cut, ship, promote, or finish a release, or when consumers still see an older version than the latest tag.
Repository instructions for coding agents working on Unica. They explain where to begin, which sources to trust, where changes belong, release work, and search practices.
Claude Code instructions for IngvarConsulting/unica: See AGENTS.md for entry points, source-of-truth ordering, search hygiene, and development rules. That file applies to Claude Code unchanged.
Design and review guidance for 1C:Enterprise APIs, which are interfaces that let software components call each other. It covers public and internal interfaces, compatibility, versioning, and moving users to changed interfaces.
A tool for reviewing the structure of a 1C configuration, a business-application setup used in the 1C platform. It reports the objects, properties, settings, and object counts it finds.
A checker for 1C configuration files, used after a configuration is created or changed. 1C is business software that uses configurable application setups.
A Russian-language development aid for 1C Configuration Extension files (CFE), which let developers customise an existing 1C configuration. It helps reuse objects from a configuration inside an extension.
A scaffolding tool for creating a 1C extension, an add-on that changes or extends an existing 1C configuration. It generates the XML source structure for a new extension.
A method for generating a procedure interceptor in a 1C extension (CFE). An interceptor runs before or after an existing procedure without parameters on an inherited object.
A diagnostic aid for BSL code and its rule settings. BSL is the programming language used by 1C, while diagnostics are automated checks that report possible code problems.
A search and investigation aid for BSL code, the programming language used by 1C business software. It helps locate implementations, callers, handlers, modules, entry points, and execution paths.
A guide for data exchange in 1C. It covers moving changes and messages between databases, including distributed information bases (РИБ), which are connected 1C databases that exchange data.
A guide for separating data in 1C databases so different tenants or groups access only their own records. Tenant boundaries are the rules that keep one organisation's data apart from another's.