Repository navigation
fix(queen): ship specs/ in the image so the scheduler can read its contract - #481
Merged
gHashTag merged 1 commit intoSep 13, 2026
Conversation
…ntract The first GitHub deploy of #480 on Railway (2026-09-13) answered GET /queen/scheduler with 503 "scheduler contract unreadable: ENOENT /app/specs/t27_compiler.wasm". The route was truthful; the Dockerfile copied apps/server and packages/* but never specs/, so the compiler and the 59 cards were absent from the image. - Dockerfile: COPY specs specs, then a RUN that fails the build unless the wasm sha256 equals the one specs/PIN names (measured locally: 4d9c0447...0aee4 matches). - docs/queen-inngest.md: how the env was actually set on Railway (variable references to the inngest/inngest service, explicit INNGEST_SERVE_HOST), that TRIOS_GITHUB_API_TOKEN is not set there yet, that the service now deploys from GitHub (root trios/agent-server) with auto deploy unavailable, and the 503 above with its fix.
gHashTag
merged commit Sep 13, 2026
e1f4f04
into
fix/queen-worker-provider-and-prompt-size
15 of 17 checks passed
❌ Tests failed — 3/2119 failed
Failed tests
|
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
The first GitHub deploy of #480 on Railway (project 999, service
trios-agent-server, 2026-09-13) answered:The route was truthful. The Dockerfile copied
apps/serverandpackages/*but neverspecs/, so the compiler wasm and the 59 cards were absent from the image (/healthwas 200 the whole time, so the old smoke check could not see it).Change
Dockerfile:COPY specs specs, then aRUNthat fails the build unless the wasm sha256 equals the onespecs/PINnames. Measured locally:4d9c0447b5ca288790ab03d3dffc2dda629ed47af9d6731a105fc923aea0aee4matches.docs/queen-inngest.md: the env as actually set on Railway (variable references to theinngest/inngestservice, explicitINNGEST_SERVE_HOST), thatTRIOS_GITHUB_API_TOKENis not among the service variables yet, that the service now deploys from GitHub (roottrios/agent-server, auto deploy currently unavailable), and this 503 with its fix.Evidence after deploy (to be added)
GET /queen/scheduler-> 200, 59 functions (33 cron: 12 with cron trigger, 21 tick-only; 26 skill), 0 refused.GET /api/inngest-> not 404/503.No secret values appear anywhere; only variable names.