docs(3.0): ag-p7j W2 — reframe core narrative docs to in-session (ag-p7j) (#527)

## What

Worker 2 of the ag-p7j 3-way swarm reconciling stale daemon/scheduler
references for AgentOps 3.0. Reframes stale `ao daemon` / `agentopsd` /
`ao schedule` / `ao overnight` prose across 7 core narrative docs to the
**in-session model**: the loop runs in session (the product +
sovereignty floor); always-on / scheduled / unattended execution is
delegated to an orchestration substrate (Gas City is the reference
City), not an AgentOps surface. Those daemon/scheduler/overnight-runner
surfaces were deleted in the 3.0 rearchitecture (ADR-0009). Mirrors
`docs/3.0.md`.

## Files (7, prose only)

- `docs/software-factory.md` — Runtime Variants daemon-submit lane →
in-session `ao rpi phased`; Surface Map drops `ao daemon submit`, adds
an out-of-session (substrate) row; "both paths" note now in-session +
Gas City delegation.
- `docs/cdlc.md` — SDLC→CDLC table: "Software factory daemon (`ao
daemon`)" → in-session loop run on a substrate (Gas City reference).
- `docs/how-it-works.md` — Dream split intro + "Dream — Private
Overnight Operator Mode" section reframed from `ao overnight` to
in-session `/dream` + CLI primitives; unattended = Gas City substrate.
- `docs/philosophy.md` — `/dream and ao overnight` → `/dream` in
session, out-of-session compounding on Gas City.
- `docs/first-value-path.md` — intro item 6, Time-Budget row, Step 7
"Optional Scheduled Lane" (`ao daemon run` / `ao schedule`) → "Optional
Out-of-Session Lane" (Gas City mayor/refinery); First-Artifacts and
Friction rows updated.
- `docs/workflows/session-lifecycle.md` — Option 3 "Bedtime Dream Run"
(`ao overnight setup/start/report`) → "Dream Compounding Run" (`/dream`
foreground); runtime-modes table row updated.
- `docs/architecture/ports-and-adapters.md` — Autonomous-loops adapter
bullet: `agentopsd daemon scheduler` removed; `/dream`,`/evolve` framed
as in-session driving adapters with out-of-session delegated to the
substrate.

No links to deleted daemon contracts existed in these files (verified).
No edits outside the 7.

## Gates

- `grep -E "ao daemon |agentopsd|ao schedule"` across the 7 files:
**CLEAN** (also clean for `ao overnight`/`ao plans`/`ao
watch`/`schedule.yaml`/`--with-schedule`).
- `markdownlint` on the 7 files: **PASS** (exit 0).
- `mkdocs build --strict`: **PASS** (exit 0; only the generic Material
upgrade banner, no link warnings/errors).
- doc-release gate (`tests/docs/validate-doc-release.sh`): **PASS**.
- learning-references check: **PASS**.

Diff stat: 7 files, +65/-72 — balanced, no collateral data loss.

Closes-scenario: ag-p7j#w2-core-docs
Bounded-context: BC1-Corpus
Evidence: docs/software-factory.md

docs/workflows/session-lifecycle.md

@@ -44,29 +44,31 @@ ao codex status
 the corpus can support it, run Codex startup, then move into RPI. The lower
 level lifecycle commands still exist when you want direct control.
 
-### Option 3: Bedtime Dream Run
+### Option 3: Dream Compounding Run
 
 ```bash
-# One-time bootstrap / scheduler guidance
-ao overnight setup --apply --runner codex --runner claude --at 01:30
-
-# Start a private overnight run now
-ao overnight start --goal "close the loop on today's auth work"
-
-# In the morning
-ao overnight report --from .agents/overnight/latest
+# A foreground compounding session against the real local .agents corpus
+/dream "close the loop on today's auth work"
 ```
 
-Use this when you want AgentOps to work against the real local `.agents` corpus
-while you are away. This is not the same as the GitHub nightly workflow:
+The session drives the CLI primitives that do the work — `ao compile`,
+`ao maturity --scan`, `ao flywheel close-loop` — and writes the `summary.json` /
+`summary.md` report contract.
 
-- GitHub nightly is the public CI proof harness
-- `ao overnight` is the private local compounding engine
+Use this when you want AgentOps to compound against the real local `.agents`
+corpus in a session you can watch. This is not the same as the GitHub nightly
+workflow:
 
-Scheduling is still external, but Dream now helps you bootstrap it honestly.
-Use `ao overnight setup` to detect the host, persist `dream.*` config, and
-generate scheduler assistance artifacts for `launchd`, `cron`, or `systemd`
-without pretending sleeping laptops have guaranteed wake behavior.
+- GitHub nightly is the public CI proof harness for the report contract
+- `/dream` is the private local compounding engine, run in session
+
+**Running Dream unattended is out-of-session orchestration**, which AgentOps
+3.0 delegates to a substrate rather than shipping its own daemon, scheduler, or
+overnight runner — those surfaces were deleted (see
+[AgentOps 3.0 north star](../3.0.md)). On the reference substrate (Gas City), a
+long-lived agent runs `/dream`-equivalent maintenance Orders on a cron `exec`
+schedule. The substrate owns when and where; AgentOps owns what the loop does.
+No tool pretends a sleeping laptop has guaranteed wake behavior.
 
 ### Option 4: Lower-Level Codex Lifecycle
 
@@ -111,7 +113,7 @@ SessionEnd would normally run.
 | Hook-capable | Natural language, `/session-start`, or startup hooks | Natural language, `/session-end`, or session-end hooks | Best fit for Claude/OpenCode when hooks are installed; `CLAUDE.md` is the startup surface and hooks stage state silently |
 | Codex optional native hooks | Quiet native `SessionStart` maintenance plus explicit `ao codex start` / `ao codex ensure-start` when context retrieval is needed | Native `Stop` hook for turn-scope close-loop; explicit `ao codex stop` / `ao codex ensure-stop` for transcript-driven closeout | Opt-in with `install-codex.sh --with-hooks`; startup hooks stay quiet and no native `SessionEnd` event exists today |
 | Codex hookless default | `ao factory start --goal "<goal>"`, `ao rpi phased`, `ao codex start`, or skill-driven `ao codex ensure-start` | `ao codex stop` or skill-driven `ao codex ensure-stop` | No startup/session-end hook surface required; lifecycle is explicit, and closeout owns the same curation hygiene as SessionEnd |
-| Dream overnight run | `ao overnight setup --apply` then `ao overnight start --goal "<goal>"` | `ao overnight report --from <dir>` | Private local overnight mode. Dream bootstraps config and scheduler assistance, while the host OS still owns actual scheduling semantics |
+| Dream compounding run | `/dream "<goal>"` (foreground, in session) | Reads `summary.json` / `summary.md` from the run dir | Private local compounding in a watchable session. Running it unattended is out-of-session orchestration, delegated to a substrate (Gas City is the reference) — AgentOps ships no daemon or scheduler |
 | Manual fallback | `ao inject`, `ao lookup` | `ao forge transcript`, `ao flywheel close-loop` | Lowest-level portable path |
 
 ---