deploy(convex): thin-path functions on dev deployment reliable-panther-823

[obvious-autobuild]

Why

The Shared Child Journal's thin path — capture a dictated entry, validate extracted events, read a per-child timeline — currently exists only as shapes in the published Effect v4 Schema Contract (art_I2TCG08V). This branch deploys the actual functions to the EXISTING Convex dev deployment reliable-panther-823 (created by Gil; the stored deploy key scopes to it — verified before any write) and proves them with a synthetic write→read loop through the Convex CLI.

What

• convex/contract.ts — canonical Event/Entry Effect v4 schemas (effect@4.0.0-rc.115), mirroring the spike-verified contract: six category literals, unix-ms wire times, confidence ∈ [0,1], non-empty strings, explicit null rejected, empty events allowed (extraction failure never blocks capture).
• convex/wire.ts + convex/schema.ts — the one-directional schema→validator mapping from the contract's "Convex mapping" section; entries indexed by captureId (idempotency) and [childId, createdAt] (timeline).
• convex/children.ts — children:create mutation (non-empty name, optional birthDate).
• convex/entries.ts — entries:createEntry mutation: raw transcript always preserved; each extraction event decoded through the canonical schema; idempotent on captureId retry (original capture wins — a retried submit with a changed payload is absorbed, no second row); validation failures return captured_with_event_errors with per-event detail while the capture itself persists.
• convex/timeline.ts — timeline:list query, per child, chronological.
• deploy/contract-smoke.ts — local decode/reject/encode verification run before deploying (7 checks, all pass).

Deployment-verified finding (F1): Convex rejects stored fields starting with _ (reserved for system fields), so the contract's wire-level _tag literal is stripped on write and re-wrapped on read — a correction to the contract's mapping table that other candidates need (the spike never executed a real insert). Also verified: import { Schema } from 'effect/Schema' does not resolve on rc.115 — a namespace import is required.

How to Review

deploy/thin-path-evidence.md holds the full redacted transcripts: deployment-scope verification (npx convex env list → reliable-panther-823), deploy output ("Schema validation complete"), the idempotency loop (duplicate submit → idempotent_hit, same entryId), the timeline showing 2 entries, not 3, and the validation-failure case (schema-precise errors returned, raw transcript preserved, zero events stored). This branch is a deployment-verification vehicle — the winning candidate's shared domain package replaces convex/contract.ts at integration.

Test Evidence

• Labels: CLOUD DEV deployment (reliable-panther-823) with synthetic data via CLI — NOT live-LLM extraction, NOT native device, NOT browser app UI.
• Visual-evidence exception: backend-only Convex deployment — no rendered UI surface exists on this branch; evidence is command transcripts + the deployment URL.
• Local gates: npm run contract:smoke pass, tsc --noEmit clean, deploy completed with schema validation.
• Full transcripts (shareable): Thin-Path Deployment Evidence — reliable-panther-823
• Deployed code commit: 94e706c; branch head with evidence: 14a038b.

Human author: Gilbert Polanco (gilbertpolanco42@gmail.com)

🔗 Obvious Project · 🧵 Obvious Thread