Version Packages

examples/llm-memory-db-mssql/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @noormdev/example-llm-memory-db-mssql
 
+## 0.0.6
+
+### Patch Changes
+
+- @noormdev/sdk@1.3.0
+
 ## 0.0.5
 
 ### Patch Changes

examples/llm-memory-db-mssql/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@noormdev/example-llm-memory-db-mssql",
-    "version": "0.0.5",
+    "version": "0.0.6",
     "private": true,
     "type": "module",
     "description": "LLM-memory schema + SDK example exercising NoORM against MSSQL with TVPs",

examples/llm-memory-db-pg/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @noormdev/example-llm-memory-db-pg
 
+## 0.0.6
+
+### Patch Changes
+
+- @noormdev/sdk@1.3.0
+
 ## 0.0.5
 
 ### Patch Changes

examples/llm-memory-db-pg/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@noormdev/example-llm-memory-db-pg",
-    "version": "0.0.5",
+    "version": "0.0.6",
     "private": true,
     "type": "module",
     "description": "Full-surface noorm example: LLM memory + task tracker schema, SDK, and tests against PostgreSQL",

examples/todo-db/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @noormdev/example-todo-db
 
+## 0.0.6
+
+### Patch Changes
+
+- @noormdev/sdk@1.3.0
+
 ## 0.0.5
 
 ### Patch Changes

examples/todo-db/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@noormdev/example-todo-db",
-    "version": "0.0.5",
+    "version": "0.0.6",
     "private": true,
     "type": "module",
     "description": "SDK integration tests exercising the todo-db example schema",

packages/cli/CHANGELOG.md

@@ -1,5 +1,68 @@
 # @noormdev/cli
 
+## 1.3.0
+
+### Minor Changes
+
+- 4c0e7c1: Make the execution history and file-execution screens scroll, and let a failed
+  file's error be read in full.
+
+  Both screens drew a fixed window — `slice(0, 15)` of the history, `slice(0, 20)`
+  of the files — while their selection cursor ranged over every record. Past that
+  window the arrow keys still moved a selection that was not on screen, and the
+  detail box under the list described a record the reader could not see, so the
+  screens were not merely unscrollable: they were reporting on rows that had
+  scrolled out from under the cursor. Both now use `SelectList`, which owns the
+  cursor and the window together and sizes itself from the terminal, so what is
+  selected is always drawn and a tall terminal shows more rows rather than the same
+  fifteen. The history list also fetches 200 records instead of 50, now that
+  reaching past the fifteenth is possible.
+
+  A failed file's error message was rendered as one line per `\n`, with no bound.
+  A stack trace therefore pushed the file list, the detail box and the hotkey hints
+  off the bottom together — and on the history screen the same message was cut at
+  80 characters instead, which drops the part that names the constraint or the
+  syntax error. Both screens now show a bounded single line in the detail box and
+  open the whole message, wrapped and scrollable, on a keypress: `e` on the history
+  screen, Enter on a file execution.
+
+  `SelectList` gains an optional `renderItem`, which lets a screen draw its own row
+  body while the list keeps the cursor, the window, the scroll indicators, focus and
+  the mouse. Without it these two screens would have had to give up the per-status
+  colour a reader scans a history list for, which is why they had their own list in
+  the first place.
+
+- 37abd22: Make `run inspect` scrollable, and show secrets partially rather than as a count.
+
+  The inspect screen rendered its context as a nested tree that grew with the
+  project, and Ink has no scroll offset — so on any real template the bottom of
+  the view sat below the fold with no key that could reach it, and the screen's
+  own footer was what got pushed off to make room. Every view it offers (summary,
+  expanded, rendered SQL, and render errors) is now a flat list of one element per
+  visual line behind a viewport, scrolled with the same `↑↓` / `^U` / `^D` keys the
+  explore and SQL screens already use.
+
+  `$.secrets` and `$.globalSecrets` reported a key count, which cannot answer the
+  question the screen is opened to answer: a stale password and a fresh one are
+  both `Object (7 keys)`. Both tiers now show a partial reveal that narrows as the
+  value gets shorter — a four-character value shows nothing, a long one shows two
+  characters and a four-character suffix — with the length beside it as a number,
+  so a value that is set but empty is distinguishable from one that is set wrong.
+  `$.env` is listed and masked on the same terms, because it is the whole of
+  `process.env` and nothing in the screen can tell which of its keys are
+  credentials.
+
+  The mouse wheel now scrolls every viewport, which it never did. Only `SelectList`
+  and `ResultTable` consumed wheel notches, so the explore detail view, the
+  full-text overlay and the row viewer ignored them — and because the TUI runs in
+  the alternate screen, which has no scrollback, and mouse tracking intercepts the
+  notches a terminal would otherwise translate into arrow keys, turning the mouse
+  on had actually removed the only wheel behaviour those panes had.
+
+  Also fixes an error path that could never render: a template whose helper failed
+  to load set the screen's error phase with a file selected, which no branch
+  matched, so the most likely failure showed as "Unknown phase".
+
 ## 1.2.0
 
 ### Minor Changes

packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noormdev/cli",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "Database schema & changeset manager CLI",
   "type": "module",
   "bin": {

packages/sdk/CHANGELOG.md

@@ -1,5 +1,7 @@
 # @noormdev/sdk
 
+## 1.3.0
+
 ## 1.2.0
 
 ### Minor Changes

packages/sdk/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noormdev/sdk",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "Database schema & changeset manager SDK",
   "type": "module",
   "main": "./dist/index.js",