fix(goal-start): fence guided bootstrap over orphaned Goal state

[hahahahahayesyeseys]

Goal And Delivered Outcome

• Goal/source and gap: [Bug]: Guard orphaned Goal state before guided bootstrap or host activation #4801. An operator-initiated reset can remove a Goal's project registry entry while its project-local active-state file survives. inspect_bootstrap_connection classified that as the ordinary registry_without_goal absence, so a guided packet kept offering connect_if_needed, fresh-agent registration, Todo writeback, host-loop activation and quota spend for the same human-readable Goal id, and a later diagnose reported a healthy Goal over state an earlier lane left behind. The gap is a missing distinction between "nothing was here" and "state is here but its authority is gone".
• Observable before -> after, with the validation row that proves it: before, the reproduction project returned connection_state: registry_without_goal together with state_file_exists: true and a bootstrap-oriented continuation (captured by the failing-before run in the regression_parity row). After, the same project returns orphaned_goal_state, ordered_steps collapses to inspect_connection + resolve_orphaned_goal_state, and all five mutation continuation commands are null (real_entrypoint row).
• Issue/task and intended base: Refs [Bug]: Guard orphaned Goal state before guided bootstrap or host activation #4801; three of its acceptance bullets are deliberately left open and named below. Base: main.

Scope And Continuation

• Completed scope: the detected fact (candidate routes over the current and legacy project state roots, reported without merging or copying), the blocking guided transaction and command pack, an operator-facing gate that keeps only the two routes that actually run today, and regression coverage including the shipped onboarding entry qualifier.
• Remaining work: (1) diagnose surfacing of an unresolved orphan; (2) a previewable archive/adopt route for project-local orphan state - measured in this slice, uninstall-project selects goals from the registry and archive-runtime resolves only a goal directory under the shared runtime root, so neither reaches this state, and the gate says so instead of projecting a command that fails; (3) an opaque Goal instance/generation id so host bindings cannot reattach across a deletion. Each changes a different command's contract and needs an owner decision on shape.
• Slice boundary / successor: the fence is independently testable and reversible, and it removes the harmful automatic continuation on its own. Follow-ups are recorded on [Bug]: Guard orphaned Goal state before guided bootstrap or host activation #4801 rather than fabricated as code here.

Validation

• Tested revision: a0ca91d (current head). Rows marked "reviewed head" were produced at 144072c, the head the review ran against; the exact-head re-run of every row is published in the review reply on this PR.
• Run state: finished
• Input classes: synthetic

Check kind	Result	Public-safe evidence / limitation
real_entrypoint	passed	start-goal --guided executed through the shipped CLI against a synthetic project reproducing the issue's shape: two ordered steps, writes_now=false, spends_quota_now=false, goal_start_connect_if_needed / goal_start_refresh_state / goal_start_host_loop_activation / goal_start_quota_should_run / goal_start_plan_prompt all null, recommended_next_step.kind=resolve_orphaned_goal_state
real_entrypoint	passed	at this head, the review's own counter-example driven through the shipped CLI: a project with a surviving state file and no registry file at all now returns orphaned_goal_state, two ordered steps, registry_exists=false, and all seven continuation command keys null
unit	passed	new module tests: 13 passed at this head, 9 at the reviewed head - detection over all four project state routes, the two absences separated, candidate matching scoped to the requested id, blocking transaction and command-pack parity, and the shipped onboarding qualifier reporting route=stop with zero actionable commands
regression_parity	passed	failing-before: with the module and wiring reverted, the new owning-smoke check asserts connection_state=registry_without_goal with state_file_exists=true, i.e. it reproduces the reported defect; with the change it passes. Negative twins pin that plain absence still keeps connect_if_needed and that a state file for a different Goal id does not block
integration	passed	reviewed head: tests/control_plane, tests/cli_commands, tests/canary: 4570 passed, 8 skipped, 1 failed - the failure is pre-existing, see the static row and the final row
static	passed	ruff check clean on all four changed paths; py_compile clean; module ceiling held: the oversized command-pack module is 2236 lines against its reviewed 2240 ceiling, so the canary's unreviewed-finding list is byte-identical to base (two findings, same paths) and this PR adds no size debt
manual	passed	the two projected preview routes were executed verbatim from the project root: backup-state --project . --current-project-only returned dry_run=true with wrote_local_registry=false, and checksums of the registry and the orphaned state file were identical before and after
integration	failed	the repository vocabulary-drift check fails in this environment for an unrelated reason: the TypeScript production parser is unavailable until dependencies are installed. It fails identically on a clean base worktree, so it is not attributed to this change

