Add remote session loading

docs/roadmap/remote.md

@@ -2,13 +2,13 @@
 
 ## Purpose
 
-This roadmap describes planned, unimplemented work for three related feature areas:
+This roadmap tracks implementation work for three related feature areas:
 
 1. `campaign.yml` configuration for stable campaign-level inputs.
 2. Remote `session.yml` loading from the existing S3 object-store backend.
 3. Logical archive locks that prevent selected top-level transcript/artifact promotions from overwriting curated archive state while still preserving run-local outputs.
 
-Treat this document as an implementation plan, not as current behavior. Keep planned behavior under `docs/roadmap/` until each phase is implemented and canonical docs are updated.
+Treat future sections of this document as an implementation plan, not as current behavior. Keep planned behavior under `docs/roadmap/` until each item is implemented and canonical docs are updated.
 
 ## Current Code Facts
 
@@ -43,7 +43,7 @@ Implementation must preserve these constraints:
 - Keep raw secrets out of configs, manifests, logs, generated configs, archive metadata, and roadmap examples.
 - Update canonical user-facing docs only after behavior is implemented.
 
-## Phase 1: Add `campaign.yml`
+## Phase 1: Add `campaign.yml` (implemented)
 
 Add campaign-level configuration for stable campaign identity and stable input files. Do not add remote campaign loading in this phase.
 
@@ -116,7 +116,7 @@ Update `prepare` to materialize the resolved campaign/session inputs into canoni
 
 Continue recording deterministic `manifest.Inputs` records with checksums. If a prepared input came from `campaign.yml`, record source/provenance using the existing manifest input fields where practical; add narrow metadata only if the existing fields cannot describe it.
 
-## Phase 2: Load Remote `session.yml`
+## Phase 2: Load Remote `session.yml` (implemented)
 
 Support running with no local session file when a remote session file exists under the canonical session prefix.