docs: finalize feat_auto_followup_studies post-PR-223 merge

docs/00_overview/DASHBOARD.md

@@ -1,12 +1,12 @@
 # RelyLoop — Release Roadmap
 
-_Top-level index across MVP1 → GA v1+ as of **2026-05-23**. Click a release name to drill into the per-release dashboard. Theme labels sourced from [`docs/01_architecture/tech-stack.md` §"Canonical release matrix"](../01_architecture/tech-stack.md). For the rich local view, open [`dashboard.html`](dashboard.html) in a browser._
+_Top-level index across MVP1 → GA v1+ as of **2026-05-24**. Click a release name to drill into the per-release dashboard. Theme labels sourced from [`docs/01_architecture/tech-stack.md` §"Canonical release matrix"](../01_architecture/tech-stack.md). For the rich local view, open [`dashboard.html`](dashboard.html) in a browser._
 
 ## Releases
 
 | Release | Theme | Progress | Status |
 |---|---|---|---|
-| [MVP1 / v0.1](MVP1_DASHBOARD.md) | The Loop | 71 / 72 scoped done · 8 remaining | **In progress** |
+| [MVP1 / v0.1](MVP1_DASHBOARD.md) | The Loop | 72 / 72 scoped done · 7 remaining | **In progress** |
 | [MVP1.5 / v0.1.5](MVP1_5_DASHBOARD.md) | Real Signals | 1 item(s) queued | **Held / queued** |
 | [MVP2 / v0.2](MVP2_DASHBOARD.md) | Observable | 1 / 1 scoped done · 1 remaining | **In progress** |
 | MVP3 / v0.3 | Production Stacks | — | **Not yet scoped** |

docs/00_overview/MVP1_5_DASHBOARD.md

@@ -2,7 +2,7 @@
 
 # RelyLoop MVP1.5 Dashboard
 
-_Reflects feature-folder state as of **2026-05-23** (latest mtime of any planned/implemented feature `.md` file). Regenerated by `make dashboard` and the `mvp1-dashboard-regen` pre-commit hook. For the rich local view (filter chips, type colors), open [`mvp1_5_dashboard.html`](mvp1_5_dashboard.html) in a browser._
+_Reflects feature-folder state as of **2026-05-24** (latest mtime of any planned/implemented feature `.md` file). Regenerated by `make dashboard` and the `mvp1-dashboard-regen` pre-commit hook. For the rich local view (filter chips, type colors), open [`mvp1_5_dashboard.html`](mvp1_5_dashboard.html) in a browser._
 
 ## Next up
 

docs/00_overview/MVP1_DASHBOARD.md

@@ -2,42 +2,37 @@
 
 # RelyLoop MVP1 Dashboard
 
-_Reflects feature-folder state as of **2026-05-23** (latest mtime of any planned/implemented feature `.md` file). Regenerated by `make dashboard` and the `mvp1-dashboard-regen` pre-commit hook. For the rich local view (filter chips, type colors), open [`mvp1_dashboard.html`](mvp1_dashboard.html) in a browser._
+_Reflects feature-folder state as of **2026-05-24** (latest mtime of any planned/implemented feature `.md` file). Regenerated by `make dashboard` and the `mvp1-dashboard-regen` pre-commit hook. For the rich local view (filter chips, type colors), open [`mvp1_dashboard.html`](mvp1_dashboard.html) in a browser._
 
 ## Next up
 
-**[feat_auto_followup_studies](../02_product/planned_features/feat_auto_followup_studies/feature_spec.md)** — Feature, currently in **Implementing**
+All scoped MVP1 features shipped 🎉
 
-> A relevance engineer can opt into auto-chaining on a per-study basis by setting `studies.config.auto_followup_depth` in the create-study wizard (or the `create_study` agent tool).
-
-Implementation in progress — resume to finish
-
-```bash
-/impl-execute docs/02_product/planned_features/feat_auto_followup_studies/implementation_plan.md --all  # resume in-progress
-```
+Pull from the Idea backlog or capture a new feature spec.
 
 ## MVP1 Progress
 
 | Metric | Value |
 |---|---|
