@decantr/cli 1.7.4 → 1.7.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md ADDED
@@ -0,0 +1,84 @@
1
+ # @decantr/cli
2
+
3
+ Support status: `core-supported`
4
+ Release channel: `stable`
5
+
6
+ Decantr’s main local operator surface for scaffolding, auditing, inspecting, and maintaining Decantr projects.
7
+
8
+ ## Install
9
+
10
+ ```bash
11
+ npm install -D @decantr/cli
12
+ ```
13
+
14
+ Or run it without installing:
15
+
16
+ ```bash
17
+ npx @decantr/cli init --blueprint=agent-marketplace --yes
18
+ ```
19
+
20
+ ## What It Does
21
+
22
+ - scaffolds Decantr projects from blueprints, archetypes, or prompts
23
+ - generates execution-pack context files for AI coding assistants
24
+ - audits projects against Decantr contracts
25
+ - searches the registry and showcase benchmark corpus
26
+ - validates, refreshes, and maintains `decantr.essence.json`
27
+
28
+ ## Common Commands
29
+
30
+ ```bash
31
+ decantr init --blueprint=agent-marketplace
32
+ decantr magic "AI-native analytics workspace"
33
+ decantr audit
34
+ decantr check
35
+ decantr registry summary --namespace @official --json
36
+ decantr showcase verification --json
37
+ ```
38
+
39
+ Offline blueprint scaffolding expects a real local content source:
40
+
41
+ ```bash
42
+ DECANTR_CONTENT_DIR=/path/to/decantr-content decantr init --blueprint=agent-marketplace --offline --yes
43
+ ```
44
+
45
+ If a requested offline blueprint, archetype, or theme cannot be resolved from local cache/custom content or `DECANTR_CONTENT_DIR`, the CLI now stops explicitly instead of silently falling back to the default scaffold.
46
+
47
+ ## Generated Context
48
+
49
+ Scaffolded projects include compiled execution packs under `.decantr/context/`, including:
50
+
51
+ - `scaffold-pack.md` / `scaffold-pack.json`
52
+ - `section-*-pack.md` / `section-*-pack.json`
53
+ - `page-*-pack.md` / `page-*-pack.json`
54
+ - `review-pack.md` / `review-pack.json`
55
+ - `pack-manifest.json`
56
+
57
+ Those files are the compact task contracts meant for AI assistants and downstream tooling.
58
+
59
+ Recommended read order for AI-assisted scaffolding:
60
+
61
+ 1. `DECANTR.md` for the design spec, CSS approach, and guard rules
62
+ 2. `.decantr/context/scaffold-pack.md` as the primary compiled shell, theme, feature, and route contract
63
+ 3. `.decantr/context/scaffold.md` as the broader app overview and topology guide
64
+ 4. matching `section-*-pack.md` and `section-*.md` files before section work
65
+ 5. matching `page-*-pack.md` files before route work
66
+
67
+ Treat the compiled execution packs as the source of truth. Use the narrative docs as secondary explanation, start with the shell and route structure first, and run `decantr check` plus `decantr audit` after implementation.
68
+
69
+ For cold-start harness or certification runs, use only the scaffolded workspace files as the contract. If local scaffold files disagree, stop and report the mismatch rather than relying on repo-global Decantr assumptions.
70
+
71
+ ## Related Packages
72
+
73
+ - `@decantr/essence-spec` for schema and guard validation
74
+ - `@decantr/registry` for registry contracts and API access
75
+ - `@decantr/verifier` for audit and critique
76
+
77
+ ## Docs
78
+
79
+ - [Decantr root README](https://github.com/decantr-ai/decantr/blob/main/README.md)
80
+ - [Package support matrix](https://github.com/decantr-ai/decantr/blob/main/docs/reference/package-support-matrix.md)
81
+
82
+ ## License
83
+
84
+ MIT
package/dist/bin.js CHANGED
@@ -1,3 +1,4 @@
1
1
  #!/usr/bin/env node
2
- import "./chunk-Y5C2O7Z7.js";
3
- import "./chunk-XKXUVNUQ.js";
2
+ import "./chunk-KAEQTVAM.js";
3
+ import "./chunk-H4H3IQJK.js";
4
+ import "./chunk-KUDAVJOR.js";