Patch Release: Explicit Smoke Modes

Forgeflow 4.3.3 makes smoke checks clearer for downstream projects and source release work. The default smoke path now matches what installed users need, while release guards are explicit.

Smoke Modes

• /forgeflow-smoke now defaults to downstream readiness checks: health, trends refresh, report refresh, and code map.
• /forgeflow-smoke --mode source runs Forgeflow source-tree release guards: command coverage, doc links, plugin manifest, release version, install manifest, and updater tests.
• /forgeflow-smoke --mode full runs downstream and source checks together.
• Installed downstream projects no longer mix project readiness checks with repo-only release tests.

Release Gate

• /forgeflow-release-check now calls smoke-check.js --mode source --json explicitly.
• Release Gate and Release Process docs include the same source-mode smoke command.
• test-release-version.js guards that source smoke remains part of release validation.

Validation

• Downstream install verification passed from /home/corye/Claude/GSD-CIC.
• Health passed from the downstream project after updating installed helpers.
• Downstream, source, and full smoke modes were run from the installed helper.
• Source-mode smoke passes in the Forgeflow repo and skips cleanly from installed downstream use.