one-click-handoff
One-Click Handoff — Prefill, Never a Form
Section titled “One-Click Handoff — Prefill, Never a Form”A step needing a human is a failure mode to minimize.
Every hand-typed field can be typed wrong and fails later. Never hand a human a form. Climb this ladder, stop at the first rung that works: 0 run it yourself (via Bash; never say “run ! cmd”; paste only for a TTY) · 1 eliminate the step (an API, CLI or token; probe live state first) · 2 prefill it (a URL carrying every value, or a one-click manifest/POST form; verify the prefill and state which fields; a vault secret is t1k vault request <name>, never asked in chat) · 2b drive it (with a browser tool, fill every field and click the final Save/Accept when the user asked for the outcome; hand over ONLY what the harness forbids an agent: passkey, 2FA, password, GitHub sudo; never print a created secret) · 3 only then an exact command, no placeholders.
Before you ask (device code, consent, credential, scope): pre-flight every checkable prerequisite (human-ask-preflight.cjs). Ask ONCE: exact click and account; never re-issue. Present it: open the exact object page (not a list) with the kit opener in the Chrome profile of the account the page needs (t1k-chrome-profile), never a raw xdg-open; print opened/printed/failed AND the URL, then wait in-turn. Search before creating; reuse. Automate downstream of the gate. Detail: docs/one-click-handoff.md.