SP-141: Document BUSINESS validation layer#355
Open
Kastriot Salihu (ksalihu) wants to merge 2 commits into
Open
SP-141: Document BUSINESS validation layer#355Kastriot Salihu (ksalihu) wants to merge 2 commits into
Kastriot Salihu (ksalihu) wants to merge 2 commits into
Conversation
… docs Document the BUSINESS validation layer in `config validate` so it is discoverable from `--help` and the user guide instead of requiring prior knowledge of the pacman API. - module.ts: `--layers` help now enumerates the allowed values (SCHEMA, BUSINESS) and notes that they can be combined. - config-commands.md: new "Validate Package Configurations" section covering `--layers`, `--nodeKeys`, console output, and the JSON report shape; new "Validate During Import" subsection clarifying that `config import --validate` runs SCHEMA only. - agentic-development-guide.md: agent step now mentions that import-time validation is SCHEMA-only and shows `config validate --layers SCHEMA BUSINESS` as the way to run business rules. - asset-registry-endpoints SKILL: same clarification for agents plus a Quick reference entry for `config validate`. Default behaviour and CLI surface are unchanged; this only adds help text and docs. Includes-AI-Code: true Co-authored-by: Cursor <cursoragent@cursor.com>
Eszter Galicz (celeszter)
previously approved these changes
May 22, 2026
The note about the ~2–3s window where a freshly-imported staging version isn't yet queryable by the validate endpoint is being tracked as a separate concern. Removing it from the skill so the documentation doesn't lock the behaviour in before the bug fix lands. Includes-AI-Code: true Co-authored-by: Cursor <cursoragent@cursor.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Surfaces the
BUSINESSvalidation layer in theconfig validatecommand so it's discoverable from--helpand the user guide, instead of requiring prior knowledge of the pacman API.--layershelp now enumerates the allowed values (SCHEMA,BUSINESS) and notes they can be combined.docs/user-guide/config-commands.mdcovering--layers,--nodeKeys, console output, and the JSON report shape.config import --validateruns theSCHEMAlayer only, and links toconfig validatefor business-rule checks.config validateentry in the agentic dev guide and theasset-registry-endpointsCursor skill.Default behaviour and CLI surface are unchanged — this only adds help text and documentation.
Relevant links
Checklist
config-validateJest spec still passes (5/5)