Build on Phases 1–7. Adds the two override paths from AGENTS.md §4 FR-10/FR-11: the shared device keycode and the versioned admin HTTP API the separate Kotlin admin app will call. - store: migration 004 adds state.grant_until and a settings table. New overrides.go records every override in `overrides` and verifies the shared keycode (bcrypt; one code for every device, §10 rule 3). ExpireLocks also clears an expired grant, and NextScheduleBoundary includes the grant end so a device re-locks on time. - effective state: a grant unlocks a device inside a schedule window; a manual lock clears a grant and a grant clears a manual lock. The retained config payload gains grant_until (additive, v stays 1). - web: /api/v1/admin/... (list, state, lock, unlock, grant) guarded by CONTROL_ADMIN_API_TOKEN, separate from the session login, plus the on-device keycode endpoint POST /api/v1/device/override with per-address throttling. A state change is published retained before the API responds. - cmd/control: `keycode` subcommand and start-up seeding from CONTROL_DEVICE_KEYCODE_HASH. - deploy/verify-phase8.sh + `make verify-phase8` prove the definition of done: an API lock reaches a real broker subscriber in well under a second. - Version 0.6.0-phase8 (compose, Makefile, docs). Measured on .13: the lock reached the TLS broker subscriber in 7 ms (handler 1 ms, request to retained publish accepted). Tests: go vet ./... and go test -count=1 ./... pass in golang:1.25-alpine. Co-Authored-By: Paperclip <noreply@paperclip.ing>
21 lines
890 B
SQL
21 lines
890 B
SQL
-- Migration 004 — Phase 8. Overrides (AGENTS.md §7, §11 Phase 8).
|
|
--
|
|
-- The shared device keycode lives in `settings` as a bcrypt hash under the key
|
|
-- 'device_keycode_hash'. It is never stored or logged in plaintext. The
|
|
-- key/value table also gives later phases a place for small settings without a
|
|
-- new migration.
|
|
--
|
|
-- grant_until is a time-limited exemption: while it is in the future the device
|
|
-- is unlocked even when a weekly window would otherwise block it. It is a
|
|
-- separate column from the manual lock's `until` so "grant 30 minutes" and
|
|
-- "lock until I unlock" cannot fight over the same value. A manual lock clears
|
|
-- a grant; a grant clears a manual lock.
|
|
|
|
ALTER TABLE state ADD COLUMN grant_until TEXT;
|
|
|
|
CREATE TABLE IF NOT EXISTS settings (
|
|
key TEXT PRIMARY KEY,
|
|
value TEXT NOT NULL,
|
|
updated_at TEXT NOT NULL DEFAULT (datetime('now'))
|
|
);
|