Workflow-backed slash commands (e.g. /AfkBuild) missing from autocomplete after 2.1.243

Version: 2.1.245 (regression appears to start at 2.1.243, released 2026-08-24)
OS: macOS 26.5.2 (Build 25F84), darwin-arm64

Summary:
A slash command backed by a project workflow script no longer appears in the / autocomplete list when starting a plain interactive session (claude from the command line, no flags).

Setup:

• Project has .claude/workflows/AfkBuild.js, a valid workflow script.
• Project .claude/settings.json sets "enableWorkflows": true.
• This previously worked (confirmed working the day before the update).

Steps to reproduce:

1. cd into the project directory.
2. Run claude (plain, no flags).
3. Start typing /Afk.

Expected: Autocomplete offers /AfkBuild (the workflow command), alongside any matching skills.

Actual: Autocomplete only shows /afkbuild-discipline (a skill in the same project) — /AfkBuild does not appear at all, and is presumably not invokable.

Suspected cause:
The 2.1.243 changelog entry: "Improved startup time: sandbox and MCP bring-up no longer block the first frame, bare launches skip subcommand registration, and workflow discovery, settings, and trust-store work is cheaper." This looks like it may have inadvertently scoped workflow-command registration to fewer launch paths than intended — nothing in the changelog indicates workflow slash commands are meant to stop appearing on a normal claude launch.

Notes:

• Not caused by the --bare CLI flag — the session was started as a plain claude invocation.
• enableWorkflows: true is confirmed present and correctly scoped in project settings; npm run vendor:check confirms the workflow file itself is valid and up to date.
• Workaround: a Workflow tool call by name (e.g. name: "AfkBuild") still works when driven by an agent inside a session; only the user-typed /AfkBuild slash form is affected.