basquetWi + New ticket
movilba MOVILBA-423

Maintain PNPM development with NPM-compatible deployment

Done normal bvbin-venus-ca

Keep PNPM as the developer package manager and keep production deployment fully compatible with NPM. Confirm and document the existing split workflow; maintain package-lock.json for npm ci; ensure deployment and ASI-facing build commands use NPM; add a consistency check so package.json, pnpm-lock.yaml, and package-lock.json cannot drift. Acceptance: a clean npm ci followed by the production build succeeds, deployment uses NPM, and the PNPM development workflow continues to work.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • wi-cli-venus created · 5w ago
  • wi-cli-venus statusChanged · 5w ago
    Dual PNPM/NPM lockfiles prepared and npm ci plus npm production build verified under Node 24.14.1; pending integration and deployment-pipeline confirmation.
  • wi-cli-venus progress · 5w ago
    Integrated and deployed dual lockfiles plus PNPM-development/NPM-deployment documentation in v5.5.129. Remaining before closure: make the actual ASI/deploy path use npm and add an enforced dual-lock consistency check.
  • wi-cli-venus progress · 5w ago
    DEV v5.5.132 synchronizes package.json and package-lock.json after the deploy bump (cefe3aa1); typecheck, health, and freshness passed. Operational finding: gitdeploydev's npm version bump mutates package-lock.json, so every scoped deployment must include that lock or the hook must enforce/stage it automatically. Dual-lock automation acceptance remains open.
  • wi-cli-venus progress · 5w ago
    Prepared the remaining dual-lock/deployment enforcement against origin/dev a393cf5d in /home/rob/Documents/work/gcaba/movilba-web-worktrees/coder04-mba-l-cc/movilba-423-npm-deploy (uncommitted). Added scripts/check-lockfile-consistency.mjs plus package script; wired dev/prod pre-deploy hooks; corrected README, ASI, and operations docs to use pnpm for development and npm ci/npm run build for deployment. Node 24.14.1 evidence: pnpm install --frozen-lockfile PASS; clean npm ci PASS; npm run build PASS (81 static pages); npm run lockfiles:check PASS; deliberate package.json-only, package-lock-only, and pnpm-lock-only drift each rejected with exit 1. Final git diff --check and bash -n hooks PASS. No commit or deploy; ready for main coder integration.
  • wi-cli-venus progress · 5w ago
    Combined with MOVILBA-424 and the focused MOVILBA-426 slice in one reviewable worktree: /home/rob/Documents/work/gcaba/movilba-web-worktrees/coder04-mba-l-cc/movilba-423-424-426-integrated, branch coder04-mba-l-cc/movilba-423-424-426-integrated at origin/dev a393cf5d. This removes package.json/docs/lockfile merge ambiguity. Combined npm lock consistency, typecheck, production build (81 pages), probe test, shell syntax, and git diff checks pass. Ready for main coder integration.
  • wi-cli-venus progress · 5w ago
    Corrected the deploy bump sequencing gap found during review. gitdeploydev v2.18 runs the repo prehook before pnpm version and later stages package.json only, so the prehook alone could not prevent a stale package-lock root version. Repo-side fix: package.json now defines the pnpm/npm version lifecycle as 'node scripts/check-lockfile-consistency.mjs && git add -- package-lock.json'. Isolated reproduction at a393cf5d used the actual relevant order: stage selected patch; pre-bump lockfiles:check PASS; pnpm version patch --no-git-tag-version ran lifecycle; deploy-equivalent git add package.json. Result 5.5.137 -> 5.5.138, package.json/package-lock top/package-lock root all 5.5.138, package-lock.json present in cached selection, and no unstaged package.json/package-lock/pnpm-lock residue; post-bump consistency check PASS. Canonical worktree remains unchanged at 5.5.137 and final diff/checker/bash syntax pass. No shared deploy-script change is required; no commit/deploy performed.
  • wi-cli-venus progress · 5w ago
    Correction to prior event: the repo lifecycle fixes MovilBA, but the shared gitdeploydev wrapper still needs the generic post-bump named-lock stage/check so every repository is protected and selected-file semantics remain centralized. DEV v5.5.140 is currently consistent because coder explicitly selected both locks. bin-venus-ca owns the wrapper fix; MOVILBA-423 remains open until enforced.
  • wi-cli-venus assigned · 5w ago
    bin-venus-ca / bin
  • wi-cli-venus verified · 5w ago
    Shared wrapper prevention completed by bin-venus-ca in gitdeploydev.sh v2.19 commit 9a1dfae. It snapshots both named lockfiles before pnpm version, runs the repository consistency check after the bump when defined, and stages only named locks whose content changed, including creation/deletion. Focused harness 9/9 and info suite 12/12 passed. DEV v5.5.140 already has PNPM development, npm deployment docs, both committed locks, successful clean npm build, and a passing consistency check.
  • wi-cli-venus completed · 5w ago
    Delivered: MovilBA dual-lock/npm build support is live in DEV v5.5.140, and shared gitdeploydev v2.19 now enforces post-version-bump lock consistency and named lock staging automatically.
chore
5w ago by wi-cli-venus
5w ago
2026-09-10 18:51