maven: scheduled routines + persistent long-term memory

Two additive proactive/recall features.

Routines (internal/routine): a third proactive class beside reminders
(user-stated) and care rules (world-state) — operator-declared clockwork.
config.routines[] (cron + literal RU body + severity) fire through the
normal dispatcher on schedule. Bodies are literal, not LLM-phrased (can't
hallucinate); rule name routine:<name> keeps them out of the care
autotuner; a cold-start guard seeds on first sight so a restart never
replays a missed schedule. Pure routine.Due + config validation, unit-
tested; the tick driver holds the last-fired map and calls fireRoutines.

Persistent memory (internal/store/memory.go): store.MemoryStore backs the
memory.Store interface with the SAME encrypted sqlite db — survives
restarts and recall text inherits at-rest encryption (no plaintext
sidecar). float32-blob vectors, brute-force cosine (ANN is a later swap
behind the interface), upsert-by-id. The daemon wires st.VectorMemory()
into wireVoice; the in-memory impl stays the test/no-store floor. Closes
the "in-memory only, lost on restart" gap (PROGRESS #8).

Gate green: gofmt/vet clean, -race across routine/config/store/mavend.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01U2PNdwDj2Gt8YW294J7oSc

internal/store/migrations.go

@@ -20,6 +20,12 @@ var migrations = []string{
 	`ALTER TABLE tools ADD COLUMN scope TEXT NOT NULL DEFAULT 'homelab';`, // #1
 	`ALTER TABLE reminders ADD COLUMN cron TEXT;
 ALTER TABLE reminders ADD COLUMN next_fire_ts INTEGER;`, // #2
+	`CREATE TABLE memory_vectors (
+		id         TEXT PRIMARY KEY,
+		vec        BLOB NOT NULL,
+		meta       TEXT NOT NULL DEFAULT '{}',
+		created_ts INTEGER NOT NULL
+	);`, // #3 — long-term vector memory (persistent backend for internal/memory)
 }
 
 // migrate applies every migration with a number greater than the DB's current