mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-07 04:12:04 +00:00
Marc-André Bombeck
a15c6fc553
Seven migrations, 0296 through 0302, apply to an empty database in order and install both triggers. The allocation had been written down as four, and every later document that quoted it inherited a range that had already moved. `scripts/verify-v137-adversarial.ts` is the allocation as a runnable artifact rather than a table somebody keeps in step by hand. It names all seven, refuses a number allocated twice, asserts each trigger is in the migration that claims it, and counts every release inventory against a written-down number instead of against "more than zero" — a list that lost half its entries satisfies a non-empty check and fails this one. It also refuses to report success when it ran no checks at all. It found two things on its first run. Eleven handler entries looked like duplicates because the key ignored the action, and an `[id]` route carries an update and a delete as separate contracts; the key includes the action now. The journey-count leg was then falsified deliberately by expecting nine, which failed on the count and exited non-zero. The `push_attempts` principals are declared optional in the schema and NOT NULL in the database, and that is deliberate rather than drift. The attribution guard is a BEFORE INSERT trigger, so a write omitting both has them filled from the legacy mirror before the constraint is checked; requiring them in the schema would force every established self-delivery writer to name a pair it has no opinion about, and relaxing the columns would let a partial pair reach the table, which is what the trigger refuses. `migrate diff` reports the difference because it cannot see triggers, so the reason is written at the columns and names the test that proves the accommodation still works. Measured rather than assumed: applying trunk's chain to its own empty database reports the same classes of diff — truncated index names, timestamp precision, foreign keys re-stated. The release adds eight lines to that, seven of them in classes trunk already carries and one of them the deliberate pair above.
scripts/
One-shot operator and build scripts. These are not part of the running application — they are run by hand during a deploy, a backfill, or a release, or wired into CI. Recurring work belongs on pg-boss (src/lib/jobs/), not here.
How to run them
From a source checkout:
pnpm dlx tsx scripts/<file>.ts
The production image intentionally removes npm, pnpm, and Corepack. Only
container-safe scripts named by an operator runbook use its pinned
healthlog-tsx launcher; scripts that import the full application dependency
graph must run from a source checkout. scripts/ is excluded from the project
typecheck.
What lives here
generate-openapi.ts— emitsdocs/api/openapi.yamlfrom the registered Zod schemas (pnpm openapi:generate).check-openapi.ts— compares a freshly generated spec against the committed YAML; CI fails on drift (pnpm openapi:check).check-env.ts— pre-deploy env-var sanity check againstenv-manifest.json(pnpm check-env); wired into CI.assert-deploy.ts— post-deploy/api/versionassertion.rotate-encryption-key.ts— AES-256-GCM key rotation; seedocs/ops/encryption-key-rotation.md.restore-backup.ts— restore an off-host AES-GCM backup from an S3-compatible bucket.repair-intake-anomalies.ts— repair historic medication-ledger defects (duplicate dose-slot rows, implausibletaken_at); dry-run by default, seedocs/ops/intake-repair.md.backfill-rollups.ts,drain-per-sample-cumulative.ts,backfill-mood-note-column.ts— historical data backfills (note: the boot-timerollup-full-backfillqueue handles new accounts automatically; the CLI is the manual fallback).seed-demo.ts+seed-demo-v15.sql— populate a demo tenant.test-notifications.ts— exercise the notification dispatcher + reminder check.fetch-geolite2.sh— download the MaxMind GeoLite2 MMDBs (needs a licence key) beforedocker build.install-hooks.sh— install the local git hooks.generate-sw-version.mjs,print-bundle-report.mjs— service-worker version stamp and bundle-size report.i18n/— locale tooling;__tests__/— tests for the scripts above.
Conventions
See ../CLAUDE.md "Tests and commands" + "Self-hosting gotchas". Operator runbooks that drive these scripts live in ../docs/ops/.