Add deterministic Vercel publishing to readout

[vikvang]

Summary

• add explicit public-deployment consent and Vercel scope selection to the readout workflow
• add deterministic helpers for scope discovery, managed-project deployment, production-alias resolution, and anonymous verification
• protect unrelated projects by requiring managed markers and separate adoption consent

Testing

• parsed all readout Python scripts with Python AST
• ran publish_vercel.py in dry-run mode
• anonymously verified a deployed readout returns HTTP 200 with an exact title match
• ran git diff --check
• exercised the publisher end to end against the managed warpdotdev/readouts-sathvik-9321 project

Agent Mode: conversation

Co-Authored-By: Oz oz-agent@warp.dev

[oz-for-oss]

@vikvang

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This PR updates the readout skill to require explicit public Vercel consent and adds helper scripts for Vercel scope discovery, publishing, and anonymous verification.

Concerns

• Scope discovery omits the authenticated user's personal Vercel account, so users without teams cannot select any deployment scope and users with teams cannot choose personal publishing.

Verdict

Found: 0 critical, 1 important, 0 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

⚠️ [IMPORTANT] vercel teams ls only returns teams, so the personal Vercel account is never offered as a scope; users without teams hit this error even though they could deploy to their own account.