RQ1 — Which release is "latest", and does it differ from the canon?

Question (BRIEF.md RQ1): which Next.js release is "latest" at scaffold time, and does it differ from the harness canon 16.4? Evidence: upstream release pages vs ~/.claude/ddx-topic-flows/VERSIONS.md.

Answer: no stable release is newer than the canon minor line. Pin the VERSIONS.md canon. Result table: ../versions.md.

Method

1. Read ~/.claude/ddx-topic-flows/VERSIONS.md (stack table verified 2026-10-10).
2. Two web searches on 2026-10-23 over npm package pages, release feeds and changelogs (novel-pattern web check, ~/.claude/ddx-coding-flows/31-novel-pattern-web-check.md).

Findings

Note: some search excerpts were stale cached snapshots (for example an npm "versions" tab showing @nestjs/core 11.1.29). The rows above use the excerpt that shows the latest dist-tag or the newest publish date. The scaffold task re-reads the real installed version from package.json / lockfile (AC1.7).

Open items

• MinIO image — VERSIONS.md has no MinIO row. The compose task must pin an exact image tag from a recorded registry check (URL + date in this page), never latest. Also check how upstream distributes the community image today before pinning — not checked here.
• Node 26 — VERSIONS.md says "26 once LTS (Oct 2026)". Stay on 24 LTS until a recorded check shows 26 LTS.

Verdict

ASSUMPTION 5 of ddx-wip/job_ui-shell-rnd-workspace/00_JOB.md holds: "latest" = canon 16.4 line. No VERSIONS.md change is needed.

• ddx-documentation — dudoxx-web-boot

adr/

• ADR 0001 — Scaffold route: dudoxx-sandbox-creator with 163XX overrides
• ADR 0002 — Auth: better-auth 1.7 in ddx-api
• ADR 0003 — Route shape: org slug, role, [entity]/[id], ?view=
• ADR 0004 — Database split: one Postgres 18 instance, six databases
• ADR 0005 — Frameworks and the approved dependency table
• ADR 0006 — API clients come from one factory
• ADR 0007 — Typed service container (DI / IoC)
• ADR 0008 — Singleton scope: what may live at module level
• ADR 0009 — One variant API for every inventory component
• ADR 0010 — Media path: presigned URLs from ddx-api after the org check
• ADR 0011 — Media proxy: MinIO only through ddx-api
• ADR 0012 — Density names: compact | cosy | large
• ADR 0013 — Platform super-admin acts as org-admin of the target org
• ADR 0014 — Unified settings: one registry, three tiers, one resolve in ddx-api
• ADR 0015 — Entity kernel: one descriptor, one access seam, one projection, one proof chain
• ADR 0016 — SSE Bus: Redis Streams log, Redis pub/sub fan-out, BullMQ outbound queue
• ADR 0017 — Layered BFF: one route table, route classes, read models
• ADR 0018 — Cluster node registry, node identity, hot plug
• ADR 0019 — Tenant branding: settings keys, vendored palettes, public platform read
• Debug overlay

deploy/

• Deploy runbook — dudoxx-web-boot
• Entity kernel — guide
• Feature map — what each role can do
• Component inventory
• Naming constitution — dudoxx-web-boot
• Observability — one log layout, one key set
• Pattern reference — P1-P23 and groups A-K
• Port map — dudoxx-web-boot

research/

• RQ1 — Which release is "latest", and does it differ from the canon?
• RQ10 — SSE through the Next.js BFF route handler (desk half)
• RQ11 — Dev latency baseline: cold compile per route + next-server RSS
• RQ2 — Route group or dynamic org slug?
• RQ3 — better-auth 1.7 vs Auth.js v5: feature matrix
• RQ4 — Separate databases or separate schemas?
• RQ5 — Which frameworks beyond shadcn earn a place?
• RQ6 — How do DI, IoC and Singleton behave across RSC, client bundles and NestJS?
• RQ7 — Which data uses the server cache, which uses TanStack Query, how is each invalidated?
• RQ8 — Media path: presigned URLs vs streaming through the BFF
• Template triage — create-nextjs code in ddx-web
• Settings — guide
• Local setup — dudoxx-web-boot
• Shell tree — SiteShell and PortalShell
• SSE event catalog
• Version pins — dudoxx-web-boot