Skip to content

fix(web): treat configured urls with uppercase schemes as secure - #8005

Merged
maria-rcks merged 1 commit into
pingdotgg:mainfrom
Lucenx9:fix/case-insensitive-url-scheme
Aug 23, 2026
Merged

fix(web): treat configured urls with uppercase schemes as secure#8005
maria-rcks merged 1 commit into
pingdotgg:mainfrom
Lucenx9:fix/case-insensitive-url-scheme

fix(web): treat configured urls with uppercase schemes as secure

83fe887
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Aug 23, 2026 in 5s

Effect Service Conventions: All clear

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.


🔍 Agent activity — 2 tool calls

💭 Looking at the diff, it seems like a small change related to case-insensitive URL scheme handling, not something tied to the Effect service. I want to check the file to confirm.

1. browse_code — apps/web/src/environments/primary/target.ts

2. browse_code — apps/web/src/environments/primary/bootstrap.test.ts

💭 This PR looks clean - no Effect service convention violations, the bug fix is appropriately scoped, and the test usage is fine. I'm now weighing a conflict: the instructions say to respond with just "All clear" when there are no findings, but the response schema also requires JSON output, so I need to figure out how to reconcile that.


Agent Credits: 0 credits
No billable model usage was recorded for this run.