[BUG] Inconsistent flag naming across commands (-f vs -o for file output)

[ranveerd11]

Bug Description

Different commands use different flags for specifying output files, causing confusion:

Command	File Flag	Notes
design export	-f, --file	Works
design import	-f, --file	Works
design validate	None	Missing file input flag
rlhf export	-o, --output	Different from design

Steps to Reproduce

# Design export uses -f
ainative-code design export -f /tmp/design.json

# RLHF export uses -o (not -f)
ainative-code rlhf export -f /tmp/rlhf.json
# Error: unknown shorthand flag: 'f' in -f

# Design validate has no file flag
ainative-code design validate -f /tmp/design.json
# Error: unknown shorthand flag: 'f' in -f

Expected Behavior

Consistent flag naming across all commands:

• Either all use -f/--file
• Or all use -o/--output

Suggested Fix

1. Standardize on -f/--file for all file input/output
2. Add -f flag to design validate
3. Change rlhf export from -o to -f

Environment

• Version: v0.1.8
• Platform: darwin/arm64