[Story] Runtime Discovery Reliability for Installed Modules and Monorepos

[djm81]

User Story

As a SpecFact CLI user installing official modules into a clean runtime or initializing IDE prompts in a monorepo, I need installed module commands and environment manager detection to reflect the real runtime state so that clean installs do not report false missing modules or block IDE setup.

OpenSpec Change

• Change ID: runtime-01-discovery-reliability
• Branch: bugfix/runtime-01-discovery-reliability
• OpenSpec source: openspec/changes/runtime-01-discovery-reliability/
• Parent feature: [Feature] Marketplace Module Distribution #353

Source Bug Reports

This user story tracks remediation for:

• [Bug] Module detection fails after clean install - commands show as available but don't execute #552
• Bug Report: Environment Manager Not Detected in Monorepo Structure #553
• Bug: 'specfact code' fails despite successful module installation #554

The bug reports remain direct user reports and are not nested directly under an epic or feature. This user story blocks those bug reports until the OpenSpec change is implemented, validated, and merged.

Scope

• Load enabled installed module src/ roots before lazy command import so clean installed modules can import sibling official module packages.
• Classify installed-but-unloadable module commands with runtime/import failure diagnostics instead of false absent-module messaging.
• Detect supported environment managers in rootless monorepos and via PATH.
• Add specfact init ide --env-manager <auto|uv|hatch|poetry|pip> for explicit operator control.

Repository Decision

Keep this remediation in nold-ai/specfact-cli; do not transfer #552, #553, or #554 to nold-ai/specfact-cli-modules. The root causes are CLI runtime discovery/loading and CLI environment manager detection.