You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[finding] getting-started/index.mdx advertises GraphQL via IGraphQLService — the contract does not exist and /graphql was removed from the dispatcher #10583
Found by the docs audit of the first-run path (#10563).
What is wrong
content/docs/getting-started/index.mdx names a contract that no longer exists
and advertises a surface that was removed:
line 99 — "GraphQL + React Server Components ... (REST ships today; GraphQL is
exposed via the IGraphQLService contract)"
line 133 — table row "Build CRUD APIs by hand | REST generated from schema
(GraphQL via the IGraphQLService contract)"
IGraphQLService does not exist anywhere in packages/** on origin/main. It
survives only in CHANGELOG history (packages/runtime/CHANGELOG.md, packages/spec/CHANGELOG.md, packages/services/service-realtime/CHANGELOG.md).
The capability went with it:
packages/runtime/src/http-dispatcher.ts:2026 — // /graphql removed — GraphQL is not in the product plan (#2462 follow-on).
packages/spec/src/system/core-services.zod.ts:130-135 — "graphql was never a CoreServiceName — it existed only here and in metadata-protocol's discovery
table, naming a /graphql surface the dispatcher had already removed"; the entry
was deleted in discovery 的 workflow / graphql 槽位还声明着两条无人挂载的 route —— #4318 同款,但目前"上了膛没击发" #4451 (v17).
No handleGraphQL in the runtime dispatcher; only stale test doubles remain in packages/adapters/hono/src/__mocks__/runtime.ts.
This lands on the second page of the first-run path, in the "Real-World Benefits"
table an evaluator reads.
Related occurrences (same defect family, in-scope pages)
// Expose via REST/GraphQL as the gloss on enable.apiEnabled, where the schema's
own .describe() says only "Expose object via automatic APIs":
content/docs/concepts/metadata-driven.mdx:474
content/docs/data-modeling/schema-design.mdx:65
content/docs/data-modeling/objects.mdx:82
Out of this card's scope, flagged for whoever fixes it
content/docs/api/index.mdx:19 carries the same stale claim (/graphql returns
501 unless an IGraphQLService implementation is registered). Not audited here — content/docs/api/** was outside #10563's scope — but it belongs to the same fix.
Found by the docs audit of the first-run path (#10563).
What is wrong
content/docs/getting-started/index.mdxnames a contract that no longer existsand advertises a surface that was removed:
exposed via the
IGraphQLServicecontract)"(GraphQL via the
IGraphQLServicecontract)"IGraphQLServicedoes not exist anywhere inpackages/**onorigin/main. Itsurvives only in CHANGELOG history (
packages/runtime/CHANGELOG.md,packages/spec/CHANGELOG.md,packages/services/service-realtime/CHANGELOG.md).The capability went with it:
packages/runtime/src/http-dispatcher.ts:2026—// /graphql removed — GraphQL is not in the product plan (#2462 follow-on).packages/spec/src/system/core-services.zod.ts:130-135— "graphqlwas never aCoreServiceName— it existed only here and in metadata-protocol's discoverytable, naming a
/graphqlsurface the dispatcher had already removed"; the entrywas deleted in discovery 的 workflow / graphql 槽位还声明着两条无人挂载的 route —— #4318 同款,但目前"上了膛没击发" #4451 (v17).
handleGraphQLin the runtime dispatcher; only stale test doubles remain inpackages/adapters/hono/src/__mocks__/runtime.ts.This lands on the second page of the first-run path, in the "Real-World Benefits"
table an evaluator reads.
Related occurrences (same defect family, in-scope pages)
// Expose via REST/GraphQLas the gloss onenable.apiEnabled, where the schema'sown
.describe()says only "Expose object via automatic APIs":content/docs/concepts/metadata-driven.mdx:474content/docs/data-modeling/schema-design.mdx:65content/docs/data-modeling/objects.mdx:82Out of this card's scope, flagged for whoever fixes it
content/docs/api/index.mdx:19carries the same stale claim (/graphqlreturns501 unless an
IGraphQLServiceimplementation is registered). Not audited here —content/docs/api/**was outside #10563's scope — but it belongs to the same fix.Back-link: #10563