KB-1490

03 — UI Deploy or Handoff

3 min read Revision 1
reportuihandoffnuxt2026-06-04

03 — UI Deploy or Safe Handoff

Decision: HANDOFF-FINAL (no deploy)

/opt/incomex/docker/nuxt-repo/web — branch main, clean tree, ahead 17 / behind 13 vs origin = github.com/Huyen1974/web-test.git (outward-facing public repo). Auto-build/deploy or push over a diverged public remote is unsafe and outside agent authority. Confirmed prior-macro call.

Live state

  • registries-pivot page + API already scaffolded AND built into the running nuxt-ssr-local:s174 container (.output/.../api/registries-pivot/*). Current page = registries count-integrity table (272 lines), reads v_count_integrity ⋈ v_living_lists. No Process Axis sections yet.
  • API convention: defineEventHandler + rpQuery (server/utils/rpGatewayDb.ts) pass-through, PG computes everything. Page: useAsyncData + $fetch. No JS math.

Handoff packet (staged, additive, edits no existing file)

/opt/incomex/docs/mcp-writes/ui-handoff-process-axis-2026-06-04/

  1. server-api-process-axis/overview.get.ts — read-only pass-through of the process-axis governance views (canon, coverage, owner flow, handlers, owner-gate readiness, dot:kg ladder, residual, trigger crosscheck). Tolerates absence of the trigger view.
  2. pages-knowledge-process-axis/index.vue — dashboard with all 7 required panels; render-only (no checkbox, no mutation); action execution stays in the guarded fail-closed server fns.
  3. GIT-STRATEGY-AND-APPLY.md — branch/commit/rebase plan, npm run build, smoke-test, rollback.

Required UI content (all in the packet)

official-vs-candidate coverage · action panel · owner decision flow · job:cut path · dot:kg ladder · trigger cross-check preview · residual status.

Git strategy (summary)

git fetch → review 13-behind → rebase 17-ahead onto origin/main on a throwaway branch → drop the 2 new files → npm run build → PR (no agent push to public main) → deploy via existing image pipeline.

Why not write into the working tree

The tree is clean; writing uncommitted files would entangle with the 17 ahead commits and confuse the operator's divergence resolution. Staged in mcp-writes instead, ready to cp on a clean checkout.

Back to Knowledge Hub knowledge/dev/reports/architecture/governed-officialization-ui-dotkg-content-trigger-axis-production-closeout-2026-06-04/03-ui-deploy-or-handoff.md