Drop the inline-spec read paths; pointer configs are the only shape#969
Merged
Conversation
RhysSullivan
force-pushed
the
spec-blob-boot-migration
branch
from
6eb9923 to
2536422
Compare
RhysSullivan
force-pushed
the
drop-inline-spec-fallback
branch
from
3115a4e to
52c0bae
Compare
This was referenced Jun 12, 2026
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 73d64a5 | Commit Preview URL Branch Preview URL |
Jun 12 2026, 05:46 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 73d64a5 | Jun 12 2026, 05:47 AM |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
RhysSullivan
force-pushed
the
spec-blob-boot-migration
branch
from
2536422 to
7b1a1e3
Compare
RhysSullivan
force-pushed
the
drop-inline-spec-fallback
branch
from
52c0bae to
26b23dd
Compare
With cloud backfilled out-of-band and the libSQL hosts rewriting at boot through the data-migration ledger, every database converges on the pointer shape (specHash / introspectionHash) before this code reads it. The transitional dual-read loaders and the optional inline fields (openapi config.spec, graphql config.introspectionJson) are gone from the stored-config schemas; addIntegration still ACCEPTS inline introspection JSON as input, but persists only the blob hash. The graphql getConfig endpoint also stops serving the introspection snapshot — same reasoning as the openapi spec removal: it's a multi-MB build artifact no client reads.
RhysSullivan
force-pushed
the
drop-inline-spec-fallback
branch
from
26b23dd to
73d64a5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
With cloud backfilled out-of-band and the libSQL hosts rewriting at boot through the data-migration ledger (previous PR), every database converges on the pointer shape (
specHash/introspectionHash) before this code reads it. This removes the transitional machinery:loadSpecText/loadIntrospectionJsonread the blob store only.config.spec, graphqlconfig.introspectionJson).addIntegrationstill accepts inline introspection JSON as input, but persists only the blob hash.getConfigendpoint stops serving the introspection snapshot — same reasoning as the openapi spec removal earlier: it's a multi-MB build artifact no client reads.Compatibility
A database that somehow reaches this code with an un-migrated inline row decodes (the schemas tolerate unknown fields) but resolves zero tools, rather than silently working off the inline text — the migrations are the supported path, and a test pins that behavior.
Testing
Projection of the new contract in spec-blob.test.ts (pointer reads work, inline rows yield no tools); full openapi/graphql suites and repo gates green.
Stack