Skip to content

docs(services-checklist): the capability-flag bullet names the retired features map and the retired workflow slot #15982

Description

@claude

Measured (2026-09-05, content/docs/kernel/services-checklist.mdx at 04b60ff7d)

One bullet in the "When a plugin registers a service" list carries two claims that were already stale before today, and both survive a per-file read:

- `features` flags follow for the slots that have one — `search`, `files`,
  `analytics`, `ai`, `workflow`, `notifications`, `i18n` (...)
  1. features is the retired spelling. 两个 discovery 生产者都在线上返回 schema 未声明的顶层字段(scoping / features / endpoints),且 REST 形状永远无法通过 DiscoverySchema #4828 renamed the runtime dispatcher's top-level features map to the canonical capabilities, which DiscoverySchema has always declared; no producer emits features today. The same page already uses capabilities.websockets elsewhere, so the page contradicts itself.
  2. workflow is a retired slot. discovery 的 workflow / graphql 槽位还声明着两条无人挂载的 route —— #4318 同款,但目前"上了膛没击发" #4451 (v17) removed the workflow slot and its CoreServiceName member outright (ADR-0115 Evidence 5), so no capability flag can follow it.

Neither is a capability flag that exists, so a reader wiring a client against this list looks for two keys that are not on the wire.

Why this is a separate card

Found while closing #14646, which rewrote the third claim in that same parenthetical (websockets is no longer hardcoded). That one was falsified by #14646's own change and was fixed in its PR under the published-docs rule. These two were wrong before it and are not in its scope — filed rather than folded in.

Suggested fix

Correct the bullet to the canonical capabilities vocabulary and drop workflow; the authoritative key list is WellKnownCapabilitiesSchema in packages/spec/src/api/discovery.zod.ts, which is closed, so the list can be checked against it rather than hand-maintained.


Generated by Claude Code

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions