validate-hypothesislisted

# Hypothesis Validator Invokes **hypothesis-tester** agent to validate design assumptions. Supports two modes: - **Feature-bound** (FEATURE_ID provided): validates hypotheses from an existing `hypotheses.md` artifact - **Ad-hoc** (HYPOTHESIS provided, no FEATURE_ID): validates a free-form hypothesis without feature context ## Input Validation At least one of FEATURE_ID or HYPOTHESIS must be provided. If neither is set: ``` ERROR: Provide either FEATURE_ID (for feature-bound validation) or --hypothesis "text" (for ad-hoc validation). ``` ### Mode Selection Mode is determined by feature-directory existence, not argument precedence: 1. If FEATURE_ID is set AND `{workRoot}/features/{FEATURE_ID}/` exists -> **feature-bound mode**. 2. If FEATURE_ID is set AND `{workRoot}/features/{FEATURE_ID}/` does NOT exist: - If HYPOTHESIS is also populated -> combine as `HYPOTHESIS = "{FEATURE_ID} {HYPOTHESIS}"`, clear FEATURE_ID -> **ad-hoc mode**. - If HYPOTHESIS is empty (lone token, no matching directory) -> error: ``` ERROR: Feature directory not found: {workRoot}/features/{FEATURE_ID}/ For ad-hoc validation, use: --hypothesis "your scenario description" ``` 3. If only HYPOTHESIS is set (no FEATURE_ID) -> **ad-hoc mode**. ## Execution ### Feature-bound Mode (FEATURE_ID provided) #### Prerequisites - `{workRoot}/features/{FEATURE_ID}/hypotheses.md` MUST exist - Created by the feature-architect agent during the design phase when high-risk assumptions are