feat(cli): forward extra arguments to launched agent

[BYK]

Summary

• Allow users to pass flags through to the agent process when using lore run or the agent shorthand
• Uses parseArgs token stream to identify the agent name position in argv, then slices everything after it as raw passthrough args
• In auto-detect mode (no agent name), unknown flags are reconstructed from the token stream and forwarded
• Supports -- as separator to forward flags that share names with lore's own options

Examples

lore --dangerously-skip-permissions           # auto-detect agent, forward the flag
lore claude --dangerously-skip-permissions    # forward to claude
lore run claude --model gpt-4                # forward --model gpt-4 to claude
lore --debug claude --flag                   # --debug goes to lore, --flag goes to agent
lore -- --verbose --debug                    # use -- to forward lore-like flags

Changes

• main.ts: Enable tokens: true in parseArgs, add extractAgentArgs() helper with three strategies:
  1. -- separator: everything after it goes to the agent
  2. Agent positional found: slice raw argv from after the agent name
  3. Auto-detect (no agent name): reconstruct unknown option tokens and forward them
• run.ts: Accept and forward extraArgs parameter through commandRun → resolveLaunchTarget → launchChild
• help.ts: Document argument forwarding with an "Agent arguments" section and new examples

Known Limitations

• In auto-detect mode without --, only boolean-style flags (e.g. --dangerously-skip-permissions) can be forwarded. Value-bearing flags like --model gpt-4 cannot be reconstructed because parseArgs treats unknown flags as booleans and separates the value as a positional. Use -- for those: lore -- --model gpt-4
• Flags that match lore's own options (--port, --debug, --host) are consumed by lore regardless of position. Use -- to prevent this: lore run claude -- --port 8080