You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<pclass="status" role="status" data-login-mode-disabled-messagehidden>Use the API-backed local server for sign-in. Run npm run dev:local-api and open http://127.0.0.1:5501/account/sign-in.html. Local DB is disabled until the local API server is running.</p>
<p>This foundation page identifies where future setup and seed actions belong. Runtime setup actions are not executable in this PR.</p>
60
+
<p>This page owns controlled Local DB setup entry points. Reseed actions call admin-gated server APIs and report visible PASS/FAIL/WARN/SKIP status.</p>
constapiBackedLoginDiagnostic=`Use the API-backed local server for sign-in. Run ${localApiStartCommand} and open ${localApiLoginUrl}.`;
30
21
conststaticModeDisabledMessage=`Use the API-backed local server for sign-in. Run ${localApiStartCommand} and open ${localApiLoginUrl}. Local DB is disabled until the local API server is running.`;
Database schema and setup reviewartifacts are owned outside runtime source.
3
+
Database schema, DML review, and seed artifacts are grouped under `docs_build/database/`.
4
4
5
5
## Ownership
6
6
7
7
- DEV database DDL belongs in `docs_build/database/ddl/`.
8
8
- DEV setup or DML review artifacts belong in `docs_build/database/dml/`.
9
-
- DDL must not be placed under `src/` or `docs/`.
10
-
- DML files in this folder are temporary setup/review artifacts unless promoted by a future Admin Site Setup workflow.
9
+
- Seed artifacts belong in `docs_build/database/seed/`.
10
+
- Guest seed artifacts belong in `docs_build/database/seed/guest/` and are read-only.
11
+
- DDL/DML/seed artifacts must not be placed under `src/` or `docs/`.
11
12
- Identity records use `key` as the primary identifier. Shared audit ownership uses `createdBy` and `updatedBy` references to `users.key`.
12
13
13
-
## Execution Boundary
14
+
## Grouping
15
+
16
+
Each product area/tool owns one grouped file in `ddl/`, `dml/`, and `seed/`. Account tables stay in `account.sql` / `account.json`; tool metadata, planning, and votes remain separate grouped files.
14
17
15
-
Codex may execute DEV database setup only.
18
+
## Execution Boundary
16
19
17
-
UAT and production SQL execution is user-controlled. Codex may prepare review artifacts, but it must not execute UAT or production SQL.
20
+
Runtime DEV setup and reseed actions must call server-side APIs. Browser pages must not directly seed authoritative DB records or generate authoritative DB keys.
18
21
19
-
Long-term seed behavior belongs in Admin -> Site Setup, not permanent seed SQL. Temporary DML files may document review setup data while the Admin Site Setup workflow is planned.
22
+
Codex may execute DEV database setup only. UAT and production SQL execution is user-controlled. Codex may prepare review artifacts, but it must not execute UAT or production SQL.
0 commit comments