getculpa 1.0.9 → 1.1.0

package/assets/culpa-compose.yml

@@ -1,146 +1,161 @@
-# Culpa — release compose file shipped inside the installers (T-087/T-088).
-# Net effect is identical to running the stack from the repository:
-# same services, same container names, same ports, same privacy default.
-# Images are pulled from ghcr.io; a locally built/tagged image with the same
-# name is used when present, which is how these pins were verified before
-# publication.
-#
-# ── RELEASE STATE: v1.0.9 PUBLISHED AND SIGNED (2026-09-03) ─────────
-# The line above is REWRITTEN BY installers/publish.sh at real-publish time —
-# this file has shipped a hand-edited, wrong publication claim twice, so the
-# claim is now mechanical, never prose. While it reads NOT PUBLISHED, the pins
-# below resolve only against locally built images and this file must not be
-# distributed. v0.11.0 is the CF9-CF12 round (UI alignment fixes, forecast
-# uncertainty-calibration repair + kappa bound + cohort/centring explain,
-# cache coverage flags, relay-mesh W1/W2c groundwork — feature-gated out of
-# shipped binaries) on top of v0.10.0, the CF7/CF8 round (forecast P50-anchor + cache
-# counterfactual math repair, founder UI list U-1..U-8 + P-1, founder
-# palette + card "i" tooltips, native CLI auto-update Option A, QW-1..4
-# container-upgrade guards, CodeRabbit PR#13 triage) on top of v0.9.0.
-# The relay and license-server carry NO changes since v0.9.0 and keep
-# their v0.9.0 images — a version is only claimed where a real diff
-# exists. A signed tag is never rebuilt (D-072), so new contents mean a
-# new version.
-#
-# Once the state line reads PUBLISHED AND SIGNED, verify before you run:
-#   cosign verify \
-#     --certificate-identity 'info@myaigi.ai' \
-#     --certificate-oidc-issuer 'https://github.com/login/oauth' \
-#     ghcr.io/myaigidev/culpa-server:v1.0.9
-# Repeat for culpa-dashboard. Both must report VERIFIED.
-#
-# If a pull fails with an authentication or "denied" error rather than a
-# missing manifest, the package has not been made public yet — the images
-# exist. Check with:
-#   gh api user/packages/container/culpa-server --jq .visibility
-# Do NOT use `docker manifest inspect` with an emptied DOCKER_CONFIG to test
-# this: on Docker Desktop for Windows the daemon authenticates through its own
-# credential store, so that check reports a false PUBLIC.
-
-services:
-  db:
-    image: postgres:16-alpine
-    container_name: culpa-db
-    environment:
-      POSTGRES_USER: culpa
-      POSTGRES_PASSWORD: culpa
-      POSTGRES_DB: culpa
-    volumes:
-      - culpa_pgdata:/var/lib/postgresql/data
-    healthcheck:
-      test: ["CMD-SHELL", "pg_isready -U culpa -d culpa"]
-      interval: 2s
-      timeout: 2s
-      retries: 30
-    restart: unless-stopped
-
-  server:
-    image: ghcr.io/myaigidev/culpa-server:v1.0.9
-    container_name: culpa-server
-    environment:
-      DATABASE_URL: postgres://culpa:culpa@db:5432/culpa
-      # full forensic capture is the default (A5); set metadata-only to opt out
-      # CF24-T1 (S2): the server binds 127.0.0.1 by DEFAULT
-      # (native/culpa-api/src/bind.rs — the binary the image actually runs).
-      # Inside a container that is unreachable through the published port, so
-      # containers must say 0.0.0.0 explicitly. The host-side `ports:` mapping
-      # below binds 127.0.0.1, so nothing OFF THIS MACHINE can reach it —
-      # reachable-by-design is always an operator's written choice, never a
-      # default.
-      #
-      # Say precisely what that does and does not cover (CF25, CodeRabbit
-      # PR #18): the `ports:` mapping governs HOST exposure only. Because the
-      # listener inside the container is 0.0.0.0, any other container attached
-      # to this Compose network reaches the server directly on 4545, without
-      # traversing the published port at all. That is ordinary Docker
-      # networking and it is fine for the services defined here — but adding a
-      # container to this network grants it API access, and the port mapping
-      # will not stop it.
-      CULPA_API_BIND: "0.0.0.0"
-      CULPA_PRIVACY_MODE: full
-      # T-120: the machine secret encrypting the customer key at rest lives
-      # here as a file — a VOLUME, so it survives container recreation
-      CULPA_SECRET_DIR: /var/lib/culpa
-      # T-M1/T-M2: scan the mounted host logs; live sweep every 5 minutes
-      CULPA_SCAN_HOME: /host
-      CULPA_SCAN_EVERY_MS: "300000"
-      # LAUNCH CONFIG (founder go, 2026-07-31 — D-041 enforcement flip;
-      # gating scope corrected 2026-08-03 by D-055): every customer-facing
-      # READ of the customer's own spend data requires a valid entitlement.
-      # Capture (ingest, scan, imports) and licensing lifecycle routes (claim,
-      # activation, license, checkout, billing-portal, entitlement, terms)
-      # are NEVER gated — a licensing failure must never break the
-      # customer's production traffic or block them from activating. Fail
-      # open ONLY on infrastructure failure (license server unreachable, DB
-      # blip, WASM missing), where the cached entitlement stands; an ABSENT
-      # or CANCELLED entitlement refuses. Activation: buy → claim in-app (or
-      # set CULPA_LICENSE_KEY, or paste the key in the dashboard under
-      # Account -> Plan & Billing -> Activate); the license server below is where the app
-      # syncs counts-only and refreshes the signed entitlement. Remove the
-      # license-server line and nothing ever leaves this machine — paid
-      # reads then stay degraded (that is the deal).
-      CULPA_TRUST_ENFORCE: "1"
-      CULPA_LICENSE_SERVER: https://culpa.fly.dev
-      # T-CF4-12 (Culpaflight4 #15): current model prices pull on first boot
-      # and refresh daily. This is a DOWNLOAD of the public price list —
-      # nothing about your usage goes anywhere (D-034). Remove the line and
-      # the committed snapshot + seeds keep pricing working offline.
-      CULPA_PRICING_SYNC: "1"
-    ports:
-      - "127.0.0.1:4545:4545"
-    volumes:
-      - culpa_data:/var/lib/culpa
-      # T-M3 ("+ See a cost"): the host's AI-tool session logs, READ-ONLY —
-      # this is what lets the in-dashboard scan see Claude Code/Codex history
-      # and keep it live. Only these two dirs, never the whole home.
-      # NARROW scope (review M2): only the session-log subdirs — ~/.claude
-      # also holds credentials/settings, which the container must never see
-      - ${CULPA_HOST_HOME:-${USERPROFILE:-${HOME:-}}}/.claude/projects:/host/.claude/projects:ro
-      - ${CULPA_HOST_HOME:-${USERPROFILE:-${HOME:-}}}/.codex/sessions:/host/.codex/sessions:ro
-    depends_on:
-      db:
-        condition: service_healthy
-    restart: unless-stopped
-
-  dashboard:
-    # Per-component release (D-087). v1.0.5 is a dashboard + relay release: no
-    # server, migration or API change, so culpa-server above deliberately stays
-    # at v1.0.3 rather than being re-tagged for a release it has no diff in
-    # (D-072: never rebuild a tag that already exists). The example this note
-    # used to give was CF14's v0.11.0/v0.11.1 pair, which no longer matches
-    # either pin in this file.
-    image: ghcr.io/myaigidev/culpa-dashboard:v1.0.9
-    container_name: culpa-dashboard
-    environment:
-      CULPA_API_BASE: http://server:4545
-    ports:
-      - "127.0.0.1:3000:3000"
-    depends_on:
-      - server
-    restart: unless-stopped
-
-volumes:
-  culpa_pgdata:
-    name: culpa_pgdata
-  culpa_data:
-    name: culpa_data
+# Culpa — release compose file shipped inside the installers (T-087/T-088).
+# Net effect is identical to running the stack from the repository:
+# same services, same container names, same ports, same privacy default.
+# Images are pulled from ghcr.io; a locally built/tagged image with the same
+# name is used when present, which is how these pins were verified before
+# publication.
+#
+# ── RELEASE STATE: v1.1.0 PUBLISHED AND SIGNED (2026-09-06) ─────────
+# The line above is REWRITTEN BY installers/publish.sh at real-publish time —
+# this file has shipped a hand-edited, wrong publication claim twice, so the
+# claim is now mechanical, never prose. While it reads NOT PUBLISHED, the pins
+# below resolve only against locally built images and this file must not be
+# distributed. v0.11.0 is the CF9-CF12 round (UI alignment fixes, forecast
+# uncertainty-calibration repair + kappa bound + cohort/centring explain,
+# cache coverage flags, relay-mesh W1/W2c groundwork — feature-gated out of
+# shipped binaries) on top of v0.10.0, the CF7/CF8 round (forecast P50-anchor + cache
+# counterfactual math repair, founder UI list U-1..U-8 + P-1, founder
+# palette + card "i" tooltips, native CLI auto-update Option A, QW-1..4
+# container-upgrade guards, CodeRabbit PR#13 triage) on top of v0.9.0.
+# The relay and license-server carry NO changes since v0.9.0 and keep
+# their v0.9.0 images — a version is only claimed where a real diff
+# exists. A signed tag is never rebuilt (D-072), so new contents mean a
+# new version.
+#
+# Once the state line reads PUBLISHED AND SIGNED, verify before you run:
+#   cosign verify \
+#     --certificate-identity 'info@myaigi.ai' \
+#     --certificate-oidc-issuer 'https://github.com/login/oauth' \
+#     ghcr.io/myaigidev/culpa-server:v1.0.6
+# Repeat for culpa-dashboard. Both must report VERIFIED.
+#
+# If a pull fails with an authentication or "denied" error rather than a
+# missing manifest, the package has not been made public yet — the images
+# exist. Check with:
+#   gh api user/packages/container/culpa-server --jq .visibility
+# Do NOT use `docker manifest inspect` with an emptied DOCKER_CONFIG to test
+# this: on Docker Desktop for Windows the daemon authenticates through its own
+# credential store, so that check reports a false PUBLIC.
+
+services:
+  db:
+    image: postgres:16-alpine
+    container_name: culpa-db
+    environment:
+      POSTGRES_USER: culpa
+      POSTGRES_PASSWORD: culpa
+      POSTGRES_DB: culpa
+    volumes:
+      - culpa_pgdata:/var/lib/postgresql/data
+    healthcheck:
+      test: ["CMD-SHELL", "pg_isready -U culpa -d culpa"]
+      interval: 2s
+      timeout: 2s
+      retries: 30
+    restart: unless-stopped
+
+  server:
+    image: ghcr.io/myaigidev/culpa-server:v1.1.0
+    container_name: culpa-server
+    environment:
+      DATABASE_URL: postgres://culpa:culpa@db:5432/culpa
+      # full forensic capture is the default (A5); set metadata-only to opt out
+      # CF24-T1 (S2): the server binds 127.0.0.1 by DEFAULT
+      # (native/culpa-api/src/bind.rs — the binary the image actually runs).
+      # Inside a container that is unreachable through the published port, so
+      # containers must say 0.0.0.0 explicitly. The host-side `ports:` mapping
+      # below binds 127.0.0.1, so nothing OFF THIS MACHINE can reach it —
+      # reachable-by-design is always an operator's written choice, never a
+      # default.
+      #
+      # Say precisely what that does and does not cover (CF25, CodeRabbit
+      # PR #18): the `ports:` mapping governs HOST exposure only. Because the
+      # listener inside the container is 0.0.0.0, any other container attached
+      # to this Compose network reaches the server directly on 4545, without
+      # traversing the published port at all. That is ordinary Docker
+      # networking and it is fine for the services defined here — but adding a
+      # container to this network grants it API access, and the port mapping
+      # will not stop it.
+      CULPA_API_BIND: "0.0.0.0"
+      CULPA_PRIVACY_MODE: full
+      # T-120: the machine secret encrypting the customer key at rest lives
+      # here as a file — a VOLUME, so it survives container recreation
+      CULPA_SECRET_DIR: /var/lib/culpa
+      # T-M1/T-M2: scan the mounted host logs; live sweep every 5 minutes
+      CULPA_SCAN_HOME: /host
+      CULPA_SCAN_EVERY_MS: "300000"
+      # ISS-V110-18: the local-models route (Ollama, LM Studio, vLLM …) must reach
+      # the HOST's runtime — "localhost" inside the container is the container
+      # itself, so the shipped default of http://localhost:11434 answered 500 and
+      # recorded nothing. Docker Desktop resolves host.docker.internal; the
+      # extra_hosts entry below maps it on Linux too. Change the port if your
+      # runtime listens elsewhere.
+      CULPA_LOCAL_UPSTREAM: http://host.docker.internal:11434
+      # LAUNCH CONFIG (founder go, 2026-07-31 — D-041 enforcement flip;
+      # gating scope corrected 2026-08-03 by D-055): every customer-facing
+      # READ of the customer's own spend data requires a valid entitlement.
+      # Capture (ingest, scan, imports) and licensing lifecycle routes (claim,
+      # activation, license, checkout, billing-portal, entitlement, terms)
+      # are NEVER gated — a licensing failure must never break the
+      # customer's production traffic or block them from activating. Fail
+      # open ONLY on infrastructure failure (license server unreachable, DB
+      # blip, WASM missing), where the cached entitlement stands; an ABSENT
+      # or CANCELLED entitlement refuses. Activation: buy → claim in-app (or
+      # set CULPA_LICENSE_KEY, or paste the key in the dashboard under
+      # Account -> Plan & Billing -> Activate); the license server below is where the app
+      # syncs counts-only and refreshes the signed entitlement. Remove the
+      # license-server line and nothing ever leaves this machine — paid
+      # reads then stay degraded (that is the deal).
+      CULPA_TRUST_ENFORCE: "1"
+      CULPA_LICENSE_SERVER: https://culpa.fly.dev
+      # T-CF4-12 (Culpaflight4 #15) — OPT-IN (Privacy Policy 4.4, founder ruling
+      # 2026-09-06): the daily public price-list download is OFF unless you turn
+      # it on. It is a DOWNLOAD only — nothing about your usage goes anywhere
+      # (D-034) — and the committed snapshot + seeds keep pricing working without
+      # it. To pick up new model prices automatically, uncomment the next line:
+      # CULPA_PRICING_SYNC: "1"
+    ports:
+      - "127.0.0.1:4545:4545"
+    # ISS-V110-18: makes host.docker.internal resolve on Linux (Docker Desktop
+    # already provides it); harmless where it already exists. On native Linux
+    # it resolves to the host's Docker gateway, so the local model runtime
+    # must listen on that interface, not only on 127.0.0.1 (Ollama:
+    # OLLAMA_HOST=0.0.0.0).
+    extra_hosts:
+      - "host.docker.internal:host-gateway"
+    volumes:
+      - culpa_data:/var/lib/culpa
+      # T-M3 ("+ See a cost"): the host's AI-tool session logs, READ-ONLY —
+      # this is what lets the in-dashboard scan see Claude Code/Codex history
+      # and keep it live. Only these two dirs, never the whole home.
+      # NARROW scope (review M2): only the session-log subdirs — ~/.claude
+      # also holds credentials/settings, which the container must never see
+      - ${CULPA_HOST_HOME:-${USERPROFILE:-${HOME:-}}}/.claude/projects:/host/.claude/projects:ro
+      - ${CULPA_HOST_HOME:-${USERPROFILE:-${HOME:-}}}/.codex/sessions:/host/.codex/sessions:ro
+    depends_on:
+      db:
+        condition: service_healthy
+    restart: unless-stopped
+
+  dashboard:
+    # Per-component release (D-087). v1.0.5 is a dashboard + relay release: no
+    # server, migration or API change, so culpa-server above deliberately stays
+    # at v1.0.3 rather than being re-tagged for a release it has no diff in
+    # (D-072: never rebuild a tag that already exists). The example this note
+    # used to give was CF14's v0.11.0/v0.11.1 pair, which no longer matches
+    # either pin in this file.
+    image: ghcr.io/myaigidev/culpa-dashboard:v1.1.0
+    container_name: culpa-dashboard
+    environment:
+      CULPA_API_BASE: http://server:4545
+    ports:
+      - "127.0.0.1:3000:3000"
+    depends_on:
+      - server
+    restart: unless-stopped
+
+volumes:
+  culpa_pgdata:
+    name: culpa_pgdata
+  culpa_data:
+    name: culpa_data