08 — UI Branch / Build / PR Strategy (Track G)

Git reality

• /opt/incomex/docker/nuxt-repo/web working tree is on main, clean.
• main is owned by the auto-snapshot cron (commits 04:00/16:00) — never push agent work to it.
• Branch feat/process-axis-dashboard exists (+2 files/+159 vs origin/main).
• Remote: github.com/Huyen1974/web-test.git.

Decision

Do NOT push from the agent. Create the dynamic-drill commit in an isolated worktree off origin/main (or extend feat/process-axis-dashboard); operator runs lint/build and pushes/opens PR.

PR package

• Branch: feat/rp-dynamic-drill (or extend feat/process-axis-dashboard).
• Title: feat(registries-pivot): dynamic drill UI — PG-backed Layer1→substrate across all axes.
• Files: 7 API routes + drill.vue + 7 components (see 05/06).
• Commands (operator): worktree add → cp from ui-package → npx eslint --fix → npm run build → push → PR.
• Deploy after merge: git pull && npm run build && pm2 reload <app>.
• Rollback: revert branch; drop 5 PG objects via 99_rollback.sql.

Full commands: ui-package/INSTALL_AND_PR.md.

Status

UI/API package = handoff-final, build-ready. Not deployed (operator-gated). Backend = live.