Add readiness evidence remediation queue - #119
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f106e1f3a1
ℹ️ 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".
| row.append(value) | ||
| elif isinstance(value, (int, float)): | ||
| row.append(value) | ||
| else: | ||
| row.append(str(value)) |
There was a problem hiding this comment.
Normalize stable values before hashing snapshots
When a saved CSV contains a blank stable field, pd.read_csv represents it as NaN, while the in-memory readiness builder emits ""; compare_readiness_frames treats both as the same empty value, but this hash encodes them as null and "". Consequently an unchanged readiness report can have no_readiness_changes while exposing different saved and proposed identities, making these identifiers unreliable anchors. Hash the same normalized boolean/text values used by the comparison.
Useful? React with 👍 / 👎.
Summary
Boundaries
Verification
Research workflow evidence only; not investment advice or a recommendation.