• Coverage and gaps: the reset that removes the registry file entirely is covered at this head after the review found the early not_connected return bypassed the fence; a registry file that exists but cannot be parsed still returns registry_invalid before the classifier and keeps its continuations, which is disclosed here rather than changed because overriding that state would hide the parse error an operator must fix. The changed paths are the goal-start connection classification, the guided/command-pack projection of a continuation, and their tests, which the rows above execute through the real CLI entry point as well as in-process. Not covered here and not changed: the diagnose projection, host-binding instance identity, and any persisted state or receipt contract - no AuthorityStore, cursor, outbox or provider arm is touched, so no conformance arm applies. The full tests/ sweep is being re-run at this head and its result is recorded in a follow-up comment on this PR.

Frontend / Visual Evidence

• UI impact: none
• Before: N/A
• After: N/A
• States and viewports shown: N/A
• Source data: none
• Attention review: no user-visible UI changes. Verified rather than assumed: no consumer of guided_transaction or connect_if_needed exists under the dashboard or desktop sources, so the affected surface is the CLI packet a host session executes.

Type of Change

• Bug fix
• New feature
• Breaking change
• Refactoring (no functional changes)
• Documentation update
• Test update

LoopX Area

• Control plane (goals, todos, quota, scheduler, registry, runtime)
• Benchmark boundary (adapters, runners, verifiers, scoring, evidence)
• Capability or extension (providers, adapters, skills)
• Public docs or presentation surface (README, protocols, dashboard)
• Build, packaging, installer, or CI
• Host or runtime integration

Technical Direction

• Direction / acceptance reference, when applicable: Core control-plane hardening; [Bug]: Guard orphaned Goal state before guided bootstrap or host activation #4801 acceptance, operator-reset safety fence.

Shared-authority RFC fixture impact

• Production-scale fixture schema: N/A - no persisted schema, receipt or cursor contract changes.
• Semantic dimensions changed, or reviewed no-impact rationale: N/A - the shared production-scale coordination fixture is not read by this path.
• Provider conformance arms run: none; no provider or AuthorityStore selection changes.
• Read-only legacy/file/PostgreSQL three-arm rehearsal (required for promotion, runtime-routing, or compatibility-projection changes): not applicable - no runtime routing or compatibility projection is changed.

Boundary Checklist

• Neither the diff nor this PR body/comments/attachments disclose private state, credentials, raw traces or verifier output, internal links, or local machine paths (including .loopx/, .codex/goals/, and live ACTIVE_GOAL_STATE.md).
• I did not duplicate maintainer-owned benchmark work unless a maintainer split out a public issue for it.
• I kept the change scoped to the linked issue/task.
• I completed the visual evidence section for UI changes, or marked UI impact none.
• Every commit includes a DCO Signed-off-by trailer (git commit -s).

[hahahahahayesyeseys]

Full tests/ sweep, as deferred in the validation section.

• This head (144072c): 91 failed, 10637 passed, 37 skipped in 41m41s.
• Same sweep on a second worktree at the same base revision whose only difference is an unrelated examples/ smoke: 91 failed, 10628 passed, 37 skipped in 41m35s.
• The two failure sets are identical: the set difference is empty in both directions. The only movement in the totals is the +9 tests this PR adds.

Attribution of the 91, all pre-existing on main in this environment and none introduced here:

group	count	reason
tests/architecture/test_semantic_*	88	the TypeScript production parser is unavailable locally, the same root cause as the vocabulary-drift advisory row above
tests/extensions/test_lark_goal_topic_runtime.py	2	date-expired absolute fixture timestamps, reported in #4797 and fixed by #4798
tests/canary/test_maintainability_ratchet.py	1	two unreviewed module findings (loopx/chat_server.py and loopx/extensions/lark/goal_topic_connections.py), byte-identical to base; this change keeps the command-pack module inside its reviewed ceiling (2236 against 2240) rather than raising it

Combined with the earlier domain-scoped run (tests/control_plane, tests/cli_commands, tests/canary: 4570 passed, 8 skipped, 1 failed with that same pre-existing ratchet finding), the changed paths are covered at both the focused and repository-wide level with no new failure.

