This page records the verified Lucia Admin + Booking Engine branch and
release seam. It does not enumerate the whole HelloLucia fleet. Use
Current System State for the
company-wide repository and product topology.
Admin and Engine repository scope
Repositories covered by this page:Admin and Engine branch roles
main is the GitHub default for both repositories, but it is not the current deployed source. Development services (lucia-booking-engine dev, lucia-admin-dev) track dev and deploy the exact commit after checks pass. Staging services (lucia-engine-staging, lucia-admin-staging) track stage, have automatic deploy disabled, and serve the older commits shown above; nothing has been promoted since those dates.
Admin and Engine release flow
git ls-remote, and the merge onto dev is a fast-forward of that SHA. No
merge names a branch tip that could move. Battery green means exit code 0:
the gate reads the exit code of the full suite, never a count of failure lines.
The package/runtime value 0.1.3.6 remains present on current Development builds, but it spans many commits and cannot identify what was promoted. The earlier version-specific promotion gate is historical. Every promotion decision must name the exact Admin and Engine commits and the evidence reviewed.
The batteries, as they stand on 2026-09-10
Enginedev (npm test) at e2166b86ac6794a1423c7b2ce1b293a3dba505c4 is one chained script; a red leg stops the chain and the exit code is nonzero. Legs that exist because of a September law, in the order they run:
dev (npm run lint && npm run build, then npm test) at 1250ec7e48ba8a377e6c198ad10d033e7ad1293b: lint is eslint .; build is vite build with a prebuild hook that runs test:daw-law-guard, so the DAW law (the workspace is never generic) guards every build; the test chain ends in test:no-acutes. Every browser smoke runs its dev server on an ephemeral port, and no smoke reads the wall clock (the property clock is pinned).
CI: the Engine dev workflow runs npm ci and the chained suite on Node 22; the Admin dev workflow runs lint, the chain and the build, and retries its browser install through apt hiccups (LUCI-241, 2026-09-09). Render deploys only after those checks pass. The v0.4 quality-bank diagnostic that older records cited (76/217) is not the gate; see
Evaluation System for the Algorithm’s replay harness as the behaviour gate.
Fieldwork: the app’s CI lint step became plain npm run lint (eslint .) on 2026-09-07 so CI can no longer be green on a red lint (FILD-163); main deploys to Cloudflare Pages (the app’s own AGENTS.md; Main’s ruling on HLLC-41, 2026-09-10, over two September comments that said Netlify). The Fieldwork API’s smoke teardown is classified (LUCI-133, Completed 2026-09-09) so a teardown failure is reported as its own class, never as a test failure.
The Development Render services deployed the exact dev commits above through their checks-pass gate on 2026-09-09 (Engine) and 2026-09-10 (Admin).
Engine Development identity and contract:
Admin and Engine Stage protection doctrine
Stage changes should follow:Local prompt safety
Local terminal prompt should show current branch. This reduces accidental work on the wrong branch.The Algorithm’s own gate
The Algorithm files (luciaIntelligenceEngineAlgorithm.js, operatorFocusBrain.js) are owned by one engineer, and every merge that changes served behaviour carries a plain-English before/after on its record plus the replay harness’s old-to-new table (HLLC-29, 2026-08-29). See LIEA doctrine.