docs: synchronize workflow archival references and review checkpoint

This commit is contained in:
jb
2026-09-05 22:48:15 -04:00
parent 45d6a41a39
commit 8d3552bc92
2 changed files with 8 additions and 4 deletions
+1 -1
View File
@@ -42,7 +42,7 @@ bun publish
Publish `@jbcode/pi-shared` before a new version of any extension that depends on it. Gitea rejects republishing an existing name/version, so bump the changed package version first.
`extensions/workflow` and `extensions/_workflows` are private historical evidence and must not be published. [ADR 0006](adr/0006-skill-led-development-workflow-04SEP2026.md) supersedes the proposed runtime merge; new development uses the `develop-workflow` skill.
`__archived/extensions/workflow` and `__archived/extensions/_workflows` are historical reference, outside active workspaces, and must not be published. [ADR 0007](adr/0007-archive-legacy-workflows-05SEP2026.md) records their archival and supersedes ADR 0006's pilot-before-retirement prerequisite; new development uses the `develop-workflow` skill.
## Install with Pi
+7 -3
View File
@@ -4,7 +4,7 @@
- Status: active
- Current phase: independent review
- Next safe action: commit verified product changes and pin the review diff.
- Next safe action: obtain fresh independent review verdicts for the remediation commit; integrate only after both approve its exact diff.
## Request and scope
@@ -29,7 +29,7 @@ Archive both `extensions/workflow` and `extensions/_workflows` under `__archived
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.
3. Update root README, current package documentation, 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.
@@ -51,7 +51,11 @@ The approved `bun install --frozen-lockfile && bun run typecheck && bun run test
## 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.
First review binding: base fee0d44e2ddd7a982e94ebf99117f69bb9bae78e, product 45d6a41a39454b968392be72301884a460725366, tree e6d974aa49c34a4e46b0194b29fe3d0995ba2f9d. Commits: 5b1e771, ea05b2f, eb52030, 45d6a41. Exact diff command: `git diff --binary --full-index --find-renames fee0d44e2ddd7a982e94ebf99117f69bb9bae78e...45d6a41a39454b968392be72301884a460725366 --`. SHA-256: 6c8ede8b38d9a718886b9374f0ea572e6662ea113b1d7354e71506f5b5ecbca0. Clean status, HEAD, and tree were unchanged before/after both reviews.
Specification reviewer archive-specification (claim-verifier, session 01a0749b-2ee1-7616-ac4f-e3f46db30922) confirmed digest and approved with no findings. Standards reviewer archive-standards (claim-verifier, session not exposed) confirmed digest and rejected two low documentation issues: stale current locations in docs/npm-packages.md, and this record still describing product commit/pinning as future work. Parent accepted and corrected both. Parent is the only mutator; reviewers own no files.
Fresh review follows the remediation commit. Its exact immutable HEAD/tree and binary-diff digest are supplied directly to both reviewers and will be recorded in the metadata-only closure once approved, avoiding a self-referential commit/digest in the product record. No product integration is authorized by the first review.
## Integration and rollback