[huangruiteng]

评审 exact head：144072cdbee74cb37b7b91ff8d5b8778f7c86366

动机

这个 PR 解决的是 #4801 中一个真实且高风险的 authority discontinuity：项目注册表不再声明某个 Goal，但同 id 的 ACTIVE_GOAL_STATE.md 仍留在项目目录时，start-goal --guided 不能把它当成全新 Goal，继续提供 bootstrap、注册新 agent、写 Todo、启用 host loop 和消费 quota 的路径。否则同一个可读 Goal id 会同时承载旧状态和新 lane 的写权限。

把这项工作拆成“先阻断危险续跑”的独立 slice 是合理的。archive/adopt、diagnose 告警和 opaque Goal generation identity 可以后续完成，因为单独落地 fence 已经能减少实际危害；但 fence 必须覆盖 issue 定义的全部“没有匹配 registry Goal、却存在 state candidate”情形。

改动思路

实现新增 loopx/control_plane/goals/orphaned_goal_state.py，把四个历史/当前项目状态根目录的候选探测、orphaned_goal_state connection projection、operator gate、command-pack 清理和 guided Markdown 渲染集中到一个 owner。inspect_bootstrap_connection 在“registry 存在且没有匹配 Goal entry”时调用该 classifier；fence_command_pack 将 bootstrap、registration、planning、refresh、host activation、quota 等 continuation 清空；guided_fence 把 transaction 收敛为 inspect_connection 和 resolve_orphaned_goal_state 两步。

这个 ownership 方向是对的：orphan 是 registry/state 的派生事实，不是新的持久化真相；现有 state-backup 根目录得到复用，也没有偷偷 copy/merge 状态。inspect 与 backup 都保持 preview-only，未把 archive/adopt 伪装成已经可用的命令。

具体改动

• orphaned_goal_state_routes 在 .loopx/goals、.codex/goals、.claude/goals、.local/goals 中按精确 Goal id 查找候选，只投影项目相对路径。
• registry_missing_goal_connection 将 truthy registry 中的“无匹配 Goal”分成普通 registry_without_goal 和 orphaned_goal_state。
• fence_command_pack 清空 7 个 mutation continuation，并把 safety contract、recommended next step 和 resolution gate 对齐。
• guided_fence 替换原 transaction 的 ordered steps，同时移除 identity selection gate；onboarding qualifier 因而返回 route=stop。
• 新增 9 个 focused tests，覆盖四种根目录、普通 absence、connected Goal、command-pack/guided parity 与 qualifier stop；bootstrap smoke 也新增了真实 CLI 形状。

阻塞问题在 loopx/bootstrap_command_pack.py:592：if not registry 仍然在新 classifier 之前直接返回 not_connected。我在 exact head 上用 shipped CLI 构造“没有 .loopx/registry.json，但 .codex/goals/reset-goal/ACTIVE_GOAL_STATE.md 存在”的项目，返回结果同时满足：

• state_file_exists=true
• connection_state=not_connected
• transaction 仍包含 connect_if_needed、select_agent_identity、Todo planning/writeback、refresh、activation、quota guard
• command pack 仍给出 bootstrap、registration、plan 和 refresh continuation

这正是 #4801 要阻断的第二 authority 风险。当前测试 helper 总会写一个 truthy registry（含另一个 live Goal），所以 9 个新测试全部通过也不会触达这个 bypass。请在 ordinary missing/empty-registry return 前复用同一 orphan projection：只有完全没有 candidate 时才返回 not_connected；并补 missing registry、empty registry 与对应 no-state negative twins，最好走真实 CLI。

对主干的风险

已覆盖的 truthy-registry 分支风险控制得不错：普通全新 Goal 与已连接 Goal 的 negative twins 保持旧行为；gate 本身不写状态，所有 projected resolution route 都不含 --execute；当前 head 与最新 origin/main 没有发现文本冲突。

但是未覆盖分支的 blast radius 很大：operator reset 若直接移除整个 registry，host 会拿到普通 onboarding packet，依次获得 bootstrap、fresh-agent、Todo、host-loop 和 quota 的可执行引导。这个漏洞不是 presentation 差异，而是 fence authority 的 false negative，因此不能在当前 head 批准。

