@hunt-labs/bytekit-cli 0.9.1 → 0.9.2

package/CHANGELOG.md

@@ -10,6 +10,21 @@ today, see [README.md](./README.md), which remains the authoritative usage guide
 
 ## [Unreleased]
 
+## [0.9.2] - 2026-08-31
+
+### Changed
+
+- Corrected the `detailValueText` doc comment in `src/output.ts`, which claimed the object arm of
+  the `details` renderer carried the SAME depth bound as the array arm through `detailJson`
+  (#3691). It carries the same **constant** (`DETAIL_MAX_DEPTH`), not the same **counter**:
+  `detailJson` takes no depth argument and starts a fresh budget from its own replacer chain. The
+  comment now records the two consequences — the arms agree level-for-level only on homogeneous
+  chains, and a mixed array/object chain can render up to `2 × DETAIL_MAX_DEPTH` levels — and why
+  threading `depth` into `detailJson` is not the fix: it would elide shapes that render today,
+  breaking the byte-identical inverse-case contract #3647 shipped under. **No consumer-visible
+  change** — this release touches one comment, and every `details` shape renders byte-identically
+  to 0.9.1.
+
 ## [0.9.1] - 2026-08-27
 
 ### Fixed

package/dist/output.js

@@ -439,8 +439,18 @@ function isDetailRecord(value) {
  * longer than the value it names.
  *
  * `depth` counts array levels already descended and is bounded by {@link DETAIL_MAX_DEPTH} (#3633);
- * the object arm carries the SAME bound through {@link detailJson} (#3647), and every remaining arm
- * terminates on its own.
+ * the object arm reuses the same CONSTANT through {@link detailJson} (#3647) but spends its OWN
+ * INDEPENDENT budget, counted from that call, and every remaining arm terminates on its own.
+ *
+ * Two budgets, not one, so: the arms agree level-for-level only on HOMOGENEOUS chains — an object
+ * sitting at array-depth 8 is not elided, while an array sitting at object-depth 8 is — and a mixed
+ * array/object chain can render up to `2 × DETAIL_MAX_DEPTH` nesting levels rather than
+ * `DETAIL_MAX_DEPTH`.
+ *
+ * Threading `depth` into {@link detailJson} is NOT the fix. It elides shapes that render today
+ * (measured across a 101-case corpus: 15 cases change instead of 10), which breaks the
+ * byte-identical inverse-case contract #3647 shipped under. Stack safety does not need it either:
+ * the array arm never resumes below an object, so the total descent is bounded at 8 + 8.
  */
 function detailValueText(value, depth = 0) {
     if (typeof value === 'string')

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hunt-labs/bytekit-cli",
-  "version": "0.9.1",
+  "version": "0.9.2",
   "description": "ByteKit CLI — wraps @hunt-labs/bytekit-sdk as shell subcommands",
   "license": "MIT",
   "type": "module",