-| Scoped items done | **71 / 72** (99%) — feat_/infra_/chore_/epic_ past idea stage |
-| Pending work | **14** items (every not-done feat/infra/chore/bug across all priorities) |
+| Scoped items done | **72 / 72** (100%) — feat_/infra_/chore_/epic_ past idea stage |
+| Pending work | **13** items (every not-done feat/infra/chore/bug across all priorities) |
 | → P0 — do next | **0** unblocking / paying daily cost |
 | → P1 | **0** high-value, ready when P0 clears |
-| → P2 (default) | 13 important to file, not blocking |
+| → P2 (default) | 12 important to file, not blocking |
 | → Backlog | 1 captured for record, not planned |
 | Open bugs | 0 |
-| Legacy "Path to MVP1" | 8 items — scoped-not-done + bugs + chore-ideas only (excludes feat/infra ideas) |
+| Legacy "Path to MVP1" | 7 items — scoped-not-done + bugs + chore-ideas only (excludes feat/infra ideas) |
 | Backlog ideas | 6 idea-only feat/infra (not yet scoped into MVP1) |
-| In flight | 1 feature(s) actively shipping |
+| In flight | 0 feature(s) actively shipping |
 
 ## Pipeline
 
-### Done (88)
+### Done (89)
 
 | Feature | Type | One-liner | Depends on | Status |
 |---|---|---|---|---|
 | [feat_agent_propose_search_space](implemented_features/2026_05_21_feat_agent_propose_search_space/feature_spec.md) | Feature | A new read-only agent tool `propose_search_space(template_id, cluster_id, judgment_list_id?, prior_study_id?) → SearchSpace JSON` that emits a deterministic, code-generated search space using the same | — | [PR #175](https://github.com/SoundMindsAI/relyloop/pull/175) merged 2026-05-21 |
+| [feat_auto_followup_studies](implemented_features/2026_05_24_feat_auto_followup_studies/feature_spec.md) | Feature | A relevance engineer can opt into auto-chaining on a per-study basis by setting `studies.config.auto_followup_depth` in the create-study wizard (or the `create_study` agent tool). | — | [PR #223](https://github.com/SoundMindsAI/relyloop/pull/223) merged 2026-05-24 |
 | [feat_chat_agent](implemented_features/2026_05_12_feat_chat_agent/feature_spec.md) | Feature | A chat surface at `/chat/{conversation_id}` streams OpenAI completions via SSE. | `feat_digest_proposal` `feat_github_pr_worker` `feat_github_webhook` `feat_llm_judgments` `feat_proposals_ui` `feat_studies_ui` `feat_study_lifecycle` `infra_adapter_elastic` `infra_foundation` `infra_optuna_eval` | [PR #60](https://github.com/SoundMindsAI/relyloop/pull/60) merged 2026-05-12 |
 | [feat_cluster_target_filter](implemented_features/2026_05_20_feat_cluster_target_filter/feature_spec.md) | Feature | Each registered cluster can optionally carry a glob pattern (`products*`, `team-a-*`, `docs-[ef][nr]-*`) that scopes `list_targets()` to the matching subset. | — | [PR #168](https://github.com/SoundMindsAI/relyloop/pull/168) merged 2026-05-20 |
 | [feat_config_repo_baseline_tracking](implemented_features/2026_05_23_feat_config_repo_baseline_tracking/feature_spec.md) | Feature | A single denormalized FK `config_repos.last_merged_proposal_id` points at the most recently merged proposal for each config repo. | — | [PR #202](https://github.com/SoundMindsAI/relyloop/pull/202) merged 2026-05-23 |
@@ -126,11 +121,9 @@ Implementation in progress — resume to finish
 | [bug_test_smoke_requires_env_vars](implemented_features/2026_05_13_bug_test_smoke_requires_env_vars/idea.md) | Bug | `backend/tests/unit/test_smoke.py::test_app_import` fails when run without `DATABASE_URL_FILE` and `POSTGRES_PASSWORD_FILE` env vars in the test environment: | — | Complete |
 | [bug_worker_optuna_init_race](implemented_features/2026_05_13_bug_worker_optuna_init_race/idea.md) | Bug | Compose ordering: | — | Complete |
 
-### Implementing (1)
+### Implementing (0)
 
-| # | Priority | Feature | Type | One-liner | Depends on | Status |
-|---|---|---|---|---|---|---|
-| 1 | P2 | [feat_auto_followup_studies](../02_product/planned_features/feat_auto_followup_studies/feature_spec.md) | Feature | A relevance engineer can opt into auto-chaining on a per-study basis by setting `studies.config.auto_followup_depth` in the create-study wizard (or the `create_study` agent tool). | — | [PR #223](https://github.com/SoundMindsAI/relyloop/pull/223) |
+_None._
 
 ### Plan (0)
 
@@ -169,8 +162,6 @@ graph LR
   classDef plan fill:#fef9c3,stroke:#854d0e,color:#854d0e;
   classDef spec fill:#dbeafe,stroke:#1e40af,color:#1e40af;
   classDef idea fill:#f1f5f9,stroke:#334155,color:#334155;
-  feat_auto_followup_studies["auto followup studies"]
-  class feat_auto_followup_studies implement;
   infra_foundation["foundation"]
   class infra_foundation done;
   feat_study_lifecycle["study lifecycle"]
@@ -313,6 +304,8 @@ graph LR
   class feat_config_repo_baseline_tracking done;
   infra_ir_measures_migration["ir measures migration"]
   class infra_ir_measures_migration done;
+  feat_auto_followup_studies["auto followup studies"]
+  class feat_auto_followup_studies done;
   feat_study_lifecycle --> feat_digest_proposal
   feat_llm_judgments --> feat_digest_proposal
   infra_foundation --> feat_llm_judgments

docs/00_overview/MVP2_DASHBOARD.md

@@ -2,7 +2,7 @@
 
 # RelyLoop MVP2 Dashboard
 
-_Reflects feature-folder state as of **2026-05-23** (latest mtime of any planned/implemented feature `.md` file). Regenerated by `make dashboard` and the `mvp1-dashboard-regen` pre-commit hook. For the rich local view (filter chips, type colors), open [`mvp2_dashboard.html`](mvp2_dashboard.html) in a browser._
+_Reflects feature-folder state as of **2026-05-24** (latest mtime of any planned/implemented feature `.md` file). Regenerated by `make dashboard` and the `mvp1-dashboard-regen` pre-commit hook. For the rich local view (filter chips, type colors), open [`mvp2_dashboard.html`](mvp2_dashboard.html) in a browser._
 
 ## Next up
 

docs/00_overview/dashboard.html

@@ -368,7 +368,7 @@
 <header>
   <h1>RelyLoop — Release Roadmap</h1>
   <div class="meta">
-    Top-level index across MVP1 → GA v1+ as of 2026-05-23. Click a release name to
+    Top-level index across MVP1 → GA v1+ as of 2026-05-24. Click a release name to
     drill into the per-release dashboard. Theme labels sourced from
     <a href="../01_architecture/tech-stack.md">tech-stack.md §"Canonical
     release matrix"</a>. See <a href="../../state.md">state.md</a> for
@@ -384,7 +384,7 @@ <h2>Releases</h2>
 <div class="roadmap-row">
   <div class="release-name"><a href="mvp1_dashboard.html">MVP1 / v0.1</a></div>
   <div class="theme">The Loop</div>
-  <div class="progress">71 / 72 scoped done · 8 remaining</div>
+  <div class="progress">72 / 72 scoped done · 7 remaining</div>
   <span class="state-pill in_progress">In progress</span>
 </div>
 

docs/02_product/planned_features/feat_auto_followup_studies/pipeline_status.md → docs/00_overview/implemented_features/2026_05_24_feat_auto_followup_studies/pipeline_status.md

@@ -32,9 +32,9 @@
 - Known UX limitation (deliberate): Cancel-from-completed-root requires operator to navigate to the in-flight descendant. Per D-13 direct-children scoping. Documented in `docs/03_runbooks/auto-followup-debugging.md` (Story 4.1).
 
 ## Implementation
-- Status: In Progress — PR #223 open and CI green; awaiting merge. All 10 stories complete + all 3 phase gates passed.
-- Branch: `feature/auto-followup-studies`
-- PR: [#223](https://github.com/SoundMindsAI/relyloop/pull/223) (opened 2026-05-23, CI all 5 jobs green, Gemini Code Assist 1 Medium accepted + applied, final GPT-5.5 review 2 Medium accepted + shipped).
+- Status: Complete — merged into main as PR #223 squash `20cf183a` on 2026-05-24.
+- Branch: `feature/auto-followup-studies` (deleted post-merge).
+- PR: [#223](https://github.com/SoundMindsAI/relyloop/pull/223) — CI all 5 jobs green, Gemini Code Assist 1 Medium accepted + applied (`auto_followup.py:215` defensive `.get()`), final GPT-5.5 cross-model review 2 Medium accepted + shipped (Story 3.2 wizard depth-selector vitest + Story 3.3 E2E spec).
 - Stories complete (10/10):
   - **Story 1.1** — Chain-gate domain + StudyConfigSpec field + error-handler prefix parser. Commit `b32645c1`.
   - **Story 1.2** — NO-OP discovery: `narrow_around_winner` was already extracted. Commit `33e9ccc7`.

docs/00_overview/mvp1_5_dashboard.html

@@ -369,7 +369,7 @@
   <div class="back-link"><a href="dashboard.html">← Roadmap overview</a></div>
   <h1>RelyLoop MVP1.5 Dashboard</h1>
   <div class="meta">
-    Reflects feature-folder state as of 2026-05-23 (latest mtime of any
+    Reflects feature-folder state as of 2026-05-24 (latest mtime of any
     <code>docs/02_product/planned_features/</code> or
     <code>docs/00_overview/implemented_features/</code> file).
     See <a href="../../state.md">state.md</a> for the active branch context,

docs/00_overview/mvp1_dashboard.html

@@ -369,7 +369,7 @@
   <div class="back-link"><a href="dashboard.html">← Roadmap overview</a></div>
   <h1>RelyLoop MVP1 Dashboard</h1>
   <div class="meta">
-    Reflects feature-folder state as of 2026-05-23 (latest mtime of any
+    Reflects feature-folder state as of 2026-05-24 (latest mtime of any
     <code>docs/02_product/planned_features/</code> or
     <code>docs/00_overview/implemented_features/</code> file).
     See <a href="../../state.md">state.md</a> for the active branch context,
@@ -382,28 +382,28 @@ <h1>RelyLoop MVP1 Dashboard</h1>
 <main>
 
 <section>
-  <div class="next-up">
-    <div class="eyebrow">Next up — Feature, currently in <strong>Implementing</strong></div>
-    <div class="title"><a href="../../docs/02_product/planned_features/feat_auto_followup_studies/feature_spec.md">Auto Followup Studies</a></div>
-    <div class="one-liner">A relevance engineer can opt into auto-chaining on a per-study basis by setting `studies.config.auto_followup_depth` in the create-study wizard (or the `create_study` agent tool).</div>
-    <div class="stage-hint">Implementation in progress — resume to finish</div>
-    <code class="cmd">/impl-execute docs/02_product/planned_features/feat_auto_followup_studies/implementation_plan.md --all  # resume in-progress</code>
+  <div class="next-up done">
+    <div class="eyebrow">Next up</div>
+    <div class="title">All scoped MVP1 features shipped 🎉</div>
+    <div class="one-liner">
+      Pull from the Idea backlog or capture a new feature spec.
+    </div>
   </div>
 </section>
 
 
 <section>
   <h2>MVP1 Progress</h2>
   <div class="kpi-row">
-    <div class="kpi ">
+    <div class="kpi complete">
       <div class="label">Scoped items done</div>
-      <div class="value">71 / 72</div>
-      <div class="sub">99% of feat_/infra_/chore_/epic_ items past idea stage</div>
-      <div class="bar"><span style="width:99%"></span></div>
+      <div class="value">72 / 72</div>
+      <div class="sub">100% of feat_/infra_/chore_/epic_ items past idea stage</div>
+      <div class="bar"><span style="width:100%"></span></div>
     </div>
     <div class="kpi warn">
       <div class="label">Pending work</div>
-      <div class="value">14</div>
+      <div class="value">13</div>
       <div class="sub">every not-done feat/infra/chore/bug across all priorities</div>
     </div>
     <div class="kpi ">
@@ -425,7 +425,7 @@ <h2>MVP1 Progress</h2>
     </div>
     <div class="kpi">
       <div class="label">P2 (default)</div>
-      <div class="value">13</div>
+      <div class="value">12</div>
       <div class="sub">important to file, not blocking</div>
     </div>
     <div class="kpi">
@@ -435,7 +435,7 @@ <h2>MVP1 Progress</h2>
     </div>
     <div class="kpi">
       <div class="label">Legacy "Path to MVP1"</div>
-      <div class="value">8</div>
+      <div class="value">7</div>
       <div class="sub">scoped not-done + bugs + chore-ideas only (excludes feat/infra ideas)</div>
     </div>
   </div>
@@ -446,7 +446,7 @@ <h2>MVP1 Progress</h2>
     </span>
     <span>
       <strong>In flight:</strong>
-      1 feature(s) actively shipping
+      0 feature(s) actively shipping
     </span>
   </div>
 </section>
@@ -646,33 +646,34 @@ <h3>Plan <span class="count">0</span></h3>
 </div>
 
 <div class="col implement">
-  <h3>Implementing <span class="count">1</span></h3>
+  <h3>Implementing <span class="count">0</span></h3>
+
+</div>
+
+<div class="col done">
+  <h3>Done <span class="count">89</span></h3>
 
 <div class="card feat" data-prefix="feat" data-priority="P2">
-  <div class="name"><a href="../../docs/02_product/planned_features/feat_auto_followup_studies/feature_spec.md">Auto Followup Studies</a></div>
+  <div class="name"><a href="../../docs/00_overview/implemented_features/2026_05_21_feat_agent_propose_search_space/feature_spec.md">Agent Propose Search Space</a></div>
   <div class="meta">
     <span class="badge feat">Feature</span>
-    <span class="badge priority" data-priority="P2">P2</span>
-    <a class="pr" href="https://github.com/SoundMindsAI/relyloop/pull/223">PR #223</a>
-  </div>
-  <div class="one-liner">A relevance engineer can opt into auto-chaining on a per-study basis by setting `studies.config.auto_followup_depth` in the create-study wizard (or the `create_study` agent tool).</div>
 
+    <a class="pr" href="https://github.com/SoundMindsAI/relyloop/pull/175">PR #175</a> <span>merged 2026-05-21</span>
+  </div>
+  <div class="one-liner">A new read-only agent tool `propose_search_space(template_id, cluster_id, judgment_list_id?, prior_study_id?) → SearchSpace JSON` that emits a deterministic, code-generated search space using the same</div>
 
-</div>
 
 </div>
 
-<div class="col done">
-  <h3>Done <span class="count">88</span></h3>
 
 <div class="card feat" data-prefix="feat" data-priority="P2">
-  <div class="name"><a href="../../docs/00_overview/implemented_features/2026_05_21_feat_agent_propose_search_space/feature_spec.md">Agent Propose Search Space</a></div>
+  <div class="name"><a href="../../docs/00_overview/implemented_features/2026_05_24_feat_auto_followup_studies/feature_spec.md">Auto Followup Studies</a></div>
   <div class="meta">
     <span class="badge feat">Feature</span>
 
-    <a class="pr" href="https://github.com/SoundMindsAI/relyloop/pull/175">PR #175</a> <span>merged 2026-05-21</span>
+    <a class="pr" href="https://github.com/SoundMindsAI/relyloop/pull/223">PR #223</a> <span>merged 2026-05-24</span>
   </div>
-  <div class="one-liner">A new read-only agent tool `propose_search_space(template_id, cluster_id, judgment_list_id?, prior_study_id?) → SearchSpace JSON` that emits a deterministic, code-generated search space using the same</div>
+  <div class="one-liner">A relevance engineer can opt into auto-chaining on a per-study basis by setting `studies.config.auto_followup_depth` in the create-study wizard (or the `create_study` agent tool).</div>
 
 
 </div>
@@ -1821,8 +1822,6 @@ <h2>Dependency graph (feat_ + infra_)</h2>
   classDef plan fill:#fef9c3,stroke:#854d0e,color:#854d0e;
   classDef spec fill:#dbeafe,stroke:#1e40af,color:#1e40af;
   classDef idea fill:#f1f5f9,stroke:#334155,color:#334155;
-  feat_auto_followup_studies[&quot;auto followup studies&quot;]
-  class feat_auto_followup_studies implement;
   infra_foundation[&quot;foundation&quot;]
   class infra_foundation done;
   feat_study_lifecycle[&quot;study lifecycle&quot;]
@@ -1965,6 +1964,8 @@ <h2>Dependency graph (feat_ + infra_)</h2>
   class feat_config_repo_baseline_tracking done;
   infra_ir_measures_migration[&quot;ir measures migration&quot;]
   class infra_ir_measures_migration done;
+  feat_auto_followup_studies[&quot;auto followup studies&quot;]
+  class feat_auto_followup_studies done;
   feat_study_lifecycle --&gt; feat_digest_proposal
   feat_llm_judgments --&gt; feat_digest_proposal
   infra_foundation --&gt; feat_llm_judgments
@@ -2018,8 +2019,6 @@ <h2>Dependency graph (feat_ + infra_)</h2>
   classDef plan fill:#fef9c3,stroke:#854d0e,color:#854d0e;
   classDef spec fill:#dbeafe,stroke:#1e40af,color:#1e40af;
   classDef idea fill:#f1f5f9,stroke:#334155,color:#334155;
-  feat_auto_followup_studies[&quot;auto followup studies&quot;]
-  class feat_auto_followup_studies implement;
   infra_foundation[&quot;foundation&quot;]
   class infra_foundation done;
   feat_study_lifecycle[&quot;study lifecycle&quot;]
@@ -2162,6 +2161,8 @@ <h2>Dependency graph (feat_ + infra_)</h2>
   class feat_config_repo_baseline_tracking done;
   infra_ir_measures_migration[&quot;ir measures migration&quot;]
   class infra_ir_measures_migration done;
+  feat_auto_followup_studies[&quot;auto followup studies&quot;]
+  class feat_auto_followup_studies done;
   feat_study_lifecycle --&gt; feat_digest_proposal
   feat_llm_judgments --&gt; feat_digest_proposal
   infra_foundation --&gt; feat_llm_judgments

docs/00_overview/mvp2_dashboard.html

@@ -369,7 +369,7 @@
   <div class="back-link"><a href="dashboard.html">← Roadmap overview</a></div>
   <h1>RelyLoop MVP2 Dashboard</h1>
   <div class="meta">
-    Reflects feature-folder state as of 2026-05-23 (latest mtime of any
+    Reflects feature-folder state as of 2026-05-24 (latest mtime of any
     <code>docs/02_product/planned_features/</code> or
     <code>docs/00_overview/implemented_features/</code> file).
     See <a href="../../state.md">state.md</a> for the active branch context,