Skip to main content

Repository Story Migration Plan

Status: IN PROGRESS
Priority: HIGH
Last updated: 2026-01-16
Related Work: E9:S01:T08 (Repository Story Abstract Space Contradiction)
Version: v0.9.1.8+1

Executive Summary​

This document provides the detailed migration plan for implementing the repository story abstract space resolution. The migration involves:

  1. Renumbering existing stories to free S01 for repository stories
  2. Creating new repository stories (S01) for FR/BR/UXR repositories
  3. Migrating repository tasks from S00 to S01
  4. Migrating perpetual tasks from T08/T12 to T101/T102
  5. Updating all references and version numbers

Migration Strategy​

Phase 1: Story Renumbering (Free S01)​

Epic 5:

  • Current: S01-S07 (Documentation Maintenance Framework, etc.)
  • Renumber to: S02-S08
  • S01 becomes available for FR Repo

Epic 6:

  • Current: S01-S07 (Framework Version Management, etc.)
  • Renumber to: S02-S08
  • S01 becomes available for BR Repo

Epic 7:

  • Check if S01 is taken
  • If taken, renumber similarly

Phase 2: Create Repository Stories (S01)​

  • Create E5:S01 (FR Repo) story document
  • Create E6:S01 (BR Repo) story document
  • Create E7:S01 (UXR Repo) story document (if needed)

Phase 3: Migrate Repository Tasks​

E5:S00 → E5:S01:

  • T31 → T31 (FR-031)
  • T34 → T34 (FR-034)
  • T35 → T35 (FR-035)
  • Versions: v0.5.0.31+0 → v0.5.1.31+0, etc.

E6:S00 → E6:S01:

  • T33 → T33 (BR-033)
  • Versions: v0.6.0.33+0 → v0.6.1.33+0

Phase 4: Migrate Perpetual Tasks​

E6:S06:

  • T08 (UKW) → T101 (UKW)
  • T12 (CMW) → T102 (CMW)
  • Versions: v0.6.6.8+21 → v0.6.6.101+21, etc.

Phase 5: Update Abstract Spaces​

  • S00 becomes Epic-level abstract space only (no tasks)
  • S01 gets story-level abstract space (v0.X.1.0+0)

Detailed Migration Steps​

Step 1: Renumber Epic 5 Stories (S01-S07 → S02-S08)​

Files to Update:

  • Epic-5.md (Story checklist)
  • Story-001-*.md → Story-002-*.md (rename files)
  • Story-002-*.md → Story-003-*.md
  • ... (continue for all stories)
  • All task documents in each story directory
  • All references in FR/BR documents
  • All changelog entries
  • All version numbers

Version Updates:

  • v0.5.1.X+Y → v0.5.2.X+Y (S01 → S02)
  • v0.5.2.X+Y → v0.5.3.X+Y (S02 → S03)
  • ... (continue for all stories)

Step 2: Renumber Epic 6 Stories (S01-S07 → S02-S08)​

Similar process to Epic 5

Step 3: Create E5:S01 (FR Repo)​

Create new story document:

  • Story-001-fr-repo.md
  • Based on Story-000-fr-repo.md but updated for S01
  • Abstract space: v0.5.1.0+0

Step 4: Migrate E5:S00 Tasks to E5:S01​

For each task (T31, T34, T35):

  • Move task file: Story-000-fr-repo/T31-*.md → Story-001-fr-repo/T31-*.md
  • Update task document (Task ID, version references)
  • Update FR document (task ID, version)
  • Update changelog entries
  • Update all cross-references

Step 5: Update S00 to Abstract Space Only​

E5:S00:

  • Remove all task references
  • Update to abstract space only (v0.5.0.0+0)
  • Update description to clarify it's Epic-level abstract space

Step 6: Migrate Perpetual Tasks (T08, T12 → T101, T102)​

E6:S06:

  • Rename task files: T08-*.md → T101-*.md
  • Update task documents (Task ID, version references)
  • Update story checklist
  • Update all references
  • Update changelog entries

Risk Assessment​

High Risk:

  • Story renumbering affects many files and references
  • Version number updates must be comprehensive
  • Cross-references must be updated accurately

Mitigation:

  • Work systematically, one epic at a time
  • Update references in batches
  • Validate after each phase
  • Use grep to find all references

Validation Checklist​

  • All stories renumbered correctly
  • All task documents updated with new IDs
  • All version numbers updated
  • All FR/BR documents updated
  • All changelog entries updated
  • All cross-references updated
  • S00 is abstract space only (no tasks)
  • S01 is repository story (with tasks)
  • Perpetual tasks in T101+ range
  • Versioning system supports 3-digit tasks
  • All validators pass

This migration plan is part of Epic 9: Release Candidate Readiness, Story 1: RC Readiness Gap Analysis. See Story-001-rc-readiness-gap-analysis.md for story context.