chore(workplan): activate CYA-WP-0004 for ralph execution (status: active)

workplans/CYA-WP-0004-dev-install-and-release-packaging.md

@@ -4,12 +4,12 @@ type: workplan
 title: "Developer Installation from Git and Release Distribution Packaging"
 domain: capabilities
 repo: can-you-assist
-status: proposed
+status: active
 owner: grok
 topic_slug: foerster-capabilities
 created: "2026-05-27"
 updated: "2026-05-27"
-state_hub_workstream_id: null
+state_hub_workstream_id: "7913b919-d76b-4374-bdc6-0330fe941666"
 ---
 
 # CYA-WP-0004: Developer Installation from Git and Release Distribution Packaging
@@ -50,7 +50,7 @@ This workplan addresses the current gap where only `pip install -e .` (editable
 id: CYA-WP-0004-T01
 status: todo
 priority: high
-state_hub_task_id: null
+state_hub_task_id: "018d0c4c-948e-4cd6-9a50-92a83725df18"
 ```
 
 - Review the current `pyproject.toml`, `src/` layout, entry points, and any hidden packaging assumptions.
@@ -70,7 +70,7 @@ state_hub_task_id: null
 id: CYA-WP-0004-T02
 status: todo
 priority: high
-state_hub_task_id: null
+state_hub_task_id: "0728680e-f9a9-4229-afcc-6c4d42d2e447"
 ```
 
 - Implement the chosen versioning approach in `pyproject.toml`.
@@ -88,7 +88,7 @@ state_hub_task_id: null
 id: CYA-WP-0004-T03
 status: todo
 priority: high
-state_hub_task_id: null
+state_hub_task_id: "14e085dd-847a-4678-a1e4-abe5e3c369aa"
 ```
 
 - Ensure `pip install "git+https://github.com/worsch/can-you-assist.git"` (and branch variants) works cleanly.
@@ -106,7 +106,7 @@ state_hub_task_id: null
 id: CYA-WP-0004-T04
 status: todo
 priority: high
-state_hub_task_id: null
+state_hub_task_id: "d49a3362-865f-4397-b127-372a2aa2c4a2"
 ```
 
 - Adopt the modern `build` frontend (`python -m build`).
@@ -124,7 +124,7 @@ state_hub_task_id: null
 id: CYA-WP-0004-T05
 status: todo
 priority: medium
-state_hub_task_id: null
+state_hub_task_id: "c97acc58-14d7-47b9-9ab3-936ab1eb92df"
 ```
 
 - Document (and optionally script) the steps to cut a release:
@@ -146,7 +146,7 @@ state_hub_task_id: null
 id: CYA-WP-0004-T06
 status: todo
 priority: high
-state_hub_task_id: null
+state_hub_task_id: "5a4dcdf8-7b0f-45cb-8eb1-46b0d60f8420"
 ```
 
 - Update README.md with clear sections for:
@@ -164,7 +164,7 @@ state_hub_task_id: null
 id: CYA-WP-0004-T07
 status: todo
 priority: medium
-state_hub_task_id: null
+state_hub_task_id: "f4ea08ab-219e-4e7f-86b9-a05e27b8a72c"
 ```
 
 - Add basic packaging verification to the development workflow (e.g., `make check-dist` or a CI step).
@@ -180,10 +180,10 @@ state_hub_task_id: null
 - Future PyPI publication may involve coordination with whatever hosting or automation is chosen later.
 - State Hub will be used to track the workplan and any packaging-related decisions or debt.
 
-## Proposed Status & Activation
+## Activation & Ralph Execution
 
-This workplan is created in `proposed` status. It should be reviewed, moved to `ready`, and activated when the team is ready to invest in making `cya` easily installable both for the primary user (from dev head) and for potential future users/contributors via proper packages.
+**Status: active** — activated for ralph-workplan loop execution (HEUREKA promise, max 20 iterations). This workplan addresses the practical gap where only editable development installs were supported, by enabling reliable installation from the development head and creating a repeatable process for versioning and building distribution packages.
 
 ---
 
-**Status note**: This workplan closes an important practical gap. Until now the project has been developed in a "works on my machine via editable install" mode. This workplan makes the tool usable by its primary user from the latest code and creates the foundation for others to consume it as a normal Python package.
+**Status note**: This workplan closes an important practical gap. It makes `cya` usable from the latest code for the primary user and creates the foundation for proper releases.