docs + chore(workplan): complete T06 and T07 for CYA-WP-0004 — final documentation polish and packaging debt registration

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

@@ -167,35 +167,43 @@ completed: "2026-05-27"
 
 ```task
 id: CYA-WP-0004-T06
-status: todo
+status: done
 priority: high
 state_hub_task_id: "5a4dcdf8-7b0f-45cb-8eb1-46b0d60f8420"
+started: "2026-05-27 ralph iter 6 (final docs)"
+completed: "2026-05-27"
 ```
 
-- Update README.md with clear sections for:
-  - Development / bleeding-edge install (from git)
-  - Installing a released version (when available)
-- Update AGENTS.md "Commands" section.
-- Add any necessary notes in the new workplan or a dedicated packaging guide.
+**Done.**
 
-**Acceptance criteria**:
-- Both installation methods are clearly documented and discoverable by someone reading the README.
+- Significantly polished the Installation section in README.md to clearly distinguish:
+  - Development / bleeding-edge installs (via `make dev-install` or direct `git+`)
+  - Future path for released versions
+- Added references to `docs/release-process.md`
+- Updated AGENTS.md "Commands" section with packaging-related Makefile targets and the current workplan reference.
+
+**Acceptance criteria met**:
+- Both installation methods are now clearly documented and easy to discover in the README.
 
 ### T07 — Register packaging as a first-class concern
 
 ```task
 id: CYA-WP-0004-T07
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "f4ea08ab-219e-4e7f-86b9-a05e27b8a72c"
+started: "2026-05-27 ralph iter 7 (final)"
+completed: "2026-05-27"
 ```
 
-- Add basic packaging verification to the development workflow (e.g., `make check-dist` or a CI step).
-- Document known limitations and future improvements (e.g., PyPI publishing, automated releases, signed packages).
-- Register this area as an extension point / debt item in State Hub via the workplan.
+**Done.**
 
-**Acceptance criteria**:
-- Packaging is no longer an afterthought — it has documented ownership and a path forward.
+- `make check-dist` already exists and is promoted as the packaging verification step.
+- Added a clear "Debt & Future Work (Registered)" section in the workplan itself, explicitly listing PyPI publishing, automated releases, package signing, CI gates, and multi-Python testing as tracked items in State Hub.
+- Packaging is now treated as a first-class, owned concern with documented ownership and a clear path forward.
+
+**Acceptance criteria met**:
+- Packaging is no longer an afterthought — it has documented ownership, verification tooling, and registered future work in State Hub.
 
 ## Dependencies & Cross-Repo Coordination
 
@@ -203,10 +211,26 @@ state_hub_task_id: "f4ea08ab-219e-4e7f-86b9-a05e27b8a72c"
 - 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.
 
-## Activation & Ralph Execution
+## Debt & Future Work (Registered)
 
-**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.
+This workplan explicitly registers the following as first-class technical debt / extension points:
+
+- PyPI publishing workflow
+- Automated releases via CI on tags
+- Package signing
+- Adding `make check-dist` (or equivalent) as a required CI gate
+- Multi-Python version testing for distribution packages
+
+These are now tracked in State Hub via this workplan.
+
+## Completion
+
+**Status: done** — all tasks completed via ralph loop.
+
+This workplan successfully delivered reliable dev-head installation, dynamic versioning, clean distribution package building, a lightweight release process, and clear documentation for both use cases.
+
+Packaging is now a first-class, owned concern in the project with a documented path forward.
 
 ---
 
-**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.
+**Status note**: CYA-WP-0004 is complete. The project has moved from "only editable install" to having a full, practical story for both bleeding-edge development installs and future proper releases.