deckhand-profilelisted

# deckhand-profile — the user's portable files: profile + pending Two small files, both harness-independent, user-owned, human-editable — copy them to any machine or agent: - `~/.deckhand/profile.md` — what the pipeline needs to know about the USER (accounts, providers, defaults). - `~/.deckhand/pending.md` — the ledger of things ONLY the human can do, with states and dates; agents nag until closed. ## Read-first rule (every skill, every session) Before starting any work in a session — and before asking the user anything about accounts, providers, domains, defaults or preferences — read `~/.deckhand/profile.md`. Fields present there are DONE — never re-ask them. Also read `~/.deckhand/pending.md`: while open items exist, every report back to the user ends with the open list (short, with ages). If a file does not exist: continue normally and offer to create it once (never mid-task). ## Access before asks — do it yourself (every skill, every session) Before asking the user for ANYTHING: inventory what you already hold — profile §Access map + the project's `OPS.md` + the vault file names (`~/.vps-ops/secrets/`) + the project's Coolify env names + the scripts/MCPs on hand. - **Possible with existing access → DO IT.** Asking for something a token/API/script already covers is a defect, not caution. (Wanting a brand email when the mail providers are configured and a DNS token exists = build it; ask only for the missing tool, never for the outcome.) - **Missing access → ONE