本地验证：focused tests 9 passed in 0.94s；examples/bootstrap-command-pack-smoke.py 通过；changed paths Ruff 通过；git diff --check 通过。按 Goal 配置 wait_for_ci=false，没有抓取或等待远端 CI。真实 missing-registry CLI 反例失败，作为本次 REQUEST_CHANGES 的决定性证据。

我的整体评价

这是一个有价值、边界合理且总体架构方向正确的 safety slice；新模块没有制造第二份持久化 authority，未来相关的小型重构也已经体现在集中 classifier/fence owner 上，无需再引入更大的 framework。当前唯一 blocker 很具体：classifier 必须覆盖 registry file 缺失/empty 的同一 orphan invariant。修复后请在新 exact head 重新跑 focused + smoke + real CLI twins；archive/adopt、diagnose 和 generation identity 仍可按 PR 已声明的后续边界继续，不要求在本 PR 扩 scope。

English verdict: REQUEST_CHANGES - head 144072cdbee74cb37b7b91ff8d5b8778f7c86366 correctly fences orphaned state when a truthy registry lacks the Goal, and 9 focused tests, the bootstrap smoke, Ruff, and diff check pass; however, a real exact-head CLI reproduction with a missing registry and surviving state still returns not_connected and exposes bootstrap/registration/Todo/activation/quota continuations, so the same classifier must cover missing and empty registries before approval.

[hahahahahayesyeseys]

Blocker fixed at this head (a0ca91d1). The classifier now runs above both absence returns instead of only inside the readable-registry branch, so a reset that removes the registry file itself can no longer reach a normal onboarding packet.

Your repro, re-run through the shipped CLI at this head (synthetic project with only .codex/goals/reset-goal/ACTIVE_GOAL_STATE.md present and no .loopx/registry.json at all):

• connection_state: orphaned_goal_state, registry_exists: false
• guided_transaction.blocked_by: orphaned_goal_state, ordered steps exactly inspect_connection + resolve_orphaned_goal_state
• bootstrap_dry_run_preview, bootstrap_after_user_confirmation, goal_start_connect_if_needed, goal_start_plan_prompt, goal_start_refresh_state, goal_start_host_loop_activation, goal_start_quota_should_run all null
• projected orphan route reported relative to the project, nothing written

Re-runs you asked for at the new exact head

check	result
focused module tests	13 passed - four new parametrized cases (missing and empty registry, each fenced and each cleared) on top of the previous nine
owning smoke	passes, now including the missing-registry case driven through the real CLI entry point
module ceiling	the command-pack module is 2233 lines against its reviewed 2240, so the canary's unreviewed-finding list is still exactly the two pre-existing paths
static	ruff check and py_compile clean on every changed path

The ordinary-absence half is pinned to be unchanged rather than merely un-broken: a genuinely fresh project still returns not_connected with the same fields it carried before (including registry_exists and the reason text, and no new keys), and its packet still exposes connect_if_needed with a non-null command.

One correction to my own framing, and one case left to you. A readable registry declaring no goals (goals: []) was already covered by the first head, because it falls through to the matching branch; the genuinely open path was the missing-file case your repro found. Both are pinned now, but for different reasons, and the test names say so.

The same false-negative shape still exists one branch earlier: when the registry file exists but cannot be parsed, inspect_bootstrap_connection returns registry_invalid before the classifier, and I measured that a packet over surviving state still carries connect_if_needed, select_agent_identity, Todo planning and writeback, refresh, activation, quota guard and the scheduler ack step, with goal_start_connect_if_needed non-null. I did not fold it in here because overriding connection_state there would bury the parse error that is the operator's actual next action, and that trade-off is yours rather than mine to make. Two shapes I would accept from you: keep registry_invalid as the state and just strip the continuations when a candidate exists, or classify it as its own blocked state that names both facts. Say which and I will land it on this branch.

archive/adopt, diagnose surfacing and opaque Goal instance identity stay as the declared follow-ups.

[huangruiteng]

评审 exact head：a0ca91d1d61341df260aaaf49742314ef9bca4dc

动机

这个 PR 处理 #4801 中一个真实且高风险的 authority discontinuity：项目注册表不再声明某个 Goal，但同 id 的 ACTIVE_GOAL_STATE.md 仍留在项目目录时，start-goal --guided 不能把它当成全新 Goal，继续提供 bootstrap、注册新 agent、写 Todo、启用 host loop 和消费 quota 的路径。否则同一个可读 Goal id 会同时承载旧状态和新 lane 的写权限。

