ci(live-e2e): `Live E2E (informational)` is red on main and every branch since the backend pin moved to 17.2.0 — the published `plugin-auth` float (objectstack#16186), not an objectui diff

[baozhoutao]

Filed by the domain:devx @ objectui execution seat (PM session session_01MM7kaS4dPpYHV5BsMyu4tQ, R45) as the consumer-side anchor for a red that is not this repository's to fix. Unassigned, unlabelled — a landing-ledger record, not a claim of priority. Dedup: semantic search for the lane's red / better-auth / no such table: sys_user returned 0 open objectui issues at 07:02Z (control queries this round return their targets).

Blocked-by: objectstack-ai/objectstack#16186

What is red

The Live E2E (informational) check run fails on every objectui ref whose e2e/live/ci/backend.env reads OBJECTSTACK_VERSION=17.2.0 / OBJECTSTACK_REF=e7d2cc67f… (landed by PR #7970 for #7689) — including main itself: the scheduled run 34017174769 on 9de3141a at 06:41Z has job 101442890465 completed: failure at the step Start ObjectStack backend (published packages) (06:48:28Z). The workflow-level conclusion stays success because .github/workflows/live-e2e.yml:60 sets continue-on-error: true on the job by design ("INFORMATIONAL, NON-REQUIRED lane"), but the job's check run reports failure, so a PM reading "every check green" sees a red on every PR.

Job log signature (job 101436925890, PR #7986 head 16aed838e; identical on PR #7985 head b520274 and on main):

WARN CORE: Core service missing, functionality may be degraded: auth
WARN System started with degraded capabilities. Missing core services: auth
[sql-driver] DATABASE_ERROR — the backend refused a read on 'sys_organization' … no such table: sys_organization
[sql-driver] DATABASE_ERROR — the backend refused a read on 'sys_user' … no such table: sys_user
Process completed with exit code 1.

Why it is not any objectui PR's

• Run history of live-e2e.yml: success on branches based before PR fix(ci): align the live-e2e backend pin with the lockfile, and pin the rule that says it must #7970 merged (e.g. PR docs(plugins): bring three documented interface blocks up to their shipped types #7985 at 09f1d485, 05:41Z), a failing job on every ref based after it, main included. Those diffs touch no backend pin and no e2e/ path.
• Cause measured upstream on objectstack#16186: published @objectstack/plugin-auth 17.1.0+ declares @better-auth/core as a caret range that now resolves to 1.7.3, which dropped createLocalAccountIssuer; a fresh objectstack dev --seed-admin never creates the system tables. That card's downstream note predicts this exactly: "objectui's Live E2E (informational) lane will now go red against the matched pair, by design".
• finding(ci): e2e/live/ci/backend.env pins OBJECTSTACK_VERSION=17.0.0-rc.2 while the lockfile resolves 17.2.0 — the live-e2e lane has been smoke-testing an unmatched pair for two minor versions #7689's triage forbids repairing the lane by reverting the pin (a failing matched pair carries more information than a green mismatched one), so there is no objectui-side fix to port.

What this card is for

• The place standing-down comments point at (PR fix(build): let turbo own build order, delete the hand-listed prebuild hooks #7986 and PR docs(plugins): bring three documented interface blocks up to their shipped types #7985 today; every PR until the upstream fix publishes) instead of re-diagnosing the same red per PR.
• The re-check trigger: when objectstack#16186 closes AND a fixed @objectstack/* version is published, the next backend.env pin move (via the finding(ci): e2e/live/ci/backend.env pins OBJECTSTACK_VERSION=17.0.0-rc.2 while the lockfile resolves 17.2.0 — the live-e2e lane has been smoke-testing an unmatched pair for two minor versions #7689 shape, ⛔ not a manual edit — fix(ci): align the live-e2e backend pin with the lockfile, and pin the rule that says it must #7970's check pins the pair to the lockfile) is what turns the lane green again. Consumer-side install-surface probe: boot the published showcase at the new version and see the seeded sign-in answer.

Refs: objectstack#16186 (cause, upstream) · #7689 / PR #7970 (the pin realignment that exposed it, by design) · #7964 (needs-user-decision, the lane's other pin)