@calcit/procs 0.13.28 → 0.13.29

package/editing-history/20260820-1704-repository-maintenance-review.md

@@ -16,5 +16,6 @@
   consolidated even within the normal current-development window.
 
 Validation: `yarn compile`, `cargo clippy --all-targets -- -D warnings`,
-`cargo test -q`, `yarn check-agent-interface`, and `cr docs check-md` over
-every Markdown file with `--entry calcit/test.cirru`.
+`cargo test -q`, `yarn check-agent-interface`,
+`cr docs check-md README.md --entry calcit/test.cirru`, and
+`./scripts/check-docs-md.sh calcit/test.cirru` for the Markdown under `docs/`.

package/editing-history/202608212200-review-followups.md

@@ -0,0 +1,11 @@
+# Review follow-ups from recent PRs
+
+- Preserved unresolved type-slot occurrences while applying intentional
+  Dynamic and JS FFI intents through nested annotations.
+- Corrected the maintenance record's Markdown validation commands and restored
+  ascending order for the 0.12.58 and 0.12.59 archive entries.
+- Documented the local `git diff` trade-off of the `.gitattributes` `-diff`
+  attribute for generated quality baselines.
+
+Validation: `cargo fmt --check`, targeted type-coverage tests, and the required
+repository checks after the follow-up changes.

package/editing-history/202608212232-unsafe-coerce-inventory.md

@@ -0,0 +1,25 @@
+# Unsafe-coerce inventory
+
+## Summary
+
+- Extended `calcit analyze weak-types` with the closed `unsafe-coerce` kind and
+  the `explicit-unsafe` intent.
+- Every executable assertion now reports its exact `code@...` Snapshot path and
+  declared target schema, without classifying it as unresolved Dynamic debt.
+- Bumped the JSON protocol to v4 and added `W_JS_FFI_UNCHECKED_COERCE` so
+  tooling can turn the inventory into a runtime-contract test checklist.
+- Kept the existing eight-metric `analyze quality` baseline stable; the new
+  inventory is deliberately visible but not budgeted until a versioned baseline
+  migration is introduced.
+
+## Validation
+
+- `cargo fmt`
+- `cargo clippy -- -D warnings`
+- `cargo test`
+- `yarn compile`
+- `yarn check-agent-interface` (13/13 scenarios)
+- `yarn check-all`
+- New debug CLI against `../respo-calcit-workflow/calcit.cirru` with
+  `analyze weak-types --only unsafe-coerce --format json --summary-only`
+  (4 inventory hits, JSON protocol v4)

package/editing-history/202608212243-unsafe-coerce-boundary-evidence.md

@@ -0,0 +1,27 @@
+# Unsafe-coerce boundary evidence
+
+## Summary
+
+- Extended the `unsafe-coerce` inventory with an explicit static `evidence`
+  object: input source form, target schema, declared `:js-ffi` capability, and
+  `js-ffi.raw.*` adapter-namespace convention.
+- Kept the evidence honest: it describes Snapshot source only and never claims
+  to have observed or validated a JavaScript runtime value.
+- Bumped `analyze.weak-types` JSON protocol to v5 and added tests for raw JS,
+  host-member, ordinary-expression, and adapter namespace classification.
+- Applied #378 review feedback before merging this follow-up: quoted and
+  quasiquoted descendants no longer create unsafe inventory debt, while `~` /
+  `~@` expressions remain executable; unsafe diagnostics now describe generic
+  runtime values rather than assuming every assertion is JavaScript-backed.
+
+## Validation
+
+- `cargo fmt`
+- `cargo clippy -- -D warnings`
+- `cargo test`
+- `yarn compile`
+- `yarn check-agent-interface` (13/13 scenarios)
+- `yarn check-all`
+- New debug CLI against `../respo-calcit-workflow/calcit.cirru`; it surfaced
+  four assertions and accurately identifies two definitions without a declared
+  `:js-ffi` capability.

package/editing-history/202608212305-quality-unsafe-boundary-gate.md

@@ -0,0 +1,13 @@
+# Quality baseline v2: explicit unsafe boundary budget
+
+- `analyze quality` now collects explicit `unsafe-coerce` occurrences as the
+  independent `unsafeCoerce` metric instead of folding them into Dynamic debt.
+- Newly written native baseline files use schema version 2 and preserve the
+  metric per definition, so an adapter moved to another definition cannot hide
+  a regression.
+- Native v1 and legacy flat eight-metric baselines remain readable and retain
+  their original enforcement. Maintainers must review and regenerate a v2
+  baseline before the new metric becomes a gate.
+- Static quality only counts visible assertions. It does not claim that a
+  Node/browser runtime contract test has executed; those remain an explicit Q3
+  requirement.

package/editing-history/202608212327-quality-agent-protocol-v2.md

