Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/ccusage/src/commands/all.ts`:
- Around line 137-146: The table configuration is incorrectly reading the CLI
flag directly (ctx.values.compact) so config defaults in mergedOptions are
ignored; change both occurrences that set forceCompact (in the tableConfig
objects used when building tables in this command) to use mergedOptions.compact
instead of ctx.values.compact so the merged config (defaults/commands.all) is
respected; search for the tableConfig declarations (and any other places where
forceCompact is assigned) in this file and replace ctx.values.compact with
mergedOptions.compact.
- Around line 66-72: The Codex rows are built without applying the requested
ordering; update the build/emission to respect mergedOptions.order by passing
the order into buildDailyReport (i.e., call buildDailyReport(..., { ..., order:
mergedOptions.order }) when constructing codexRows) and/or apply the same
ordering step used for Claude rows right after codexRows is produced; then
ensure the JSON emission block (the codex JSON path around the current emit at
lines 121-123) and the table rendering block (the codex table path around lines
216-249) use the ordered codexRows (or call the shared order helper used
elsewhere) before emitting.
- Around line 38-41: The code treats --jq as toggling JSON mode (useJson =
Boolean(mergedOptions.json) || mergedOptions.jq != null) but still always dumps
the entire payload before returning; update the output path (the block around
lines 97–128 that currently prints the full payload and returns) to detect
mergedOptions.jq and, when present, run the jq filter against the JSON payload
and print the filtered result (fall back to printing full JSON only when
mergedOptions.jq is absent); keep the existing logger.level adjustment for pure
JSON mode (useJson) but ensure applying mergedOptions.jq controls final printed
output rather than always dumping the raw payload.
- Around line 30-259: The current try/catch around normalizeFilterDate should be
replaced with the repository's Result-based pattern: use Result.try to call
normalizeFilterDate for mergedOptions.since and mergedOptions.until, check
Result.isFailure for each result, call logger.error with the
result.error.message and process.exit(1) on failure, and assign
codexSince/codexUntil from the successful result.value; update the block that
currently references normalizeFilterDate, mergedOptions, logger.error, and
process.exit to use Result.try, Result.isFailure, and result.value instead.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/ccusage/src/commands/all.ts`:
- Around line 75-81: The Codex rows returned by buildDailyReport (used in
codexRowsRaw) are formatted for display with locale/timezone, so for --json/--jq
output create a separate JSON payload that preserves canonical ISO timestamps:
iterate codexRowsRaw (or better, map directly from codexEvents if original
timestamps are available) and produce codexJsonRows where each item contains a
stable date field (e.g., date_iso or date) set to an ISO 8601 UTC string
(Date.toISOString of the original timestamp) plus the remaining numeric/metric
fields; replace usages that currently emit the display rows (the code around
codexRowsRaw and the similar block at lines 132-134) to emit this new
codexJsonRows for JSON/JQ output while leaving display formatting unchanged for
human output.
- Around line 32-280: Add an in-source Vitest block guarded by if
(import.meta.vitest != null) that unit-tests the allCommand export covering key
branches: JSON output (--json), jq processing (--jq), row ordering
(mergedOptions.order asc/desc) and the combined total line; create a mock ctx
and stub/spy the helper functions used by allCommand (loadDailyUsageData,
loadTokenUsageEvents, buildDailyReport, processWithJq) and logger methods so you
can assert outputs and error paths, and stub CodexPricingSource (pricingSource)
to avoid real disposal side-effects (ensure its Symbol.dispose is a no-op).
Locate tests around the allCommand definition and use the same mergedOptions
inputs (e.g., set mergedOptions.jq, mergedOptions.json, mergedOptions.order) to
drive each branch and assert the expected log/output, and verify combinedCost is
computed from claudeTotals.totalCost and codexTotals.costUSD.

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@apps/ccusage/src/commands/all.ts`:
- Around line 41-44: The code sets logger.level = 0 when useJson (computed from
mergedOptions.json or mergedOptions.jq) but never restores it, causing global
side effects; update the all command to save the original logger.level into a
local variable before setting it to 0 and then restore that saved level after
the JSON/JQ execution completes (ensure restoration runs in finally/callback to
cover errors). Apply the same save-and-restore pattern to the second occurrence
that currently sets logger.level (the block around the other JSON/JQ handling)
so subsequent in-process invocations do not inherit the muted logging state.