本轮复审确认上一轮指出的 missing/empty-registry 漏洞已经修复：当前 head 会在这些分支调用统一的 orphan classifier，并保留普通无状态新项目的旧行为。这是实质性进展。但我继续沿着同一 authority invariant 检查真实输入边界，发现 invalid/unparseable registry 仍从更早的分支绕过 classifier，因此当前 head 仍不能批准。

改动思路

实现把候选状态探测、orphaned_goal_state connection projection、operator gate、command-pack 清理和 guided Markdown 渲染集中在 loopx/control_plane/goals/orphaned_goal_state.py。inspect_bootstrap_connection 现在不仅覆盖“registry 存在但无匹配 Goal entry”，也通过 unregistered_goal_connection 覆盖 missing/empty registry；fence_command_pack 将 bootstrap、registration、planning、refresh、host activation、quota 等 continuation 清空；guided_fence 把 transaction 收敛为只读 inspect 与 resolution preview。

这个 ownership 方向仍然正确：orphan 是 registry/state 的派生事实，不是新的持久化真相；四个 current/legacy state roots 得到复用，也没有偷偷 copy、adopt 或合并状态。此次修复也没有复制第二套 fence。剩余问题应继续复用同一 classifier，而不是新增 registry-error 专用安全模型。

具体改动

• orphaned_goal_state_routes 在 .loopx/goals、.codex/goals、.claude/goals、.local/goals 中按精确 Goal id 查找候选，只投影项目相对路径。
• goal_connection_without_matching_entry 现在同时服务 registry-without-goal 与 unregistered project，两类路径都能区分普通 absence 和 orphaned state。
• fence_command_pack 清空 mutation continuations，并把 safety contract、recommended next step 和 resolution gate 对齐；guided_fence 同步移除 identity selection 与后续 mutation steps。
• focused tests 增至 13 个，新增 missing registry、empty registry 及 no-state negative twins；bootstrap smoke 也覆盖了真实 CLI 形状。

剩余 blocker 位于 loopx/bootstrap_command_pack.py:580。if registry_error 在 unregistered_goal_connection 和 orphan projection 之前直接返回 registry_invalid。我在当前 exact head 上构造了一个 disposable project：.loopx/registry.json 内容不可解析，同时 .codex/goals/reset-goal/ACTIVE_GOAL_STATE.md 存在。shipped source CLI 的结果同时满足：

• connection_state=registry_invalid
• state_file_exists=true
• safety contract 仍报告 orphaned_goal_state_blocks_continuation=false
• transaction 仍包含 connect_if_needed、select_agent_identity、Todo planning/writeback、refresh、activation 和 quota guard
• command pack 仍给出 bootstrap、registration、plan 与 refresh continuation

这和上一轮 missing-registry 反例的安全后果相同：registry 已经不再提供可信 Goal authority，但 surviving state 存在时 host 仍拿到了建立第二 authority 的可执行引导。registry_invalid 诊断当然要保留；需要修的是它不应同时放行 mutation continuation。最小修复是在 registry-error 分支探测同一 orphan candidate，保留 parse error/registry_invalid 事实，但投影现有 no-continuation fence。请补 invalid-registry + surviving-state 的真实 CLI regression，以及 invalid-registry + no-state 的 negative twin，确保不是把所有 registry 解析错误都误报成 orphan。

对主干的风险

已覆盖的分支风险控制得不错：普通全新 Goal、missing/empty registry 无 candidate、已连接 Goal都保留既有行为；gate 本身不写状态，resolution routes 也保持 preview-only。当前 head 的 missing/empty 修复没有引入新的持久化状态或权限。

但 invalid registry 并非罕见的理论输入：中断写入、人工编辑或部分损坏都可能触发 parse error。此时 packet 一方面告诉 operator registry 不可信，另一方面仍提供 bootstrap、fresh-agent、Todo、host-loop 和 quota continuation；这是一个相互矛盾的 authority projection。影响范围跨过 CLI presentation，进入后续写路径，因此仍是 P1 blocker。

本地验证：tests/control_plane/test_start_goal_orphaned_goal_state.py 为 13 passed in 2.90s；examples/bootstrap-command-pack-smoke.py 通过；changed paths Ruff 通过；git diff --check 通过。按 Goal 配置 wait_for_ci=false，没有抓取或等待远端 CI。真实 invalid-registry CLI 反例未满足安全 invariant，是本次 REQUEST_CHANGES 的决定性证据。

