Handoff · 2026-08-09 · account switch

Publish Warp 0.6.119

Everything is prepared and every gate is proven open — nothing was published. Four steps finish it, and the next session can start cold from this page.

Marketplace untouched · branch release/0.6.119-grok-pass · 6/6 surfaces live-verified

Status: nothing published — the marketplace checkout is untouched and verified clean. All gates proven open on a read-only dry run. Paste this page’s §1 to your next session and it can finish cold.

01

The publish — four steps, all gates already proven

Use branch release/0.6.119-grok-pass (pushed). It is the COMPLETE one — it carries both the grok PASS receipt AND the installer pin bump. PR #317’s branch has the receipt but NOT the pin, so publishing from it refuses at the first gate.
  1. Confirm the gates still open. In a worktree on that branch, run the dry run. Expect four green lines: installer coupling OK · acceptance OK 6 surfaces · walk receipt OK · “would sync 256 files.” If main moved and the version changed, re-sync the pin + ledger first.
    ↘ the command
    bash scripts/release-to-marketplace.sh --marketplace ~/de-skills-main --dry-run
  2. Publish. Drop --dry-run. It syncs 256 files into the marketplace checkout.
  3. Commit and push the marketplace checkout. That push is what teammates’ claude plugin update actually reads. Until it lands, nothing has reached anyone.
  4. Redeploy the get-warp Worker. So the SERVED installer carries the new pin. Skipping this is how the one-paste install broke once before — the deploy script self-checks served-vs-repo, so it’s gated, but it must actually be run.
  5. Merge the receipts branch to main so the record lives there too.
Consequence: every teammate’s next update moves 0.6.106 → 0.6.119 — the four typed doors, the watcher rule, the grok belt, and today’s cures. The installer pin is the regression guard from the 0.6.16→0.6.17 break; it is already bumped on this branch.
02

Why it’s safe to publish — six surfaces, live-verified

Every line is a real dispatch with a recomputable run id, not a test suite. Full receipts in docs/acceptance/0.6.119.acceptance.md.

1Sealed door
Live codex dispatch returned COMPLETE, work harvested.
2API door
Live kimi-k2 call returned COMPLETE; the model answered “PONG.”
3Sandbox Worker
The 0.6.82 scar surface — the one that once shipped undeployed. Live dispatch COMPLETE, plus a read-only health check answering 200. It answers in production.
4Cloud door
Clean retry COMPLETE. Attempt one’s genuine vendor failure was kept in the record, not hidden.
5Doctor
DISPATCH READY / HEALTHY against the installed 0.6.119 bay.
6Grok seat
Re-authorized mid-session, then re-exercised live: COMPLETE, work harvested to bay/grokseat-verify. The earlier honest UNRUN is named, not erased.

Cold install walk: YES-WITH-STUMBLES — materialized clean off the local 0.6.119 build, since it isn’t marketplace-published yet. That resolves at step 3.

03

Also open — unrelated to the publish

PR #316 — the version-race fix
Both courts CONFIRMED the design. Four small cures before merge: custody should diff the merge-base rather than main’s tip; the stamp tool should refuse when not at origin’s tip; one self-contradicting line in its declaration; and a sabotage test that only bites on Linux (passes vacuously on macOS). Cure, merge, then run the stamp once on main.
Follow-ons named by courts
The watcher-rule needs its MECHANICS correction (a watch lives only while a tracked child of yours runs; “standing by” in a final message is a dead watch). Two unwatched test suites need CI seats. Door 3’s jq-immunity is real but untested.
Yours alone
The runner token file (world-readable, live token — rotate + lock). The disk guard still whitelists delete commands under pressure — a policy call you parked. And ~/vet-database has two app logs growing by the megabyte, wanting a logrotate.
04

What actually shipped today

  1. Reliability primitive #1 is complete. All four doors — sealed, api, sandbox, cloud — now hand back a typed value instead of prose. Merged to main and live on this machine. It’s the foundation fail-and-reroute stands on.
  2. An integrity hole was found and designed shut. Your instinct that something felt “funky” about version churn was right: two branches could green a build where one version number named two different content sets. Design ratified, built, courted; four cures from landing.
  3. Grok is diagnosed and reconnected. The quiet-quit was the CLI ending runs without granting the next turn; the belt shipped, and the seat is live and building again.
  4. Every bug today was caught before main. A false green in the cloud door, a death certificate for a living run, a dry-run that mutated the record, a test that could never pass — all caught by independent judges, cured with proof, then landed.