Skip to content

馃敩 feat: Begin the OpenShell Backend Evaluation Track - #282

Open
lia-by-librechat[bot] wants to merge 2 commits into
mainfrom
lia/openshell-backend
Open

lia-by-librechat[bot] wants to merge 2 commits into
mainfrom
lia/openshell-backend

Conversation

@lia-by-librechat

@lia-by-librechat lia-by-librechat Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Start the Code API OpenShell backend track without changing production routing.
  • Pin OpenShell v0.1.2 and add an explicit lifecycle probe with a strict policy, digest-pinned image, phase timeouts, redacted errors, and independent cleanup.
  • Add focused offline tests to CI and document signed-runner compatibility, isolation, queue fencing, lifecycle, license, and rollout gates.

Verification

  • 20 focused Node probe tests pass locally.
  • JavaScript syntax, Prettier, and patch whitespace checks pass.
  • Official v0.1.2 CLI version and create/exec help-parser flags verified without starting a gateway.
  • Live gateway, hardened runner compatibility, tenant isolation, and load tests are not run. These remain acceptance gates, not claimed capabilities.

The CLI is an evaluation dependency only. No SDK, deployed gateway, registered backend, production defaults, or state migration is added.

@lia-by-librechat

Copy link
Copy Markdown
Contributor Author

Head: ab2029e

Starts the OpenShell evaluation track with a pinned lifecycle probe, strict policy, offline regression tests, and integration/rollout gates. No production backend or routing change.

Local: 20 probe tests pass; JavaScript syntax, Prettier, and patch whitespace checks pass. Live gateway, runner compatibility, isolation, and load checks remain unrun.

@lia-by-librechat

Copy link
Copy Markdown
Contributor Author

Verification update for ab2029e:

The 20 probe tests also pass on Node 20.11.0. Deployment Config Tests, including the new probe step, pass.

CI Code Package Tests (Node 24.16.0) failed in the existing process-lock contention test with "Missing expected rejection." Its test and implementation are byte-identical to the PR base. Lambda MicroVM Runner Image remains running. No unrelated lock changes are included.

@lia-by-librechat

Copy link
Copy Markdown
Contributor Author

Independent review complete for ab2029e.

No findings at any severity. Reviewed the complete patch and pinned upstream contracts. Focused probe tests and additional child-process cancellation checks passed. No new head was pushed.

Local verification: 20 probe tests pass on both Node 20.11.0 and 24.16.0; JavaScript syntax, Prettier, patch whitespace, and documentation link checks pass. Official v0.1.2 CLI version and create/exec help-parser flags were verified without a gateway. No TypeScript files changed, so workspace typechecks were not run.

CI: all completed lanes pass except Code Package Tests (Node 24.16.0), which failed in the unchanged process-lock contention test. Lambda MicroVM Runner Image (arm64) remains running.

Live gateway, hardened-runner compatibility, effective policy enforcement, tenant isolation, crash reconciliation, and scaling tests remain unrun acceptance gates. No deployment or production routing change.

@lia-by-librechat

Copy link
Copy Markdown
Contributor Author

Focused fix: #283, head 73742a8028c0de2bad6a708f8324471c169b8514.

Node 24 forced-GC reproduction received the exact locked marker, then logged a FileHandle GC-close warning. The lock fd disappeared while the owner remained alive, allowing the competing acquisition. The fixture鈥檚 interval kept the process alive without retaining its pending promise resolver.

A timer-backed wait preserves the descriptor. The strengthened test forces GC before exact IPC readiness and still checks rejection under contention plus release after SIGKILL. It passes 100/100 focused repetitions. Restoring only the orphaned wait reproduces Missing expected rejection.

GitHub denied the failed-lane retry with 403 Resource not accessible by integration. #282 remains unmodified; #283 has fresh CI.

@lia-by-librechat

Copy link
Copy Markdown
Contributor Author

Head: f549734

Updated from main 05bad85, including the merged process-lock contention regression fix (#283). The PR still contains only the OpenShell evaluation probe, policy, offline tests, and documentation. No backend or production routing change.

Focused local checks and a fresh independent review are running for this exact head. CI has restarted. Live gateway execution and signed-runner compatibility remain unproven.

@lia-by-librechat

Copy link
Copy Markdown
Contributor Author

Verification for f549734:

Local: all 20 OpenShell probe tests pass; JavaScript syntax, Prettier, and patch whitespace checks pass. Code package typecheck and build pass. The merged contention regression passes with its explicit post-GC readiness marker.

This validates the evaluation harness offline. It does not establish live OpenShell lifecycle reliability, remote policy enforcement, or Code API runner compatibility. New-head independent review and CI are still running.

@lia-by-librechat

Copy link
Copy Markdown
Contributor Author

Independent review complete for f549734. No findings at any severity. Additional fake-CLI SIGINT/SIGTERM and deletion-cancellation checks passed.

Local: 20 probe tests, Code package typecheck/build, the merged contention regression, syntax, formatting, and whitespace checks pass.

CI at 01:03 UTC: nine checks pass, including Node 24. Node 20 package tests and the arm64 Lambda runner image remain running. No failures.

This is an offline-tested evaluation harness, not a working OpenShell backend. Live lifecycle, hardened-runner compatibility, policy enforcement, tenant isolation, remote termination, orphan reconciliation, and scaling remain unverified. No deployment or routing change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant