[schemas] Fix typed-reasoning-edges COMMENT syntax error

[AnkitClassicVision]

Summary

The COMMENT ON FUNCTION public.thought_edges_upsert IS clause uses runtime string concatenation ('...' || '...' || '...'), which Postgres rejects. COMMENT requires a single string literal, not an expression.

Repro

Apply the schema against Supabase:

supabase db query --linked --file schemas/typed-reasoning-edges/schema.sql

Fails with:

ERROR:  42601: syntax error at or near "||"
LINE 258:   'Insert or (on duplicate key) bump support_count + refresh temporal bounds. ' ||

Fix

Replaced || with SQL-standard adjacent-string-literal concatenation — the parser joins adjacent 'a' 'b' into 'ab' when separated only by whitespace, so the multi-line source stays readable while producing a valid single literal.

-- before
COMMENT ON FUNCTION public.thought_edges_upsert IS
  'Insert or (on duplicate key) ... ' ||
  'Call via POST ... ' ||
  'you want ...';

-- after
COMMENT ON FUNCTION public.thought_edges_upsert IS
  'Insert or (on duplicate key) ... '
  'Call via POST ... '
  'you want ...';

Test plan

• Hit the original error by applying schema as-is
• Apply patched schema against a Supabase Pro project — applies cleanly
• Verify \df+ public.thought_edges_upsert shows the merged description

🤖 Generated with Claude Code