import from-code command not available (v0.40.4)

[danieldekay]

Description

The import from-code command referenced in the specfact.01-import prompt is not available in the current CLI version (v0.40.4).

Steps to Reproduce

specfact --no-interactive import from-code legacy-api --repo .

Actual Result

Command 'import' is not installed.
Install workflow bundles with specfact init --profile <profile> or specfact module install <bundle>.

Expected Result

The command should extract routes, schemas, relationships, and contracts from the codebase and create a plan bundle.

Investigation

• Installed nold-ai/specfact-codebase (v0.40.17) — provides code commands (analyze, drift, repro, validate) but no import command
• Installed all available modules: specfact-project, specfact-spec, specfact-backlog, specfact-govern, specfact-codebase
• None expose an import from-code or top-level import command
• CLI is up to date (specfact upgrade --check-only confirms v0.40.4 is latest)

Environment

• OS: macOS
• SpecFact CLI: v0.40.4
• Modules: specfact-project 0.40.19, specfact-spec 0.40.14, specfact-codebase 0.40.17, specfact-backlog 0.41.9, specfact-govern 0.40.17

Question

Is import from-code part of a module not yet published to the marketplace, or has the command been renamed/restructured? The specfact.01-import prompt template references this command extensively.

[djm81]

Created OpenSpec bugfix change issue-407-import-command-guidance and linked it to this issue.

Summary of what needs to be fixed:

• shipped import prompt resources still instruct users to run the removed flat command specfact import from-code
• canonical prompt/validation metadata still encodes the flat import syntax instead of specfact project import from-code
• import-related suggestion/recovery text still recommends the removed flat command in some paths
• targeted validation/test coverage is needed so prompt/help surfaces cannot regress back to removed flat command syntax

OpenSpec artifacts were added in the local bugfix/issue-407-import-command-guidance worktree and openspec validate issue-407-import-command-guidance --strict passes.

[djm81]

Follow-up after investigating the module migration history:

What happened:

• import from-code was part of the old pre-bundle command model.
• During the module migration, the command was classified under the project family (import_cmd -> specfact-project) instead of the codebase family.
• Later migration work also copied a large part of the brownfield/code-analysis internals into specfact_project, while other migration docs still described those internals as specfact-codebase ownership.
• The result is that the current shipped bundle surface does not expose the brownfield import workflow in a coherent public place, while prompts and docs still reference the removed flat/root form.

Why the command is no longer there in the way users expect:

• The old flat/root specfact import from-code ... path was removed as part of the grouped-command migration.
• The replacement ownership/model for brownfield import was never cleanly finalized, so the runtime surface and guidance drifted apart.
• In practice this left users with code commands for analysis/validation, but without the expected import entrypoint available from the installed bundle surface.

How this will be fixed:

• A dedicated OpenSpec follow-up has now been created: module-migration-11-project-codebase-ownership-realignment.
• This change treats the problem as an ownership/boundary issue, not just a docs bug.
• Target direction: code-first brownfield workflows such as import from-code will be reclassified under specfact code ..., while specfact project ... will be narrowed to SpecFact bundle/workspace artifact lifecycle commands.
• It also requires aligning pending migration changes so we do not hard-code the wrong command ownership again.

Short version: the command disappeared from the expected surface because the module split left project vs codebase ownership ambiguous. We are correcting that at the spec/change level first so the runtime, docs, prompts, and bundle boundaries can be fixed consistently.

[djm81]

Tracked by change issue #408 under feature #354 and architecture epic #194.