feat: env-file import for workspace credentials — one parser, two doors

[pythonlearner1025]

Env-file import for workspace credentials

One parser, two doors. An admin moves the keys in a dotenv file into the
workspace credential store, from either surface:

• Agents: blitz-cred import [--check] [--label TEXT] FILE|- on any
  workspace-admin machine. The acting member is the machine's member,
  resolved at call time — same rule as the pull wire.
• Humans: the credentials tab in the workspace details dialog gets an
  import block: paste or choose a file, watch a live preview, then import.

Both surfaces call the same import. The webApp preview and --check are the
same dryRun flag on the same request, so the preview is a promise: the same
parse, the same outcomes, no writes.

Wire

• POST /workspaces/self/credentials/dotenv (box plane)
• POST /workspaces/:id/credentials/dotenv (session plane)
• Body { text, label?, dryRun? } → { results: [{ name, line, outcome, reason? }], linesRead }

Outcomes are store-level facts: stored, rotated (a live name's value
changed), unchanged (same value, nothing written — a re-run of the same
file must not read as fifty rotations), refused (per line, with a reason;
the rest of the file still imports). No value ever travels back.

Parser

The least surprising slice of dotenv: NAME=value, optional export , #
comments, one matching pair of surrounding quotes. No escape expansion, no
line continuation — the pull wire refuses a newline anyway, so a multi-line
value (PEM, JSON key) is refused with "base64-encode it first" instead of
storing a fragment. A duplicated name keeps the last line and reports the
earlier one.

Storage

Each key goes through putWorkspaceCredential, so import invents no second
rotation semantics: one live row per name, the revoked row stays as the
audit trail, blitz-cred serves the new value on the next pull.

Contract

New cross-runtime corpus packages/schema/fixtures/credential-import/
(valid + invalid), pinned by test/credential-import.test.ts (CP produces
the valid fixture byte for byte) and
broker/internal/workspace/credimport_test.go (Go consumer accepts valid,
refuses print-unsafe bodies). CLAUDE.md contract table has the new row.

Comments (round two)

A credential can carry a one-line comment saying what the key is for.

• blitz-cred list prints it after a #; agents read the comments to pick
  the right key. The read is a new box route
  (GET /workspaces/self/credentials, names and comments, never values),
  so deployed boxes with the old strict decoder keep working.
• printf '%s' "$VALUE" | blitz-cred put NAME --comment "…" stores one key
  with its comment (box-plane PUT /workspaces/self/credentials,
  workspace-admin gate, value on stdin so argv never holds a secret).
• The credentials tab shows comments on rows and offers a comment field in
  the add-or-rotate form.
• The comment is tri-state on the wire: absent keeps the live row's comment
  across a rotation — so an env-file re-import cannot erase explanations —
  explicit null clears, a string sets. Import itself never reads or writes
  comments.
• Migration 0045 adds the column; new corpus
  packages/schema/fixtures/credential-list/ pins the list wire on both
  sides.

Docs

agent-rules.md (the baked ~/.claude/CLAUDE.md) gains a "Sharing secrets
with the workspace" section: import, check, the one-line rule, and the
delete-the-file-afterwards guidance.

🤖 Generated with Claude Code

https://claude.ai/code/session_012R7NUDJXy3eUBeKFYTMt1A