我的整体评价

当前 head 正确修复了上一轮反馈，而且集中 classifier/fence owner 的方向合理；bounded future-facing pass 不需要再引入新的 framework。剩余修改也很局部：让 parse-error 分支保留诊断但复用既有 orphan fence，并用 state/no-state twins 固定语义。修复后请在新 exact head 重新跑 focused tests、bootstrap smoke、Ruff、diff check 与真实 CLI twins；archive/adopt、diagnose 和 Goal-generation identity 仍可保持本 PR 已声明的后续边界，不要求扩大范围。

English verdict: REQUEST_CHANGES - head a0ca91d1d61341df260aaaf49742314ef9bca4dc fixes the prior missing/empty-registry bypass, and 13 focused tests, the bootstrap smoke, Ruff, and diff check pass; however, an exact-head real-CLI reproduction with an invalid registry and surviving Goal state still reports registry_invalid while exposing bootstrap, registration, Todo, activation, and quota continuations, so the existing orphan fence must also cover that branch while preserving the parse diagnostic.

[hahahahahayesyeseys]

Recording the CI attribution for this head so nobody has to re-derive it: both red lanes here reproduce outside this PR.

Python Tests - 11 failing tests at this head, and the same workflow on main's own push produced the identical set: the difference in both directions is empty (main run vs this PR run). The files are tests/control_plane/test_settled_replay_construction.py (8), test_blocked_transition_notice.py (2) and test_selection_replan_reentry.py (1). None of them imports or renders the goal-start packet this PR changes.

node-minimum-compatibility - 2 failures, sqlite legacy|native full mixed head reports effective ownership without writes. Both fail closed on the runner's bundled SQLite 3.50.2 against the qualified floor (3.51.3+ / 3.50.7+ / 3.44.6+) and ask for the Node 22.22.3 runtime; the message is a runtime-qualification gate, not an assertion about ownership. An unrelated PR opened the same window fails those same two tests, and this PR touches no TypeScript, provider or Node path.

Local exact-head numbers for this branch remain: 13 focused tests passed, the owning smoke passed, ruff and py_compile clean, and the command-pack module stays at 2233 against its reviewed 2240 ceiling.

[hahahahahayesyeseys]

Full tests/ sweep at this head (a0ca91d1), completing the row the body deferred: 91 failed, 10641 passed, 37 skipped in 38m59s.

Against the same sweep at the reviewed head 144072cd (91 failed, 10637 passed), the failure sets are identical - the difference in both directions is empty - and the passed count moved by exactly the 4 cases added for the registry-absence branch. The 91 remain the pre-existing set attributed earlier: 88 tests/architecture/test_semantic_* from the unavailable local TypeScript parser, 2 date-expired Lark fixtures (the base predates 277f43ab2, which froze that clock on main), and the tests/canary maintainability ratchet that is red on main.

[Job28703]

Independent review of exact head a0ca91d1d61341df260aaaf49742314ef9bca4dc (adversarial review chain, reviewer PASS at second revision):

Verdict: REQUEST_CHANGES — concurring with the second maintainer round.

The fence correctly covers missing/empty registries (13 focused tests, real-CLI smoke, roots aligned verbatim with state_backup.py:154-157). The remaining P1 blocker, verified by reading the head source directly: bootstrap_command_pack.py:580 returns registry_invalid before any orphan classification, so an unparseable registry with surviving ACTIVE_GOAL_STATE.md still exposes bootstrap/registration/Todo/quota continuations — same second-authority risk the PR exists to close. The disclosed keep-reason (preserving the parse diagnostic) does not conflict with projecting the existing fence alongside it.

CI note: the pytest/test-shard reds at this head come from test_settled_replay_construction.py (8), test_blocked_transition_notice.py (2), test_selection_replan_reentry.py (1) — none import or render the goal-start packet this PR changes; the file does not even exist in the PR tree (CI runs the merge ref). Node-min's two sqlite cases are the SQLite 3.50.2 runtime-qualification gate, fixed for the lease-inspection suite by #4857.

Suggested fix shape is the maintainer's: probe the same orphan candidate in the registry-error branch, keep the registry_invalid diagnostic, project the no-continuation fence, and pin invalid-registry ± surviving-state real-CLI twins.