@decantr/cli - npm Package Compare versions

Comparing version

3.11.2

3.11.3

+2

-2

package.json

		@@ -14,3 +14,3 @@ {
		"@decantr/telemetry": "3.8.1",
		"@decantr/verifier": "3.11.2",
		"@decantr/verifier": "3.11.3",
		"ajv": "^8.20.0"
		@@ -66,3 +66,3 @@ },
		"type": "module",
		"version": "3.11.2"
		"version": "3.11.3"
		}

+4

-4

README.md

		@@ -10,3 +10,3 @@ # @decantr/cli

		The current stable version is Decantr 3.11.2. Bare `decantr verify` is now zero-write Changed-UI Assurance: it scopes the current Git change, auto-selects one changed UI app when provable, and reports at most three source-anchored findings. It is not quantitatively adoption-proven.
		The current stable version is Decantr 3.11.3. Bare `decantr verify` is zero-write Changed-UI Assurance: it scopes the current Git change, auto-selects one changed UI app when provable, and reports at most three source-anchored findings. SvelteKit task context keeps `+page.svelte` as the implementation and page-data modules as supporting authority. The release is not quantitatively adoption-proven.

		@@ -24,4 +24,4 @@ The zero-setup entry point is `verify`. The deeper CLI loop remains Observe -> Prepare -> Verify -> Report through `scan`, `task <target>`, `verify --full`, and `ci`. Routes are one UI surface among layouts, components, stories, overlays, flows, packages, runtime states, and exact files. Shipped behavior must not be presented as evidence that Decantr improves frontier models; that remains a separate research question.
		```bash
		npx @decantr/cli@3.11.2 verify
		npx @decantr/cli@3.11.2 scan
		npx @decantr/cli@3.11.3 verify
		npx @decantr/cli@3.11.3 scan
		npx @decantr/cli new my-app --blueprint=esports-hq
		@@ -119,3 +119,3 @@ ```

		Published 3.10.0 `decantr scan` is look-don't-touch reconnaissance for selected-app scope, independent authority axes, taskable routes and surfaces, components, styling, typed graph readiness, and limitations. Authored framework route sources remain the implementation authority. TanStack generated metadata may corroborate public paths without becoming an edit target; Astro content pages are separated from response endpoints; Angular scans begin at the selected production bootstrap/router graph and carry resolved external component resources into task context. Inferred or unresolved route evidence is withheld from governed route maps. Attached Essence V4 apps may derive graph previews in memory while scan still writes nothing.
		Published 3.10.0 `decantr scan` is look-don't-touch reconnaissance for selected-app scope, independent authority axes, taskable routes and surfaces, components, styling, typed graph readiness, and limitations. Authored framework route sources remain the implementation authority. TanStack generated metadata may corroborate public paths without becoming an edit target; Astro content pages are separated from response endpoints; SvelteKit `+page.svelte` files remain taskable while colocated page-data modules are supporting authority; Angular scans begin at the selected production bootstrap/router graph and carry resolved external component resources into task context. Inferred or unresolved route evidence is withheld from governed route maps. Attached Essence V4 apps may derive graph previews in memory while scan still writes nothing.

		@@ -122,0 +122,0 @@ Scan separates UI-surface authority, topology, taskability, component-inventory, styling-authority, runtime-evidence, and source-scope axes. It keeps tests, stories, fixtures, mocks, generated files, build output, packages, and sibling apps separate from production authority.

@decantr/cli - npm Package Compare versions

Improved metrics

Dependency changes