chore(workplan): activate CYA-WP-0001 + record operator decisions

- Frontmatter: status `ready` → `active`
- Added "Status Update — 2026-05-26 (Activated)" section documenting
  the resolved stack choices and the specific direction on T03 (safety)
  and T05 (phase-memory).
- Annotated the T03 and T05 task descriptions with the operator's
  explicit guidance (rule-based risk assessment first + ADR requirement;
  strictly minimal no-op ports for memory).
- Linked the resolved State Hub Decision `a644364b-11c4-49a9-bf17-99063382e27b`.
- Updated Current Evidence to reflect bootstrap completion and activation.

This authorizes implementation of the narrow console-native MVP slice
to begin (starting with T01).

Resolves: State Hub Decision D1 (now `resolved`)

workplans/CYA-WP-0001-console-native-mvp.md

@@ -4,15 +4,33 @@ type: workplan
 title: "Console-Native MVP: CLI Skeleton, Safe Assistance Flow, and Integration Boundaries"
 domain: capabilities
 repo: can-you-assist
-status: ready
+status: active
 owner: grok
 topic_slug: foerster-capabilities
 created: "2026-05-25"
-updated: "2026-05-25"
+updated: "2026-05-26"
+state_hub_decision_id: "a644364b-11c4-49a9-bf17-99063382e27b"
 ---
 
 # CYA-WP-0001: Console-Native MVP — CLI Skeleton, Safe Assistance Flow, and Integration Boundaries
 
+## Status Update — 2026-05-26 (Activated)
+
+This workplan is moved from `ready` to `active` immediately following resolution of State Hub Decision `a644364b-11c4-49a9-bf17-99063382e27b`.
+
+**Stack technology choices (accepted per agent recommendations):**
+- Primary language/runtime: **Python**
+- CLI framework: **Typer**
+- Terminal presentation: **rich**
+- Configuration format: **TOML** (alignment with sibling patterns)
+- Packaging/layout: **Full modern Python package** (`pyproject.toml` + `src/` layout) from day 1
+
+**Additional operator direction recorded in the decision:**
+- **Phase-memory integration (T05):** Keep strictly minimal. Pure explicit ports / no-op implementations with clear "replace with real phase-memory integration" markers. No placeholder local JSON file or store in this slice.
+- **Safety / risk classification (T03):** Implement genuine rule-based assessment as the primary mechanism. Surface the classification results to the LLM as structured context where relevant. The LLM is allowed to propose actions or refine classifications, but any architecture-level, policy, or significant design decisions that arise must be captured as ADRs in this repository.
+
+The narrow MVP slice is now authorized to proceed. Implementation of T01 (scaffolding + Typer CLI entrypoint) can begin.
+
 ## Goal
 
 Deliver the first narrow, usable slice of `cya` (the can-you-assist console assistant) that proves the core loop:
@@ -24,7 +42,7 @@ This workplan establishes the CLI surface, context collector, safety layer, and
 ## Current Evidence
 
 - High-quality intent, scope, and agent instruction documents exist and are consistent (INTENT.md, SCOPE.md, AGENTS.md, README.md, wiki/CyaSpeechModeExtension.md).
-- State Hub bootstrap workstream `repo-integration-can-you-assist` (id `0a1233fd-75ab-4726-8857-6c97de939069`) is active. Its Task T02 ("Write first workplan and initialise workplans/") is the direct driver for creating this file.
+- State Hub bootstrap workstream `repo-integration-can-you-assist` (id `0a1233fd-75ab-4726-8857-6c97de939069`) — both bootstrap tasks are now complete. Decision D1 (`a644364b-11c4-49a9-bf17-99063382e27b`) has been resolved with the choices above; this workplan is now `active`.
 - Sibling projects exist and are further along:
   - `llm-connect` (real Python package with multi-provider adapters, config, tests).
   - `phase-memory` (foundational workplans complete; local runtime, ports, and contracts exist).
@@ -120,6 +138,8 @@ priority: high
 
 This is a core product behavior, not an afterthought.
 
+**Operator direction (2026-05-26):** Implement genuine rule-based assessment as the primary mechanism. Provide the classification results to the LLM as structured context where relevant. The LLM may propose or refine, but any architecture-level or policy decisions that surface must be raised as ADRs.
+
 Build a risk classifier (simple rules + optional LLM assistance for edge cases) that labels suggestions as one of:
 
 - safe
@@ -180,6 +200,8 @@ priority: medium
 
 Prepare the ground for `phase-memory` without pulling a dependency or inventing hidden state.
 
+**Operator direction (2026-05-26):** Keep strictly minimal in this slice. Pure explicit ports with no-op implementations and clear "to be replaced by real phase-memory integration" markers. No local JSON placeholder or file-backed store yet.
+
 Define clear ports / extension points for the memory capabilities that INTENT.md says must remain under user control:
 
 - Remember a preference or workflow pattern.