Stabilize memory Phase 2 input ordering

[jif-oai]

Why

Phase 2 still needs to choose the most relevant stage-1 memory outputs by usage and recency, but exposing that ranking as the rendered raw_memories.md order creates unnecessary large diff. Usage-count or timestamp changes can reshuffle otherwise unchanged memories, making the workspace diff noisy and giving the consolidation prompt a misleading recency signal from file position.
This fix will reduce token consumption

What Changed

• Keep the existing top-N Phase 2 selection ranking by usage_count, last_usage, source_updated_at, and thread_id.
• Return the selected rows in stable ascending thread_id order before syncing Phase 2 filesystem inputs.
• Update the memory README, raw memories header, and consolidation prompt so they describe the stable order and tell the prompt to use metadata and workspace diffs instead of file order as the recency signal.
• Adjust the memory runtime tests to use deterministic thread IDs and assert the stable return order separately from the ranked selection semantics.

Test Coverage

• Existing memory runtime tests in codex-rs/state/src/runtime/memories.rs now cover the stable returned ordering for Phase 2 inputs.

[jif-oai]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

ℹ️ 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".