Add Browsie consumer browser agent project

[shubh24]

Summary

• add Browsie under projects/browsie as a complete consumer browser-agent reference project
• document the Stagehand, Browserbase, Eve, Context, vault, Live View, CAPTCHA, cancellation, Linq, and workbench architecture
• add standalone setup, environment, testing, deployment, security, contribution, coding-agent, and skill guidance
• add a projects cookbook collection and generated catalog/topic entries
• exclude local secrets, runtime state, build output, internal planning files, and the source commercial font asset

Validation

• pnpm test: 84 passed, 7 credential-dependent live tests skipped
• pnpm typecheck: passed
• pnpm lint: passed with 6 warnings and no errors
• pnpm build: passed
• pnpm test:linq-local: passed
• python3 scripts/verify.py: passed; 1,304 files scanned
• git diff --check: passed

Production boundary

This is a production-oriented, self-hosted reference application. The README states the work that is still required for a multi-user or multi-instance service, including durable metadata storage, KMS, tenant isolation, access control, single-use handoff links, rate limits, and audit retention. No live service test or billable external call was made for this PR.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​next@​16.3.0-preview.6
	npm/​eslint-config-next@​16.3.0-preview.6
	npm/​@​ai-sdk/​openai@​4.0.46
	npm/​microsandbox@​0.5.10
	npm/​lucide-react@​1.49.0
	npm/​eve@​0.47.6
	npm/​react@​19.3.0
	npm/​@​1password/​sdk@​0.5.0
	npm/​react-dom@​19.3.0
	npm/​@​browserbasehq/​sdk@​2.18.0
	npm/​ai@​7.0.82

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	Critical CVE: Next.js: Unauthenticated Remote Code Execution on windows-hosted servers CVE: GHSA-p293-qw3h-jr36 Next.js: Unauthenticated Remote Code Execution on windows-hosted servers (CRITICAL) Affected versions: >= 13.4.0 < 15.5.24; >= 16.0.0 < 16.3.3 Patched version: 16.3.3 From: projects/browsie/package.json → npm/next@16.3.0-preview.6 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@16.3.0-preview.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn
	Critical CVE: Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used CVE: GHSA-2xp9-vwfh-vxw4 Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used (CRITICAL) Affected versions: >= 10.0.0 < 15.5.24; >= 16.0.0 < 16.3.3 Patched version: 16.3.3 From: projects/browsie/package.json → npm/next@16.3.0-preview.6 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@16.3.0-preview.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn

View full report