Repository navigation
fix(lastcode): repair nightly promotion after replay - #89
Merged
Merged
Conversation
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.
The live nightly replay exposed three blockers in the promoted checkpoint: open-PR detection queried the upstream repository, worktree cleanup lost the new upstream missing-path semantics during conflict resolution, and entrypoint fallback compared non-canonical macOS paths.
Scope GitHub PR counting explicitly to the LastCode fork, reconcile worktree removal so missing paths are safe while locked registrations still fail, and canonicalize both entrypoint paths. The existing upstream and LastCode tests cover the integrated behavior, with a focused assertion for the GitHub CLI repository argument.
Validation:
Built by GPT-5.6-Sol with the Codex harness.