Repository navigation
t27c serve: Railway GraphQL host backpack.railway.com/graphql does not answer; the API is backboard.railway.com/graphql/ - #6091
Conversation
RAILWAY_GRAPHQL pointed at a Railway GraphQL host that does not answer (HTTP 000 within 15 s, measured 2026-10-04), so every `t27c serve` session-create failed before reaching Railway. The constant now targets Railway's public API at backboard.railway.com/graphql/v2 (HTTP 200), and the GraphQL call returns an answer - success or a Railway error - not a connection timeout. Add a unit test asserting the endpoint's host and path so the retired host cannot come back unnoticed, and record the measurement in docs/now/2026-10-04-railway-graphql-host.md. No Railway token or variable was set or read; CI runs the cargo tests. Closes #6085
A pull request must add exactly one docs/now entry and a bee has no way to know that: its brief names a boundary file and acceptance criteria, and docs/now/ is neither. The publisher adds it rather than failing the gate. Closes #6085 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Reviewer bee verdict for head 65d6ac35135ff39334d1d072bb73e0af64fb894a (tools/bees/reviewer.py, zai glm-4.7-flash, glm-4.5-flash, 12 turns, 258 s).
The review below approved this head. The bot does not approve a head that changes bootstrap/src/railway.rs: a person decides. Nothing here counts as an approval.
BEE-VERDICT: NEEDS_PERSON
summary: Updated Railway GraphQL endpoint from non-responding backpack.railway.com to working backboard.railway.com API
criterion: FR-001 -- met -- bootstrap/src/railway.rs:10 changed the constant to the correct endpoint
criterion: FR-002 -- met -- bootstrap/src/railway.rs:277-291 added comprehensive unit test
criterion: FR-003 -- met -- docs/now/2026-10-04-railway-graphql-host.md created with measurement table
discounted-check: duplicate-bodies -- already failed on master (API rate limit prevented detailed analysis)
discounted-check: fpga-conformance -- already failed on master (elaboration errors rose from 176 to 178, likely due to iverilog version change)
discounted-check: spec-guards -- already failed on master with identical ring drift/unrelated status
Evidence
Evidence
Acceptance Criteria Verification
-
FR-001:
RAILWAY_GRAPHQLbecomeshttps://backboard.railway.com/graphql/v2; no other reference tobackpack.railwayremains- ✅ MET - The constant was updated from
https://backpack.railway.com/graphqltohttps://backboard.railway.com/graphql/v2 - ✅ MET -
grep -c "backpack.railway" bootstrap/src/railway.rsprints0
- ✅ MET - The constant was updated from
-
FR-002: Unit test added to assert the constant's host and path
- ✅ MET - Added
railway_graphql_targets_public_api()test that:- Asserts full URL matches
https://backboard.railway.com/graphql/v2 - Separately asserts host is
backboard.railway.com - Separately asserts path is
graphql/v2
- Asserts full URL matches
- ✅ MET - Added
-
FR-003: Documentation entry with measurement table
- ✅ MET - Created
docs/now/2026-10-04-railway-graphql-host.mdwith the measurement table showing:https://backpack.railway.com/graphqlreturns 000 (no answer)https://backboard.railway.com/graphql/v2returns 200 with response
- ✅ MET - Created
Success Criteria
- ✅
grep -c "backboard.railway.com/graphql/v2" bootstrap/src/railway.rsprints3(at least 1 required) - ✅
grep -c "backpack.railway" bootstrap/src/railway.rsprints0
Boundary Respect
The PR only touches:
bootstrap/src/railway.rs(within boundary)docs/now/files (within boundary)
Red Checks Analysis
All three red checks were already failing on master for the same reasons, so they don't count against this head:
duplicate-bodies: Failed on master (API rate limit prevented log access)spec-guards: Failed on master - multiple rings showed DRIFTED/UNRELATED statusfpga-conformance: Failed on master - elaboration errors increased from 176 to 178
Issue Goals
The issue stated that t27c serve fails because the Railway GraphQL host doesn't answer. This change updates the endpoint to Railway's public API that does answer, exactly as requested.
Closes #6085
Written by a bee on
queen-6085and published bytools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.🤖 Generated with Claude Code