@intentius/behold 0.6.0 → 0.8.0

package/AGENTS.md

@@ -17,7 +17,7 @@ apply creds.
 ## Getting a server
 
 ```sh
-npx @intentius/behold serve <chant-project-dir> --port 4600   # or: preview / demo
+npx @intentius/behold serve <chant-project-dir> --port 4600   # or: preview / demo / doctor
 ```
 
 `behold demo` needs no project at all — it copies the bundled example and serves
@@ -28,7 +28,14 @@ graph.
 ## The read loop
 
 0. **discover** — GET `/api` lists every route with a one-line description,
-   plus the server's version and a link back to this guide.
+   plus the server's version and a link back to this guide. Before the server
+   exists (or when a route answers with an error you'd have to guess at), run
+   `npx @intentius/behold doctor <dir> --json`: a read-only diagnosis of the
+   project's kind, its own chant install and version, declared lexicons, the
+   envs the picker will infer, the bound kube context versus the ambient one,
+   substrate readiness and committed Ops. Each check is
+   `{name, status: pass|warn|fail, detail, fix}`; the process exits non-zero
+   iff something failed. It starts no server and changes nothing.
 1. **observe** — GET `/api/graph` (JSON: `{ ir, svg, meta }`). The mixed graph
    of the project, every node with `id`/`kind`/`lexicon`/`attrs`/`sourceLoc`. Drift
    status, when present, is `attrs._status` (`good`=managed, `warn`=foreign,

package/README.md

@@ -30,17 +30,27 @@ npx @intentius/behold demo            # copies the example to ./behold-demo, ins
 The copied project is yours: edit its source and watch the graph change live.
 There's a whole catalog — `behold demo --list` names the rest (`behold demo
 k8s` stands the same loop up on a throwaway k3d cluster: runtime Pods, field
-ownership). Every loaded demo lands in the panel's recents, so switching
-between them is the Scope tab.
+ownership; `behold demo argo-estate` needs nothing at all — a three-project
+Argo CD estate, declared only, so it runs where Docker doesn't). Every loaded
+demo lands in the panel's recents, so switching between them is the Scope tab.
 
 Already have a chant project?
 
 ```sh
 cd my-chant-project
+npx @intentius/behold doctor          # will this project serve well? (read-only)
 npx @intentius/behold preview         # → http://localhost:4600, this project's graph
 npx @intentius/behold serve . --env prod --poll 30   # live drift overlay
 ```
 
+`behold doctor` is the first thing to run on a project behold hasn't seen: one
+line each for the project's kind, its own chant install and version, declared
+lexicons, the envs the picker will infer, the kube context chant binds versus
+your ambient one, substrate readiness and committed Ops — pass/warn/fail with
+a one-line fix. It starts nothing and changes nothing; it exits non-zero only
+when something would actually stop behold serving the project well, so CI can
+gate on it. `--json` for scripts and agents.
+
 Driving it from an agent or script? `GET /api` lists every JSON route;
 [AGENTS.md](./AGENTS.md) (shipped in the package) is the read/act contract.
 

package/demos.json

@@ -26,6 +26,14 @@
       "setup": "bash scripts/estate-up.sh",
       "serve": { "env": "local", "dirs": ["control-plane", "app-a", "app-b"] }
     },
+    {
+      "name": "argo-estate",
+      "description": "The Argo CD mirror of flux-estate, declared only: an AppProject plus one Application per app project, served with the two apps as one composed estate — project edges from each Application to the AppProject it names, and each Application's destination namespace drawn as a box holding that app's objects. No cluster, no Argo install, no Docker.",
+      "source": "bundled",
+      "dir": "example-argo-estate",
+      "requires": [],
+      "serve": { "dirs": ["control-plane", "app-a", "app-b"] }
+    },
     {
       "name": "fountain",
       "description": "The mature estate: self-hosted fountain (a real app) on a throwaway k3d cluster — tiers (try the ha tier picker), seams, drift, runtime Pods. Clones INTENTIUS/fountain-ops; ~5 minutes, mostly image pulls. `just down` in the clone removes the cluster.",