`fedify init` prompt flow and documented CLI options are out of sync

[dahlia]

Summary

The current fedify init implementation does not match the documented interactive flow and CLI options. This is visible in the npm distribution, but the underlying problem is that the implementation and documentation have diverged.

Steps to reproduce

1. Run npx -y @fedify/cli@2.0.5 init --help
2. Compare the displayed options with the documentation at docs/cli.md
3. Run npx -y @fedify/cli@2.0.5 init and observe the prompt order

Actual behavior

The current implementation:

• does not expose -r/--runtime
• always goes through a web framework selection step
• does not provide a bare-bones/no-framework path
• prompts in the order dir -> web framework -> package manager -> message queue -> key-value store

Expected behavior

Either:

• the implementation should match the documented flow and options
  or:
• the documentation should be updated to match the implementation

At the moment they describe different products.

Evidence

The code in packages/init/src/command.ts defines only --web-framework, --package-manager, --kv-store, and --message-queue.
The code in packages/init/src/ask/mod.ts runs prompts in this order: fillDir, fillWebFramework, fillPackageManager, fillMessageQueue, fillKvStore.
However, docs/cli.md still documents:

• -r/--runtime
• runtime-first flow
• optional web framework integration
• fresh as a web framework option

Root cause

This appears to be a documentation/UX contract drift after the init functionality was moved into @fedify/init and the prompt model was simplified around package managers rather than an explicit runtime abstraction.

Suggested fix

Choose one source of truth and align the other side to it:

• If the current implementation is intended, update docs/cli.md and related docs to remove --runtime, remove bare-bones wording, and document the actual prompt order and available frameworks
• If the documentation reflects the intended UX, restore a runtime abstraction in the CLI and reintroduce the documented no-framework flow

Notes

This issue is intentionally scoped to the prompt flow and CLI/documentation contract mismatch. The JSR/Deno crash reported in #623 should be tracked separately.

[sij411]

Can you assign me on this

[sij411]

./fedify init --help
Initialize a new Fedify project directory.
Usage: fedify init [-w/--web-framework WEB_FRAMEWORK] [-p/--package-manager PACKAGE_MANAGER] [-k/--kv-store KV_STORE] [-m/
       --message-queue MESSAGE_QUEUE] [--dry-run] [[-d/--debug]] [(--ignore-config | --config PATH)] [DIR]

Initialize a new Fedify project directory.
By default, it initializes the current directory.  You can specify a different directory as an argument.
Unless you specify all options (-w/--web-framework, -p/--package-manager, -k/--kv-store, and -m/--message-queue), it will prompt you to
select the options interactively.

Initialization options:
  -w, --web-framework WEB_FRAMEWORK  The web framework to integrate Fedify with. (choices: hono, nitro, next, elysia, express)
  -p, --package-manager PACKAGE_MANAGER  The package manager to use for installing dependencies. (choices: deno, pnpm, bun, yarn, npm)
  -k, --kv-store KV_STORE     The key-value store to use for caching and some other features. (choices: denokv, redis, postgres)
  -m, --message-queue MESSAGE_QUEUE  The message queue to use for background tasks. (choices: denokv, redis, postgres, amqp)
  --dry-run                   Perform a trial run with no changes made.
  DIR                         The project directory to initialize.  If a specified directory does not exist, it will be created.

Global options:
  -d, --debug                 Enable debug mode.
  --ignore-config             Ignore all configuration files.
  --config PATH               Load an additional configuration file.

I run this, and there is no runtime related options. So I think we should fix the documentation. I'm not sure when, but somehow the doc is outdated.