Currently published 0.1.3 is stale

[PatrickBig]

@kodus/agent-readiness@0.1.3 on the npm registry (published 2026-03-09) is an older, stale build

This is a docs-vs-install divergence: the README documents both flags (lines 172–173) and contains a LiteLLM
config example using model: (lines 367–376), but neither works with the published package.

Reproduction

  npx @kodus/agent-readiness@latest --help
  # available: --ai, --api-key, --ci, --format, --min-level, --no-color, --init, --no-web
  # missing:   --model, --api-base-url

  npx @kodus/agent-readiness@latest --ai --model my-model
  # error: unknown option '--model'

Or via config, which the README explicitly supports:

  # .kodus-readiness.yml
  model: "my-model"
  apiBaseUrl: "http://localhost:4000/v1"

In 0.1.3, model: is silently ignored. (Note: the published build does read config.apiBaseUrl, but since the model
is pinned to gpt-5-mini, pointing it at a gateway that doesn't serve gpt-5-mini just fails.)

Because the version on main was never bumped, npm outdated and npx @latest both silently hand out the March build.

Impact

1. Local/self-hosted LLMs are unusable through the published package — the README's own LiteLLM example doesn't
   work as installed. Ollama, vLLM, LM Studio, OpenRouter all blocked.
2. Model is pinned to gpt-5-mini with no override path.
3. Config is a trap: users following the README set model: and see no effect (no error), wasting time.
4. Docs drift is invisible: same version on main and the registry means npm view shows no signal that a newer
   build exists in the repo.

Suggested fix

1. Bump package.json (0.1.4 or 0.2.0) — a straight republish of 0.1.3 will be rejected since that version is
   taken.
2. npm publish from current main (already includes PRs feat: add oxlint and oxfmt support #4, feat: add Bun runtime detection #5, fix: recognize uv.lock files #7, feat: make LLM model and API base URL configurable #11).
3. Consider an auto-publish workflow (on tag or merge to main) so the registry can't silently lag the repo again.

If desired, I can help draft a plan for auto-publish. Maintainer with access to npm namespace would need to furnish CI vars with secrets needed to perform the automatic publishing.