@effected/app 0.1.2 → 0.1.4

package/README.md

@@ -27,7 +27,7 @@ The other half is the namespace itself. An application names it for its director
 
 This package is the composition that gets both right, and that is all it is. It owns **no domain logic**: no service, no schema, no error class, and it re-exports nothing. The entire surface is layer factories, one config preset and one type alias. If a change here wants a `Context.Service`, that is the signal the change belongs in one of the three packages beneath it.
 
-**Nothing may depend on `@effected/app`.** A library taking an application control plane as a dependency would drag a SQLite driver into its own consumers' trees. This is the package an application composes at its edge — and the only one in the kit whose docs show where OpenTelemetry goes.
+**No library or package may depend on `@effected/app`** — but the application at the top of the graph is exactly its intended consumer. A library taking an application control plane as a dependency would drag a SQLite driver into its own consumers' trees. This is the package an application composes at its edge — and the only one in the kit whose docs show where OpenTelemetry goes.
 
 ## Install
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/app",
-	"version": "0.1.2",
+	"version": "0.1.4",
 	"private": false,
 	"description": "The application control plane for Effect: one layer wiring XDG-namespaced directories, a migrated SQLite store, a TTL cache and a config file to the same place.",
 	"keywords": [
@@ -38,9 +38,9 @@
 		"./package.json": "./package.json"
 	},
 	"peerDependencies": {
-		"@effected/config-file": "0.1.1",
+		"@effected/config-file": "0.1.3",
 		"@effected/store": "0.1.0",
-		"@effected/xdg": "0.1.1",
+		"@effected/xdg": "0.1.3",
 		"effect": "4.0.0-beta.98"
 	},
 	"engines": {