Fix Codex Fast mode accounting from current trace records

[Anri-Lombard]

Summary

CodexBar currently misses Fast/Priority mode for current Codex/Luna sessions. Those sessions record priority usage in Submission trace rows with service_tier: Some(Some("priority")), while the scanner only recognized legacy websocket request rows.

This causes current Fast mode sessions to be classified as standard-cost usage.

Changes

• Include current priority Submission rows in bounded and incremental SQLite scans.
• Parse the submission turn ID and thread ID without retaining prompt text.
• Keep legacy websocket trace parsing unchanged.
• Add parser and SQLite regression coverage.
• Regenerate the parser hash required by the repository checks.

Validation

• swift test --filter CostUsageScannerCodexPriorityTests — 21 passed
• swift test --filter CostUsageScannerPriorityTests — 16 passed
• make check — passed, including SwiftFormat/SwiftLint and repository gates
• make test — passed, 758 selections across 64 groups

Observed local evidence: Codex logs contain service_tier: Some(Some("priority")) for current sessions, while the pre-fix CodexBar cache classified the same session as standard.

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: Fix Codex Fast mode accounting from current trace records This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d0b94e5806

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restrict the priority marker to thread settings

When a standard-mode user prompt itself contains service_tier: Some(Some("priority"))—for example, while debugging or pasting a trace—the serialized Submission row includes that text in op: UserInput even though its actual ThreadSettingsOverrides uses the default tier. This whole-body check therefore marks that standard turn as Fast and overstates its cost; inspect the actual thread_settings field rather than accepting the marker anywhere in the prompt-bearing row.

Useful? React with 👍 / 👎.