Force Sleep Endpoint

TOS-6024: force one full sleep cycle NOW (owner/admin only).

The owner-facing counterpart of the scheduled quiet-hours dispatcher: an owner training or tuning an agent should be able to run the whole sleep pipeline (settle -> replay -> decay -> consolidate -> dormancy -> feedback -> retrospect -> REM -> prior_seed -> waking_validate) on demand instead of waiting for the Mind's derived quiet window and its 20h recycle cadence, so consolidation/lesson-processing is immediately testable.

Authorization mirrors the other ORG-WIDE mutating routes here (require_admin=True): self, an active owner of the agent, or the org OWNER role. An org admin/edit member is refused - a forced cycle rewrites the Mind's salience and confidence wholesale, the same class of act as /rebuild, not a per-belief edit.

The cycle runs as a detached background task (it can take minutes); admission is validated synchronously so a refusal (no Mind, already sleeping) is an immediate 404/409 with the real reason, not a silent no-op. There is deliberately no recent-activity gate here (TOS-7771): a forced cycle is for testing and power use; only the scheduled dispatcher waits for the Mind to go quiet. While it runs, /sleep-status reports state: "sleeping" and the /sleep-report timeline records the episode with trigger_reason: "administrative".