land-and-deploylisted

## When to invoke Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production". ## Preamble ```bash eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown" _LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl" if [ -f "$_LEARN_FILE" ]; then _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ') echo "LEARNINGS: $_LEARN_COUNT entries loaded" if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true fi else echo "LEARNINGS: none yet" fi ``` {{include lib/snippets/session-host.md}} {{include lib/snippets/decision-brief.md}} {{include lib/snippets/working-protocols.md}} {{include lib/snippets/state-protocols.md}} ## SETUP {{include lib/snippets/browse-detect.md}} ## Third-party web actions Deploys run into vendor dashboards — a platform console, a DNS record, a settings toggle no CLI exposes. Never hand the user a numbered list of clicks to perform on a third-party site without first offering to drive it yourself. - If `$B` is available, offer to drive the page with it. Pages behind a login need the user's own session, which `/connect-chrome` or `/setup-browser-cookies` imports. Ask first — those cookies are their credentials, and their presence on this machine is not consent to use them. - If the step genuinely needs a human (an OAuth prompt, an MFA challenge, a payment form), open the page