[Bug]: fw upgrade --dry-run run from a consumer project prints no preview at all (only 'would clone' / 'would re-invoke') #106

Bug Description

From a vendored consumer, the bare call clones upstream and re-invokes itself. In dry-run mode it stops before cloning, so the operator gets only:

Bare-from-consumer detected — auto-cloning upstream
  Upstream URL:  https://github.com/DimitriGeelen/agentic-engineering-framework.git
  Resolved via:  .framework.yaml upstream_repo:
  Target:        <project>
  [dry-run] would clone ... into /tmp/fw-upstream-XXXX/fw
  [dry-run] would re-invoke: /tmp/fw-upstream-XXXX/fw/bin/fw upgrade <project> --dry-run

Nothing about the target version, the files that would change, or the local edits that would be overwritten. Run from a clone, the same dry run prints the full ten-step preview, including the step 4b warning about local files that would be overwritten (the most useful line before an upgrade).

Steps to Reproduce

1. In a vendored consumer: .agentic-framework/bin/fw upgrade --dry-run (or with --from-upstream <url>).
2. Seven lines, no preview.

Expected Behavior

In dry-run, clone upstream into a temporary directory anyway (it does not modify the project) and print the full preview, then remove the clone.

Actual Behavior

The preview is empty, so an operator either upgrades blind or has to find the clone-based workaround alone (which also needs the workaround of the clone's bin/fw re-routing, reported separately).

fw doctor output

AI Agent

Claude Code

Operating System

Linux

Additional Context

1.8.11 (e42aa41), vendored consumer, Linux (Ubuntu 20.04), non-root account, Claude Code. Also found independently by another consumer project on the same host; its reproduction was re-run here on 1.8.11.