-- +goose Up
-- Add a verifier column to skill_relationships so the WS8 two step human in the loop gate records WHO
-- activated a curated edge, distinct from WHO approved the proposal that staged it. The proposal carries the
-- approver and approved_at (the first human step); the staged edge carries verified_at (already present) and
-- now verifier (the second, distinct human step). Keeping the two actors on two rows is what makes the gate a
-- genuine two person, two action control rather than one click. The column is nullable: an edge seeded by an
-- earlier ontology load or by WS2 and WS3 has no curation verifier, and a staged but not yet verified edge has
-- neither verified_at nor verifier set. The resolver still keys activation on verified_at alone, so this
-- column is metadata for the audit trail, never a scoring input. Global migrator owned table, app SELECT only.
ALTER TABLE skill_relationships ADD COLUMN IF NOT EXISTS verifier uuid;

-- +goose Down
ALTER TABLE skill_relationships DROP COLUMN IF EXISTS verifier;