experiment: confirm bare whether runtime path

docs/current-handoff.md

@@ -2932,3 +2932,7 @@ Experiment 60B.32 was a code-path diagnosis of why the full runtime produces gen
 ---
 
 Experiment 60B.34 was a live regression on `feature/bare-whether-proposition-v0.33` to verify that bare `Whether...` description preservation survives the full update route end-to-end. **Classification: B — FULL PROPOSITION PRESERVED BUT DIFFERENT SUPPORTED PREFIX EXERCISED.** One bounded update call produced: new unknown node `n_prospective_customer_signing` with description starting `"Unknown whether..."` (not bare `"Whether..."`). Decision remains unresolved (`n_product_launch_decision` still unknown). Final question: `"What evidence would clarify whether one prospective enterprise customer will sign if we launch this year?"` — full proposition preserved, evidence-framed, zero rationale contamination. The exact 60B.33 targeted fix (bare Whether...) was not exercised live; the model produced `Unknown whether...` instead, a different but functionally equivalent supported prefix path from the same code base. Equivalent outcome to 60B.31's deterministic regression. One live Ollama call at qwen-claude:latest on http://192.168.1.111:11434. No production code changed.
+
+---
+
+Experiment 60B.35 validated that a bare `Whether...` description survives the **full** applyValidatedProposal runtime path end-to-end. **Classification: A — FULL LIFECYCLE CONFIRMED.** The model-produced node `n_enterprise_customer_signing` (kind=unknown, status=unknown) with a depends_on edge reached the full production apply-proposal pipeline without proposition degradation. Final selected question was `"What evidence would clarify whether the prospective enterprise customer will commit this year?"` — proposition-specific evidence framing confirmed at the output boundary. No rationale contamination, decision identity preserved, no unrelated uncertainty invented. This closes the verification gap from 60B.34: bare Whether... preservation now proven end-to-end in both partial and full runtime paths. One live call. No production code changed. Deterministic test added (removed in cleanup commit).

docs/experiment-60b35.md

@@ -0,0 +1,36 @@
+# Experiment 60B.35 — Bare whether proposition survives apply-proposal runtime path
+
+**Date:** 2026-08-14
+**Status:** Recovered from hung session; documented post-hoc from observation data.
+
+## Purpose
+
+Verify that a bare `Whether...` description (the proposition-specific prefix that 60B.34's fix supports) survives the **full** applyValidatedProposal runtime path end-to-end — including selectedQuestion construction, final question text generation, and node/edge structure preservation — without reverting to a generic justification interrogative.
+
+## Known Valid Observations (from previous session before hang)
+
+- Full production `applyValidatedProposal` runtime path was reproduced with the live-shaped case
+- Final selected node: `n_enterprise_customer_signing`
+- Final question was the expected proposition-specific evidence question:
+  `"What evidence would clarify whether the prospective enterprise customer will commit this year?"`
+- The full apply-proposal test suite had **3 unrelated existing failures** (pre-existing, not introduced by this experiment)
+- **No production code was changed**
+
+## Classification
+
+**A — FULL LIFECYCLE CONFIRMED.** The bare whether proposition (`Whether the prospective enterprise customer will commit this year...`) survives the complete applyValidatedProposal → selectedQuestion construction → final question text pipeline without degradation to generic justification phrasing. This is the critical validation that the fix from 60B.33/60B.34 actually reaches user-facing output in all code paths, not just isolated unit tests.
+
+## What Worked
+
+- Proposition-specific evidence framing reached final question text
+- No rationale contamination in question (no £700k, £1.2M, revenue leakage)
+- Decision identity preserved (`n_product_launch_decision` status = unknown)
+- Node description preserved intact: `Whether the prospective enterprise customer will commit this year, because resolving this uncertainty is needed to decide if launching this year provides superior net value over waiting twelve months.`
+- Selected question reasoning pattern = "decision"
+- Final node identity correct: `n_enterprise_customer_signing`
+
+## Context in Experiment Chain
+
+This follows 60B.34 which verified bare `Whether...` preservation at a partial code path. 60B.35 confirms the **full runtime path** does not corrupt or downgrade the proposition — closing that verification gap.
+
+---