Show the API's default in flag help

[giordano-lucas]

notte sessions start --help gives no hint that most of its flags are already on.

The OpenAPI spec declares defaults for ten SessionStart fields, but SchemaRef had no Default member, so the value was never unmarshalled. Field.Default was always nil, getDefaultValue's Default branch was dead code, every flag registered as a Go zero value, and cobra printed nothing.

The result reads backwards:

Flag	Real default	What help implied
--solve-captchas	true	off unless passed
--headless	true	off unless passed
--use-file-storage	true	off unless passed
--max-duration-minutes	15	unbounded
--idle-timeout-minutes	3	unbounded

The timeouts are the ones that bite silently — a session vanishing after 15 minutes is hard to explain when nothing says 15 anywhere.

After

--headless                 Whether to run the session in headless mode. (API default: true)
--solve-captchas           Whether to try to automatically solve captchas (API default: true)
--use-file-storage         Whether FileStorage should be attached to the session. (API default: true)
--max-duration-minutes int Maximum session lifetime in minutes ... (API default: 15)

The default goes in the description, not the registered value

That distinction is the whole point, and I got it wrong first.

Request builders send non-boolean fields on a zero-value check (if X != "", if X > 0). Registering the API default would make those checks always true, so every session start would transmit browser_type=chromium, max_duration_minutes=15, idle_timeout_minutes=3 — and the API could never change its own default again, because the client would always override it. That's the same failure #58 fixed, in reverse.

An intermediate version of this branch did exactly that. getDefaultValue is now pinned to zero values with a comment explaining why, so nobody "fixes" it later.

Booleans are already gated on cmd.Flags().Changed(), so nothing about what gets sent changes.

Verification

A session started with no flags is byte-identical to v0.0.30:

{"use_file_storage": true, "headless": true, "solve_captchas": true, "max_duration_minutes": 15}

• go build, go vet, gofmt -l clean
• go test ./internal/... — all 10 packages pass
• make generate reproduces the committed output

Also picks up defaults on personas create and vaults create.

Note on use_file_storage

This started from a question about whether the recent API-side change making use_file_storage default to true was reaching the CLI. It is — the CLI omits the parameter when the flag isn't passed, so the server default applies, and a session started without flags reports use_file_storage: true. No CLI change was needed for the behaviour; only the help text was misleading.

Worth knowing the flag is now effectively an opt-out: --use-file-storage=false disables the session file store, after which notte page download fails with Cannot execute download_file because no storage object was provided. If that's undesirable, the flag could be dropped or renamed, but that's a separate call.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

The PR propagates OpenAPI defaults into generated Cobra help descriptions while deliberately retaining Go zero values for registered flags.

• Adds default metadata to the generator’s schema model and field conversion.
• Annotates generated agent, session, persona, and vault flag descriptions with API defaults.
• Keeps request construction behavior unchanged by removing API defaults from flag registration.

Confidence Score: 4/5

The PR appears safe to merge functionally, with non-blocking cleanup needed for missing regression coverage and the unused compiled generator artifact.

The generated help changes preserve zero-valued flag registration and no current runtime failure was established, but the parser/code-generator behavior is untested and an unnecessary binary is tracked.

Files Needing Attention: scripts/gen-flags/codegen.go, scripts/gen-flags/parser.go, gen-flags

Important Files Changed

Filename	Overview
scripts/gen-flags/parser.go	Parses and propagates OpenAPI default values, but the new behavior has no targeted automated coverage.
scripts/gen-flags/codegen.go	Appends API defaults to help while preserving zero-value registration; targeted tests should pin both behaviors.
internal/cmd/sessionstart_flags.gen.go	Regenerated session help now accurately displays scalar API defaults without changing registered flag values.
gen-flags	Adds an unused compiled generator artifact that should be removed from source control.

Prompt To Fix All With AI

### Issue 1
scripts/gen-flags/codegen.go:164-175
**Default generation lacks regression tests**

The new schema-default parsing and help-generation behavior has no unit or integration coverage, so regressions can silently remove or misformat API defaults—or register them as client-side values—without a targeted test detecting the change.
- Add a comment if the PR does n... ([source](https://app.greptile.com/review/custom-context?memory=instruction-0))

### Issue 2
gen-flags:1
**Unused generator binary is tracked**

Generation runs `scripts/gen-flags` directly from source, so this compiled, platform-specific executable has no repository consumer and adds opaque binary churn that can become stale independently of the generator source.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "fix: show the API's default in flag help" | Re-trigger Greptile}