JSON.stringify(input) + ::jsonb cast produced a jsonb string value
instead of a jsonb object. The postgres library's unsafe() with a
raw object + ::jsonb correctly stores a jsonb object.

This caused collectChildPutPageSlugs to return 0 results (can't
extract ->>'slug' from a jsonb string), making dream synthesize
report '0 pages written' even though subagents successfully wrote
16 pages to the database.

Fix: pass objects as-is to executeRaw, let the postgres driver
handle serialization. Non-object values wrapped in {_raw: ...}
as a safety fallback.

This reverts commit 80b3909.

JSON.stringify(input) + ::jsonb cast produced a jsonb string value
instead of a jsonb object. The postgres library's unsafe() with a
raw object + ::jsonb correctly stores a jsonb object.

This caused collectChildPutPageSlugs to return 0 results (can't
extract ->>'slug' from a jsonb string), making dream synthesize
report '0 pages written' even though subagents successfully wrote
16 pages to the database.

Fix: pass objects as-is to executeRaw, let the postgres driver
handle serialization. Non-object values wrapped in {_raw: ...}
as a safety fallback.

…nb + doctor

The four `subagent_*` jsonb writers in `src/core/minions/handlers/subagent.ts`
(persistMessage, persistToolExecPending, persistToolExecComplete,
persistToolExecFailed) used `engine.executeRaw` with `JSON.stringify(value)`
plus `$N::jsonb` cast. On the postgres-engine path that goes through
postgres.js's `unsafe()`, that combination produces a jsonb string scalar
instead of an object — exactly the v0.12.0 double-encode shape, on a second
set of tables.

Verified empirically (probe inside this branch, not committed):

  P1 JSON.stringify(obj) + $::jsonb → jsonb_typeof='string'  (broken)
  P3 raw object + $::jsonb           → jsonb_typeof='object' (correct)
  P4 sql.json(obj) via unsafe        → jsonb_typeof='object' (correct)

The four call sites are changed to pass the raw value. postgres.js v3
auto-encodes objects/arrays for jsonb columns (already what queue.ts:233
relies on for `minion_jobs.data`, never broken). PGLite handles raw values
identically (verified — all three patterns produce object jsonb on PGLite).

Existing data on the user's brain at the time of fix:
  subagent_messages.content_blocks: 40/40 corrupt
  subagent_tool_executions.input:   39/39 corrupt
  subagent_tool_executions.output:  39/39 corrupt
All 118 rows repaired by `gbrain repair-jsonb` after extending TARGETS.

Symptom this resolves: dream synthesize's orchestrator
(`collectChildPutPageSlugs` in src/core/cycle/synthesize.ts:459) queries
`input->>'slug'` to gather slugs the subagent wrote; on string-typed jsonb
that operator returns NULL, so `pages_written` reports 0 even when child
subagents successfully wrote pages. The reverse-write step that mirrors
DB → markdown is then skipped, leaving real synthesized pages stranded
in the DB. After this fix, the orchestrator picks up slugs correctly and
the full dream cycle closes the loop.

Companion changes:
  - `repair-jsonb` extended from 5 → 8 columns (subagent_messages.content
    _blocks, subagent_tool_executions.{input,output}); guards each target
    with `to_regclass()` so pre-v0.15 brains that lack the subagent_*
    tables don't throw at upgrade time.
  - `doctor`'s `jsonb_integrity` check extended to the same 8 columns
    with the same guard. Any future user hitting this bug from upstream
    master gets a clear "X rows double-encoded ... Fix: gbrain
    repair-jsonb" warning instead of silent dream failures.
  - `repair-jsonb.ts` header comment retracted: the prior claim that
    parameterized `$N::jsonb` was always safe was wrong; safety came
    from queue.ts/etc. passing raw objects, not from the binding form.

Upstream history: PR garrytan#525 was a chmod fix mis-attributed by local commits;
the real outstanding upstream PR is garrytan#539 (zombie lock + post-hoc data
repair via UPDATE) which does NOT patch the write path. Master HEAD still
ships the buggy form. This patch is upstream-worthy as a follow-up to

Tests: 245 pass across minions, subagent-handler, cycle-synthesize,
cycle-patterns, repair-jsonb, migrations-v0_12_2, and doctor. typecheck
clean.

…nb + doctor

The four `subagent_*` jsonb writers in `src/core/minions/handlers/subagent.ts`
(persistMessage, persistToolExecPending, persistToolExecComplete,
persistToolExecFailed) used `engine.executeRaw` with `JSON.stringify(value)`
plus `$N::jsonb` cast. On the postgres-engine path that goes through
postgres.js's `unsafe()`, that combination produces a jsonb string scalar
instead of an object — exactly the v0.12.0 double-encode shape, on a second
set of tables.

Verified empirically (probe inside this branch, not committed):

  P1 JSON.stringify(obj) + $::jsonb → jsonb_typeof='string'  (broken)
  P3 raw object + $::jsonb           → jsonb_typeof='object' (correct)
  P4 sql.json(obj) via unsafe        → jsonb_typeof='object' (correct)

The four call sites are changed to pass the raw value. postgres.js v3
auto-encodes objects/arrays for jsonb columns (already what queue.ts:233
relies on for `minion_jobs.data`, never broken). PGLite handles raw values
identically (verified — all three patterns produce object jsonb on PGLite).

