Add D1 data model and Drizzle schema; update AGENTS.md for Codex Cloud

[catoncat]

Motivation

• Introduce a normalized D1 relational index to support user/session/collection/note discovery while keeping KV note payloads as the source of truth.
• Provide a clear, portable schema compatible with Cloudflare D1 / SQLite and Drizzle code generation.
• Document Codex Cloud environment behavior for mainline being unavailable so agents skip Mainline commands in that container.

Description

• Add docs/data-model.md containing the D1 data model, ER diagram, table definitions, constraints, and equivalent SQL for users, sessions, collections, notes_index, and collection_notes.
• Add src/schema.ts which implements the schema in Drizzle with table definitions, indexes, checks, relations, and exports schema, collectionVisibilityValues, and noteModerationStatusValues.
• Update AGENTS.md to include a Codex Cloud environment note instructing agents to skip mainline CLI commands and use the git-native workflow instead.

Testing

• No automated tests were run as part of this change.

---

Codex Task

---

Summary by cubic

Add a normalized Cloudflare D1 schema (users, sessions, collections, notes_index, collection_notes) and a drizzle-orm schema to enable account-backed note discovery while keeping KV note bodies as the source of truth. Also document that Codex Cloud containers skip the mainline CLI and use a git-native workflow.

• New Features
  • Added docs/data-model.md with ER diagram, table/constraint details, and equivalent D1/SQLite SQL.
  • Added src/schema.ts implementing the Drizzle schema, relations, and exports: schema, collectionVisibilityValues, noteModerationStatusValues.
  • Updated AGENTS.md with a Codex Cloud note to skip mainline commands and not report skip notices; use the git-native workflow instead.

^{Written for commit 9f7d36d. Summary will update on new commits.}

[catoncat]

@codex fix the ci error
Run npm ci
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@cloudflare/kv-asset-handler@0.5.0',
npm warn EBADENGINE required: { node: '>=22.0.0' },
npm warn EBADENGINE current: { node: 'v20.20.2', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: 'miniflare@4.20260507.1',
npm warn EBADENGINE required: { node: '>=22.0.0' },
npm warn EBADENGINE current: { node: 'v20.20.2', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: 'wrangler@4.90.0',
npm warn EBADENGINE required: { node: '>=22.0.0' },
npm warn EBADENGINE current: { node: 'v20.20.2', npm: '10.8.2' }
npm warn EBADENGINE }
npm error code EUSAGE
npm error
npm error npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
npm error
npm error Missing: @emnapi/runtime@1.10.0 from lock file
npm error Missing: @emnapi/core@1.10.0 from lock file
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm error [--no-bin-links] [--no-fund] [--dry-run]
npm error [-w|--workspace [-w|--workspace ...]]
npm error [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci" for more info
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-06-02T02_07_36_721Z-debug-0.log
Error: Process completed with exit code 1.

[chatgpt-codex-connector]

To use Codex here, create an environment for this repo.

[cubic-dev-ai]

3 issues found across 3 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/data-model.md">

<violation number="1" location="docs/data-model.md:3">
P2: The new data-model doc conflicts with the repository’s KV-only/no-account storage contract, creating a contradictory architecture spec.</violation>
</file>

<file name="src/schema.ts">

<violation number="1" location="src/schema.ts:63">
P2: CHECK constraints duplicate enum literals instead of deriving from the exported enum arrays, creating a drift risk that can cause runtime constraint failures.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: The new data-model doc conflicts with the repository’s KV-only/no-account storage contract, creating a contradictory architecture spec.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At docs/data-model.md, line 3:

<comment>The new data-model doc conflicts with the repository’s KV-only/no-account storage contract, creating a contradictory architecture spec.</comment>

<file context>
@@ -0,0 +1,275 @@
+# D1 Data Model
+
+This is the first D1 relational schema for account-backed note organization while keeping the existing KV note body (`n:<slug>`) and metadata (`m:<slug>`) layout as the source of truth for short-lived note content.
+
+## Scope and goals
</file context>

[cubic-dev-ai]

P2: CHECK constraints duplicate enum literals instead of deriving from the exported enum arrays, creating a drift risk that can cause runtime constraint failures.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/schema.ts, line 63:

<comment>CHECK constraints duplicate enum literals instead of deriving from the exported enum arrays, creating a drift risk that can cause runtime constraint failures.</comment>

<file context>
@@ -0,0 +1,170 @@
+    index("collections_visibility_idx").on(table.visibility),
+    check(
+      "collections_visibility_check",
+      sql`${table.visibility} in ('public', 'unlisted', 'private')`,
+    ),
+  ],
</file context>