From accf834b3ee4da5c049c1154423098caf3caed4c Mon Sep 17 00:00:00 2001 From: saravanakumardb1 Date: Mon, 23 Mar 2026 15:49:05 -0700 Subject: [PATCH] docs(pnpm): record gitea registry rehearsal checkpoint --- docs/pnpm/PNPM_MIGRATION.md | 35 ++++++++++++++++++++++++++++++----- 1 file changed, 30 insertions(+), 5 deletions(-) diff --git a/docs/pnpm/PNPM_MIGRATION.md b/docs/pnpm/PNPM_MIGRATION.md index e4767e68..df3c91b7 100644 --- a/docs/pnpm/PNPM_MIGRATION.md +++ b/docs/pnpm/PNPM_MIGRATION.md @@ -8,6 +8,8 @@ This tracker is for repos that still require an `npm` to `pnpm` migration, plus This tracker is **not** a claim that every listed repo is still on `npm` today. Some repos may already use `pnpm` in part or in full; those repos should be handled here only if they still require migration cleanup, downstream validation, or tracker-hosting updates. +This migration is a **repo-by-repo standardization effort across independent repositories**. It is **not** a plan to merge product repos into a single mega-monorepo. `learning_ai_common_plat` remains the canonical `pnpm` workspace for shared packages/services, while product repos stay independently versioned and independently deployable. + ## Objective Standardize on `pnpm` for: @@ -84,11 +86,33 @@ Equivalent readiness checks should include, at minimum, the repo's canonical ins ## Current Status -- **Ready for sequential rollout:** yes -- **Ready for parallel or one-shot migration:** N/A — all repos migrated -- **Current next repo:** ✅ ALL COMPLETE +- **Ready for sequential rollout:** complete +- **Ready for parallel or one-shot migration:** N/A — tracker is in post-migration maintenance state +- **Current next repo:** none — tracker complete unless a follow-up cleanup or newly discovered regression reopens a repo - **Completed pilot:** `learning_ai_flowmonk` +## Follow-up Validation: Local Gitea npm Registry Rehearsal + +This tracker remains complete for the pnpm migration itself. + +However, a new post-migration validation stream is now in progress: + +- replacing tarball-based `@bytelyst/*` Docker consumption with the local Gitea npm registry +- validating the full flow on this Mac before any Azure rollout +- using `learning_ai_flowmonk` as the first registry-migration pilot + +Current status: + +- host-side local Gitea registry publishing is validated +- host-side local consumer installs are validated +- FlowMonk host-side install, typecheck, and tests against the local Gitea registry are validated +- Docker-side validation remains blocked by the local Homebrew Gitea ↔ Docker build networking and tarball URL generation path + +Commit ledger for this follow-up stream: + +- docs/script baseline commit: `7116749` +- tracker/roadmap update commit: `TBD` + ## Pilot Evidence ### `learning_ai_flowmonk` @@ -269,5 +293,6 @@ The old product-level roadmap location now exists only as a pointer: - canonical tracker: this file - completed pilot: `learning_ai_flowmonk` -- next repo in sequence: `learning_ai_local_memory_gpt` -- rule: do not move to the next repo until the current repo passes verification, audit, readiness, commit, push, and tracker update +- next repo in sequence: none — sequential rollout is complete +- current mode: maintain completion state, reopen individual repos only for migration regressions, cleanup, or downstream alignment work +- rule: if any repo is reopened, do not move to the next repo until the current repo passes verification, audit, readiness, commit, push, and tracker update