[codex] Improve client mod coexistence safeguards#41
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ddb3fe4d7a
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 572d8fccd9
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b66e074c59
ℹ️ 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".
Summary
This keeps Eclipse friendlier when another client UI mod or runtime loader is present without adopting any peer-mod behavior:
UIOptions.AttributeBuffs=falseRuntime Evidence
Local proof run
eclipse-bloodcrafthub / combined-candidate / 20260517-111812was markedpass-with-warningafter a dedicated harness rerun.Observed success markers:
The warning is intentionally not fixed here: Bloodcraft still logs an early startup-check warning and
NullReferenceExceptionbefore later initialization. That should be handled in a separate Bloodcraft follow-up.Validation
dotnet build Eclipse.csproj --configuration Release --no-restore -p:DeployToClient=falseC:\Program Files\Git\bin\bash.exe .codex/scripts/version-metadata.sh.codex/scripts/*.ps1git diff --check/git diff --cached --check