jb/harness-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: plan legacy workflow archival

Browse Source
This commit is contained in:
jb
2026-09-05 22:39:13 -04:00
parent fee0d44e2d
commit 5b1e771ec1
1 changed files with 58 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/workflow/archive-workflows-record.md
+58
View File
@@ -0,0 +1,58 @@
# Archive legacy workflows
## Status
- Status: waiting
- Current phase: plan approval
- Next safe action: obtain approval before product changes.
## Request and scope
Archive both `extensions/workflow` and `extensions/_workflows` under `__archived/extensions/`. Preserve source and tests as historical reference, not supported runnable packages. Keep `develop-workflow`, historical documentation, live Pi configuration, existing worktrees, and skill validation evidence intact.
## Git identity
- Source branch: main
- Base commit: fee0d44e2ddd7a982e94ebf99117f69bb9bae78e
- Feature branch: feature/archive-workflows
- Worktree: /srv/data/code/jb-pi/harness-tools/.worktrees/archive-workflows
- Omitted source changes: none; source was clean.
## Acceptance criteria
- Both implementations and their tests are retained in the archive.
- Active workspace inventory, lockfile, and root test commands no longer reference them.
- Current docs explain the archive and explicit pilot-prerequisite override; skill validation remains open.
- Active checks pass or failures are reported with evidence; independent reviewers approve the pinned diff.
## Approved implementation plan and gates
1. Move tracked files for both implementations to `__archived/extensions/`, preserving historical code unchanged. Add an archive README explaining historical relative imports and how to recover runnable sources from Git. Fix the moved workflow README's repository documentation links.
2. Remove the obsolete workspace exclusion and legacy test globs from `package.json`; update workspace inventory assertions and only legacy workspace entries in `bun.lock`. No third-party version or dependency changes. The existing TypeScript include already excludes archives.
3. Update root README, retirement TODO, and ADR 0006 with an explicit pointer to a small retirement ADR. Keep separate scenario/pilot validation TODO open. Preserve historical plans and ADR content rather than mass-rewriting old paths.
4. Verify focused package/link tests, root typecheck, and full `bun run test`. There are no root lint/build scripts. Check archived file preservation and absence of active imports. No UI change, installation, publishing, host configuration, or production access.
5. Commit verified work; fetch/rebase main, reverify any changed tree, obtain separate standards and specification reviews of the exact binary diff, fast-forward local main, commit closure metadata, and safely remove only this worktree/branch. Rollback is a focused revert of the archival product commit.
- Scope approval: user selected Archive both.
- Retirement gate: user selected Archive now, explicitly overriding the deferred three-pilot prerequisite. This does not claim pilot success.
- Plan approval: pending.
## Ownership
Parent agent owns all mutations listed above, including this record and new archival README/ADR. No subagent owns files. Mutating implementation deadline: 15 minutes; stop and checkpoint if exceeded. Reviewers are read-only and distinct from the parent.
## Verification matrix
Pending: `bun run test:packages`, `bun run test:links`, `bun run typecheck`, `bun run test`, `git diff --check`, archive byte-preservation check.
## Review
Pending. Pin base, product HEAD, tree, commit list, exact `git diff --binary --full-index --find-renames <base>...<head> --` SHA-256, reviewer identities and verdicts before integration.
## Integration and rollback
Pending local fast-forward after review; rollback via focused revert.
## Checkpoints and blockers
None beyond plan approval.