🐛 fix: complete Effect 4 runtime compatibility - #1463
Merged
roninjin10 merged 15 commits intoAug 1, 2026
Conversation
N0xMare
force-pushed
the
nox/fix-effect4-workflow-make
branch
from
July 31, 2026 07:39
4145d21 to
852e842
Compare
N0xMare
force-pushed
the
nox/fix-effect4-workflow-make
branch
from
July 31, 2026 18:32
852e842 to
92ca474
Compare
This was referenced Jul 31, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…low-make # Conflicts: # apps/observability/src/metrics/index.d.ts
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ants Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
roninjin10
added a commit
to N0xMare/smithers
that referenced
this pull request
Aug 11, 2026
Rebasing smithersai#1461 past the merged smithersai#1463/smithersai#1449 layers dropped the branch's merge-commit resolutions and left three kinds of residue: - every new Nanocodex file still imported the pre-rename `smithers-orchestrator` / `@smithers-orchestrator/*` specifiers; - the CI hardening that lived only in a merge commit (workflow-level `permissions: contents: read`, `persist-credentials: false` on the `test` and `coverage` checkouts) was lost; - `scripts/qualify-nanocodex-release.{mjs,test.mjs}` regained the `downloadArchive` network path the final commit had deleted. Restore all three so the branch matches the PR head's intent on top of current main. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
roninjin10
added a commit
to N0xMare/smithers
that referenced
this pull request
Aug 11, 2026
Rebasing smithersai#1461 past the merged smithersai#1463/smithersai#1449 layers dropped the branch's merge-commit resolutions and left three kinds of residue: - every new Nanocodex file still imported the pre-rename `smithers-orchestrator` / `@smithers-orchestrator/*` specifiers; - the CI hardening that lived only in a merge commit (workflow-level `permissions: contents: read`, `persist-credentials: false` on the `test` and `coverage` checkouts) was lost; - `scripts/qualify-nanocodex-release.{mjs,test.mjs}` regained the `downloadArchive` network path the final commit had deleted. Restore all three so the branch matches the PR head's intent on top of current main. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
roninjin10
added a commit
that referenced
this pull request
Aug 11, 2026
Rebasing #1461 past the merged #1463/#1449 layers dropped the branch's merge-commit resolutions and left three kinds of residue: - every new Nanocodex file still imported the pre-rename `smithers-orchestrator` / `@smithers-orchestrator/*` specifiers; - the CI hardening that lived only in a merge commit (workflow-level `permissions: contents: read`, `persist-credentials: false` on the `test` and `coverage` checkouts) was lost; - `scripts/qualify-nanocodex-release.{mjs,test.mjs}` regained the `downloadArchive` network path the final commit had deleted. Restore all three so the branch matches the PR head's intent on top of current main. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why this belongs together
The original Workflow.make repair exposed the adjacent Effect 4 runtime and declaration incompatibilities that prevented the bridge from operating reliably end to end. This update keeps those compatibility repairs together while excluding generic checkpoint and Nanocodex backend feature work.
Verification
Stack and merge order
This is layer 1 of 3 in the current compatibility/feature stack:
7bb8e91b209efb30ce7f0f60bab9b7599292762df0c287dfb5c0f37f4657d25148c8ef5bc4cb6f30f9a247f9c82033ab2cdaf6034c76e85b0dd35f00Merge in that order. Because these are cross-repository PRs, all three bases intentionally remain
main; the later PR diffs are cumulative until their predecessors land.