Existing data on the user's brain at the time of fix:
  subagent_messages.content_blocks: 40/40 corrupt
  subagent_tool_executions.input:   39/39 corrupt
  subagent_tool_executions.output:  39/39 corrupt
All 118 rows repaired by `gbrain repair-jsonb` after extending TARGETS.

Symptom this resolves: dream synthesize's orchestrator
(`collectChildPutPageSlugs` in src/core/cycle/synthesize.ts:459) queries
`input->>'slug'` to gather slugs the subagent wrote; on string-typed jsonb
that operator returns NULL, so `pages_written` reports 0 even when child
subagents successfully wrote pages. The reverse-write step that mirrors
DB → markdown is then skipped, leaving real synthesized pages stranded
in the DB. After this fix, the orchestrator picks up slugs correctly and
the full dream cycle closes the loop.

Companion changes:
  - `repair-jsonb` extended from 5 → 8 columns (subagent_messages.content
    _blocks, subagent_tool_executions.{input,output}); guards each target
    with `to_regclass()` so pre-v0.15 brains that lack the subagent_*
    tables don't throw at upgrade time.
  - `doctor`'s `jsonb_integrity` check extended to the same 8 columns
    with the same guard. Any future user hitting this bug from upstream
    master gets a clear "X rows double-encoded ... Fix: gbrain
    repair-jsonb" warning instead of silent dream failures.
  - `repair-jsonb.ts` header comment retracted: the prior claim that
    parameterized `$N::jsonb` was always safe was wrong; safety came
    from queue.ts/etc. passing raw objects, not from the binding form.

Upstream history: PR garrytan#525 was a chmod fix mis-attributed by local commits;
the real outstanding upstream PR is garrytan#539 (zombie lock + post-hoc data
repair via UPDATE) which does NOT patch the write path. Master HEAD still
ships the buggy form. This patch is upstream-worthy as a follow-up to

Tests: 245 pass across minions, subagent-handler, cycle-synthesize,
cycle-patterns, repair-jsonb, migrations-v0_12_2, and doctor. typecheck
clean.

…nb + doctor

The four `subagent_*` jsonb writers in `src/core/minions/handlers/subagent.ts`
(persistMessage, persistToolExecPending, persistToolExecComplete,
persistToolExecFailed) used `engine.executeRaw` with `JSON.stringify(value)`
plus `$N::jsonb` cast. On the postgres-engine path that goes through
postgres.js's `unsafe()`, that combination produces a jsonb string scalar
instead of an object — exactly the v0.12.0 double-encode shape, on a second
set of tables.

Verified empirically (probe inside this branch, not committed):

  P1 JSON.stringify(obj) + $::jsonb → jsonb_typeof='string'  (broken)
  P3 raw object + $::jsonb           → jsonb_typeof='object' (correct)
  P4 sql.json(obj) via unsafe        → jsonb_typeof='object' (correct)

The four call sites are changed to pass the raw value. postgres.js v3
auto-encodes objects/arrays for jsonb columns (already what queue.ts:233
relies on for `minion_jobs.data`, never broken). PGLite handles raw values
identically (verified — all three patterns produce object jsonb on PGLite).

Existing data on the user's brain at the time of fix:
  subagent_messages.content_blocks: 40/40 corrupt
  subagent_tool_executions.input:   39/39 corrupt
  subagent_tool_executions.output:  39/39 corrupt
All 118 rows repaired by `gbrain repair-jsonb` after extending TARGETS.

Symptom this resolves: dream synthesize's orchestrator
(`collectChildPutPageSlugs` in src/core/cycle/synthesize.ts:459) queries
`input->>'slug'` to gather slugs the subagent wrote; on string-typed jsonb
that operator returns NULL, so `pages_written` reports 0 even when child
subagents successfully wrote pages. The reverse-write step that mirrors
DB → markdown is then skipped, leaving real synthesized pages stranded
in the DB. After this fix, the orchestrator picks up slugs correctly and
the full dream cycle closes the loop.

Companion changes:
  - `repair-jsonb` extended from 5 → 8 columns (subagent_messages.content
    _blocks, subagent_tool_executions.{input,output}); guards each target
    with `to_regclass()` so pre-v0.15 brains that lack the subagent_*
    tables don't throw at upgrade time.
  - `doctor`'s `jsonb_integrity` check extended to the same 8 columns
    with the same guard. Any future user hitting this bug from upstream
    master gets a clear "X rows double-encoded ... Fix: gbrain
    repair-jsonb" warning instead of silent dream failures.
  - `repair-jsonb.ts` header comment retracted: the prior claim that
    parameterized `$N::jsonb` was always safe was wrong; safety came
    from queue.ts/etc. passing raw objects, not from the binding form.

Upstream history: PR garrytan#525 was a chmod fix mis-attributed by local commits;
the real outstanding upstream PR is garrytan#539 (zombie lock + post-hoc data
repair via UPDATE) which does NOT patch the write path. Master HEAD still
ships the buggy form. This patch is upstream-worthy as a follow-up to

Tests: 245 pass across minions, subagent-handler, cycle-synthesize,
cycle-patterns, repair-jsonb, migrations-v0_12_2, and doctor. typecheck
clean.