Role Set Template Disposable Local SQL Dry-Run
Purpose
This page documents the manual disposable local dry-run scaffold for validating the local-only role-set template draft against a throwaway SQLite target when explicitly requested outside normal app runtime.
The app exposes no migration control, runtime query, role-set storage, write endpoint, CRUD UI, user assignment, identity storage, submissions, tracking, analytics, scoring, or production/preview database target.
Manual Flag-Gated Behavior
Status
manual-local-disposable-only
manual-local-disposable-onlyDefault SQL Behavior
false
disabledManual Flag
--local-disposable-only
D1 Targeted
false
not-targetedWrangler Used
false
not-usedRuntime Dependency
false
noneDisposable Local Target Rules
- temporary artifacts may appear only under .tmp/role-set-template-dry-run during an explicit manual run
- .tmp/ is gitignored
- temporary artifacts are deleted by default after completion
- temporary artifacts are never app runtime storage
- temporary artifacts are never production or preview database files
Table creation scope: disposable-local-only. Production targeted: false. Preview targeted: false. App data writes: false.
Script Location
scripts/local/dry-run-role-set-template-migration-draft.mjs
This script is not referenced by package scripts, Astro pages, endpoints, or app runtime imports.
Draft Artifact Location
docs/architecture/migration-drafts/role-set-template-config-draft.sql.md
Validator: scripts/local/validate-role-set-template-migration-draft.mjs. The validator must pass before any disposable local path can continue.
Safety Checks
- explicit manual flag required
- validator must pass before SQL dry-run path
- draft must be outside active migrations folder
- draft must contain LOCAL-ONLY and DO NOT RUN labels
- active migrations folder must remain unchanged
- prohibited table names must be absent from draft SQL
- prohibited sensitive fields must be absent from draft SQL
- D1 usage must be absent
- wrangler usage must be absent
- dry-run target must be disposable and local
- temp files must be ignored by git
- SQL execution must never happen during import
- SQL execution must never happen during build
- SQL execution must never happen during tests unless a specific manual command is explicitly run
Allowed Outputs
Prohibited Outputs
- tracked generated SQL execution logs
- production reports
- preview reports
- D1 output
- seed records
- user records
- resident records
- submission records
- staff decision records
- audit records for app runtime
- persistent app database files
Failure Modes And Stop Conditions
| Failure modes | Stop conditions |
|---|---|
| manual flag missing; validator fails; draft artifact missing; draft artifact appears in active migrations folder; local-only labels missing; active migrations folder changes unexpectedly; prohibited table name appears; prohibited sensitive field appears; D1 target appears; wrangler wrapper appears; production target appears; preview target appears; local SQLite engine unavailable; disposable target cannot be cleaned up | manual flag not present; validator does not pass; draft is not local-only; draft is inside active migrations folder; any prohibited table appears; any prohibited field appears; any D1 target appears; any production or preview target appears; any runtime endpoint writes role-set data; active migrations folder changes unexpectedly |
What Remains Blocked
No D1 target, wrangler use, production or preview database target, active migration, runtime query, package script, write endpoint, CRUD UI, role-set runtime storage, user assignment, identity storage, submissions, staff decisions, tracking, analytics, scoring, billing, lead capture, or sensitive storage is active.
- no production activation approved
- no preview D1 targeting approved
- no active migration approved
- no write endpoint approved
- no CRUD UI approved
- no user assignment approved
- no identity storage approved
- no submissions approved
- no attendance tracking approved
- no participation tracking approved
- no participation analytics approved
- no scoring, ranking, or compliance metrics approved
- staff/privacy approval still required
- separate activation review still required
Recommended Next Phase
Phase 7.12 - Role Set Template Migration Activation Review, Planning Only
Boundaries: future phase only; no production activation yet; no preview D1 targeting yet; no active migration until explicit approval; no write endpoints; no CRUD UI; no user assignment; no submissions.
future-only