Release: Profile Operations And First-Run Evidence

Forgeflow 4.3.23 turns the profile system into an operational workflow, captures first-run outcomes as local evidence, and adds a compact release verification shortcut. The release also teaches review agents how to treat profile guidance without letting preferences override current instructions, safety, or validation evidence.

Profile Operations

• New /forgeflow-profile-review command groups profile conflicts, scope moves, ask-user prompts, and cleanup actions before agent-heavy work.
• New check-profile-compliance.js verifies profile guidance boundaries across installed-safe command, helper, and representative agent prompt files.
• Atlas, Compass, Lumen, Warden, Smith, and Arbiter review prompts now include explicit profile-guidance boundaries.
• Project intelligence now raises a profile-review next-work candidate when profile suggestions or conflicts need attention.

First-Run Evidence

• New /forgeflow-first-run-result records local first-run health, smoke, profile, decision, friction, next action, and notes under .forgeflow/<project>/first-run-results/.
• First-run free text is intentionally conservative: it rejects secrets, private URLs, paths, source snippets, raw settings markers, and likely customer or account names.
• Result filenames include UUID suffixes so repeated or concurrent recordings do not overwrite prior evidence.

Release Verification

• New /forgeflow-release-verify prints the compact local post-publish verification summary for sharing.
• The release verification wrapper accepts --save, --compare-last, and --json in any order.
• Release gate, health, install manifest, runtime helper contract, README, and wiki docs now include the new helpers and commands.

Validation

• Full scripts/forgeflow/test-*.js suite
• node scripts/forgeflow/smoke-check.js --mode source --json
• git diff --check
• Forgeflow review loop reached approval from Warden, Atlas, and Compass after privacy and collision fixes.