fix(web): keep remote icon visible on hover - #82
Conversation
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
|
@codex review |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
22461f0 to
2010bb7
Compare
|
@codex review |
|
Codex Review: Didn't find any major issues. Bravo. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
2010bb7 to
72e09bc
Compare
72e09bc to
891be0a
Compare
|
@codex review |
|
Codex Review: Didn't find any major issues. 👍 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
## Problem Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. ## Fix The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 ## Validation - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed ## UI evidence The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
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: - three pending upstream nightlies replayed and published as immutable checkpoints - PR #82 and PR #86 retain identical stable patch IDs after replay - focused checkpoint, worktree, and entrypoint tests passed - exact-head quick CI passed all test suites; post-CI shared-config guard observed an unrelated concurrent branch setting change Built by GPT-5.6-Sol with the Codex harness.
Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row. The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved. Upstream proposal: pingdotgg#8132 - Focused formatting and lint for `LegacySidebar.tsx` - Web typecheck - `apps/web/src/legacySidebarScale.test.ts` (3 tests) - Push-gated quick local CI: format, lint, all workspace typechecks, and all workspace tests passed The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero. Implemented with GPT-5.6 Codex in the T3 Code harness.
Problem
Hovering a remote-machine thread hides its cloud icon along with the timestamp, removing useful machine context just as the user is about to act on the row.
Fix
The remote indicator now sits beside the hover-fading metadata block. The timestamp or jump hint still yields to the archive action, while the cloud stays visible. LastCode-specific sidebar scaling and annotation behavior are preserved.
Validation
LegacySidebar.tsxapps/web/src/legacySidebarScale.test.ts(3 tests)UI evidence
The reporter supplied the before screenshot. Automated after-image capture was not available because this clean worktree has no paired remote-environment fixture. The DOM relationship was verified directly: the cloud is no longer a descendant of the metadata element whose hover class sets opacity to zero.
Implemented with GPT-5.6 Codex in the T3 Code harness.