Skip to main content

Epic 5, Story 1, Task 68: Packaged Frameworks — Consumer Paths and Versioning Hygiene

Task ID: E5:S01:T68
Status: ✅ COMPLETE
Priority: HIGH
Estimated Effort: Medium
Created: 2026-03-25
Last updated: 2026-03-30 (Release v0.5.1.68+2 — consumer RW layout doc; kanban/numbering README; packages semver policy)
Version: v0.5.1.68+2
Version Anchor: Forensic release v0.5.1.68+2 — rw-validators-consumer-layout.md; workflow mgt + packages README; numbering + kanban cross-links
Code: E5S01T68

Repository Pattern: Internal scaffold (no FR yet).

Scope​

After merging Epic 5 RW/validator/doc work to main, consumers copying packages/frameworks/* need a coherent story for:

  1. Paths — rw-config.yaml kanban_root, scripts_path, and validation scripts (validate_rw_task_intent, validate_rw_task_complete) relative to their repo layout.
  2. Cross-package mentions — Kanban / numbering / doc-lifecycle READMEs: pointers to workflow mgt when RW validators or .cursorrules fragments are installed.
  3. Versioning — When to bump framework package version fields in README frontmatter (e.g. workflow mgt 2.2.0) vs ai-dev-kit repo version; optional short release checklist for publishing or tagging framework drops.

This task is scoping + documentation + checklist, not a full dependency architecture change (see Epic 6 ADRs if needed).

Input​

Deliverable​

  • Consumer checklist or “Installing workflow mgt from package” appendix: config keys, validator invocation, Kanban optional.
  • Cross-readme audit (kanban, numbering, doc-lifecycle): add or fix links where RW/validators are assumed.
  • Versioning note for maintainers: when a merge to main should trigger a framework README version bump.

Acceptance Criteria​

  • E5:S01:T65 — workflow mgt README count alignment.
  • E5:S01:T67 — install docs RW token.
  • E5:S01:T56 / FR-056 — broader doc standardization.

Story: Story-001-fr-repo.md