@caatinga/core 0.2.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Kaleido contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,33 @@
+# @caatinga/core
+
+Core config, artifacts, command orchestration, and error primitives for Caatinga.
+
+## Supported Use
+
+`@caatinga/core` is primarily an internal package for the Caatinga CLI and templates; direct use beyond the documented config/template helpers is advanced and less stable than the CLI contract.
+
+## What Is In This Package
+
+- `defineConfig` for Caatinga project config files generated by Caatinga templates
+- config loading and validation
+- artifact resolution and update helpers
+- shared command orchestration primitives
+- public `CAATINGA_*` error foundations used by higher-level packages
+
+## Consumer Guidance
+
+If you want the supported end-user workflow, use `@caatinga/cli`.
+
+If you are authoring a Caatinga project, importing `defineConfig` from `@caatinga/core` in `caatinga.config.ts` is part of the intended template/config surface.
+
+Reach for broader `@caatinga/core` APIs directly only when you are building advanced tooling on top of Caatinga internals and are prepared to track lower-level package changes more closely than a CLI consumer.
+
+## Stability Posture
+
+Being published does not make every export a first-class end-user contract. The stable consumer surfaces are:
+
+- the documented CLI workflow in `@caatinga/cli`
+- the documented `@caatinga/client` APIs
+- the narrow `@caatinga/core` config/template surface used by generated projects, including `defineConfig`
+
+Direct `@caatinga/core` usage should be treated as advanced integration with a narrower support posture than the CLI package.