@tridha643/hestia 1.2.0 → 1.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tridha643/hestia",
-  "version": "1.2.0",
+  "version": "1.3.1",
   "description": "Per-worktree isolated development stacks for humans and coding agents",
   "repository": {
     "type": "git",

package/skills/hestia/SKILL.md

@@ -46,6 +46,16 @@ at `~/.hestia/repositories/<repoId>.toml`, optional committed `hestia.toml`,
 then automatic discovery. Conflicts fail rather than silently overriding a
 workload source. `.hestia/` must remain ignored.
 
+Configured proc and Wrangler workloads may declare environment values. Literal
+`${endpoint:<alias>.host}`, `${endpoint:<alias>.port}`, and
+`${endpoint:<alias>.url}` references resolve only after the producing workload
+is ready, while `{port}` resolves to the receiving process's own assigned
+port. A value shaped as `{ file = ".hestia/..." }` reads ignored local
+material into memory; Hestia refuses file inputs outside `.hestia/` and never
+persists their contents. Use `cwd` to select a package-local `.env.schema`,
+`varlock = true` to compose that package's resolver, and `health_path` when
+port ownership alone doesn't prove that the application compiled successfully.
+
 ## Run and consume structured endpoints
 
 ```bash
@@ -240,7 +250,8 @@ JSON/NDJSON commands.
 Run `down` before switching or deleting the branch. After deletion, use the
 recorded project with `hestia down --project <project>`. Docker workloads
 cannot be stopped individually (`backend-not-stoppable`); proc/Wrangler
-workloads can. Named volumes are retained unless `--destroy` is explicit.
+workloads can. Named volumes and project-built images are retained unless
+`--destroy` is explicit (it adds `-v --rmi local`; shared base images stay).
 
 ## Stable error remedies