Brain flywheel 6: promote, prune, and synthesize on cadence — the dream cycle, employed #1685

Problem — The dream family exists as manual skills with a dead substrate; its curation semantics (connect, promote, prune, schema-check, synthesize) never run on schedule.
Approach — Register the five curation motions as warranted notturno jobs implementing the dream semantics on the claim layer: connect (cross-links), promote (one PR per vault, capped, human-merged), prune + schema-check (hygiene diffs), synthesize (cross-claim patterns → hopper proposals).

Acceptance Criteria

• The promote job opens one PR per vault with scope-team claims, respects the 10-cap, and never auto-merges
• The prune job emits hygiene diffs + flagged drift, applying only unambiguous fixes
• The synthesize job proposes hopper items from cross-claim patterns without touching human-fed strategy sections
• Each job files pass receipts; the registry runs them on their cadences
• The manual /dream invocation is documented as retired in favor of the jobs

Testing Decisions

Reuse the dream skills' documented semantics as the behavioral spec; hermetic fixtures per job; a live dry-run smoke mirroring the notturno parity discipline.

Key Decisions

Promotion stays double-gated — author visibility tag + human PR merge. Synthesize proposes to the hopper, never to strategy.

Source

Part of #1679. Vault spec spec-20261002-090500-company-brain-flywheel. The dream skill family documents the curation semantics each job implements.

Notes

Slice 6 of 9 — blocked by 3, 4, 5 (index, stamps, and lifecycle feed its inputs).