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

[lucifer]

Contribution Type

• Schema (/schemas)

What does this do?

Fixes a syntax error in schemas/typed-reasoning-edges/schema.sql that prevents the migration from running. The COMMENT ON FUNCTION public.thought_edges_upsert IS ... statement uses the SQL || concatenation operator to join three string literals, but PostgreSQL's COMMENT statement requires a single string literal after IS, not an expression. Pasting the script into the Supabase SQL editor fails with:

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

Collapsing the three pieces into one literal lets the schema apply cleanly. No behavior change — same comment text.

Requirements

None beyond what schemas/typed-reasoning-edges/ already lists.

Checklist

• I've read CONTRIBUTING.md
• No credentials, API keys, or secrets are included
• Reproduced the error in Supabase SQL editor and verified the patched script runs

Test plan

• Apply schemas/typed-reasoning-edges/schema.sql from this branch in Supabase SQL editor against a brain that already has schemas/entity-extraction/ applied
• Verify the thought_edges table exists, the temporal columns on edges exist, and SELECT obj_description('public.thought_edges_upsert'::regproc); returns the expected comment

🤖 Generated with Claude Code

[github-actions]

Hey @lucifer — welcome to Open Brain Source! 👋

Thanks for submitting your first PR. The automated review will run shortly and check things like metadata, folder structure, and README completeness. If anything needs fixing, the review comment will tell you exactly what.

Once the automated checks pass, a human admin will review for quality and clarity. Expect a response within a few days.

If you have questions, check out CONTRIBUTING.md or open an issue.

[lucifer]

Have we stalled? This should be a strightforward pass

[alanshurafa]

Thanks for the contribution. Confirmed the fix: PostgreSQL's COMMENT ON FUNCTION ... IS clause takes a single string literal, not a ||-concatenated expression, so the original three-part version would fail to parse. Collapsing it into one literal resolves the error with no behavior change.

One note for the maintainer: #227 makes the same fix to the same lines of schemas/typed-reasoning-edges/schema.sql. The two diffs are byte-identical. A maintainer will likely land one and close the other. Recommend maintainer review.

— Alan (community reviewer; non-binding)

[justfinethanku]

Maintainer pass complete. Verified this is a surgical SQL syntax fix to the existing COMMENT ON FUNCTION ... IS string literal, refreshed the branch against current main, and confirmed there are no unresolved review threads to carry forward.