@cowliss/cli 0.9.0 → 0.10.0

package/dist/index.js

@@ -3170,8 +3170,15 @@ const insertAppSchema = createInsertSchema(apps$1);
 const bytea = customType({ dataType: () => "bytea" });
 /**
 * What an artifact is: a journey or template bundle as `cow build` emitted
-* it, the wasm module the server compiled from it, or the gzipped source
-* tarball of the repo the push was built from.
+* it, or the gzipped source tarball of the repo the push was built from.
+*
+* `module` is still a value of the Postgres enum and no longer a value here
+* (ticket 22/05). Compiled modules are not stored: a module is a
+* deterministic function of its bundle, so the rows were Postgres caching
+* what the sandbox's own disk cache already holds, at about 2MB each of
+* which 1.34MB is the QuickJS engine Javy links into every one. Dropping
+* the enum value itself would mean recreating the type and rewriting the
+* column, for a label nothing writes.
 */
 const artifactKindEnum = pgEnum("artifact_kind", [
 	"bundle",
@@ -4395,10 +4402,16 @@ const versionStatusEnum = pgEnum("version_status", [
 * use; an execution pins the journey version it started on for its whole
 * life (ADR 0004).
 *
-* `moduleDigest` is the content address and is null until the compile
-* settles: a version that never compiled has no module to be addressed by,
-* and Postgres leaves nulls out of the unique index, so a key that fails to
-* compile twice records both failures.
+* The content address is the manifest's `bundle`, which is what the
+* developer actually pushed. `moduleDigest` is a derived compile result,
+* null until the compile settles and rewritable afterwards: the toolchain
+* that produced it is ours, not the tenant's, so bumping Javy is a
+* background recompile rather than a new version in a customer's history
+* (ADR 0011, amended 2026-09-19).
+*
+* The uniqueness that follows is "one ready version per key per bundle": a
+* key whose bundle does not compile records every attempt, and the next
+* push of that bundle is a retry rather than a duplicate.
 *
 * `pushedAt` is the ordering key rather than a creation stamp, because an
 * unchanged key gets no new version: a push that re-sends bytes a version
@@ -4430,7 +4443,7 @@ const versions$1 = pgTable("versions", {
 	}),
 	error: text("error")
 }, (table) => [
-	uniqueIndex("versions_org_id_kind_key_module_digest_unique").on(table.orgId, table.kind, table.key, table.moduleDigest),
+	uniqueIndex("versions_org_id_kind_key_bundle_unique").on(table.orgId, table.kind, table.key, sql`(${table.manifest}->>'bundle')`).where(sql`${table.status} = 'ready'`),
 	index("versions_org_id_kind_key_pushed_at_idx").on(table.orgId, table.kind, table.key, table.pushedAt),
 	index("versions_org_id_push_id_idx").on(table.orgId, table.pushId),
 	foreignKey({
@@ -6343,15 +6356,23 @@ const versionSchema = selectVersionSchema.extend({
 * version" column shows (the short digest, when it was pushed, whether it
 * compiled) and the push its source archive lives on. The manifest entry is
 * left out, because a journey row already carries what its own entry says.
+*
+* `bundle` is lifted out of that entry because it is the version's address:
+* it is there from the moment the push lands, and it does not move when a
+* recompile rewrites `moduleDigest` (ADR 0011, amended 2026-09-19). The
+* compiled module's digest is not on the wire at all; nothing outside the
+* sandbox has a use for it.
 */
 const versionSummarySchema = selectVersionSchema.pick({
 	id: true,
 	status: true,
-	moduleDigest: true,
 	pushId: true,
 	appId: true,
 	error: true
-}).extend({ pushedAt: z.iso.datetime() });
+}).extend({
+	pushedAt: z.iso.datetime(),
+	bundle: digestSchema
+});
 /**
 * A push as the API reports it, with the versions it created: `cow push`
 * returns as soon as the upload is stored, so what is compiling, what is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cowliss/cli",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "type": "module",
   "bin": {
     "cow": "./dist/index.js"