@@ -0,0 +1,7 @@
+# Quality agent protocol v2 assertion
+
+- The Agent CLI smoke check now expects `analyze.quality` protocol v2 and
+  asserts that the newly versioned `unsafeCoerce` metric is present.
+- This keeps the development-process check aligned with the public JSON
+  contract, preventing a future accidental downgrade or silent omission of the
+  new boundary budget.

package/editing-history/202608212330-release-asset-manifest.md

@@ -0,0 +1,9 @@
+# Versioned release asset manifest
+
+- The release workflow now publishes `calcit-release-manifest.json` alongside
+  `calcit`, `caps`, and `cr-wasm`.
+- Manifest schema v1 records release version, filename, byte size, and SHA-256
+  for each asset. Setup tooling can verify a downloaded binary before adding it
+  to `PATH`, without trusting a successful HTTP response alone.
+- The generator uses Node standard-library APIs and has a focused fixture test
+  so the release file remains deterministic and machine-readable.

package/editing-history/202608212334-quality-v1-reporting.md

@@ -0,0 +1,10 @@
+# Honest v1 quality-baseline reporting
+
+- Native quality baseline v1 intentionally lacks the later `unsafeCoerce`
+  budget. It still enforces its original eight metrics.
+- The report now labels this mode `native-baseline-v1` and normalizes the
+  unenforced metric to the current count, preventing a positive delta from
+  being mistaken for a rejected regression.
+- This supports staged ecosystem upgrades: old released CLIs can keep their
+  accepted baseline while a reviewed v2 migration starts enforcing explicit
+  host-boundary inventory.

package/editing-history/202608212344-quality-metric-name-comparison.md

@@ -0,0 +1,5 @@
+# Quality metric name comparison
+
+The static-quality gate compares each metric to its limit by its stable wire name,
+rather than relying on the parallel ordering of two metric arrays. This keeps new
+or reordered metrics from silently being compared with a different budget.

package/editing-history/202608212345-release-manifest-review.md

@@ -0,0 +1,6 @@
+# Release manifest review follow-up
+
+The release-manifest helper now emits a single-line usage error instead of a
+stack trace. The publishing workflow passes the release tag through an
+environment variable, preventing release metadata from being interpolated into
+shell source.

package/editing-history/202608212346-quality-baseline-migration-docs.md

@@ -0,0 +1,5 @@
+# Quality baseline migration wording
+
+The upgrade guide now states that `unsafe-coerce` occurrence comparison applies
+to native v2 or regenerated quality baselines only. Existing native v1 and
+flat baselines retain their eight-metric compatibility behavior.

package/editing-history/202608220012-release-0-13-29.md

@@ -0,0 +1,5 @@
+# Release 0.13.29
+
+This release ships the static-quality unsafe-boundary gate, JS FFI contract
+workflow improvements, and the release asset manifest consumed by
+setup-calcit 1.3.0. Cargo and npm package versions advance together.

package/editing-history/ARCHIVE.md

@@ -26,13 +26,13 @@ Git history.
 | 0.12.55 | Semantic snapshot entry descriptions and canonical symbol storage for entry functions. |
 | 0.12.56 | Routine version bump after snapshot/entry work. |
 | 0.12.57 | CLI mutation, atomic staging, test deduplication (PR #284) plus Windows staged-file synchronization fixes. |
+| 0.12.58 | Receiver-first method inference and nominal trait identity fixes. |
+| 0.12.59 | Top-level nominal value schema fix. |
 | 0.13.0 | Concentrated breaking-change baseline for the Option/Result/Unit/JsNullish public contracts. |
 | 0.13.1 | Fixed recursive expansion of self-referential nominal struct type annotations. |
 | 0.13.2 | Struct/enum data model cleanup (PR #301), direct required Struct field access, symbol-based nominal formatting. |
 | 0.13.3 | Struct/Enum terminology migration, deprecated API analysis, cross-backend canonical EDN formatting. |
 | 0.13.4 | Typed host FFI (external-object traits) merged and released. |
-| 0.12.58 | Receiver-first method inference and nominal trait identity fixes. |
-| 0.12.59 | Top-level nominal value schema fix. |
 | 0.13.5 | Typed `js-get` / `js-set` field access plus named-type preservation. |
 | 0.13.6 | Opt-in raw-JS-FFI warning and readable low-cost JS emission. |
 | 0.13.7 | Definition-attached core tests and safer, less noisy `cr` edits. |

package/lib/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@calcit/procs",
-    "version": "0.13.28",
+    "version": "0.13.29",
     "main": "./lib/calcit.procs.mjs",
     "devDependencies": {
         "@types/node": "^25.7.0",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@calcit/procs",
-  "version": "0.13.28",
+  "version": "0.13.29",
   "main": "./lib/calcit.procs.mjs",
   "devDependencies": {
     "@types/node": "^25.7.0",