bug: Codex interactive resume uses invalid provider session IDs

[furquanuddin94]

Summary

Codex interactive resume can fail because Stoneforge persists invalid provider session IDs captured from terminal text.

Symptom

When resuming a Codex Director session, Stoneforge can invoke:

codex resume management

Codex exits with:

No saved session found with ID management. Run `codex resume` without an ID to choose from existing sessions.

Expected behavior

Stoneforge should resume with a real Codex session UUID, or not offer resume when no valid provider session ID is known.

Evidence

In local Smithy agent history, the Director has persisted bogus providerSessionId values:

management
found
_ID
s

Codex's own session metadata uses UUID-shaped IDs, for example:

019e125f-e248-7082-b93e-b02a506378e3

Likely cause

The Codex interactive session output parser appears to treat broad terminal text matches as provider session IDs. For example, ordinary output text such as Agent Session Management can produce management, and No saved session found... can produce found.

That captured value is persisted in session history and later sent back to Codex resume.

Environment

• Codex CLI: 0.130.0
• Stoneforge local dev stack: pnpm dev
• Provider: Codex
• Session type: interactive Director