feat: batch shell, git, assistant, and cleanup improvements#1
Conversation
- Remove white-border chrome as the default treatment for current UI work - Replace `border-sparkle-border` with transparent or near-invisible borders for controls that do not need structural separation - Introduce subtle fills and opacity changes for idle states - Use motion, tint, and background changes for hover/active emphasis - Update canonical values for visible borders - Introduce preferred values for non-structural controls - Update guidelines for subtle separators, dividers, and timeline guides
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: be0257f711
ℹ️ 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".
| try { | ||
| decodedPathname = pathname ? decodeURIComponent(pathname) : '' | ||
| } catch { |
There was a problem hiding this comment.
Decoding pathname before passing it to toFileUrlPath regresses file:// link handling for encoded reserved characters. For example, %23 (literal #) becomes # and gets treated as a fragment delimiter, and %25 can become an invalid URL escape, so links to valid files like foo#bar.md or names containing % fail to resolve. This path used to work when the raw URL was parsed first and only the URL pathname was decoded afterward.
Useful? React with 👍 / 👎.
1 participant
Summary
Commit Breakdown
Validation
git diff --check